[Bug 216082] New: suspend to RAM makes changes to BIOS (?) but not permanent
https://bugzilla.novell.com/show_bug.cgi?id=216082 Summary: suspend to RAM makes changes to BIOS (?) but not permanent Product: SUSE LINUX 10.0 Version: Final Platform: i686 OS/Version: SuSE Linux 10.0 Status: NEW Severity: Minor Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: bluedzins@wp.pl QAContact: qa@suse.de Dell Latitude D610, native res 1400x1050. I set in BIOS that smaller res should be displayed in smaller window. So no matter what res is set one pixel is one pixel. Ok, KDE launched, I resized the size of the screen. Everything works fine. But when I close the lid (suspend to RAM) and open it again and then resize the screen, even the smaller res fits entire screen -- so it violates BIOS settings. It is not firmware fault, Windows XP also suspends to RAM on lid close and changing screen res is fine all the time. -- 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=216082 gregkh@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=216082 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.com Status|NEW |ASSIGNED ------- Comment #1 from pavel@novell.com 2006-11-08 13:00 MST ------- Are you sure it suspends to ram on lid close? "XP happens to work is not good enough reason to believe firwmare is not responsible". What happens in init=/bin/bash? -- 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=216082 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |bluedzins@wp.pl -- 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=216082 bluedzins@wp.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|bluedzins@wp.pl | ------- Comment #2 from bluedzins@wp.pl 2006-11-09 00:11 MST -------
Are you sure it suspends to ram on lid close?
Hmm, I set it to suspend to ram and it looks like it suspends to RAM, but of course I don't bet my head on it.
"XP happens to work is not good enough reason to believe firwmare is not responsible".
Ok, you are right. Anyway, it would be nice if SuSE works at least as well as XP in that matter.
What happens in init=/bin/bash?
I am sorry, but I don't understand it. -- 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=216082 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |bluedzins@wp.pl ------- Comment #3 from pavel@novell.com 2006-11-10 05:03 MST ------- Boot with init=/bin/bash (on grub command line), and see if it happens, too. -- 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=216082 bluedzins@wp.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|bluedzins@wp.pl | ------- Comment #4 from bluedzins@wp.pl 2006-11-10 11:05 MST ------- How can I force this mode to get ACPI settings from Yast and to change the screen resolution? I have no clue so it is pretty hard to test anything. Just to ensure we are talking about the same thing -- suse started, 20 lines or so appeared and prompt # that's it. -- 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=216082 ------- Comment #5 from pavel@novell.com 2006-11-13 04:22 MST ------- I'm not sure what your Yast question means. Yep, so boot with init=/bin/bash, you'll get # prompt. Now close and reopen the lid. Does the screen resolution change? Anyway, you are using ancient version (suse 10.0), and your bug appears to be BIOS-related. I'm not sure if we want to debug it. -- 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=216082 ------- Comment #6 from bluedzins@wp.pl 2006-11-13 06:55 MST -------
Yep, so boot with init=/bin/bash, you'll get # prompt. Now close and reopen the lid. Does the screen resolution change?
I have no idea. The screen is not recovered (this is my question about Yast ACPI settings). Computer has no clue what to do on lid close. And as I reported earlier without suspend to RAM it is just blank. Btw. the screen res should not change and it is very doubtful it did. I was talking about the _size_ of the display, not the resolution (logical).
Anyway, you are using ancient version (suse 10.0),
? The current stable is just one number in revision higher -- 10.1.
and your bug appears to be BIOS-related.
Of course. -- 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=216082 ------- Comment #7 from seife@novell.com 2006-11-13 09:44 MST ------- I have had a report (on suspend-devel?) that "vbetool post" actually changed the "zoom display to panel size" settings. I did, however, decide that i do not care since having "suspend to ram working with changed zoom setting" certainly seems better than "suspend to RAM not working at all". -- 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=216082 ------- Comment #8 from bluedzins@wp.pl 2006-11-13 11:57 MST ------- In general, buggy software is better than software not working at all, but the question arises -- what is the point of bug reports. -- 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=216082 ------- Comment #9 from seife@novell.com 2006-11-13 16:57 MST ------- The "i don't care" part was meant as "i know it's not perfect, but i'll still add it to the whitelist", not as "i am totally not interested in fixing it" :-) What happens here is probably: - during boot, VESA BIOS is POSTing the card - then, the Laptop BIOS is setting some fancy register, and disables the "zoom" (if it is set like that in the BIOS). Our problem is: - the only thing we can use to reinitialize the card in a generic way is the VESA BIOS - so we run the VESA BIOS POST code. - this code probably resets the "zoom bit" in the card. - since we do not have exact knowledge about the internals of the card, we cannot restore it exactly. You could try if it works better when using the native framebuffer driver for that card (probably radeonfb if this is a ATI card), since these native driver (as opposed to the standard vesafb) has more knowledge about the card and might be able to restore it better after resume. Your bug report is appreciated, but i fear that there is not much we can do for you here :-( -- 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=216082 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|suspend to RAM makes changes|D610 has video problems after closing/reopening |to BIOS (?) but not |the lid |permanent | ------- Comment #10 from pavel@novell.com 2006-11-13 17:18 MST ------- Actually, this report is junk. In init=/bin/bash mode, closing of lid will not cause suspend to RAM. If screen still goes dark, something is seriously wrong with your hardware. (I think we have had such report before, and it happened also in Windows safe mode). To verify this, try closing/re-opening the lid at grub boot prompt, and report what happens. -- 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=216082 ------- Comment #11 from bluedzins@wp.pl 2006-11-14 00:10 MST ------- Stefan,
What happens here is probably:
I don't understand this description, but here some facts that might help: * the latest firmware, A06 * Intel 915 hardware * 1400x1050 (SXGA+) * I use screen "extender" software since SuSE fails to utilize my 1400x1050 (it recognizes it correctly, but then screen is set to 1280x1024 -- this is well know bug) Pavel,
Actually, this report is junk.
Calm down a bit, because now you are just being rude.
In init=/bin/bash mode, closing of lid will not cause suspend to RAM. If screen still goes dark, something is seriously wrong with your hardware.
Sure ;-/
To verify this, try closing/re-opening the lid at grub boot prompt, and report what happens.
On lid close screen just blanked out, no anything fancy, but when I opened the lid the screen was 100% restored without a problem. -- 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=216082 ------- Comment #12 from seife@novell.com 2006-11-14 00:59 MST ------- (In reply to comment #11)
Stefan,
What happens here is probably:
I don't understand this description, but here some facts that might help: * the latest firmware, A06 * Intel 915 hardware * 1400x1050 (SXGA+) * I use screen "extender" software since SuSE fails to utilize my 1400x1050 (it recognizes it correctly, but then screen is set to 1280x1024 -- this is well know bug)
Yes, and it should work fine with some manual tweaking in 10.1/10.2, using 855resolution or 915resolution. There is some hidden bit in your graphics card that gets set by the BIOS or your screen extender software, but without documentation for the DELL bios (and somebody willing to write the software), there is not much we can do about it. -- 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=216082 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Comment #13 from pavel@novell.com 2006-11-23 07:26 MST ------- I do not know what the screen "extender" is, and it may be a problem here. Try reporting problem against it. You may also want to try 10.2 as seife suggests. -- 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