Mainboard: ASUS P8Z77-V
nVidia GTX680 using latest driver from nVidia repo
When attempting a suspend to RAM and the screen goes black (but stays on), the Caps Lock and Scroll Lock start blinking. Hard disks (sound like) turned off but fans and everything else stays on. The only way to get out of the situation is to push the Reset button on the box.
Windows 7 can sleep this machine without problem, so the problem is not the hardware. I tried 3 installations of openSUSE 13.2 and Tumbleweed - no luck.
Blinking caps and scroll means kernel panic. You may try current kernel (https://en.opensuse.org/Kernel) but you will have to install nVidia using installer, not RPM.
I know it is kernel panic. However when I was using Tumbleweed (earlier) and was always with the latest kernel that didn’t help.
Reading around the web I found other people complaining about similar issues and it seems related to nVidia. However the pages I found didn’t show any solution, so I was hoping someone might know here about a fix.
Yes. Actually I am right back from a clean reinstall after which I tried with the default driver (nouveau). Same result - suspend to rum doesn’t work properly.
If this happens with nouveau and latest kernel, you should report it. But you will need at least stack trace for this. Can you reproduce it with nouveau in text mode (which would make it possible to provide picture of oops)? If no, do you have second PC so you could setup netconsole to capture oops? It may also be possible to configure crash dump, but without explicit request from some developer it makes little sense.
both return nothing (simply goes to the next line)
I have also experimented earlier today with s2ram (with some of the options given here) but the result is always the same. The machine doesn’t turn off.
Stack trace is printed by kernel to console when it crashes. But when you are in graphical mode it is not visible. Hence suggestion to try to reproduce it in text mode.
both return nothing (simply goes to the next line)
Which is correct - this command returns exist code and prints nothing. So you do have pm-utils. Try to remove them for testing.
I have also experimented earlier today with s2ram (with some of the options given here) but the result is always the same. The machine doesn’t turn off.
Well, s2ram basically runs the same set of quirks as pm-utils.