- 1 Display manager fails to load with fast SSD
- 2 Hibernation with systemd
- 3 Removing rc.local
- 4 Replacing ConsoleKit with systemd-logind -> networkmanager
- 5 video group is still needed!
- 6 GNOME 3.6 issues inhibited commands
- 7 Should we add a note about cups under 'Transitioning from initscripts to systemd'?
Display manager fails to load with fast SSD
I was having a problem with my display manager (LXDM) not loading on my laptop, which has a Sandisk Extreme SSD. Xorg.log would show errors like "No screens found."
I eventually figured out that the problem was that my computer was booting so fast that KMS didn't have enough time to kick in before X was started. I solved by adding the KMS driver (i915 in my case) to the initramfs.
- This is a general problem that needs to be solved in the display manager. GDM already implements the bits for the CanGraphical flag.
- -- Falconindy (talk) 21:34, 2 September 2012 (UTC)
Hibernation with systemd
The hibernation section should be considered a hack since systemd does not directly handle the backend that handles power management. Systemd uses the Upower interface to handle such requests
-- Yungtrizzle (talk) 06:25, 10 October 2012
- I talked about hibernation process with Lennart Poettering and he said that systemd-hibernate does only "echo disk > /sys/power/state" . As far as i can see, it works perfectly with tuxonice, since it seems it is now using the same userspace API as kernel hibernation; so it works even without hibernate-script installed (i use it without that package).
- -- Nierro (talk) 13:54, 24 October 2012
- what is the #Hibernation section all about anyway? It makes it sound like you need to use uswsusp to hibernate while it should work out of the box just fine. It doesn't explain at all why you would want to use uswsusp instead of the default command. I don't use hibernate nor do I know what uswsusp actually does, so what am I missing here? ::-- 65kid (talk) 15:12, 25 October 2012 (UTC)
- Hey Nierro, do
systemctl suspendreally do different things on your box? In my setup (linux-pf, systemd 195-2), if I do the latter, my box is also in suspend mode, meaning that my power button is glowing on and off and I don't see grub after pressing the power button again but are back to my desktop almost immediately. To me, it rather seems as if
systemctl hibernategoes into hybrid mode?
- -- jakobh ✉ 10:07, 29 October 2012 (UTC)
- Hey Nierro, do
It isn't clear how to get rid of rc.local. It would be useful to include this statement from the forum discussion in moving from a mixed system to a pure system:
/etc/rc.local.shutdown and turn them into service files (or, if you intend to keep them as they are, copy
-- Myshkin (talk) 00:21, 13 Oct 2012
- I added a new section Systemd#.2Fetc.2Frc.local_emulation_for_systemd that covers how to emulate
/etc/rc.localin a pure systemd environment. Closing.
Replacing ConsoleKit with systemd-logind -> networkmanager
- 0.9.6.0-2 in [extra] was compiled on 2012-09-19 and the change to systemd was on 2012-09-29, so as far as I can see, it still needs to be recompiled. https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/networkmanager&id=c34580e6e35b9e87f7dc27f360507143d4fd9106
- -- 65kid (talk) 20:00, 15 October 2012 (UTC)
video group is still needed!
"Adding your user to groups (optical, audio, scanner, ...) is not necessary for most use cases with systemd. The groups can even cause some functionality to break." (Systemd#Supplementary_information)
- No, the statement is correct and you don't need the video group. see https://bbs.archlinux.org/viewtopic.php?pid=1183090#p1183090 65kid (talk) 14:05, 31 October 2012 (UTC)
GNOME 3.6 issues inhibited commands
It seems that GNOME 3.6 now issues the necessary "inhibited" commands, at my system now doesn't suspend twice with the standard configuration anymore. However I'm not familiar enough with the whole concept to be absolutely sure, so I won't update the page itself. Maybe someone with more competence regarding the inhibited commands can confirm this and edit the page?
-- Johnpatcher (talk) 00:34, 31 October 2012 (UTC)
Should we add a note about cups under 'Transitioning from initscripts to systemd'?
Are there any more sockets that change?
Copied from the Cups wiki:
Systemd uses a different cups socket file located at:
The default cups socket file is located at:
Edit /etc/cups/cupsd.conf and /etc/cups/client.conf as root to use the Systemd socket instead of the default. Make sure to restart CUPS when you are done:
# systemctl restart cups
JKAbrams 5 November 2012