[Bug 220865] New: s2ram does not work on IBM X41 Tablet
https://bugzilla.novell.com/show_bug.cgi?id=220865 Summary: s2ram does not work on IBM X41 Tablet Product: openSUSE 10.2 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Mobile Devices AssignedTo: seife@novell.com ReportedBy: dkukawka@novell.com QAContact: qa@suse.de Suspend 2 RAM does not work on a IBM X41 Tablet PC. It work on console, but break the complete X server. The option for the machine are complete wrong (should be -a3 only): e121:~ # s2ram -n Machine matched entry 224: sys_vendor = 'IBM' sys_product = '1869*' sys_version = '' bios_version = '' Fixes: 0x2c VBE_SAVE VBE_POST Machine is in the whitelist but perhaps using vbetool unnecessarily. Please try to find minimal options. This machine can be identified by: sys_vendor = "IBM" sys_product = "1869CSU" sys_version = "ThinkPad X41 Tablet" bios_version = "75ET57WW (2.03 )" See http://en.opensuse.org/S2ram for 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=220865 mhopf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhopf@novell.com Summary|s2ram does not work on IBM |s2ram does not work on IBM X41 Tablet and on |X41 Tablet |Dell D410 ------- Comment #1 from mhopf@novell.com 2006-11-14 10:29 MST ------- Same on this Dell D410. This machine (presumably) prefectly suspends & resumes with s2ram -f. So neither VBE_SAVE nor VBE_POST are neccessary, they are actually extremely harmfull (constant Xserver crash). e43 18:25:20 ~ <999> sudo s2ram -n Machine matched entry 42: sys_vendor = 'Dell Inc.' sys_product = 'Latitude D410 *' sys_version = '' bios_version = '' Fixes: 0xc VBE_SAVE VBE_POST This machine can be identified by: sys_vendor = "Dell Inc." sys_product = "Latitude D410 " sys_version = "" bios_version = "A04" -- 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=220865 ------- Comment #2 from seife@novell.com 2006-11-14 15:20 MST ------- (In reply to comment #0)
Suspend 2 RAM does not work on a IBM X41 Tablet PC. It work on console, but break the complete X server.
The option for the machine are complete wrong (should be -a3 only):
e121:~ # s2ram -n Machine matched entry 224: sys_vendor = 'IBM' sys_product = '1869*' sys_version = '' bios_version = '' Fixes: 0x2c VBE_SAVE VBE_POST Machine is in the whitelist but perhaps using vbetool unnecessarily. Please try to find minimal options.
yes, this is an unverified entry we took on initial import from ubuntus acpi-support package. I fixed the entry for this Thinkpad to be S3_BIOS|S3_MODE (-a 3). -- 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=220865 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pavel@novell.com Status|NEW |ASSIGNED ------- Comment #3 from seife@novell.com 2006-11-14 15:22 MST ------- (In reply to comment #1)
Same on this Dell D410. This machine (presumably) prefectly suspends & resumes with s2ram -f.
On the text console or from X?
So neither VBE_SAVE nor VBE_POST are neccessary, they are actually extremely harmfull (constant Xserver crash).
Well, i'd guess that the X server is somewhat buggy now, since AFAIR it could handle this case earlier (i think i tested the D410, but am not sure anymore. I assumed you were constantly testing this machine with the latest code). Note that "-a X" options usually do not work with DELLs. -- 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=220865 ------- Comment #4 from mhopf@novell.com 2006-11-15 08:19 MST ------- (In reply to comment #3)
Same on this Dell D410. This machine (presumably) prefectly suspends & resumes with s2ram -f.
On the text console or from X?
Ok, I tested it once more. X crashes as soon as -s is involved.
From X: s2ram -f works as intended, s2ram -f -p as well.
From console: s2ram -f leaves the display dark, is revived after switching to X and back. s2ram -f -p -m works pretty much, only the background image is missing. After switching a console front and back, everything looks fine. This also leaves the Xserver intact.
Well, i'd guess that the X server is somewhat buggy now, since AFAIR it could handle this case earlier (i think i tested the D410, but am not sure anymore.
Just tested this: s2ram -f works as in 10.2b2+. s2ram (-f -p -s) restores the framebuffer, but the top few lines are distorted. But yes, the Xserver didn't die. So we have an regression in the intel driver here. Sigh. Maybe (as posting VBE bios here isn't really specified anyway) something has been changed that made it incompatible. -m wasn't available in 10.1. I, personally, would say that is the cleanest solution.
assumed you were constantly testing this machine with the latest code).
I almost never use suspend to ram on this machine.
Note that "-a X" options usually do not work with DELLs.
Never ever tried one of those. -- 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=220865 ------- Comment #5 from seife@novell.com 2006-11-15 09:39 MST ------- (In reply to comment #4)
(In reply to comment #3)
Same on this Dell D410. This machine (presumably) prefectly suspends & resumes with s2ram -f.
On the text console or from X?
Ok, I tested it once more. X crashes as soon as -s is involved.
Ok. I _knew_ that -s was evil!!!1! :-)
s2ram -f -p -m works pretty much, only the background image is missing.
This is normal. Framebuffer contents are not saved and the card looses it clears it apparently on VBE mode setting.
After switching a console front and back, everything looks fine. This also leaves the Xserver intact.
Cool, so we'll take "-p -m" (which is my favourite on if "-a X" does not work anyway). Thanks for testing.
Well, i'd guess that the X server is somewhat buggy now, since AFAIR it could handle this case earlier (i think i tested the D410, but am not sure anymore.
Just tested this:
s2ram -f works as in 10.2b2+. s2ram (-f -p -s) restores the framebuffer, but the top few lines are distorted. But yes, the Xserver didn't die.
The distortion is again normal, it is more an accident that parts of the framebuffer contents are restored at all :-)
So we have an regression in the intel driver here. Sigh. Maybe (as posting VBE bios here isn't really specified anyway) something has been changed that made it incompatible.
-m wasn't available in 10.1. I, personally, would say that is the cleanest solution.
Me too :-)
assumed you were constantly testing this machine with the latest code).
I almost never use suspend to ram on this machine.
Ts ts ts... bad boy :-)
Note that "-a X" options usually do not work with DELLs.
Never ever tried one of those.
The Dell's usually just boot instead of resuming with them. I'll submit a package with a fixed whitelist soon. -- 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=220865 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #6 from seife@novell.com 2006-11-15 09:42 MST ------- package submitted -- 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=220865 behlert@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED -- 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