Systemd and suspend to disk

Hello,
I have the same problem as described in this bug:
[systemd] hibernation does not work: https://bugs.archlinux.org/task/37028
I followed the report to:
Dave Reisner (falconindy) wrote:
Therefore: If you want the resume hook to work with the systemd hook, you need to go write code. You have a few options:
1) Write a generalized solution for running the shell based hooks under systemd.
2) Write an sd-resume hook which replicates the functionality of the resume hook.
3) Write some other method of writing the resume device major:minor to /sys/power/resume which doesn't take place in early userspace. I'd bet that, for a lot of systems, you might even be able to get away with using tmpfiles.d for this.
Due to the lack of knowledge for 1) and 2), I went for 3):
cat /etc/tmpfiles.d/resume.conf
w /sys/power/resume - - - - 8:8
which also writes successfully the 8:8 in my /sys/power/resume .
However, it does not work.
If I want to resume from my suspend to disk I get "root not clean, recovering journal" etc. and I'm at a fresh session.
Any ideas?

I tried it and I can confirm that using tmpfiles.d doesn't work here either.
You're right that there's not so much to see in the previous boot. At the end of the log, when hibernating:
Mar 08 21:51:03 amd64box systemd[1]: Starting Sleep.
Mar 08 21:51:03 amd64box systemd[1]: Reached target Sleep.
Mar 08 21:51:03 amd64box systemd[1]: Starting Hibernate...
Mar 08 21:51:03 amd64box kernel: PM: Hibernation mode set to 'platform'
Mar 08 21:51:03 amd64box systemd-sleep[3523]: Suspending system...
I can see harddisk activity and I believe that the image is written correctly to the disk.
I think the problem is when resuming. Before the systemd initrd starts I can see the lines:
Mar 08 21:51:48 localhost kernel: PM: Checking hibernation image partition /dev/sda2
Mar 08 21:51:48 localhost kernel: PM: Hibernation image not present or could not be loaded.
Later in the boot:
Mar 08 21:52:00 amd64box swapon[205]: swapon: /dev/sda2: software suspend data detected. Rewriting the swap signature.
Mar 08 21:52:00 amd64box kernel: Adding 2104508k swap on /dev/sda2. Priority:-1 extents:1 across:2104508k FS
Mar 08 21:52:00 amd64box systemd[1]: Activated swap /dev/sda2.
Mar 08 21:52:00 amd64box systemd[1]: Starting Swap.
Mar 08 21:52:00 amd64box systemd[1]: Reached target Swap.
[*1]
And a bit later when the tmpfiles service is executed:
Mar 08 21:52:03 amd64box systemd[1]: Starting Create Volatile Files and Directories...
Mar 08 21:52:03 amd64box systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Mar 08 21:52:03 amd64box kernel: PM: Starting manual resume from disk
Mar 08 21:52:03 amd64box kernel: PM: Hibernation image partition 8:2 present
Mar 08 21:52:03 amd64box kernel: PM: Looking for hibernation image.
Mar 08 21:52:03 amd64box kernel: PM: Image not found (code -22)
Mar 08 21:52:03 amd64box kernel: PM: Hibernation image not present or could not be loaded.
Mar 08 21:52:03 amd64box systemd[1]: Started Create Volatile Files and Directories.
Despite that it's not working I believe it's a bit late to resume when using the regular tmpfiles.d (rootfs got already checked and corruption detected, the above swap message about rewriting it's signature, which I'm not sure what it means etc.).
Therefor I tried to enforce the execution of the systemd-tmpfiles-setup service in the early systemd initrd (which it didn't do before), by a custom hook.
Unfortunately the result is very similar to above:
Mar 08 21:49:12 localhost systemd[1]: systemd 210 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
Mar 08 21:49:12 localhost systemd[1]: Detected architecture 'x86-64'.
Mar 08 21:49:12 localhost systemd[1]: Running in initial RAM disk.
Mar 08 21:49:12 localhost systemd[1]: No hostname configured.
Mar 08 21:49:12 localhost systemd[1]: Set hostname to <localhost>.
Mar 08 21:49:12 localhost systemd[1]: Initializing machine ID from random generator.
Mar 08 21:49:12 localhost systemd[1]: Expecting device dev-disk-by\x2duuid-feb08c40\x2d0056\x2d4532\x2dbe2f\x2d33eaa5f20a24.device...
Mar 08 21:49:12 localhost systemd[1]: Starting Paths.
Mar 08 21:49:12 localhost systemd[1]: Reached target Paths.
Mar 08 21:49:12 localhost systemd[1]: Starting Timers.
Mar 08 21:49:12 localhost systemd[1]: Reached target Timers.
Mar 08 21:49:12 localhost systemd[1]: Starting -.slice.
Mar 08 21:49:12 localhost systemd[1]: Created slice -.slice.
Mar 08 21:49:12 localhost systemd[1]: Starting udev Control Socket.
Mar 08 21:49:12 localhost systemd[1]: Listening on udev Control Socket.
Mar 08 21:49:12 localhost systemd[1]: Starting udev Kernel Socket.
Mar 08 21:49:12 localhost systemd[1]: Listening on udev Kernel Socket.
Mar 08 21:49:12 localhost systemd[1]: Starting Journal Socket.
Mar 08 21:49:12 localhost systemd[1]: Listening on Journal Socket.
Mar 08 21:49:12 localhost systemd[1]: Starting Sockets.
Mar 08 21:49:12 localhost systemd[1]: Reached target Sockets.
Mar 08 21:49:12 localhost systemd[1]: Starting system.slice.
Mar 08 21:49:12 localhost systemd[1]: Created slice system.slice.
Mar 08 21:49:12 localhost systemd[1]: Starting Slices.
Mar 08 21:49:12 localhost systemd[1]: Reached target Slices.
Mar 08 21:49:12 localhost systemd[1]: Starting system-systemd\x2dfsck.slice.
Mar 08 21:49:12 localhost systemd[1]: Created slice system-systemd\x2dfsck.slice.
Mar 08 21:49:12 localhost systemd[1]: Starting udev Coldplug all Devices...
Mar 08 21:49:12 localhost systemd[1]: Starting Journal Service...
Mar 08 21:49:12 localhost systemd[1]: Started Journal Service.
Mar 08 21:49:12 localhost kernel: PM: Starting manual resume from disk
Mar 08 21:49:12 localhost kernel: PM: Hibernation image partition 8:2 present
Mar 08 21:49:12 localhost kernel: PM: Looking for hibernation image.
Mar 08 21:49:12 localhost kernel: SCSI subsystem initialized
Mar 08 21:49:12 localhost kernel: PM: Image not found (code -6)
Mar 08 21:49:12 localhost kernel: PM: Hibernation image not present or could not be loaded.
Mar 08 21:49:12 localhost systemd-udevd[63]: starting version 210
Mar 08 21:49:12 localhost systemd-journal[52]: Journal started
Mar 08 21:49:12 localhost systemd[1]: Starting Create list of required static device nodes for the current kernel...
Mar 08 21:49:12 localhost systemd[1]: Starting Swap.
Mar 08 21:49:12 localhost systemd[1]: Reached target Swap.
Mar 08 21:49:12 localhost systemd[1]: Starting Local File Systems.
Mar 08 21:49:12 localhost systemd[1]: Reached target Local File Systems.
Mar 08 21:49:12 localhost systemd[1]: Starting Create Volatile Files and Directories...
Mar 08 21:49:12 localhost systemd[1]: Started Create list of required static device nodes for the current kernel.
Mar 08 21:49:12 localhost systemd[1]: Starting Create static device nodes in /dev...
Mar 08 21:49:12 localhost systemd[1]: Started Create static device nodes in /dev.
Mar 08 21:49:12 localhost systemd[1]: Started Create Volatile Files and Directories.
Mar 08 21:49:12 localhost systemd[1]: Starting udev Kernel Device Manager...
Mar 08 21:49:12 localhost systemd[1]: Started udev Kernel Device Manager.
Mar 08 21:49:12 localhost systemd[1]: Started udev Coldplug all Devices.
Mar 08 21:49:12 localhost systemd[1]: Starting System Initialization.
Mar 08 21:49:12 localhost systemd[1]: Reached target System Initialization.
Mar 08 21:49:12 localhost systemd[1]: Starting Basic System.
Mar 08 21:49:12 localhost systemd[1]: Reached target Basic System.
The error code is -6 instead of -22 now...
Weird enough that the kernel: PM: messages appear above the "Starting Create Volatile Files and Directories..." which is the execution of systemd-tmpfiles-setup...
So currently I've reached a bit of a dead end on this. Maybe someone else can give an input...
[*1]: When looking at this I note that it's a bit contradictory. The kernel says it cannot find an image but swapon says it's there...
Edit: Some useful information, but also somewhat mad: http://www.freedesktop.org/software/sys … ootup.html (man bootup)
Last edited by rebootl (2014-03-09 13:52:08)

Similar Messages

Switched to systemd and now idle disk activity?

Just switched over to systemd and now I'm seeing diskactivity like what I see with windows (or used to with 2k/xp). Every now there's disk activity in the system. I logged out to console and it still happens. I don't see any log files growing. So what happened ? it's almost like a heart beat followed later by a single then another.

This is a very poor way to ask a question. You provide no details whatsoever that might be able to help you find an answer. But assuming that your problem is simply an i/o issue, I like to use iotop to see what kinds of crap is being written to (or read from) disk.

[solved] Suspend to RAM and later to disk

Hello,
I am a new laptop owner (and new Archlinux user).
On its original operating system, my laptop has a feature which basically does:
1- suspend to RAM
2- after 1 hour in this suspend mode, it wakes up briefly and suspend to disk
I found many wiki pages about suspending either to disk or to RAM or even both, like https://wiki.archlinux.org/index.php/Su … _Hibernate and that works fine with my laptop.
But none gave me a solution with this kind of behavior.
Note that this is different from "hybrid-sleep" which suspend to RAM and disk at the same time and use disk save in case the battery if emptied.
I see many benefits from what I look for:
- very fast suspend (on lid close for instance);
- if I re-open the lid within the hour, very quick restore;
- if I let the laptop as it is, I know it will automatically suspend to disk and thus I do not worry about battery usage;
- compared to hybrid-sleep, if I forget my laptop in sleep mode, the battery state will be about the same as when I stopped working, whereas hybrid-sleep needs a recharge.
So, do you know if it is possible to suspend to RAM and later to disk on Archlinux?
Any pointers on how to do so?
Thanks!
Last edited by cjlano (2013-04-08 20:53:38)

Hello,
Here is my solution for a Archlinux / systemd "suspend sedation" based on http://askubuntu.com/questions/12383/ho … -hibernate
The following script is a Systemd sleep hook. It uses a RTC wake up event (rtcwake) to get out of suspend state and go to hibernate state. If the system leaves suspend state before the RTC event, the RTC wake is cancelled.
Save the following code in /usr/lib/systemd/system-sleep/suspend-sedation.sh, and make it executable.
#!/bin/bash
# Purpose: Auto hibernates after a period of sleep
# Edit the "autohibernate" variable below to set the number of seconds to sleep.
lockfile=/var/run/systemd/rtchibernate.lock
curtime=$(date +%s)
# 30 min
autohibernate=1800
case $1/$2 in
pre/suspend)
# Suspending. Record current time, and set a wake up timer.
echo "Suspending until" `date -d "$autohibernate seconds"`
echo "$curtime" > $lockfile
rtcwake -m no -s $autohibernate
post/suspend)
# Coming out of sleep
sustime=$(cat $lockfile)
echo -n "Back from suspend... "
rm $lockfile
# Did we wake up due to the rtc timer above?
if [ $(($curtime - $sustime)) -ge $autohibernate ]
then
# Then hibernate
echo "hibernate"
/usr/bin/systemctl hibernate
else
echo "wake-up"
# Otherwise cancel the rtc timer and wake up normally.
rtcwake -m disable
fi
esac
This script outputs some log you can view using
journalctl -b -u systemd-suspend
Any improvements welcome!

