Fedora 12 notebook failing wake up from suspend

[pstahle]

Hi,

I am running into a problem with Fedora 12 not waking up from suspend. I am running on an older HP Pavilion with an AMD 64 Turion, ATI express 200m, and 2 gig of ram. After the notebook has been suspending I go to wake it up and it sounds like it is doing just that with the fans whirling up and lights around the keyboard coming on, but the screen remains blank and no lights come on when I hit caps lock. I have tried Mepis and that distro comes out of suspend mode just fine as does Windows. Any ideas where to look for this problem would be appreciated?

Thanks,
Patrick

[leerumler]

I'm having the same problem on a Sager NP980.

[pstahle]

Hi,

I did find a thread in here about stating it is a bug in the open radeon driver and if you have a chipset that supports the radeonhd driver to give it a go. I also saw a bug report on this problem. The bad news is it was reported for both Fedora 10 & 11, which tells me not to hold your breath for a quick fix.

Unfortunately for me, 200m chipset does not seem to be supported by the radeonhd driver and from what the thread is saying older ati chipsets will not be supported in the closed source driver, whenever that comes out for fedora 12.

This is the first ATI chipset I have had to deal with in linux, and so far my experience has not been good (NVidia experienc much better). Seems like most 3d games I have tried do not work with open radeon driver... But I can't complain much since I got the notebook for free.

Patrick

[CSchwangler]

One thing you could try is adding nomodeset to the kernel line in /boot/grub/menu.lst. I previously had problems with kernel mode setting and ATI cards.

[PhillyFloyd]

can you post any useful logfiles? maybe messages after the suspend fails .... there are issues with the GM45 chipset but that was resolved with 2.6.31.6-158 and upstream, but intel chipsets tend to get fixed much more quickly than ATI for obvious reasons

[pstahle]

nomodeset - I tried nomodeset but it didn't change anything. Still frooze up.

What log messages do you think I should look in? I didn't look in dmesg. I Can look in it tonight when I can get my hands on the notebook....

[PhillyFloyd]

Yeah you can use dmesg or just /var/log/messages

In /var/log/messages look for kernel: PM: or the word "freezing" -- I think usually NetworkManager is the first to sleep so you can also look for that

Anyway post everything after that and up to the restart (since it won't wake up) ;-)

[pstahle]

Really not much in the log between sleep failure and restart but here it is:

Dec 4 22:49:11 pstahlehp NetworkManager: <info> Sleeping...
Dec 4 22:49:11 pstahlehp NetworkManager: <info> (wlan0): now unmanaged
Dec 4 22:49:11 pstahlehp NetworkManager: <info> (wlan0): device state change: 8 -> 1 (reason 37)
Dec 4 22:49:11 pstahlehp NetworkManager: <info> (wlan0): deactivating device (reason: 37).
Dec 4 22:49:11 pstahlehp NetworkManager: <info> (wlan0): canceled DHCP transaction, dhcp client pid 1997
Dec 4 22:49:11 pstahlehp NetworkManager: <WARN> check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess#012
Dec 4 22:49:11 pstahlehp avahi-daemon[1107]: Withdrawing address record for 192.168.15.113 on wlan0.
Dec 4 22:49:11 pstahlehp avahi-daemon[1107]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.15.113.
Dec 4 22:49:11 pstahlehp avahi-daemon[1107]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dec 4 22:49:11 pstahlehp NetworkManager: <info> (wlan0): cleaning up...
Dec 4 22:49:11 pstahlehp NetworkManager: <info> (wlan0): taking down device.
Dec 4 22:49:11 pstahlehp avahi-daemon[1107]: Withdrawing address record for fe80::214:a5ff:fe4d:b153 on wlan0.
Dec 4 22:49:11 pstahlehp NetworkManager: <info> (eth0): now unmanaged
Dec 4 22:49:11 pstahlehp NetworkManager: <info> (eth0): device state change: 2 -> 1 (reason 37)
Dec 4 22:49:11 pstahlehp NetworkManager: <info> (eth0): cleaning up...
Dec 4 22:49:11 pstahlehp NetworkManager: <info> (eth0): taking down device.
Dec 4 22:56:50 pstahlehp kernel: imklog 4.4.1, log source = /proc/kmsg started.

The last line is the first entry from restart....

thanks,
Patrick

Would be interesting to see if the other person's logs match mine.....

[CSchwangler]

There seems to be a similar problem with Intel cards. I know that your card is ATI, but it may be worth trying the suggested workaround:

https://fedoraproject.org/wiki/Commo...top_lid_closed

[David Batson]

Originally Posted by CSchwangler

There seems to be a similar problem with Intel cards. I know that your card is ATI, but it may be worth trying the suggested workaround:

https://fedoraproject.org/wiki/Commo...top_lid_closed

I might have to give that a shot. I am not sure what happened this morning, but I turned off the backlight with my hotkey sequence (and radeontool). Likely some minutes or hours later my display went into suspend mode. When I went to my laptop this morning I could not get the display back but I could tell the computer was not shut off or in suspend mode. I had to do a hard power-off to get my desktop back. This has happened a couple of times to me, but I did not know what was the culprit. FTR, I am using the radeon driver.

EDIT: I got the command to work but I had to edit it slightly. I put the file in /etc/acpi/actions

#!/bin/bash
xrandr --output LVDS --off
xrandr --output LVDS --auto

Now the next time I can't bring the display back, I will try executing my hotkey sequence to run this file.

[linuxlewis]

Did anyone ever find a solution to this? I am having the same issue with an AMD chipset, Lenovo G555, Radeon HD 4220 integrated graphics.

Thanks

[bikemandan]

Both my desktop and laptop have some very odd sleep but slightly different resume from sleep behaviors which are at least similar to what's mentioned here.

This workaround works for both my desktop (msi-something-or-other) and my lenovo T61:

ctrl-alt-f2 (switch to another virtual terminal)
ctrl-alt-f1 (switch back to the x11 owned virtual terminal)

Of course this depends on what terminal x11 owns for you, but the default seems to be terminal 1.

I'm running kernel 2.6.32.11-99.fc12.x86_64 on the laptop, so whenever the upstream fix was committed, it still hasn't made it into fedora's kernel tree. (.14-127 is available, I know.)

Dan

[linuxlewis]

Thank you for your response but switching terminals does nothing for me, the screen still stays black. I tried F1 through F7 and nothing. The only thing that works thus far is killing the power and starting over.

[pstahle]

I just upgraded to Fedora 13, and the problem still isn't fixed....

Wish this laptop and an nvidia chipset in it....

[librae8226]

Same problem...
Need help.
OS: Fedora 12
notebook: Lenovo B450, NVIDIA G105M