From ArchWiki
Jump to navigation Jump to search

initrd usage

if you are using an initrd without udev hook, mounting of additional lvm partitions will fail during boot. Add udev to your hooks and rebuild initrd.


Note: In a pure systemd installation, installing systemd-sysvcompat removes initscripts and sysvinit, permits the export of LANG in /etc/locale.conf, and creates symlinks to halt, reboot, etc. But you can manually remove initscripts and sysvinit as described here.

This note does not seem accurate. On my up-to-date system, systemd-sysvcompat only conflicted with, and tried to remove sysvinit - which fails due to the initscripts dependency. I had to specifically remove both sysvinit and initscripts before attempting to install systemd-sysvcompat. Troymc (talk) 00:02, 2 September 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.

Just a tip for SSD users, not sure if it should be added to the page or not. --Steev (talk) 16:59, 2 September 2012 (UTC)

  • 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)

Bootloader kernel parameter

Should it be init=/bin/systemd or init=/usr/lib/systemd/systemd I think the first one is recommended when you install systemd. AdrianTM (talk) 04:02, 5 September 2012 (UTC)

You're right, pacman says /bin/systemd, which is a symlink to /usr/lib/systemd/systemd. Both might work, though I prefer to stick with the pacman message. Traced the wiki discrepancy back to this edit and the following ones. --Emiralle (talk) 16:57, 5 September 2012 (UTC)