This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Suspend to RAM not work

Tags: None
(comma "," separated)
horizon
Registered Member
Posts
9
Karma
0
OS

Suspend to RAM not work

Tue Jun 16, 2015 5:01 pm
Hi all,

I'm using KDE 5 with Kubuntu and I have latest updates installed (kernel version: 3.19.0-21-generic).
The machine is a Lenovo IdeaPad Z510 laptop.
After hitting Sleep in App launcher menu or running pm-suspend command, it goes to sleep, but after resuming, nothing works and system just freezes and I should do a hard poweroff. Also, I don't have any Hibernate option in the menu.

Please tell me if I should provide more detailed informations.
Thanks for your help.
luebking
Karma
0

Re: Suspend to RAM not work

Tue Jun 16, 2015 8:54 pm
nvidia system?

Does pressing "SHIFT+Alt+F12" (suspending the compositor) before (or maybe even after) STR help?
Do you have a "don't use framebuffer terminals" warning in "dmesg | grep -i nvrm"?
horizon
Registered Member
Posts
9
Karma
0
OS

Re: Suspend to RAM not work

Wed Jun 17, 2015 4:42 pm
Thank you luebking,

Yes it's nvidia. I add this point that my system did not work with the nvidia's recommended driver (in KDE settings device manager), so still nouveau is used.

Pressing SHIFT+Alt+F12 didn't help before or after sleep. When I do that, my panel is going gray and tray icons getting small! Also, I see "Alt+Shift+F12 = Suspend Compositing" in syslog. It's all that I can say about that.

No luebking, there's nothing about nvrm or that message in dmesg.
luebking
Karma
0

Re: Suspend to RAM not work

Wed Jun 17, 2015 4:47 pm
the nvrm message is from the nvidia blob, so it's expectable to be absent.

The "not working suggested driver" is a downstream (fedora) issue, but it's certainly worth trying the nvidia blob on the problem - what kind of chip is it? ("lspci | grep -i nvidia")
horizon
Registered Member
Posts
9
Karma
0
OS

Re: Suspend to RAM not work

Wed Jun 17, 2015 5:21 pm
$ lspci | grep -i nvidia
07:00.0 3D controller: NVIDIA Corporation GK208M [GeForce GT 740M] (rev a1)
luebking
Karma
0

Re: Suspend to RAM not work

Wed Jun 17, 2015 5:39 pm
The GPU is supported by any recent nvidia driver, you do NOT want to pick the legacy (304.xxx) one.
In how far does it "not work"?
horizon
Registered Member
Posts
9
Karma
0
OS

Re: Suspend to RAM not work

Wed Jun 17, 2015 6:16 pm
Actually I tried to install KDE recommended driver, a couple of weeks ago, and I couldn't get a normal X session after the system restart.
Now, I have recent updates installed, and I'm going to test it again. The version now is nvidia-346.
I will post the results.

Thank you very much.
horizon
Registered Member
Posts
9
Karma
0
OS

Re: Suspend to RAM not work

Wed Jun 17, 2015 6:32 pm
Still no success I think!
The KDE login screen did not comp up normally, I had to kill Xorg or sddm processes several times until an X session appears. But, after login, there's clearly some problems like big fonts, ugly animations, disappeared mouse pointer in some areas, etc. By the way, I'll check suspend in this state.
horizon
Registered Member
Posts
9
Karma
0
OS

Re: Suspend to RAM not work

Wed Jun 17, 2015 7:06 pm
Suspend functionality did not work with nvidia driver loaded. Also, no help with pressing Alt+Shift+F12.
In dmesg log, I had this about nvrm:
[ 18.931452] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015
luebking
Karma
0

Re: Suspend to RAM not work

Wed Jun 17, 2015 9:44 pm
It's more than unlikely a graphical issue then - either X or some kernel module (likely neither nvidia nor nouveau) will stall.

Try to access VT2 (ctrl+alt+F2) or ping/ssh the machine.
If you can ssh into it: profit.

If it doesn't respond, the kernel is completely frozen.
For a _very_ wild shot, add "dis_ucode_ldr" to the kernel parameters (in grub).
This will disable (auto-)loading of microcode into the CPU.
horizon
Registered Member
Posts
9
Karma
0
OS

Re: Suspend to RAM not work

Thu Jun 18, 2015 6:39 pm
Hi,

It's completely frozen, and there's no access, neither by virtual terminals nor ssh/ping.
How does adding `dis_ucode_ldr' help? What should I do after adding it?

Thanks.
luebking
Karma
0

Re: Suspend to RAM not work

Thu Jun 18, 2015 7:10 pm
dis_ucode_ldr prevents loading of microcode into the prcoessor (by 90% chance you're not using specific microcode anyway) and it caused some trouble here.

It's a kernel parameter, ie. you'd edit the boot selection in grub (about the first thing you'll see on reboots, where you'd select between different OS's) and boot with it (you can ensure it's in by "cat /proc/cmdline")

The just STR, wait & wakeup and see whether it now works.

The option applies to the kernel and remains set until your next reboot. If it works, you may want to add it to the kernel parameters in grub (likely configured in /etc/default/grub, but i don't know for sure for fedora)


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], rockscient