Hmph. (Jumpy) Touchpad issues and Suspend idiosyncrasies.

(I'll try not to turn this into a novel, but I guess when I have a problem it just happens that I naturally try to describe everything that goes on for full disclosure. Bear with me.)
I just got a hold of an older laptop, a Dell Latitude C640, and to my dismay setting up Linux on it hasn't been the walk in the park I'd hoped it'd be. I read a bunch of articles about Linux on this machine before I got it and most seemed to have a pretty easy time of everything. Of course this might be because the laptop is quite a few years old and older Linux kernels acted different ways, but I guess I assumed that things would be even easier using a modern distro.
The Touchpad
It worked fine on the install of Windows XP that came installed on it, with no problems at all. Before installing any flavor of Linux I ran Knoppix on it just kind of to make sure things would go OK. It was a little dated, being Knoppix 5.10, but I figured it'd do for my purposes.
The first time I booted it seemed to work OK, with the mouse cursor behaving mostly as it should, with a little lag. I've used this same Knoppix disk on another laptop and it did much the same thing. After another boot, however, I saw that things weren't going to be so easy. The cursor immediately drifted off into one of the screen's corners (it didn't seem to care much which one it was in, as long as it was in one) and would refuse to come out. I could move the cursor a little ways off of the edge of the screen, but not far enough to click anything, and it would immediately go back as soon as I released my finger. So I tried a few other disks. First I tried a CD I have for Crunchbang Linux (just a minimalist, Openbox-based Ubuntu flavor), and then Knoppix 4. Both gave very similar results. Crunchbang let me have a little bit more control over the cursor for a little while after booting, maybe for about a minute, and then the same behavior cropped up. I only booted with Knoppix 4 once, but it was pretty much the same deal.
I started reading up on what might be going on and came across a thread on the Linux Mint forums that seemed to be describing an issue very close to mine (though mine is completely unrelated to the AC adapter and persists whether it's plugged in or not). Someone in the thread suggested it was a kernel issue, since it's definitely not a hardware issue, so I then booted into a copy of DSL I had lying around, which uses the 2.4 kernel. Sure enough everything worked without problems. This caused me to believe, going by some of the conclusions from the Lnux Mint thread and apparently mistakenly, that the issue may have been with the 2.6 Debian kernels, so I figured I'd just get Arch installed and see how things went.
After getting X set up and working properly I saw that the issue was going to be much the same. To get around the cursor being dragged into the corner against my will I found out that if I ran without HAL or that if I disabled hot-plugging I could use the touchpad, although not flawlessly. Here's xorg.conf:
Section "ServerLayout"
Identifier "Xorg"
Screen 0 "Default" 0 0
InputDevice "Touchpad" "CorePointer"
# InputDevice "USB Mouse" "SendCoreEvents"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
Option "AutoAddDevices" "false"
EndSection
Section "Module"
Load "glx"
Load "dri"
Load "drm"
Load "synaptics"
EndSection
Section "InputDevice"
Identifier "Touchpad"
Driver "synaptics"
Option "SHMConfig" "true"
Option "AlwaysCore" "true"
Option "MinSpeed" "0.05"
Option "MaxSpeed" "0.40"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "FastTaps" "1"
Option "VertEdgeScroll" "true"
Option "HorizEdgeScroll" "true"
Option "Emulate3Buttons" "true"
EndSection
#Section "InputDevice"
# Identifier "USB Mouse"
# Driver "evdev"
# Option "SendCoreEvents" "true"
#EndSection
Section "Monitor"
Identifier "LCD"
EndSection
Section "Device"
Identifier "Radeon Mobility 7500"
Driver "radeon"
EndSection
Section "Screen"
Identifier "Default"
Device "Radeon Mobility 7500"
Monitor "LCD"
DefaultColorDepth 24
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Group "video"
Mode 0666
EndSection
The "AutoAddDevice" option is the only thing that seems to make any difference in usability at all; without it I can't use the touchpad at all, and with it I can, but to varying degrees. I've found that right after I boot up everything seems to work exactly how it's supposed to, but shortly after, sometimes 15 seconds, sometimes many minutes, things seem to get kind of unresponsive. The cursor will go where I want it to go, but it jumps around and does it very slowly. The mouse buttons also get very unresponsive. Right click is especially bad, and I often have to hold down the button just to get it to do what I want, but left click is very bad too, requiring me to push the button down for almost a full second, sometimes several times. Taps on the pad, after things go wrong, also stop being recognized, forcing me to use the buttons (which I'm OK with). It's usable, but the behavior is not ideal whatsoever—it's rather annoying.
The most aggravating thing, I think, is that I can't seem to find anyone else using this same model that has this issue. The latest I've seen is from January: An Ubuntu (8.10) user reports no issues and is very pleased (see comments at the bottom of the page).
Suspend (both to disk and RAM)
I actually did install the latest Crunchbang (9.04.01, the 32-bit "Lite" edition) first to see if anything would clear up by installing it rather than running the live CD, but I only had it installed for a few hours. I didn't really get into messing with xorg.conf that much yet, only really touching "FingerLow" and "FingerHigh" settings, so the touchpad issue was still nagging me. I did play around a bit though and found out that suspend to RAM and suspend to disk worked pretty much from the go, only requiring that I installed uswsusp. Issuing a simple "sudo pm-suspend" or "sudo pm-hiberate" put the computer to sleep and it woke back up without any issue at all.
But suspend on Arch is proving to be a pain in the neck. Suspend to RAM simply will not work; the computer shuts down but will not resume, leaving me only a blank screen with an unresponsive keyboard. Suspend to disk works (using hibernate-script as pm-hibernate doesn't seem to do anything at all), but it works very poorly; both suspending and resuming take a very, very long time—so long, in fact, that I'm just better off shutting down and restarting normally, since the boot time is better. I don't know what accounts for the drastic difference in distros, and this isn't the first experience I've had with suspension working on Ubuntu but not on Arch. What is different in the Ubuntu implementation of pm-utils than the Arch way? Is it the Ubuntu kernel? Is there any way to implement the Ubuntu way with Arch (because, after all, I'd prefer to use Arch)?
I'm considering installing Crunchbang once again if I can't get things to work the way I want them to in the next few days on Arch. And, if I can't make the touchpad work in a satisfactory manner on Cruchbang, I might just have to reinstall Windows. I don't want to do that.

