nc6400 won't resume from standby

Calling all serious WinXP, ACHI, SATA, driver,IRQ, etc., Guru dudes!!!!!!

I got this nc6400 laptop that I recently installed WinXP Home onto.
After a serious education in slipstreaming, nlite, etc., etc. I created a boot disk and was able to load a system onto a 120gig Toshiba SATA HDD. (Google and these message boards are a wonderful thing!!!)

Here's the setup:
nc6400 Intel Centrino core-duo
WinXP Home (SP2) with all the (seemingly) applicable hotfixes, updates, etc.
82801G (ICH7 Family) chipset drivers (used the Intel chip utility)
82801GBM SATA AHCI Controller
Toshiba MK1246GSX HDD

After wrestling with some driver issues I finally have this box working fairly well except for one small thing. I like to use standby and this $#%&*(!@)&^%# thing will not resume from standby.

I get a quick flash of blue on the screen (video working !?!?), the speakers click and the mute button LED comes on and stays on (Audio OK??), the HDD lights comes on for a second then goes out (Initial disk read??), the cooling fan comes on and stays on, and the power switch LED lights as does the power light on the front panel. After that - nothing. There isn't any keyboard, mouse, usb, wireless card, or any inputs/changes that will do anything. The only thing that works is holding down the power button to force a full shutdown. The reboots are fine.

I have compared drivers to another nc6400 that is configured similarly and it works on that box, but not on mine.

Using that info I have updated/checked/rolled-back just about every driver and it doesn't help. I think I have also messed with just about every power management setting windows has - no help.

It does work fine when resuming from hibernate.

I have read some info on the boards about the ICH7 drivers not allowing the SATA HDD to restart from standy, but most of that was with guys using LINUX.

I only have one device in Device Manager that isn't happy.
It's HP Mobile Data Protection Sensor and it says "This device cannot find enough free resources that it can use. (Code 12). If you want to use this device, you will need to disable one of the other devices on this system."

I have uninstalled and re-installed, updated the driver, etc. etc. and it doesn't help. It seems that this device is trying to use IRQ23 and it must already be in use (although I can't seem to find any devices that are trying to use IRQ23). This issue may(probably) not even be related. However, I've tried to reassign IRQ's, but the area to do that on the resources tabs of all the device drivers are shaded and will not allow any changes. Also noted something kinda different - there are like 7-8 devices that all share both IRQ10 and IRQ11 in my IRQ map. Doesn't seem right, but that's way over my feeble architecture knowledge. Check the attachment.



I have the BIOS set up identically to the machine that does work - so I'm thinking that this isn't an issue.

And that just about sums up my total knowledge of computers.

Anybody got any ideas??

 

BTW - Here's the IRQ summary from the machine that works. Why would the IRQ summary (and IRQ assignments) be so different between 2 machines? THis machine is using WinXP Pro. Will that make the difference? They're both x86 systems. Check out the attachment.



Thanks for the thoughts.

 

I know I have had many issues with standby, much like yours except mine were due to server related hardware in my laptop. I used cpu rightmark clock management, and in the advanced cpu settings, you can enable cpu low power states and acpi states. I know my opteron will only shut off when I have the ACPI set to C2 (Stop Grant).

If this does not work for you, you can try the other choices in the acpi settings.

Good luck, remember you have to reboot for acpi changes to be saved.

K-TRON

 

Thanks K-TRON.

I tried the utility you mentioned. I tried all the combinations with no difference in the resume hang.

After scouring more message boards I figured out that WinXP Home will not support a multi processor ACPI. Probably should have known that already, but some of us it just takes longer.

That would appear to explain the difference in the "computer" driver in device manager between the other machine I have access to (a WinXP Pro system) and mine (WinXP Home). The computer device detail on my machine says "Advanced Configuration and Power Interface (ACPI) PC" and shows a hardware ID of "acpiapic_up" where as the other machine is "ACPI multiprocessor PC" and "acpiapic_mp" respectively.

The "_up" is uni-processor and the "_mp" is multiprocessor. Probably also why that HP Mobile Data Protection Sensor driver doesn't have a resource conflict on the other machine and it does on mine.

This also probably answers my question about IRQ's in the inital post above. The multiprocessor ACPI machine assigns many of the IRQ's in pairs - no doubt one device being assigned to and IRQ# of one processor and another device being assigned the same IRQ# but for to the other processor.

This shouldn't really (seemingly) have any affect on standy and resume tho.
I don't know - it's got me stumped. 'Course, that doesn't usually take too much.

Man - this is turning into more of a blog than a post!!! Time to go do something else for a while. Thanks in advace if you can come up with something.

 

Sounds like an ATI video card issue.
I sometimes have this issue on my nc6400 too, where the notebook actually resumes from standby, just the display backlight won't come on (you can see the things on the screen, just without backlight).
It doesn't seem to do it anymore after my last system restore. Sounds like a bad driver issue.

 

I thought at one point too, but I've got my box set up the same as the other nc6400 that I have access to. Same driver, same revision, etc. And that one works fine? Is there some kind of control panel to make any setup changes to the video besides just the ones avail thu winXP???

 

Try removing the video card driver for a bit, and try it with the windows one. I have the same problem with my ASUS F3Tc, but I've got used to it. Either this, or old drivers.

 

OK - I'll try it.
Ya just never know.
Tanks.