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 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pavel@novell.com --- Comment #1 from Stefan Seyfried 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#c3 --- Comment #3 from Andrew Horoszczak 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 seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396875#c5 --- Comment #5 from Stefan Seyfried 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 ah@forex.pl added comment https://bugzilla.novell.com/show_bug.cgi?id=396875#c7 Andrew Horoszczak changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX |REMIND --- Comment #7 from Andrew Horoszczak 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.