Suspend to ram in KDE vs. GNOME

I recently switched over to KDE for a little bit to test it out and see how it felt. I decided to stick with GNOME, but I realized that in KDE, the "start" menu's suspend to ram worked perfectly fine. Switching back to GNOME, it hangs at a blinking cursor when I try the suspend to ram via the "start menu". The commandline pm-suspend works fine.
What's the difference between the way KDE and GNOME call suspend?

Hello majiq!
Is there any error output after this method, or What experience do you have(Kde) ?

Similar Messages

[SOLVED for now] Suspend-to-RAM broken - immediately turns on again

Hi everyone,
Susped-to-RAM was working flawlessly on my lenovo IdeaPad S12 Netbook until recently:
When I Suspend-to-RAM (via KDE) the system apparently suspends correctly but then it instantly turns back on. So the problem is not that I cannot suspend but rather that the system turns back on immediately after suspending. Usually the system could only be turned back on by pressing a button on the keyboard or the power button (not by moving the mouse or opening the laptop lid).
I unplugged all attached devices, including mouse, keyboard, power supply and network but that doesn't help.
I'm pretty clueless what could cause this and would be happy if someone could point me in some direction. This used to work until recently but I don't know what update broke it.
Last edited by Vortex375 (2012-03-02 16:37:18)