At least for the moment I've given up and reinstalled Windows XP, but I'm still kind of looking for solutions. Suspend and hibernate are things I find to be somewhat important, but secondary to the touchpad issues, so I'm focusing on those.
Out of curiosity today I test out pretty much every live CD I have in the house. I found an old Ubuntu CD for 6.06 (Dapper) and had a little bit of luck with it. By default pretty much every live CD configures Xorg to use an additional mouse that isn't present; to fix this I edited the "ServerLayout" section xorg.conf to only use the touchpad. With this old Ubuntu CD, this achieved the desired result (mostly). The touchpad worked how it ought to with no lag, but a few features were not implemented.
Ubuntu 6.06 used the 0.4.3 version of the synaptics driver; newer Linux distros usually use 0.99 and above. I tried my Knoppix 5.1 CD again, editing xorg.conf again to reflect the absence of an external mouse, but I did not get the behavior I was hoping for. When I checked I found out that Knoppix 5.1 came with the 0.14.6 version of the synaptics driver.
Turns out that 0.14.5 was something of a turning point for the driver.
Makefile support for Xorg 7.0 has been added.
Two-finger scrolling and pressure dependent motion
speed have been implemented. A new parameter has
been added to give greater control over tap
behavior.
(http://freshmeat.net/projects/synaptics/releases/228794)
I suspect that the problem is coming from the addition of the "pressure dependent motion speed." I don't know what options control this to toy with them.
However, I'm not so sure. This sounds like it would be something that would toy with my mind, making me think I'm experiencing "mouse lag" when certain options are really just conflicting, but as I had to point out again on another forum on which I posted this same thread, when using Arch (and the most recent synaptics driver) things started out fine and only after a little while, sometimes less than a minute, sometimes many, would things start to act up. Either some progress is being made to resolve this problem with the latest releases, or something is going wrong internally that I do not understand. I just cannot understand why, with the newest drivers, it's only after some use that the problem kicks in while when using all others the problems are immediate.

[Solved] Suspend to Disk: systemd-hibernate.service Fails

Howdy-ha, folks. I know this looks pretty mundane, but for the life of me I can't get hibernation to work. Each time I run systemctl hibernate the screen will go blank as though preparing to suspend, then come back on; journalctl shows the same error messages:
PM: Cannot find swap device, try swapon -a.
PM: Cannot get swap writer
Failed to start Hibernate.
Dependency failed for Hibernate.
Service sleep.target is not needed anymore. Stopping.
Unit systemd-hibernate.service entered failed state.
This happens when swap is mounted, and "swapon" says as much. I've been working on this for about four hours now, and none of what I've found seems to pertain to my situation (most of the "solutions" were "Increase partition size').
What I've tried:
- Three different kernels---linux-ck custom build and linux-ck-sandybridge from graysky's repo (both with BFQ and CFQ: see below), as well as the stock Arch kernel
- A 2 Gb swap file at /swapfile on my SSD;
- A 4 Gb swap partition on /dev/mmcblk0 (an SD card, and my preferred method/location, if possible);
- An 8 Gb swap partition on HDD /dev/sdb2
Reasons for wanting hibernate rather than suspend-to-RAM:
- Maximize battery life.
- There's some kind of issue with Linux-ck and suspending to RAM; it'll work once, then freeze in a kernel panic the second time, forcing a hard reset. The stock kernel suspends to RAM, but still won't hibernate
- I put a lot of time into building a custom Linux-ck kernel, and would rather not have to start the configuration over with the stock kernel if possible.
I'm working with limited space on my boot drive and, as mentioned, increasing the amount of swap has no bearing on this. The resulting phenomenon and error messages are the same, regardless of size and medium. I've exhausted my ideas on where to look, and what to even look for. Thanks a lot to everyone in advance (especially you,karol; don't think I don't see you lurking back there )
Last edited by ANOKNUSA (2013-11-17 05:32:14)

I rebooted, so trying to recreate the same situation:
$ free -h
total used free shared buffers cached
Mem: 7.7G 7.2G 525M 0B 32M 2.3G
-/+ buffers/cache: 4.8G 2.9G
Swap: 3.7G 0B 3.7G
top reports nearly the same thing:
top - 20:00:13 up 22 min, 1 user, load average: 0.12, 0.22, 0.14
Tasks: 155 total, 1 running, 154 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.1 us, 0.3 sy, 0.1 ni, 99.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 8061380 total, 7500096 used, 561284 free, 34432 buffers
KiB Swap: 3872236 total, 0 used, 3872236 free, 2417172 cached
htop, however, reports about 1.5 Gb more free RAM. After reboot, swappiness is still set to 100 with the same results.
EDIT:
ANOKNUSA wrote: I'll test it again with the other locations mentioned in the OP, and get back to you.
Even though I rebooted, I haven't done this yet, so ignore it for the moment.
Last edited by ANOKNUSA (2013-08-28 01:06:10)

[solved] Unloading modules before suspend to disk

Hi, I'm trying to get my Asus U36jc to suspend to disk and resume. Suspending seems to go fine, but after resuming I get an unresponsive notebook (no response on key presses or ping) showing a black screen. Then immediately the fan gets louder and the notebook gets warmer.
Just before the machine goes to sleep, I see this in my screen:
xhci_hcd 0000:04:00.0: PCI post-resume error -110!
xhci_hcd 0000:04:00.0: HC died; cleaning up
xhci_hcd 0000:04:00.0: HC died; cleaning up
dpm_run_callback(): pci_pm_resume+0x0/0xb0 returns -110
PM: Device 0000:04:00.0 failed to resume async: error -110
hda-codec: out of range cmd 0:20:400:fffff7ff
I found this guide (https://www.kernel.org/doc/Documentatio … ugging.txt) and using that I determined that when I first remove modules ehci_pci, ehci_hcd and xhci_hcd, suspend to disk and resume seem to work fine.
I found out here (https://wiki.archlinux.org/index.php/Pm … end_to_RAM) how to unload modules prior to suspending to RAM, but that doesn't seem to work for suspend to disk, and I can't find how to unload modules prior to that. Can someone tell me how to do that?
Thanks for any help!
Last edited by diederick76 (2013-09-25 20:27:36)

I'm not sure if pm-utils is deprecated, it doesn't say so here (https://wiki.archlinux.org/index.php/Pm-utils). In any case its a dependency of upower, which is a dependency of kdelibs, so as long as I want to use KDE my harddrive is stuck with it.
However, I decided to try your suggestion to use systemd:
# asus36JC.service
[Unit]
Description=Script upon suspend/resume
Before=sleep.target
StopWhenUnneeded=no
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/home/diederick/bin/no_modules
ExecStop=/home/diederick/bin/modules
[Install]
WantedBy=sleep.target
It seemed to work perfectly for a couple of times in a row (modules were there before and afterwards) until I restarted the notebook, when the problem was back. But then I remembered to enable the service and now it works. Thanks a lot!

[SOLVED]systemd and make a camera visible GUI-wise in your filemanager

After reading a lot about systemd in the wiki and in this forum I understand there are different opionons about systemd. Anyway, I have a adapted all the changes to rc.conf leaving out only a few daemons to start there. So why not give systemd a try? If you dont want to read the full posting I finally got it to work, basically by reading carefully and checking the suggested tests in the systemd wiki. (loginctl)
As suggested by the wiki, I tried the systemd yesterday. Enabled via systemctl some services to "replace" my rc.conf daemons. I got what I thought everything to work, including autologin directly to my Xfce4 desktop. Everything except the digital camera.
When starting Arch traditionally via initscripts I immediately can see the camera in the filemanager (Nautilus) when the camera is attached via USB.
Some minutes later, after adding "init=/usr/lib/systemd/systemd" to the APPEND line in Syslinux and rebooting, my machine reboots
fine.But when connecting the camera again it is not visible graphically.
The camera is there because when using gphoto2 (the commandline) as root I can transfer pictures etc.
Even if I am no happy CLI user I can handle it when necessary. Handling pictures a graphical view of them is much easier...
As the wiki about systemd says one can try it out. I have not removed anything from the system and when starting Arch again, the initscript way, I can see the camera again in my filemanager, gthumb works again and pictures can be transferred to my machine.
In the wiki again, this time about digital cameras
Permission issues
Camera devices should be granted permission using ACLs. For this to work, users need to have consolekit or systemd running and the user session must be registered with them accordingly.
Check this using /usr/bin/ck-list-sessions to verify a value of "TRUE" should be returned for both the "active" and "is-local" fields:
$ ck-list-sessions | grep TRUE
active = TRUE
is-local = TRUE
ACL=Atlantic Container Line is what first comes into my mind. I have had some connections to transport business...I admit I had to google it to find the correct interpretation of this mumbo-jumbo.
The wiki also gives a "hint", if this is not working try to use the obsolete camera group and edit some udev rules.
Should not be necessary when it has worked before systemd and earlier experiences
But what is this about "Permission issues"? Here is my listings relative the wiki hints. All seems OK.. or why the heck are there two sessions??
[leif@krasaki ~]$ ck-list-sessions | grep TRUE
is-local = TRUE
active = TRUE
is-local = TRUE
[leif@krasaki ~]$ ck-list-sessions
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ''
x11-display-device = ''
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2012-10-24T07:12:56.499847Z'
login-session-id = '1'
idle-since-hint = '2012-10-24T07:13:26.994037Z'
Session2:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2012-10-24T07:13:02.361157Z'
login-session-id = '1'
[leif@krasaki ~]$
As one can see, the ACTIVE values are here as the wiki says. But no camera. Those values are the same, wheter which way the machine is started. But 2 sessions??
Further reading in the systemd wiki article and consolekit vs systemd.logind gives a clue.
From the wiki:
In order to check the status of your user session, you can use loginctl. To see if your user session is properly set up, check if the following command contains Active=yes. All polkit actions like suspending the system or mounting external drives with Udisks should then work automatically.
So when started via systemd and running logintctl, it gives this surprising result. Does not matter wheter as normal user, nor as root....
[leif@krasaki ~]$ loginctl
SESSION UID USER SEAT
1 1000 leif seat0
1 sessions listed.
[leif@krasaki ~]$ loginctl show-session 1
Id=1
Timestamp=Wed, 24 Oct 2012 10:57:03 +0200
TimestampMonotonic=20040019
DefaultControlGroup=name=systemd:/user/leif/1
VTNr=1
TTY=tty1
Remote=no
Service=login
Leader=315
Audit=1
Type=tty
Class=user
Active=no
State=online
KillProcesses=no
IdleHint=yes
IdleSinceHint=1351069009642296
IdleSinceHintMonotonic=6664433
Name=leif
[leif@krasaki ~]$
Surprising? Should it not have been Active=Yes? So something is wrong in my settings although it had worked "before" starting using systemd..
OK, so far. Lost? Not yet. Double check again everything and I found the culprit, my ~/.bash_profile which had worked before seemed a bit different to what is suggested in the wiki. The old one, actually started 2 sessions, as also could be seen here above checking ck-list-sessions. That was the problem
Using a fresh edited ~/.bash_profile as suggested here, the camera is visible graphically
Finally, just for fun, start again the old initscipt way. Enabling daemon and so on. Still 2 sessions going on....Here it was the "/.xinitrc, which also had some old fashions and I removed the ck-launch-session from the exec line. So even here, now only 1 session..
Anyway, now the camera is visible, both starting with initscripts, naturally also some daemons active in rc.conf and by starting with systemd.
I rest my case and it seems systemd works with everything on my machine which is just a normal desktop used by an old man.
Thanks for reading...

Solved now! Boot times are as fast as posssible on my HDD I think. Only thing after uninstalling initscripst and initscripts-systemd was that locale was not set inspite of a correct /etc/locale.conf. I had to make /etc/profile.d/locale.sh with this content;
if [ -s /etc/locale.conf ]; then
. /etc/locale.conf
fi
export LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE
export LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS
export LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION

Computer reboot instead of resume after suspend to disk

Hi,
I install minimal KDE on my laptop. Everything work fine but suspend.
- When I suspend to disk, initially it seem to work well. when I press power button, system act a new boot, not resume the session before.
- When I suspend to ram, everything work well: it really suspend, lock screen and reactive when press Enter, application work normally but I cannot re-connect to network. I use wicd as network manager, it always show popup: "Unable get IP from ..."
Here is output of lspci:
[duclong@king-of-dragon ~]$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
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: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)
02:00.0 Ethernet controller: Atheros Communications AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)
03:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
and here is rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Asia/Ho_Chi_Minh"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(atl1e pcspkr snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-codec snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="king-of-dragon"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(!eth0 !eth1)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(@syslog-ng dbus !hal laptop-mode !network @wicd @alsa !netfs crond kdm fam samba)

please do not create multiple threads in different sub forums for similar issues.
Please read our forum rules and follow them.
Closing....

Suspend to disk

Hi
Can i ge my mbp to suspend to disk instead do ram immediatly after closing the lid, or via a command?
Thanx for any help
Selon

There are two solutions:
1. Remove A/C power, then remove the battery for about 10 seconds. The computer will automatically go into Safe Sleep mode.
2. Open your Terminal app (Utilities folder) and at the prompt enter the following command line followed by a return:
prompt> sudo pmset -a hibernatemode 1
You will be prompted for your password which will not be echoed. Quit the Terminal app.
From now on your computer will automatically go into Safe Sleep (hibernate) mode when you close the lid. To return to the normal sleep mode open the Terminal app and enter the above command line but change the "1" to a "3".

Systemd and bootchart

Greetings,
I'm using systemd as default init system and before I'm buying a solid state disk, I want to know some information about the boot time with my hdd, so I installed bootchart from the AUR. The wiki says, I should add init=/bin/bootchartd to the kernel line of the menu.lst grub file. But because I'm already using systemd, the kernel line has already init=/bin/systemd at its end. Is it possible to use both systemd and bootchart? I know there's also another way (putting it into /etc/rc.sysinit), but I would like to prevent that, because the wiki disadvises to do it.
Regards,
Nils

If you look through the systemd thread here, there are instructions. Basically, install bootchart2 and enable its service, if I remember correctly.

Systemd and nm_dispatcher (on remote shares)

Hi,
On my laptop I'm using systemd and networkmanager, like many of you I suppose.
I have an NFS-server setup at home and one at work, so I would prefer to only connect to the NFS-server within my reach and not send out credentials into the wild when the other NFS-server is not around. I thought that nm_dispatcher is the perfect solution and I wrote a script that accomplishes this with the sysV initscripts.
Now I'm using systemd and my laptop won't shutdown anymore: it hangs at unmounting my disks.
I guess the nm_dispatcher-script to unmount the NFS-exports is never run, and so the NFS-exports are never unmounted.
Questions:
1. Is this the expected behaviour or is this a bug somewhere?
2. Can systemd do this natively? I know it is able to mount remote shares, but can you also specify that the mount should only be tried if connected to a specific SSID?
THX!
Last edited by zenlord (2012-08-23 11:31:34)

Sharepoints is not needed in your case, it's for controlling what "other" Isers can access.
Logging into the Remote one with the Remote one's User &PW gives you the samr rights as being there and logging onto it!

Systemd and Webcam and Suspension on Lid Closing

Yesterday I finally switched to systemd and two problems came along.
The first one is that my computer now suspends when I close the lid. The screen goes dark and I have to hit buttons, this didn't happen before. Oh, now that I write this post I remember that there was an xscreensaver update, and maybe it could be related.
The second one is that the webcam light now turns on randomly at times. I might be going paranoid, but I just don't like it, I feel like I'm being spied on. I am sure no Kernel update caused this too. How can I blacklist/rmmod my webcam driver/module? I don't know how to find it, and because I'm on a laptop I can't remove it. I could tape it, but I'm looking for a cleaner solution.
Any ideas? Thank you in advance.
After some testing, I discovered that the webcam light is turned on ONLY when I get back from a "suspension". So, the issues are related.
Last edited by ephan (2012-10-21 09:31:30)

derhamster wrote:
For the first one: Its probably not related to xscreensaver. Check
/etc/systemd/logind.conf
and
man 5 logind.conf
That worked, thanks a lot!
However, I can't start "xinit" on tty1 now. It says (davidarch is my hostname):
davidarch login: [OK] Started Network Manager.
Starting WPA Supplicant
[OK] Started WPA Supplicant
And then it just sits there and I have to start X on tty2.
Any ideas on how to fix this? Thanks.

Systemd and plymouth

Hi.
I just installed pure systemd and is working ok... I'm using plymouth with that and... plymouth is working ok when booting but plymouth is not working when rebooting or shutingdown PC, why ?
I'm using nvidia drivers with v86d to get plymouth to work and I have added it to mkinitcpio.conf and rebuilded mkinitcpio. I have enabled gdm-plymouth.service to start gdm automatic...
any ideas why plymouth not working when rebooting ?
thanks,

I'm starting plymouth with mkinitcpio.cong [root@ASUS siamer]# systemctl enable plymouth-s The unit files have no [Install] section. [root@ASUS siamer]# journalctl | grep Sep 09 22:06:45 ASUS systemd[1]: plymouth-start.service: Sep 09 22:06:45 ASUS systemd[1]: Unit Sep 09 22:07:07 ASUS systemd[1]: plymouth-quit-wait.service Sep 09 22:07:07 ASUS systemd[1]: Unit only gdm I'm starting with systemd by [root@ASUS siamer]# systemctl --fail
UNIT LOAD ACTIVE SUB proc-sys...misc.automount loaded active waiting sys-devi...d-card0.device loaded active plugged sys-devi...da-sda1.device loaded active plugged sys-devi...da-sda2.device loaded active plugged sys-devi...da-sda3.device loaded active plugged sys-devi...da-sda4.device loaded active plugged sys-devi...da-sda5.device loaded active plugged sys-devi...ock-sda.device loaded active plugged sys-devi...ock-sr0.device loaded active plugged sys-devi...et-eth0.device loaded active plugged sys-devi...t-wlan0.device loaded active plugged sys-devi...y-ttyS0.device loaded active plugged sys-devi...y-ttyS1.device loaded active plugged sys-devi...y-ttyS2.device loaded active plugged sys-devi...y-ttyS3.device loaded active plugged sys-module-fuse.device loaded active plugged -.mount loaded active mounted dev-hugepages.mount loaded active mounted dev-mqueue.mount loaded active mounted home.mount loaded active mounted mnt-disk.mount loaded active mounted run-user-1000-gvfs.mount loaded active mounted sys-fs-f...nections.mount loaded active mounted sys-kernel-debug.mount loaded active mounted tmp.mount loaded active mounted systemd-...d-console.path loaded active waiting systemd-...-plymouth.path loaded active waiting systemd-...word-wall.path loaded active waiting accounts-daemon.service loaded active running colord-sane.service loaded active running colord.service loaded active running console-...daemon.service loaded active running console-...-start.service loaded active exited dbus.service loaded active running gdm-plymouth.service loaded active running tart.service
They are not meant to be enabled using systemctl.
plymouth
control process ex...03
plymouth-start.service entered failed...e.
operation timed...g.
plymouth-quit-wait.service entered fa...e.
gdm-plymouth.service and is working fine...
JOB DESCRIPTION
Arbitrary Executable File
MCP79 High Definition Audi
ST9500325AS
ST9500325AS
ST9500325AS
ST9500325AS
ST9500325AS
ST9500325AS
HL-DT-STDVDRAM_GT10N
RTL8111/8168B PCI Express
AR9285 Wireless Network Ad
/sys/devices/platform/seri
/sys/devices/platform/seri
/sys/devices/platform/seri
/sys/devices/platform/seri
/sys/module/fuse
/
Huge Pages File System
POSIX Message Queue File S
/home
/mnt/disk
/run/user/1000/gvfs
FUSE Control File System
Debug File System
/tmp
Dispatch Password Requests
Forward Password Requests
Forward Password Requests
Accounts Service
Daemon for monitoring atta
Manage, Install and Genera
Console Manager
Console System Startup Log
D-Bus System Message Bus
GNOME Display Manager
class="__cf_email__" data-cfemail="83e4e6f7f7fac3f7f7fab2adf0e6f1f5eae0e6">[email protected] loaded active running Getty on tty1
Network Manager
Wait for Plymouth Boot Scr
Show Plymouth Boot Screen
RealtimeKit Scheduling Pol
Journal Service
Login Service
Remount Root and Kernel Fi
Apply Kernel Variables
Recreate Volatile Files an
udev Coldplug all Devices
udev Kernel Device Manager
Permit User Sessions
Setup Virtual Console
Storage Daemon
Daemon for power managemen
WPA supplicant
D-Bus System Message Bus S
/dev/initctl Compatibility
Journal Socket
Delayed Shutdown Socket
udev Control Socket
udev Kernel Socket
/dev/sda1
Basic System
Encrypted Volumes
Login Prompts
Graphical Interface
Local File Systems (Pre)
Local File Systems
Multi-User
Network
Remote File Systems
Sockets
Sound Card
Swap
System Initialization
Daily Cleanup of Temporary

[SOLVED] systemd and pm-utils quirks (gma500_gfx)

Hi,
I have a netbook with the infamous poulsbo/gma500 chipset. To suspend it on the console (I am not yet at X ;-) ) I need to add the --quirk-vbemode-restore option to pm-suspend as described in the wiki [1]. How can I get the same effect when migrating to systemd (and therefore switching to systemctl and dropping pm-utils)?
Thanks
[1] https://wiki.archlinux.org/index.php/Poulsbo
Last edited by olaf.the.lost.viking (2012-08-22 23:13:22)

The code is in /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler and /usr/lib/pm-utils/sleep.d/99video. The substantial part is
# save/restore the vbe mode
vbe_savemode() { vbe vbemode get |savestate vbemode; }
vbe_restoremode()
# this is a little mode complicated to handle special-casing mode 3.
local vbemode=$(restorestate vbemode)
if [ "$vbemode" = "3" ]; then
vbe vgamode set $vbemode
else
vbe vbemode set $vbemode
fi
Note that vbe function only forwards its arguments to vbetool. You could place something like this into /usr/lib/systemd/system-sleep/99video
#!/bin/sh
TMPFILE=/tmp/gma500-state
vbe_savemode() {
vbetool vbemode get > $TMPFILE
vbe_restoremode() {
# this is a little mode complicated to handle special-casing mode 3.
local vbemode=$(cat $TMPFILE)
if [ "$vbemode" = "3" ]; then
vbetool vgamode set $vbemode
else
vbetool vbemode set $vbemode
fi
if [[ $1 == "pre" ]]; then
vbe_savemode
elif [[ $1 == "post" ]]; then
[ -O /tmp/gma500-state ] && vbe_restoremode
fi

Problems with waking from standby (suspend to disk)

Hello,
I have a late-2010 MacBook Air 11.6". I am running Lion 10.7.2.
To save battery life and also increase data protection via FileVault 2, I set the hibernatemode to 25 (alwas immediately suspend to disk) and enabled destruction of the FV key on standby (pmset -a hibernatemode 25 DestroyFVKeyOnStandby). Suspending works fine; and when I open the lid to resume from standby, I get the password prompt for FileVault's full disk encryption. After entering the password, the resume process starts. But then in some cases, my display stays black and I cannot turn it on again (tried closing/opening the lid, pressing Ctrl+Shift+Eject, connecting external monitor, ...)
If this behavior occurs, I can find entries like the following in my kernel.log:
Dec 23 13:30:15 mba kernel[0]: NVDA::setPowerState(0xffffff800c6b3000, 0 -> 2) timed out after 61662 ms
Is that a hardware bug? Any idea how I could possibly work around it?
Any help would be greatly appreciated!
Best Regards

Hi Aaron,
Check this blog and follow the steps mentioned, let us know if it works:
Something happened and the install of Windows 8.1 can't be completed. (And now you're annoyed)
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Systemd and suspend to disk

Similar Messages

Maybe you are looking for