[Bug 257454] New: suspend to ram/lid close: please fix to it to the previous state
https://bugzilla.novell.com/show_bug.cgi?id=257454 Summary: suspend to ram/lid close: please fix to it to the previous state Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: bluedzins@wp.pl QAContact: qa@suse.de It would be a wish, if I didn't see it working properly. But I saw it, so I have pretty good comparison. In opensuse 10.0, setting lid close to suspend to ram worked no to so bad. You set it, you closed the lid, the screen went blank, the power led was blinking. In opensuse 10.2 from the start there were problems with kpowersave, events, etc. Today I updated kpowersave and checked it. Now, the StR requires the grub is working in vga=0 (new requirement) which makes the console unusable, when I close the lid the response time is longer, X11 switches to console mode, that it blanks the screen and finally StR is done. Please, fix it as it worked in 10.0. Much faster, reliable, and I could set vga mode whatever I wanted. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257454 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |pavel@novell.com |maintainers@forge.provo.nove| |ll.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257454 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #1 from pavel@novell.com 2007-03-27 17:10 MST ------- We can't "just revert", because it would break suspend for many people, and you did not provide nearly enough info to fix the problem... starting with type of your system. Feel free to create new report for "need vga=0", but do include the details. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257454 bluedzins@wp.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Comment #2 from bluedzins@wp.pl 2007-03-28 08:08 MST ------- Pavel, I am not saying the code should be reverted, but the behaviour -- what the user experiences and sees. My system is Dell Latitude D610. I'd better reopen this one, I don't want to make a mess with several reports on the same topic. My concerns are: * StR switches to console before it executes (it didn't before) * StR is slower than before * StR requires vga=0 which is a killer because it limits the way you can work -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257454 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|pavel@novell.com |seife@novell.com Status|REOPENED |ASSIGNED ------- Comment #3 from seife@novell.com 2007-03-28 12:19 MST ------- What happens if you do not do vga=0? Does it hang or does it just not suspend? If it does just refuse to suspend, please go to http://en.opensuse.org/S2ram and try the steps there to find the best options for your machine. (In reply to comment #2)
* StR switches to console before it executes (it didn't before)
Of course it did. Just later in the suspend process.
* StR is slower than before
Yes, and more safe (the network is shut down via NetworkManager and we prepare more of the system for suspend. But if you are brave, you can go ahead, read http://en.opensuse.org/Pm-utils and disable some of the hooks.
* StR requires vga=0 which is a killer because it limits the way you can work
Maybe the whitelist entry for your machine is simply not correct and it would work with vesafb, too, but i cannot verify this without hardware, so you need to test it by yourself.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257454 ------- Comment #4 from bluedzins@wp.pl 2007-03-28 14:05 MST -------
What happens if you do not do vga=0? Does it hang or does it just not suspend?
The screen is turned off (not blanked, but turned off). There is no suspend. I cannot get the screen back on, so I have to blindly shutdown KDE and get back to console (I test StR in runlevel 3). Then, the screen is on.
If it does just refuse to suspend, please go to http://en.opensuse.org/S2ram and try the steps there to find the best options for your machine.
I will look at it, thank you.
* StR switches to console before it executes (it didn't before) Of course it did. Just later in the suspend process.
Hmm, if it did, it had to be some non-visual switch, because I was unable to see any messages. And now I can see them.
* StR requires vga=0 which is a killer because it limits the way you can work Maybe the whitelist entry for your machine is simply not correct and it would work with vesafb, too, but i cannot verify this without hardware, so you need to test it by yourself.
I would like to, but what should I do? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257454 ------- Comment #5 from bluedzins@wp.pl 2007-03-29 04:40 MST ------- I just have read about option for S2Ram for Dell, I tried it but it does not work with vga mode other than 0 (0x317 to be specific). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257454 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME ------- Comment #6 from seife@novell.com 2007-06-06 12:23 MST ------- so it only does work with vga=0 and thus the whitelist entry is actually correct. We cannot suspend without vga=0, so you have to choose between "fancy console" and suspend to RAM. Sorry for that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257454 ------- Comment #7 from bluedzins@wp.pl 2007-06-07 00:36 MST ------- To be exact, several months later, when struggling with s2ram again, and with your help I managed to run s2ram with vga!=0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com