Page 1 of 1

"turn on wireless capability"

Posted: Tue Sep 25, 2012 10:41 pm
by systemBuilder
I have had 3 different T420's (my employer keeps swapping the machine for various reasons) but this has happened on all of these laptops.

After coming out of hibernate, at least half the time I have to troubleshoot the wireless and then "turn on wireless capability"

Often times I will be surfing the web and everything will instantly fail. Then when I troubleshoot the problem the troubll shooter says, "We recommend you : turn on wireless capability". This is sheer Lunacy, is there some way to stop my wireless card from turning off ?? Or is this just some sort of catch-all message that is used when it's time to reset a poorly designed / locked up wireless card ??

Thinkpad T420
Nvidia NV4200 graphics
1600x900 display
Intel Centrino N6300 AGN Wireless Card
Gobi Card (I never use the Gobi card)
Windows-7

Re: "turn on wireless capability"

Posted: Wed Sep 26, 2012 2:24 am
by catalinus
systemBuilder wrote:I have had 3 different T420's (my employer keeps swapping the machine for various reasons) but this has happened on all of these laptops.

After coming out of hibernate, at least half the time I have to troubleshoot the wireless and then "turn on wireless capability"

Often times I will be surfing the web and everything will instantly fail. Then when I troubleshoot the problem the troubll shooter says, "We recommend you : turn on wireless capability". This is sheer Lunacy, is there some way to stop my wireless card from turning off ?? Or is this just some sort of catch-all message that is used when it's time to reset a poorly designed / locked up wireless card ??

Thinkpad T420
Nvidia NV4200 graphics
1600x900 display
Intel Centrino N6300 AGN Wireless Card
Gobi Card (I never use the Gobi card)
Windows-7

I believe there is somewhere a group of settings that automatically stop wireless stuff (and other things, but that is beside this point) in order to minimize power consumption - however I am in a hurry right now so I can not point precisely where that is (I believe I might have changes something in more than one place anyway). Also I believe the problem is more visible when running on batteries.