[opensuse] Fwd: Dell D820 & Suspend to ram on SUSE 10.1, SLED or SLES
Hi, I've had Suspend to ram work on my Dell D820, by using "s2ram -f", this was running 0pensuse 10.1 However when I moved up to SLED I've gotten a problem where it seems to work but after a few minutes my keyboard start writing multiple characters when pressing the key only once, and typically my Firefox will freeze. Switching to console Ctrl-Alt F1 everything looks just fine, but my X windows environment is frozen. Resetting it by moving to runlevel 1 and back to 5 doesnot fix it - only a full reboot brings me back to normal. As explained these problems ONLY occur after a suspend to ram and a return, never after a complete shutdown - so it has to be a suspend problem - I just cant figure out which one. I have gone thru all the different options that S2ram has - and none of them solves the issue. Somewhere I've seem postings hinting that it may be an APIC related issue, but why the subtle difference between opensuse 10.1 and SLED then ? Any ideas ? KR Bjørn ________________________________ Bjørn Kelsen Instructor CNE,CNI,CLE,CLP,CTT+,LPIC 1,MCP Mobil: +45 28 111 692 E mail: bk@nle.dk Next Level Education Byvaenget 4 4652 Haarlev Tlf: +45 70 222 331 Web: www.nle.dk _______________________________ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2006-11-21 at 11:05 +0100, Bjørn Kelsen wrote:
Hi,
I've had Suspend to ram work on my Dell D820, by using "s2ram -f", this was running 0pensuse 10.1 However when I moved up to SLED I've gotten a problem where it seems to work but after a few minutes my keyboard start writing multiple characters when pressing the key only once, and typically my Firefox will freeze. Switching to console Ctrl-Alt F1 everything looks just fine, but my X windows environment is frozen. Resetting it by moving to runlevel 1 and back to 5 doesnot fix it - only a full reboot brings me back to normal. As explained these problems ONLY occur after a suspend to ram and a return, never after a complete shutdown - so it has to be a suspend problem - I just cant figure out which one.
I have gone thru all the different options that S2ram has - and none of them solves the issue.
Somewhere I've seem postings hinting that it may be an APIC related issue, but why the subtle difference between opensuse 10.1 and SLED then ?
Any ideas ?
KR Bjørn
How did you get it to work for 10.1? I have tried s2ram -f and get my sound broken, and every x seconds my screen flickers to black and back, wireless messed up, multiple chars, etc. Did you have to edit some config files? E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-11-21 at 11:05 +0100, Bjørn Kelsen wrote:
I've had Suspend to ram work on my Dell D820, by using "s2ram -f", this was running 0pensuse 10.1 However when I moved up to SLED I've gotten a problem where it seems to work but after a few minutes my keyboard start writing multiple characters when pressing the key only once, and typically my Firefox will freeze. Switching to console Ctrl-Alt F1 everything looks just fine, but my X windows environment is frozen.
Are you using the nvidia binary driver, perhaps? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFaFKGtTMYHG2NR9URAgTRAJ9vJEKJTQ/3Z7D/BTav8B+bKYEyTwCaAg8H 4J7Co0sLoQPdbuw8eFyyNes= =JHNO -----END PGP SIGNATURE-----
participants (3)
-
Bjørn Kelsen
-
Carlos E. R.
-
Hans van der Merwe