- 1 Lack of internet connection using static ip address without netcfg or NetworkManager
- 2 initrd usage
- 3 Display manager fails to load with fast SSD
- 4 Confusion in new Installation section
- 5 Hibernation with Systemd
- 6 Removing rc.local
- 7 Add information on permissions needed by systemd?
- 8 Replacing ConsoleKit with systemd-logind -> networkmanager
Lack of internet connection using static ip address without netcfg or NetworkManager
See [A pure systemd installation] it instructs to remove the initscripts package. When doing so take care not to use the -s option of pacman with -R as it removes the iproute2 package also unless you have another package with iproute2 as a dependency.
pacman -R initscripts pacman -Rn initscripts
Not safe when iproute2 will also be removed:
pacman -Rs initscripts pacman -Rns initscripts
If you are using an initrd without the
udev hook, mounting of additional LVM partitions will fail during boot. Add
udev to your mkinitcpio hooks and rebuild the initrd.
-- Ronnyyy (talk) 19:50, 6 June 2012 (UTC)
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.
Confusion in new Installation section
See [mixed systemd/initscripts] which teaches that to run a mixed systemd/initscripts setup, one should install systemd-sysvcompat but doing this will remove initscripts.
% sudo pacman -S systemd-sysvcompat resolving dependencies... looking for inter-conflicts... :: systemd-sysvcompat and sysvinit are in conflict. Remove sysvinit? [y/N] y :: systemd-sysvcompat and initscripts are in conflict. Remove initscripts? [y/N] n error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: systemd-sysvcompat and initscripts are in conflict
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
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
Add information on permissions needed by systemd?
There is no indication as to what any of the permissions for the files that need to be created for systemd should be. My guess is that root:root 644 is correct, but it would be nice if the settings were explicitly mentioned in the wiki.
Replacing ConsoleKit with systemd-logind -> networkmanager
As of networkmanager 0.9.6.0-2 in (extra) we do no more have to recompile it with systemd support from abs, is this right? So the note should be upgraded. Am i missing anything?
- 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)
Damn, you're right. I did not see that pkgrel=3 while we are still using -2. Sorry, it means i'm still using my recompiled package, while i thought i was using the extra one.