sicash / open-hardware-monitor

Automatically exported from code.google.com/p/open-hardware-monitor
0 stars 0 forks source link

Can't wake from standby/hibernation when ATI Mobility HD 2600 is monitored #401

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What is the expected output? What do you see instead?
Expect laptop to wake up. Laptop power LED is on but blank screen, no hard disk 
activity, no USB power (mouse is off).

What version of the product are you using? On what operating system?
Version: 0.5.1.0 on XP SP2

Please provide any additional information below.
Currently using OHM with all hardware monitored except GPU.

Please attach a Report created with "File / Save Report...".

Original issue reported on code.google.com by wehon...@gmail.com on 23 Oct 2012 at 7:57

Attachments:

GoogleCodeExporter commented 9 years ago
After further testing I found that I can't run OHM at all even with GPU 
monitoring turned off because the display won't wake from hibernation by 
itself. After waking up from hibernation, I have to attach an external display 
in order to wake up the laptop display.

Original comment by wehon...@gmail.com on 29 Oct 2012 at 6:26

GoogleCodeExporter commented 9 years ago
This is very strange.

Have you tried with all monitoring disabled (File -> Hardware -> ...)?

And the problem occurs only when the Open Hardware Monitor is running? When 
running other applications there is no problem with hibernation?

Original comment by moel.mich on 29 Oct 2012 at 7:04

GoogleCodeExporter commented 9 years ago
Experimented without any extra applications running after boot -

I was able to recreate the wake up problem from standby or hibernation with GPU 
monitoring enabled. Wake up from standby leaves the laptop with blank screen 
and a non-working keyboard. Wake up from hibernation gives blue screen with 
stop 0x7F(0x00, 0x00, 0x00, 0x00).

However, I was unable to recreate hibernation wake up problem mentioned in 
comment #1. I will leave OHM running (without GPU monitoring) to see if there 
is any particular app that may cause this problem.

Original comment by wehon...@gmail.com on 31 Oct 2012 at 7:06