T42 EXTREMELY slow to wake up...

[dcdomain]

Whenever I move my ThinkPad, before opening the laptop I always have to make sure I plug in the power cord, otherwise it'll take forever to get it out of the standby/suspend mode. Anyone know if I can remedy this? I suppose it has something to do with the power management.

I'm guessing since it's in the process of 'waking up', even if I connect a power cord at that point, it doesn't detect it until it's done waking up. Sometimes this takes a good minute or two. Extremely annoying. Especially when I'm on the road and I only need to view some information for a few seconds. I'll have to open it, wait a minute or two for it to wake up then it'll work albeit slowly, view my two lines worth of information and then close it again.

[goofball]

well....I found the cure for MY X40 slowness in waking up: Firefox. Whenever I put my computer to sleep without exiting Firefox, it will take forever to wake it up, especially if I have multiple tabs opened simulatneously. So, from now on, I would totally exit Firefox before closing the lid/putting the X40 to sleep. Don't know if that helps you or not, but, so far, FF is the only culprit for me.

[JHEM]

Darren,

When you're moving around with the machine, do you turn off the WiFi before putting it to sleep?

If you put it in standby while it's connected to your WAP and then move it out of range it will take seemingly FOREVER to start up again as it's searching for the no longer available connection! If I'm out and about and forget to turn off WiFi before putting it in standby I'll see the same problem you're experiencing when I wake it up again.

Regards,

James

[JohnDrake]

Make sure the embedded controller firmware, BIOS, and power management driver are current. Embedded controller first.

For the T42, look here:
http://www-307.ibm.com/pc/support/site. ... MIGR-55386

[dcdomain]

Woah you people brought this thread back from the dead. Thanks for the advice. I think it might be the wireless, but doesn't that usually occur after the screen is already on? Or is that when it's still searching.

My main problem is that the screen takes forever to even come up. I think I see the HD light churning, but the screen will take a full two minutes or so to turn on... and then from there, I might have to wait a bit longer for the wi-fi stuff.

[ian]

I use three wireless and two cabled networks. I read this thread with interest as I've only recently discovered the joys of hibernation (for my Thinkpad, I might add...)

I did some tests to check the wireless theory. Runing on my home (wireless) network I pressed Fn+F12 and the closedown took in the region of 15 seconds. I drove to work and plugged in the power lead on my desk then pressed the button - roughly 20 seconds to connect to the wireless network and be up and running.

I did the same with a wired connection and the times are pretty much identical - tomorrow I'll try disconnecting the power lead as the machine goes to sleep...

[Leon]

make sure Wireless Zero Configuration service is NOT disabled...

[Elhabash]

Normally the moves Ian described work well with me, but most of the time when I was on a wired connection and then switch location (in hypersleep), it doesn't get an ip anymore for the wireless. Sometimes repair works.
Waking up is not affected, though. It also tries to connect to the network only after the desktop is at your disposal.

BTW, Turning Wireless zero config on/off does not influence my networking in any predictable pattern.

[Elhabash]

You might also want to try defragmenting the hyberfil.sys (or the partition where it's on). It helped me a lot.