[Bug 396875] New: s2ram does not work on HP Pavilion and permamently(?) corrupts display on nVidia
https://bugzilla.novell.com/show_bug.cgi?id=396875 Summary: s2ram does not work on HP Pavilion and permamently(?) corrupts display on nVidia Product: openSUSE 11.0 Version: RC 1 Platform: HP OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: zoz@novell.com ReportedBy: ah@forex.pl QAContact: qa@suse.de Found By: --- in kde4 the command to suspend to ram did nothing (not even initialize the process0 so I followed the procedure with init=/bin/bash s2ram -f - started to put machine to sleep - but when i woke PC up the video did not resume (the CAPS lOCK and NUM LOCKS were responding) I tried adding -a and other swiches - but it (strangely) complained that it needs kerlnel > 2.6.16 and the command with additional switches did not execute now when I rebooted the machine - even after unpluging it from the wall I noticed screen artifacts - randomly flashing thin horizontal lines (one pixel high) on my screen (even in text mode) and bunches of randomly flashing pixels towards the right hand of the display why does it not go away? could it be hardware defect? and if so how could s2ram have caused it? linx:~ # s2ram -i This machine can be identified by: sys_vendor = "HP-Pavilion" sys_product = "GJ306AA-ABE m8175.es" sys_version = " " bios_version = "5.05 " See http://en.opensuse.org/S2ram for details. Display Info Vendor: nVidia Corporation Model: GeForce 8400 GS Driver: nv -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=396875 Danny Kukawka <dkukawka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dkukawka@novell.com AssignedTo|zoz@novell.com |seife@novell.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.
https://bugzilla.novell.com/show_bug.cgi?id=396875 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396875#c1 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pavel@novell.com --- Comment #1 from Stefan Seyfried <seife@novell.com> 2008-06-05 07:21:26 MDT --- (In reply to comment #0 from Andrew Horoszczak)
in kde4 the command to suspend to ram did nothing (not even initialize the process0
yes, because your machine is probably not known to s2ram, or known to not work.
so I followed the procedure with init=/bin/bash
s2ram -f - started to put machine to sleep - but when i woke PC up the video did not resume (the CAPS lOCK and NUM LOCKS were responding)
good.
I tried adding -a and other swiches - but it (strangely) complained that it needs kerlnel > 2.6.16 and the command with additional switches did not execute
you probably had not mounted the /proc filesystem.
now when I rebooted the machine - even after unpluging it from the wall I noticed screen artifacts - randomly flashing thin horizontal lines (one pixel high) on my screen (even in text mode) and bunches of randomly flashing pixels towards the right hand of the display
why does it not go away? could it be hardware defect?
Might be, maybe some bad contacts on the graphics card or something like that.
and if so how could s2ram have caused it?
I cannot imagine how s2ram could have caused that, i think it is just a coincidence. (You surely can damage badly constructed hardware by software, e.g. by overclocking and similar, but s2ram does nothing like that). s2ram does only execute code that's in the BIOS, so it should be safe for the hardware IMHO. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=396875 User ah@forex.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=396875#c2 --- Comment #2 from Andrew Horoszczak <ah@forex.pl> 2008-06-05 13:15:22 MDT --- Stefan, Thank you for prompt help. yes indeed it was coincidence and loose contacts on the card now that I have ruled out the hardware defect - I feel more courageous to continue experimenting .. I assume it is worth the effort (since the keyboard is responding) I did issue the mount /proc command - but indeed I did not check if it worked I will do some more tests and report back -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=396875 User ah@forex.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=396875#c3 --- Comment #3 from Andrew Horoszczak <ah@forex.pl> 2008-06-05 14:15:24 MDT --- I have now tried all 10 recommended variations of switches unfortunately none worked (I am still to do combination with -v) however, I have question - since it seems that except the display the PC is operational - would it help the diagnostics if after resuming - I would ssh to this PC from another machine ? Also I am using HDMI output of the nVidia card - does it make any difference if I switch to regular D-SUB connector / monitor ? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=396875 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396875#c4 Pavel Machek <pavel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|s2ram does not work on HP Pavilion and |s2ram does not work on HP Pavilion |permamently(?) corrupts display on nVidia | --- Comment #4 from Pavel Machek <pavel@novell.com> 2008-06-06 02:05:07 MDT --- I don't think ssh access is too useful :-(. Yes, HDMI might be aproblem; but don't put your hopes too high... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=396875 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396875#c5 --- Comment #5 from Stefan Seyfried <seife@novell.com> 2008-06-06 02:14:31 MDT --- If you are using the proprietary nvidia driver, it might work from within X with plain "s2ram -f". Apparently the nvidia driver knows how to get the light back on again... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=396875 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396875#c6 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #6 from Stefan Seyfried <seife@novell.com> 2008-06-27 08:37:41 MDT --- Sorry, with NVidia, we cannot do much if the normal process with s2ram options does not help, the only hope is the nvidia binary driver, which might have other issues of course. So i'll close this as "WONTFIX", even though it rather is a "CANTFIX", but we don't have that as a resolution ;-) Sorry again, and good luck. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=396875 User ah@forex.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=396875#c7 Andrew Horoszczak <ah@forex.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX |REMIND --- Comment #7 from Andrew Horoszczak <ah@forex.pl> 2008-06-30 09:06:24 MDT --- Stefan, Some good news - i have waited for Suse 11 gold and now I have downloaded the binary nvidia driveres - and with them it WORKS! so I think it is safe to add this machine to known list = provided that binary nvidia drivers are installed do you need anything from me in terms of machine identification? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=396875 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396875#c9 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #9 from Stefan Seyfried <seife@novell.com> 2008-09-18 10:16:00 MDT --- Unfortunately there is no way to add it as "works only with binary drivers". However, with 11.1 the handling will change slightly, so that we will enable suspend by default if the nvidia driver is installed / loaded, so it should hopefully be fine. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com