From ArchWiki
Revision as of 16:19, 21 October 2012 by Jstjohn (Talk | contribs) (Lack of internet connection using static ip address without netcfg or NetworkManager: re)

Jump to: navigation, search

Lack of internet connection using static ip address without netcfg or NetworkManager

See Systemd#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

-- imatechguy (talk) 00:28, 11 Oct 2012 (UTC)

  • It is fixed. iproute2 is in base group now. Close.
-- Fengchao (talk) 02:19, 18 October 2012 (UTC)
  • Only the iproute2 build in [testing] is in the base group. It's been in [testing] for nearly a week, so hopefully it'll be released soon.
-- Jstjohn (talk) 16:19, 21 October 2012 (UTC)

initrd usage

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)

Note added in Lvm. Close. -- Fengchao (talk) 02:34, 18 October 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)

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

Graysky (talk) 09:28, 3 October 2012 (UTC)

Only pure systemd installation ask user to install systemd-sysvcompat. Close. -- Fengchao (talk) 02:14, 18 October 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‎

Removing rc.local

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:

Go through /etc/rc.local and /etc/rc.local.shutdown and turn them into service files (or, if you intend to keep them as they are, copy /usr/lib/systemd/system/rc-local{,.shutdown}.service to /etc/systemd/system/).
--‎ 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.
-- Apeschel (talk) 18:14, 14 October 2012‎

  • I added info on the file permissions for the systemd config files [1].
-- Jstjohn (talk) 21:51, 16 October 2012 (UTC)

Replacing ConsoleKit with systemd-logind -> networkmanager

As of networkmanager 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?
-- Nierro (talk) 09:31, 15 October 2012

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.
-- Nierro (talk) 16:35, 15 October 2012

Removing systemd-sysvcompat

So I was thinking: lets go all the way and remove systemd-sysvcompat. After some scary moments I found out init=/usr/lib/systemd/systemd has to be enabled since otherwise there is nothing to boot into. I also noticed this removes the reboot and poweroff commands ( systemctl {reboot,shutdown} replace these).

Now, is this the recommended way to go in the future, or should everyone keep systemd-sysvcompat installed?
-- Lonaowna (talk) 23:56, 20 October 2012 (UTC)