Red Hat Bugzilla – Bug 241028
Resume from Suspend does not work on Gateway M255
Last modified: 2015-03-04 20:18:40 EST
Description of problem:
Resuming from Suspend does not work on a Gateway M255 laptop. Upon pressing the
power button to resume, the fan cicks on and some of the lights light up.
However the screen stays blank and the harddrive seems to never kick in.
Version-Release number of selected component (if applicable):
Every time i try to resume.
Steps to Reproduce:
1. Suspend laptop either with gnome's button or pm-suspend
2. Press power button to resume
Laptop never resumes, fans spin up, lights (wifi/power) turn on, screen stays off.
Should resume to fully working state.
I don't know if it is related but this laptop suspended/resumed with FC6,
however the screen's backlight would be off and i would have to hit the
brightness UP button on my keyboard to get see the screen. This doesn't work in F7
I tried all of the --quirks options to pm-suspend and various combinations of
them without any difference.
Here is my smolt report:
And i am attaching my dmesg output after pm-utils debugging.
Let me know if there is any more info that I could provide to help out.
Created attachment 155286 [details]
pm-utils debugged dmesg
Can you try going through to get the appropriate quirks?
As I said i tried _all_ of the quirks and various combonations that seemd like
they made sense. All of my attempts had the same outcome _unless_ I was doing it
wrong, that website doesn't quite describe how to 'use' the quirks. I was doing
pm-suspend --quirk-vbestate-restore --quirk-vbemode-restore
that is proper usage correct?
(In reply to comment #3)
> that website doesn't quite describe how to 'use' the quirks.
I'll fix that today.
> that is proper usage correct?
Yes, you're doing it right. Were there any quirks already listed for gateway?
No, there were no gateway quirks listed. I've seen some mention of kernel
arguments. Are those still possible fixes? If so, what might be relevant ones?
(In reply to comment #5)
> No, there were no gateway quirks listed. I've seen some mention of kernel
> arguments. Are those still possible fixes? If so, what might be relevant ones?
To be honest, you've just got to try all of the combinations of quirks to find
one that works. It's not great that there are no gateway laptops listed,
although I would really appreciate it if you were the first! :-)
Ok, so I've been able to do a little more testing and i've come to find:
Part of the problem is the same as mentioned here:
It's some problem with the current F7 kernel, 2.6.21-1.3194.fc7 with the latest
f8 kernel: 2.6.21-1.3218.fc8 and the --quirk-s3-bios suspending works _better_
but there are still problems.
Just to be clear wit the F7 kernel and the s3-bios quirk it has the same
behavior as before locking up on resume. With the F8 kernel without the s3-bios
it does not lockup (i can type reboot in tty1 and it will reboot) the display
just never comes up.
With F8 kernel and -s3-bios the display does not turn on initially after resume
... i have to press the brightness up key on my keyboard, this is the same
behavior as with FC6. It's not a major issue, but it woudl be better if it
didn't happen. I've tried nearly every possible combonation of quirks and none
of them seem to make the display come back on on its own.
Now for the bigger problem. Even with the F8 kernel, suspend/resume only works
once. if i suspend/resume/suspend and attempt to resume again, it will lockup as
it did with the F7 kernel.
Let me know if there's any way i can provide more information to get this resolved.
>i have to press the brightness up key on my keyboard
If you do after resuming:
for bl in /sys/class/backlight/* ; do
[ -d $bl ] || continue
[ -f $bl/brightness ] || continue
echo 0 > $bl/brightness
echo $BR > $bl/brightness
Does this restore the video? You might have to put this in a script file to
avoid typing this in blind ;-)
>suspend/resume only works once.
How does it fail the second time?
(In reply to comment #8)
> Does this restore the video? You might have to put this in a script file to
> avoid typing this in blind ;-)
You can use pm-utils --reset-brightness with pm-utils in devel (or soon in
updates-testing) to test this.
Unfortunately I Can't test this anymore. This laptop's motherboard fried _twice_
and gateway replaced it with a M265 (very similar laptop but it has the 965
chipset instead of the 945 i think) .... With this new laptop suspend/resume
works very good with 184.108.40.206-65.fc7
Ok, thank you. I close this then, if someone else has a problem with this
notebook, please reopen this bug or file a new one.