Vortex375 wrote:
Update:
The system stays asleep when I unload the ehci_hcd and ohci_hcd before suspending (unloading just ehci_hcd as suggested on other sites doesn't work).
So some kind of usb device seems to trigger the wakeup. As I said before I don't have any usb devices plugged in, though.
Since unloading the usb drivers is not very convenient I would really like to find out what exactly causes the wakeup. I don't really have a clue where to start, though.
I use a script to unload ehci_hcd automatically when I suspend (my issue is slightly different, it doesn't immediately come back, it just doesn't finish suspending and gets stuck on a black screen)
I'd imagine a script someone similar to this would work:
http://thecodecentral.com/2011/01/18/fi … orking-bug
Last edited by bwat47 (2012-03-02 01:23:23)

KDE vs Gnome vs XFCE (amount of ram used.)

I run the command:
coda ~ $ free -m
total used free shared buffers cached
Mem: 2010 1341 669 0 78 890
-/+ buffers/cache: 373 1637
Swap: 1474 0 1474
So I'm using a total of 373 megs of ram on KDE.
I have an old laptop, and I want to know if I have enough ram to run gnome without excessively using swap.
And if not, I'll just use XFCE.
How much RAM (on average) does Gnome and XFCE use?

Dirhael wrote:
lucke wrote:Does anyone perhaps have any meaningful and comparable figures for XP/Vista, running basic desktop apps?
I don't think you'll find any with meaningful figures, and the figures here aren't all that useful either. I mean, even comparing memory usage between two different users with the exact same programs running and the very same hardware will give you very different results unless it's measured directly after a cold boot (and the numbers you'll get then is meaningless anyway), seeing as usage patterns will have a major effect on how much memory any application will use.
Agreed.
What is also not being taken into account here is kernel modules loaded.
Unloading unused modules may reduce significantly, the amount of used memory (i.e. free up memory)
Note the +/-buffers line presents the (used and) free mem available to applications.
Last edited by keratos (2008-04-29 12:01:48)

LG R510 - Suspend-to-RAM problem

Hi, I'm having trouble using the suspend-to-ram feature on my LG R510 laptop. I tried suspending the machine using the suspend feature integrated in KDE-4.2 as well as using the command-line tools s2ram and pm-suspend. The machine behaves exactly the same in all cases:
The system (apparently) suspends without errors. It also correctly restores to it's former state upon wakeup. Even the X-Server starts and seems to work fine.
However, the hard-drive can no longer be accessed after wakeup, leaving you with a "dead" system.
If you try running a command from a shell it will trigger either "command not found" or "input/output error" messages. For that reason I'm unable to gather any diagnostic information from the continued system. Since the hard-drive cannot be accessed, no logs get written after wakeup either.
The hard-drive does spin up when the system wakes up (I can clearly hear it). There is probably some problem with the hard-drive controller. However, I wasn't able to find any specific information about Intel ICH9 chipsets and suspend-to-RAM yet.
I will post some details about the system. Please feel free to ask for additional information.
$ uname -a
Linux klappkeks 2.6.28-ARCH #1 SMP PREEMPT Sun Mar 8 10:55:58 CET 2009 x86_64 Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz GenuineIntel GNU/Linux
# s2ram -i
This machine can be identified by:
sys_vendor = "LG Electronics"
sys_product = "R510"
sys_version = "03"
bios_version = "QL8L3B92"
# lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 9600M GS (rev a1)
02:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

It seems this is a BIOS bug of the LG R510. There is a workaround: You have to set your hard drive to IDE mode.
To do this, open the BIOS setup utility by pressing F2 during startup. Look for the "HDC configure as" option and switch it from AHCI to IDE.
Note that this might reduce disk performance. So far, I haven't noticed any difference after switching to IDE. Suspend-to-RAM works like a charm now.
By the way, a similar problem occurs on HP notebooks where it can be fixed through a BIOS update. Unfortunately there is no update available for the LG R510 yet.

[SOLVED} Suspend to ram does not work (with sleep, s2ram, pm-utils)

Hi.
I would like to ask for one thing: i can't suspend to ram or resume from suspend to ram.
I treid to check over www in order to find some help, some solutions, and how to fix that. Unfortunately, i found these:
https://forums.opensuse.org/showthread. … 13-2/page2
https://bugzilla.opensuse.org/show_bug.cgi?id=913105
https://forums.opensuse.org/showthread. … S-13-1-x64
Bug 91921 - WD 2TB Caviar black causes hard lock on resume S2RAM
https://bugzilla.kernel.org/show_bug.cgi?id=91921
In fact, when i was researching of this problem i wanted to check if my graphic card and memory are failing so a did few changes (removed memory stick and so one) but in doing this i removed almost all of my hard disk drives because i didn't want to hurt them with many reboots or resets.
What did i find? It is strange, kernel version is not important because i checked most of them.
I removed 2x2TB Seagate F14 series along with 4x3TB WD Green. Then i checked s2ram, it went to suspend, and resumes correctly. Everything works. I put it to sleep with s2ram -f -a 1. Works
I attached my 4x3TB WD Green drives. I put computer to sleep with s2ram...it causes hard lock, black screen, i could do only poweroff by powerbutton. s2ram -f -a 1 causes freez. Sometimes, but not constantly, s2ram -f -a 3 -p is being able to suspend...(mostly it does a freez, hard lock computer) but sometimes it is able to put it to a sleep, but resume just freezes everyting - no blinking cursor, no blinking num lock led and so on.
I know that you would suggest me to check logs - this is the main problem. Logs for pm-suspend works when i suspend or resume without WD drives attached. When i have them connected, i'm not able to check pm-logs because computer hangs, freezes and logs are not being stored/writed to pm-suspend.log and pm-powersave.log.
Could somebody help? Point me to a solution? I can't check logs because there are not any when freezing occurs. I checked openSuse thread and many others and for other systems there were some kernel fixex, patches.
They wrote that WD blacks are at fault because they don't have APM. Well, in fact my WD Green have APM with very aggresive factory settings: they park heads over 8 seconds not being used. I disabled it in firmware but disabling it is not the point and not the problem. People have the same problem even with APM and parking heads on other WD drives, i found it that some have it with WD Red's drives and even with very old 320GB WD Blue series - what is more funny, i have 640GB AAKS blue from WD and with this drive i can suspend or resume - APM on this drive is also unavilable, like in Green series because i changed it with wdidle with prebootable cd. I can't supend or resume with 3TB WD Greens.
BTW - suspend to disk, with pm-utils and uswsusp works ok, in 100% every time. (i had to add "shutdown method = shutdown" to /etc/suspend.conf from uswsusp package).
On Windows machine it works. Can suspend, can resume, can hibernate.
Last edited by firekage (2015-03-07 03:27:28)

Hm, sometimes i found myself astonished because some things just does not work at all on one machine, while the other one has no problem at all. I was trying to find why suspend to ram won't work at all...and while i was searching i found one topic that was leading to upower dbus. Similar problem with upower i found, by coincidence, on Manjaro forum.
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
this command above returns all the time:
Error org.freedesktop.DBus.Error.UnknownMethod: Method "Suspend" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I tried this:
sudo systemctl enable acpid.service
sudo systemctl --system daemon-reload
sudo systemctl restart systemd-logind
As soon as i enabled and started acpid.service...my supend to ram, from kde, works like a charm, without graphic problem, or freezing.
There is few question: why on my desktop suspend doesen't work out of the box, when even archwiki says it should? Why on my netbook machine (Acer AOD270) that has the same package installed it works out of the box? Why on my desktop machine acpid.service was not enabled, was not started and was not running while on the notebook it does?
Anyway...i fixed it by a big coincidence because on Fedora forum somebody has problem with suspend to ram with nvidia GTX750 and this card was new like my card (GTX660). He posted the same problem with upower that i posted in quotes and because of this i found another thing on Manjaro forum and that was it!
BTW - this problem, i now think, is not related to my WD drives because it works with them. I think that there was another one ugly thing that broke my suspend to ram ability - bios of my motherboard (so called uefi bios with support for old one) has no option for S1-S5 stated (like the previous motherboards had) and only have ASPM...and ASPM is in my opinion broken but i will try to veryfi it one again later.
Last edited by firekage (2015-03-07 03:29:20)

Resume from suspend to ram fails (pm-utils)

Hi,
When I suspend to ram the computer seems to suspend normally, but the resume fails and it triggers a normal boot instead.
I'm on a Lenovo Thinkpad X60 laptop with the 2.6.30 kernel and gnome-power-manager (pm-utils).

Unfortunately, every laptop seems to have its own idiosyncrasies with this (not to mention differences in different users' setups---e.g., what devices are attached, what modules are loaded). So it takes some serious trial and error to figure out how to get this to work. All I can suggest is that you become intimately familiar with the wiki page, and with the HAL quirks site, and that you try to eliminate all the daemons and so on you can while still generating the problem (e.g., boot into a virtual console instead of gnome, if you're comfortable with that). Then start a process of trying different quirks as explained on those webpages. Take good notes so you don't lose track of which combinations of quirks show result in what behavior.
The HAL quirks site will also point you to what other users using your laptop, or similar laptops, found to work. But trial and error may still be necessary.

Pc doesn't resume from suspend to ram anymore (new 3.4.2 kernel)

hi.
I was using nouveau without problem and with the little trick of using acpi_os_name="Microsoft Windows NT" kernel parameter, I was able to suspend to ram from gnome, and resume the pc without problem
Not anymore. Now, if I suspend to ram, the pc does not resume. It correctly wake up the dvd drive, the hard-drive, began to read stuff on the hdd but the led of the power button stays blinking and the screen is not waken up.
I am thinking this is due to the update of nouveau and a new regression but this seems related to the bios or hardware. For example. If after the broken resume, I hold down 10 seconds the power button to power off, and press it again to power on, the led is still blinking and it does not boot. I need to power off by removing the power cord.
Is it because I run (to test it) the nvida-173xx, and that did something to the graphic card ?
Did anyone got similar problem with the new nouveau driver ?
I tried to downgrade libgl, libdrm, libdrm-nouveau, nouveau-dri, xf86-video-nouveau and mesa but I still got the problem. so ?
I have a geforce 8300 GS. the pc is an inspiron 531
Last edited by solstice (2012-06-18 08:56:49)

Probably I have the same issue with geforce GTS250.
After upgrading to kernel 3.4.2 or so, my system doesn't resume from suspend, only black screen and cannot switch to other ttys.
I first thought this problem be caused by the kernel, but downgrading nvidia to 295.53-2 solved this problem on kernel 3.4.3 so this likely is caused by nvidia 302.17.
In my case there is something like error in pm-suspend.log when resume failed:
Fri Jun 22 05:36:12 JST: Awake.
Fri Jun 22 05:36:12 JST: Running hooks for resume
Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:
/usr/lib/pm-utils/sleep.d/95led resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:
/usr/lib/pm-utils/sleep.d/90clock resume suspend: success.
Running hook /etc/pm/sleep.d/90alsa resume suspend:
xcb_connection_has_error() returned true
And curiously, if I had launched vlc media player before suspend, resume worked well even on nvidia 302.17.

Cannot resume from suspend to ram (fglrx)

Hello,
I have recently installed Catalyst drivers, instead of xf86-video-ati. I have laptop with PowerXPress(Intel/AMD hybrid graphics).
I can't resume after suspend to ram. System freezes with black screen, tty switching doesn't work and I have to shutdown by holding power button.
If I add "nomodeset" to GRUB, X fails to start. xorg.conf generated using "aticonfig --initial". Catalyst driver works fine.
DE/DM: KDE 4/kwin
Graphic cards: Intel HD Graphics 3000; AMD Radeon 7600M.
Laptop: HP pavillion g6 2004er.

Welcome to the forum!
Yes, some Lenovo employees do read and post to this forum. Mark is quite active, and several others post as well. In addition, there are lurkers who just read without making public comments although sometimes they ask the mod team to either gather more information or pass along advice.
However, here are the expectations of their participation from the Welcome message:
These communities have been created to provide a high quality atmosphere in which users of Lenovo products and services may share experiences and expertise. While members from Lenovo may participate at intervals to engage in the discussions and offer advice and suggestions, this forum is not designed as a dedicated and staffed support channel.
The bottom line is there's no guarantee that you will get an answer to a question here directly from Lenovo.
On the other hand, you just might! ;-)
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Jane
2015 X1 Carbon, ThinkPad Slate, T410s, X301, X200 Tablet, T60p, HP TouchPad, iPad Air 2, iPhone 5S, IdeaTab A2107A, Yoga Tablet, Yoga 3 Pro
I am not a Lenovo Employee.
I AM one of those crazy ThinkPad zealots!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!

[Solved] Suspend to ram doesn't work correctly on Acer Aspire 5100

Hi people of the archlinux forum.
Finally I decided to change from ubuntu to archlinux because I wanted to learn more about the world of linux.:D
I have already almost completely set up my laptop, but I have a problem when suspending to ram. The problem comes out when i wake up the laptop, and the screen starts to flicker and will not go away until i restart the laptop.
This is my laptop after the suspend:
I'm using pm-utils to suspend and hibernate my laptop, and the hibernate works fine. All settings were made following the arch wiki.
this is my xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "dri"
Load "extmod"
Load "glx"
Load "dbe"
Load "dri2"
Load "record"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
#DisplaySize 330 210 # mm
Identifier "Monitor0"
VendorName "AUO"
ModelName "2174"
EndSection
Section "Device"
### Available Driver options are:-
### Values: : integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "Dac6Bit" # [<bool>]
#Option "Dac8Bit" # [<bool>]
#Option "BusType" # [<str>]
#Option "CPPIOMode" # [<bool>]
#Option "CPusecTimeout" # 
#Option "AGPMode" # 
#Option "AGPFastWrite" # [<bool>]
#Option "AGPSize" # 
#Option "GARTSize" # 
#Option "RingSize" # 
#Option "BufferSize" # 
#Option "EnableDepthMoves" # [<bool>]
#Option "EnablePageFlip" # [<bool>]
#Option "NoBackBuffer" # [<bool>]
#Option "DMAForXv" # [<bool>]
#Option "FBTexPercent" # 
#Option "DepthBits" # 
#Option "PCIAPERSize" # 
#Option "AccelDFS" # [<bool>]
#Option "IgnoreEDID" # [<bool>]
#Option "CustomEDID" # [<str>]
#Option "DisplayPriority" # [<str>]
#Option "PanelSize" # [<str>]
#Option "ForceMinDotClock" # <freq>
#Option "ColorTiling" # [<bool>]
#Option "VideoKey" # 
#Option "RageTheatreCrystal" # 
#Option "RageTheatreTunerPort" # 
#Option "RageTheatreCompositePort" # 
#Option "RageTheatreSVideoPort" # 
#Option "TunerType" # 
#Option "RageTheatreMicrocPath" # <str>
#Option "RageTheatreMicrocType" # <str>
#Option "ScalerWidth" # 
#Option "RenderAccel" # [<bool>]
#Option "SubPixelOrder" # [<str>]
#Option "ShowCache" # [<bool>]
#Option "ClockGating" # [<bool>]
#Option "VGAAccess" # [<bool>]
#Option "ReverseDDC" # [<bool>]
#Option "LVDSProbePLL" # [<bool>]
#Option "AccelMethod" # <str>
#Option "DRI" # [<bool>]
#Option "ConnectorTable" # <str>
#Option "DefaultConnectorTable" # [<bool>]
#Option "DefaultTMDSPLL" # [<bool>]
#Option "TVDACLoadDetect" # [<bool>]
#Option "ForceTVOut" # [<bool>]
#Option "TVStandard" # <str>
#Option "IgnoreLidStatus" # [<bool>]
#Option "DefaultTVDACAdj" # [<bool>]
#Option "Int10" # [<bool>]
#Option "EXAVSync" # [<bool>]
#Option "ATOMTVOut" # [<bool>]
#Option "R4xxATOM" # [<bool>]
#Option "ForceLowPowerMode" # [<bool>]
#Option "DynamicPM" # [<bool>]
#Option "NewPLL" # [<bool>]
#Option "ZaphodHeads" # <str>
Identifier "Card0"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "RS482 [Radeon Xpress 200M]"
BusID "PCI:1:5:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
I know you maybe need more info, but i don't really know what do you need... please tell me what do you need and a post it!
Sorry for my english this isn't my native languaje... Thanks you for all
Last edited by geonunez (2010-07-08 20:19:09)

I have the same problem with my Acer Aspire 5100 (video ATI Xpress1100).
xorg.conf is not used. Turning KMS off doesn`t help.
I have tried to use uswsusp, but it doesn`t help. s2ram -n output correctly identify my laptop, which means it is in "whitelist" and correct settings for this hardware is known. s2ram suspend works, but screen blinking after waking up remains the same.
[Sydorenko@SLE ~]$ sudo s2ram -n
Machine matched entry 17:
sys_vendor = 'Acer *'
sys_product = 'Aspire 5100 *'
sys_version = ''
bios_version = ''
Fixes: 0x3 S3_BIOS S3_MODE
This machine can be identified by:
sys_vendor = "Acer "
sys_product = "Aspire 5100 "
sys_version = "V3.10A"
bios_version = "V3.10A"
See http://suspend.sf.net/s2ram-support.html for details.
Last edited by SydMax (2010-06-06 16:53:50)

Start up from 'suspend to ram' no longer starts wireless

When I finish with my desktop work I usually suspend to ram since it allows for quick startup. After a recent system upgrade, returning from suspend to ram no longer activates the wireless connection. NetworkManager is running in the processes list, but doesn't seem to do anything. I have to turn the computer off completely and then on again to get it to work.
Anyone else experiencing this?

I had the same issue, but on Chakra, did you try systemctl restart NetworkManager? I think that solves it without a complete reboot.

[Solved] Suspend to RAM no longer works

Suspend to RAM when closing my laptop lid worked out the box for me since I put Arch on my Dell XPS 14. After doing a pacman -Su yesterday (where I noticed that the kernel was updated, but it might be something else) it no longer works. Running 'systemctl suspend' in the terminal does work. Do I have to update a config?
Last edited by skip (2014-04-01 19:48:23)

For anyone else that finds this, systemd 212 doesn't suspend with lid closed with or without external monitor for those using the Nvidia proprietary drivers. Nvidia doesn't provide the necessary information for systemd to know whether or not an external monitor is connected, and thus it plays it safe and doesn't suspend. This is explained nicely at the Freedesktop bug linked above, but I wanted to pass it along here for those that won't follow the link.
Sounds like they're leaning toward reversing the preference (dock/external display users will need to opt out of suspending with lid close) in future versions since non-dock/monitor users >> dock/monitor users.

Suspend to ram doesen't work

Hi. I would like to ask for your advice. I have problem with suspend to ram. In order to have nvidia drivers i had to install newest kernel, 3.12.xx. I found that suspend to ram doesen't work. I put my computer in sleep mode by typing
sudo systemctl suspend
, everything works, computer goes in sleep mode but after resume from it, after wake up i have only black screen with unblinking cursor on the left upper corner of screen. I can't kill x, can't do anything in tty, only hard reset.
I removed nvidia drivers in order to check older kernel, and found that with nouveau drivers kernel 3.9 works, i can suspend and resume. I did another thing. I installed clean Arch, updated it with pacman -Syu, and installed nvidia drivers - the same problem with resuming from suspend. So on fresh and updated system i removed nvidia again, installed old kernel with nouveau - suspend works with resume.
Could somebody help me? Maybe you can point me to a solution? I would like to have nvidia drivers installed and working suspend with resume from suspend to ram.
I checked pm-suspend.log:
http://pastebin.archlinux.fr/478611
I don't see anything wrong here. I asked on polish site about kernel 3.12, and with Ubuntu they said it works. Why on Arch only kernel 3.9 works with resuming from suspend to ram and olny when there are no nvidia drivers (because they need new kernel, i could even use old but i'm not so exprienced to compile kernel myself, won't do that, and with downgrade script from AUR i didn't found nvidia driver for older kernels. There are old kernel, even 3.0.xx but only nvidia drivers from 325 that they need 3.12 kernel).
My spec is AMD X4 955, NVIDIA GTX260, 4GB ram. Arch is x32, kernel 3.12.5.1 (other don't work with resume too, only 3.9 with nouveau).
Last edited by firekage (2013-12-22 12:33:45)

I will try it, but i don't think that this "fix" will really help me - i installed newest driver, installed binary driver from nvidia website on kernel 3.9.8.1 and resuming from suspend to ram works. With newer kernel it just doesen't so if this would be a nvidia MSI problem than i would have it also on kernel 3.9.8.1 where i installed newest drivers ( i installed binary because i don't know which package from aur would work with this kernel, and on aur thare are only drivers from 325, no older).
Edit - just as i said. Doesen't work. It is not related to nvidia because it happens on nouveau. It is kernel fault.
Last edited by firekage (2013-12-25 02:25:34)

Suspend to Ram doesn't work

Hello,
I tried to get Suspend to Ram, but whatever way I use. Nothing worked.
First try was with
echo -n "mem" > /sys/power/state
I then got only a blinking cursor on a black screen for 20 seconds and then I see my console back with the error message
write error: Resource temporarily unavailable
Next thing the hibernate-scripts.
I changed hibernate.conf to
#TryMethod suspend2.conf
#TryMethod disk.conf
TryMethod ram.conf
After a run I have the same behaviour like in the first method.
cat /var/log/hibernate.log outputs
Starting suspend at Thu Mar 15 09:54:41 CET 2007
hibernate: [01] Executing CheckLastResume ...
hibernate: [01] Executing CheckRunlevel ...
hibernate: [01] Executing LockFileGet ...
hibernate: [01] Executing NewKernelFileCheck ...
hibernate: [10] Executing EnsureSysfsPowerStateCapable ...
hibernate: [11] Executing XHacksSuspendHook1 ...
hibernate: [59] Executing RemountXFSBootRO ...
hibernate: [89] Executing SaveKernelModprobe ...
hibernate: [91] Executing ModulesUnloadBlacklist ...
hibernate: [95] Executing XHacksSuspendHook2 ...
hibernate: [97] Executing VbetoolSaveState ...
'vbetool' utility not found. Vbetool disabled.
hibernate: [98] Executing CheckRunlevel ...
hibernate: [99] Executing DoSysfsPowerStateSuspend ...
hibernate: Activating sysfs power state mem ...
hibernate: [97] Executing VbetoolRestoreState ...
hibernate: [90] Executing ModulesLoad ...
hibernate: [89] Executing RestoreKernelModprobe ...
hibernate: [85] Executing XHacksResumeHook2 ...
hibernate: [70] Executing ClockRestore ...
hibernate: [59] Executing RemountXFSBootRW ...
hibernate: [11] Executing XHacksResumeHook1 ...
hibernate: [01] Executing NoteLastResume ...
hibernate: [01] Executing LockFilePut ...
Resumed at Thu Mar 15 09:55:04 CET 2007
Ok for the last attempt I installed powersave, run the powersaved daemon and typed "powersave -u" into my console.
My machine switched to text and I could read
Disabling non-boot CPUs
Stoppings Tasks
But then again I returned to my Desktop.
cat /var/log/suspend2ram.log
suspend2ram initiated: 2007-03-15 10:03:52 AM
Debug info follows here, please include in your bug reports. Thanks.
Loaded modules:
Module Size Used by
forcedeth 40200 0
ipv6 252480 10
it87 16784 0
hwmon_vid 3072 1 it87
eeprom 5904 0
i2c_isa 4096 1 it87
usbhid 34592 0
hid 25088 1 usbhid
snd_bt87x 12004 1
bt878 9208 0
ff_memless 5256 1 usbhid
rtc 10416 0
ppp_generic 23444 0
slhc 6272 1 ppp_generic
snd_mpu401 6376 0
snd_mpu401_uart 7040 1 snd_mpu401
shpchp 29588 0
ehci_hcd 30092 0
pci_hotplug 27976 1 shpchp
nvidia_agp 6556 1
agpgart 26200 1 nvidia_agp
pcspkr 2816 0
i2c_nforce2 5120 0
ohci_hcd 18948 0
tsdev 6336 0
evdev 8192 4
joydev 8384 0
sidewinder 11264 0
emu10k1_gp 3200 0
gameport 11784 3 sidewinder,emu10k1_gp
cx8800 29324 0
cx88xx 60452 1 cx8800
tuner 59816 0
tvaudio 21788 0
msp3400 28960 0
bttv 166004 2 bt878
video_buf 20356 3 cx8800,cx88xx,bttv
ir_common 26628 2 cx88xx,bttv
compat_ioctl32 1536 2 cx8800,bttv
i2c_algo_bit 7304 2 cx88xx,bttv
btcx_risc 4360 3 cx8800,cx88xx,bttv
tveeprom 13840 2 cx88xx,bttv
videodev 25216 3 cx8800,cx88xx,bttv
v4l2_common 22656 5 cx8800,tuner,msp3400,bttv,videodev
v4l1_compat 13956 2 cx8800,videodev
lirc_i2c 8964 2
i2c_core 17792 12 it87,eeprom,i2c_isa,i2c_nforce2,cx88xx,tuner,tvaudio,msp3400,bttv,i2c_algo_bit,tveeprom,lirc_i2c
lirc_dev 12532 1 lirc_i2c
capability 3592 0
commoncap 5632 1 capability
snd_seq_oss 29184 0
snd_seq_midi_event 6528 1 snd_seq_oss
snd_seq 46672 4 snd_seq_oss,snd_seq_midi_event
snd_pcm_oss 39072 0
snd_mixer_oss 14464 1 snd_pcm_oss
snd_intel8x0 28828 1
snd_emu10k1 112448 3
snd_rawmidi 19104 2 snd_mpu401_uart,snd_emu10k1
snd_ac97_codec 91940 2 snd_intel8x0,snd_emu10k1
ac97_bus 2432 1 snd_ac97_codec
snd_pcm 68484 6 snd_bt87x,snd_pcm_oss,snd_intel8x0,snd_emu10k1,snd_ac97_codec
snd_seq_device 6796 4 snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi
snd_timer 18820 3 snd_seq,snd_emu10k1,snd_pcm
snd_page_alloc 7816 4 snd_bt87x,snd_intel8x0,snd_emu10k1,snd_pcm
snd_util_mem 3840 1 snd_emu10k1
snd_hwdep 7044 1 snd_emu10k1
snd 43492 24 snd_bt87x,snd_mpu401,snd_mpu401_uart,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_seq_device,snd_timer,snd_hwdep
soundcore 6496 1 snd
usbcore 115464 4 usbhid,ehci_hcd,ohci_hcd
ext3 119688 3
jbd 55336 1 ext3
mbcache 7044 1 ext3
ide_cd 35744 0
cdrom 34464 1 ide_cd
ide_disk 13312 5
amd74xx 13852 0 [permanent]
generic 4740 0 [permanent]
ide_core 108616 4 ide_cd,ide_disk,amd74xx,generic
sata_nv 14980 0
libata 94100 1 sata_nv
Memory info:
total used free shared buffers cached
Mem: 775600 675048 100552 0 44228 313144
-/+ buffers/cache: 317676 457924
Swap: 1004020 0 1004020
/proc/cmdline: root=/dev/hdb8 acpi_sleep=s3_bios ro vga=773
========we are going to sleep, preparing.========
== checking runlevel ==
no shutdown/reboot in progress, good.
== Unmounting FAT/NTFS filesystems: ==
none found in /etc/mtab
== FAT/NTFS filesystems unmounted ==
Stopping services: ('netfs network cups alsa' configured)
stopping netfs:
## stty: standard input: Inappropriate ioctl for device
## :: Unmounting Network Filesystems 9G [BUSY] 9G [DONE]
stopping network:
## stty: standard input: Inappropriate ioctl for device
## stty: standard input: Inappropriate ioctl for device
## :: Stopping Network 9G [BUSY] 9G [DONE]
stopping cups:
## stty: standard input: Inappropriate ioctl for device
## :: Stopping CUPS Daemon 9G [BUSY] 9G [DONE]
ejecting PCMCIA cards...
Unloading modules: ('prism54 ' configured)
checking prism54
prepare_sleep finished for suspend2ram
/usr/sbin/s2ram not found, falling back to echo.
==== finished, return code 11 ====
========we are back from suspend, cleaning up.========
== restore_after_sleep: restart and reload everything ==
Resuming:
switched back to console: ' 7'
reactivating ACPI fan FAN
Reloading modules:
inserting PCMCIA cards...
Restarting services:
starting cups:
## stty: standard input: Inappropriate ioctl for device
## :: Starting CUPS Daemon 9G [BUSY] 9G [DONE]
starting network:
## stty: standard input: Inappropriate ioctl for device
## :: Starting Network 9G [BUSY] 9G [DONE]
starting netfs:
## stty: standard input: Inappropriate ioctl for device
## :: Mounting Network Filesystems 9G [BUSY] 9G [DONE]
Remounting filesystems:
not necessary.
======================================
restore_after_suspend_to_ram: finished
Btw after installing powersave I get an
Enabling non-boot CPUs
when "echo -n "mem > /sys/power/state".
And the hibernate-script crashed at the vbetool-line, leaving me with a black screen.
But I don't think thats the main problem, because my machine even don't goes to the S3-sleep.

dystoptic wrote:Shows mem and disk.
Do you use the proprietary ati driver or the xorg implementation?
Edit: Seems to be the free one, right? With my ati card i had a lot of struggle in connection with suspend to ram(with the free and the proprietary driver), i don't remember how i solved it, but finally it worked one time...
Last edited by buddabrod (2007-03-19 00:40:24)

Suspend to ram stopped working with Acer Aspire 5930G - Arch64

Suspend to ram recently stopped working on my laptop running Arch64. When ever I press the suspend to ram button in kde4 simply nothing happens, no screen flashing or error messages of any kind. I tried to install the pm-utils package and run pm-suspend, but with the same result. The program just ran and nothing happened and no feedback, not even in dmesg.
Here are the recent packages I've installed:
[2009-05-20 00:53] synchronizing package lists
[2009-05-20 00:53] starting full system upgrade
[2009-05-20 00:54] upgraded cpio (2.9-4 -> 2.9-5)
[2009-05-20 00:54] upgraded curl (7.19.4-1 -> 7.19.5-1)
[2009-05-20 00:54] upgraded gconf (2.26.1-2 -> 2.26.2-1)
[2009-05-20 00:54] upgraded glib2 (2.20.1-1 -> 2.20.2-1)
[2009-05-20 00:54] upgraded gmp (4.3.0-1 -> 4.3.1-2)
[2009-05-20 00:54] upgraded gsl (1.12-1 -> 1.12-2)
[2009-05-20 00:54] upgraded gstreamer0.10 (0.10.22-1 -> 0.10.23-1)
[2009-05-20 00:54] upgraded gstreamer0.10-base (0.10.22-1 -> 0.10.23-1)
[2009-05-20 00:54] upgraded irssi (0.8.12-5 -> 0.8.13-1)
[2009-05-20 00:54] upgraded libdrm (2.4.9-1 -> 2.4.11-1)
[2009-05-20 00:54] upgraded libsndfile (1.0.19-1 -> 1.0.20-1)
[2009-05-20 00:54] upgraded mesa (7.4.1-1 -> 7.4.2-1)
[2009-05-20 00:54] upgraded netcfg (2.1.3-3 -> 2.2.0b1-1)
[2009-05-20 00:54] upgraded poppler (0.10.6-1 -> 0.10.7-1)
[2009-05-20 00:54] upgraded poppler-glib (0.10.6-1 -> 0.10.7-1)
[2009-05-20 00:54] upgraded poppler-qt (0.10.6-1 -> 0.10.7-1)
[2009-05-20 00:54] upgraded ppp (2.4.4-7 -> 2.4.4-8)
[2009-05-20 00:54] upgraded psmisc (22.6-2.1 -> 22.7-1)
[2009-05-20 00:54] upgraded pycairo (1.8.2-1 -> 1.8.4-1)
[2009-05-20 00:54] upgraded subversion (1.6.2-1 -> 1.6.2-2)
[2009-05-21 12:57] installed festival (1.96beta-2)
[2009-05-21 13:01] installed festival-awb-arctic (1.0-1)
[2009-05-21 13:03] removed festival-awb-arctic (1.0-1)
[2009-05-21 13:03] removed festival (1.96beta-2)
[2009-05-21 13:48] installed libmikmod (3.1.12-2)
[2009-05-21 13:48] installed smpeg (0.4.4-5)
[2009-05-21 13:48] installed sdl_mixer (1.2.8-3)
[2009-05-21 13:48] installed ode (0.11-1)
[2009-05-21 13:48] installed sdl_ttf (2.0.9-1)
[2009-05-21 13:48] installed sdl_net (1.2.7-2)
[2009-05-21 13:48] installed xmoto (0.5.1-2)
Note, I tried to do a -Syu just now and got a new kernel, but it did not change anything.
EDIT: I'm also currently running the nvidia 180.60 driver.
Last edited by Avenger (2009-05-22 17:52:05)

search the forums: http://bbs.archlinux.org/viewtopic.php?pid=556030
in the future, i would definately use yaourt to upgrade since it displays better what is being updated and from where.
edit: if pm-suspend fails, check its log (/var/log/pm-suspend.log)
Last edited by eldragon (2009-05-22 18:16:08)

Suspend to RAM works but awakes immediately (pm-suspend)

Hello,
After after years of being unable to make suspend to RAM works on my lenovo Y530, I have finally found people who can do it. The trick is simply to add a new rule in /etc/pm/sleep.d/. I will edit the arch wiki page concerning the Y530 if I get it to work, but right now my problem is that the laptop immediately awakes after what seems to be a fully working suspend to RAM. Here is the log of pm-suspend :
Initial commandline parameters:
Wed Dec 29 19:24:32 CET 2010: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux inflames 2.6.36-ARCH #1 SMP PREEMPT Fri Dec 10 20:32:37 CET 2010 x86_64 Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz GenuineIntel GNU/Linux
Module Size Used by
iwlagn 304281 0
cryptd 6262 0
aes_x86_64 7412 2
aes_generic 26170 1 aes_x86_64
loop 15194 2
ipv6 281833 12
usbhid 36325 0
hid 76168 1 usbhid
uvcvideo 61404 0
videodev 64318 1 uvcvideo
v4l1_compat 15578 2 uvcvideo,videodev
v4l2_compat_ioctl32 10212 1 videodev
arc4 1378 2
ecb 2041 2
snd_hda_codec_nvhdmi 14827 1
snd_hda_codec_si3054 3822 1
snd_hda_codec_realtek 275887 1
joydev 10055 0
iwlcore 110506 1 iwlagn
mac80211 196159 2 iwlagn,iwlcore
snd_hda_intel 22285 2
snd_hda_codec 79384 4 snd_hda_codec_nvhdmi,snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 6110 1 snd_hda_codec
snd_pcm 71921 3 snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec
snd_timer 19265 1 snd_pcm
snd 57562 11 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 5969 1 snd
snd_page_alloc 7249 2 snd_hda_intel,snd_pcm
cfg80211 143110 3 iwlagn,iwlcore,mac80211
asus_laptop 14243 0
sparse_keymap 2563 1 asus_laptop
ideapad_acpi 3504 0
rfkill 15882 3 cfg80211,asus_laptop,ideapad_acpi
uhci_hcd 21926 0
sdhci_pci 6664 0
sdhci 16638 1 sdhci_pci
ehci_hcd 36988 0
psmouse 52592 0
mmc_core 59333 1 sdhci
led_class 2331 2 asus_laptop,sdhci
tg3 121889 0
video 19305 0
libphy 17083 1 tg3
output 1940 1 video
usbcore 137570 5 usbhid,uvcvideo,uhci_hcd,ehci_hcd
iTCO_wdt 10669 0
iTCO_vendor_support 1801 1 iTCO_wdt
firewire_ohci 26841 0
firewire_core 49430 1 firewire_ohci
crc_itu_t 1297 1 firewire_core
sg 25652 0
serio_raw 4486 0
pcspkr 1819 0
evdev 8519 14
ext2 63599 2
thermal 12242 0
fan 3274 0
button 4834 0
battery 10231 0
ac 3105 0
cpufreq_conservative 8676 0
cpufreq_userspace 2112 0
cpufreq_powersave 958 0
cpufreq_ondemand 8215 0
acpi_cpufreq 5865 1
freq_table 2323 2 cpufreq_ondemand,acpi_cpufreq
processor 25936 3 acpi_cpufreq
mperf 1243 1 acpi_cpufreq
vboxnetadp 4889 0
vboxnetflt 18948 0
vboxdrv 1760035 2 vboxnetadp,vboxnetflt
fuse 64259 3
nvidia 10081406 41
i2c_core 18726 2 videodev,nvidia
sr_mod 14954 0
cdrom 35851 1 sr_mod
ext4 313574 1
mbcache 5722 2 ext2,ext4
jbd2 69002 1 ext4
crc16 1297 1 ext4
sd_mod 25856 4
ahci 20353 3
libahci 17982 1 ahci
libata 156316 2 ahci,libahci
scsi_mod 124891 4 sg,sr_mod,sd_mod,libata
total used free shared buffers cached
Mem: 2986404 1515468 1470936 0 179156 646152
-/+ buffers/cache: 690160 2296244
Swap: 8755388 0 8755388
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
Running hook /etc/pm/sleep.d/20_custom-ehci_hcd suspend suspend:
0000:00:1a.70000:00:1d.7
/etc/pm/sleep.d/20_custom-ehci_hcd suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
nVidia binary video drive detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Wed Dec 29 19:24:33 CET 2010: performing suspend
Switching from vt7 to vt1
switching back to vt7
Wed Dec 29 19:24:40 CET 2010: Awake.
Wed Dec 29 19:24:40 CET 2010: Running hooks for resume
Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:
/usr/lib/pm-utils/sleep.d/95led resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:
/usr/lib/pm-utils/sleep.d/90clock resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend:
Reloaded unloaded modules.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: success.
Running hook /etc/pm/sleep.d/20_custom-ehci_hcd resume suspend:
0000:00:1a.70000:00:1d.7
/etc/pm/sleep.d/20_custom-ehci_hcd resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg resume suspend:
/usr/lib/pm-utils/sleep.d/11netcfg resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub resume suspend:
/usr/lib/pm-utils/sleep.d/01grub resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave resume suspend:
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00logging resume suspend:
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
Wed Dec 29 19:24:40 CET 2010: Finished.
As you can see, everything works fine, except the fact that the computer awakes 7 seconds after going to sleep... Of course I'm not touching it when it goes to sleep. I've also tried to disconnect everything I could (USB device and wifi).
Is there anyone who have already seen this kind of thing?

Just out of curiosity, are you wired in to a network? I've heard that data transfer over ethernet will trigger the wake-on-lan settings in the BIOS, which would wake it from sleep.

Suspend to ram in KDE vs. GNOME

Similar Messages

Maybe you are looking for