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
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.