Thinkpads Forum

I don't know if this helps, or if anyone experiences this, but I noticed on my X41 that when I standby for an extended period with Firefox window(s)(tabs) open when I go into standby, I have trouble recovering from standby using the Fn key, and I also have to use the Fn spacebar to activate the screen once it finally wakes up with a blank dark screen. However if I standby with noFirefox windows open before I stand-by, recovery from standby is immediate and normal and the screen comes up with backlight on. This happens on three different X series laptops.

i too experience the problem where the screen will remain black, and i have to get it back by using Fn + space bar.

I have also seen that issue with FireFox when resuming from hibernate.

I was also seeing my system lock-up completely under Firefox - the system would completely freeze and be non-responsive. I'm now using IE 7 beta 3 and no freeze-ups so far.

I had thought that I was past this problem of screen won't come on after PM timeout, but it's baaack. Fn+F7 doesn't work in my case only Fn+F4, but this scales all of my active CAD windows down and they have to be manually resized individually when I access them. Major PITA.

I use FireFox/Thunderbird, so I'll go a day without using either to see if they're potential culprits.

I have noticed, though, that when my machine refuses to suspend on cover close or even when using Fn + F4 that the Windows Start>Shutdown>StandBy sequence still works.

After a failed standby attempt do a windows shutdown. My machine goes through the shutdown process to a certain point, but at that point it kills some process then goes into standby. When I resume from standby it completes the shutdown.

I just don't know what process is causing the problem. I don't recall ever experiencing a problem without a fix for this long on any previous T'Pad system. It's quite disappointing.

Hi folks...

I solved my issues of the screen not waking from sleep, the system becoming unresponsive when trying to wake it.

I just went into the BIOS at startup and set all the IRQ ports to "Auto-Select"

that did the trick. Your mileage may vary, but give it a whiril.

An update was released recently, probably a BIOS or video driver that claimed to fix just this problem. So far so good. I haven't seen the problem since I performed the update and it's been several weeks.

Does anyone else remember what update claimed to fix this?

-darren

It was supposedly a Windows Update http://support.microsoft.com/kb/917332/en-us that did the trick for some.

The monitor does not turn on when you move the mouse or press any key after you configure the "Power Options" settings on a Windows XP SP2-based portable computer

I haven't installed it yet, but I haven't seen this issue since my last go round with System Updater.

That's the one. From the description:

Consider the following scenario. You have a Microsoft Windows XP Service Pack 2 (SP2)-based portable computer that uses a dual-core processor or that uses an Intel Pentium 4 Processor that supports hyper-threading technology (HT Technology). You use Power Options in Control Panel to configure the computer to enter a standby or a hibernation state when you close the lid. You also configure the computer to turn off the monitor after a period of inactivity.

In this scenario, the computer correctly enters a standby or a hibernation state after you close the lid, and then the computer correctly resumes activity when you reopen the lid. Also, the monitor turns off correctly after the period of inactivity that you specify. However, the monitor does not turn on again when you move the mouse or press any key.

Couldn't be more bang on. Has fixed it for me. Thanks for the link Scratch.

-darren

How did you actually get this fix? The page says to "contact Microsoft." I can't even imagine how big a black hole that would get me into!

Thanks -- Barb

http://hf.xable.net/

I too was wondering how to get it. The above site came up in a google search. Looks to be pretty useful for getting hotfixes which aren't publicly released.

cheers!

Excellent! Thanks.

My 2nd Advanced Dock went bad. No serial or USB ports working. No resume from standby. It took 6 weeks for the 3rd one to arrive, but it's the latest FRU and supposedly fixes everything. See the link:
http://www-307.ibm.com/pc/support/site. ... MIGR-65164

I can now resume from standby or hibernation. Cool. For the sencond time, I hope it lasts.
Jon

For what it's worth, I had this resume for standby problem with my factory fresh Z60m earlier this year. For me it turned out to be the Intel WiFi card, switching to Atheros solve the problem immediately.

I have 2 week old T60 and I had the very same problem - I left the system unatteded for 1 hr and it was just blank. It was powered on, and I could not get it back to activity at all - no key combinations including Ctrl-Alt-Del worked. I had to unplug the power and remove the battery and restart the machine

Applying the MS update mentioned above has seemed to fix mine. Before I did that, I noticed that using Fn-F4 to wake it up worked even when nothing else did. So that might be worth a try.

This problem was caused by the ACPI mode,you can change it to "ACPI Multi Processor"mode in system property.The old configuration can't assigned enough "IRQ" to Multi processor system.I fixed this problem by this method on my T60.

kai jiang wrote:This problem was caused by the ACPI mode,you can change it to "ACPI Multi Processor"mode in system property.

Where exactly is this "system property"? I realized the MS fix doesn't seem to have really fixed the problem after all.

-- Barbara

kai jiang wrote:This problem was caused by the ACPI mode,you can change it to "ACPI Multi Processor"mode in system property.The old configuration can't assigned enough "IRQ" to Multi processor system.I fixed this problem by this method on my T60.

Success. Thanks for the answer. Unfortunately I was using an old image that didn't already have the correct HAL in there. For that I referenced:

http://blog.case.edu/djc6/2005/09/22/im ... s_wsysprep

I had to pull out an old XP Pro CD lying around the office and I used the snippet contained in the link:

expand HALMACPI.DL_ C:\Windows\System32\HAL.DLL
expand NTKRNLMP.EX_ C:\Windows\System32\NTOSKRNL.EXE
expand NTKRPAMP.EX_ C:\Windows\System32\NTKRNLPA.EXE

ringonian wrote:

kai jiang wrote:This problem was caused by the ACPI mode,you can change it to "ACPI Multi Processor"mode in system property.The old configuration can't assigned enough "IRQ" to Multi processor system.I fixed this problem by this method on my T60.

Success. Thanks for the answer. Unfortunately I was using an old image that didn't already have the correct HAL in there. For that I referenced:

http://blog.case.edu/djc6/2005/09/22/im ... s_wsysprep

I had to pull out an old XP Pro CD lying around the office and I used the snippet contained in the link:

expand HALMACPI.DL_ C:\Windows\System32\HAL.DLL
expand NTKRNLMP.EX_ C:\Windows\System32\NTOSKRNL.EXE
expand NTKRPAMP.EX_ C:\Windows\System32\NTKRNLPA.EXE

Oh, and I forgot to mention that I got a 0x7e error on the reboot. So then I proceeded to reboot into Safe Mode until the kernel completed its reinstall.