From 3c372cfdc3bee1930e86c2b4dc210a374e8487f6 Mon Sep 17 00:00:00 2001 From: Tom Gundersen Date: Fri, 29 Jun 2012 15:14:01 +0200 Subject: vconsole: configure it only after udev has settled If we configure the console too early, the settings will be lost when the KMS driver is loaded. This fixes FS#30482, which is a duplicate of FS#29781 (which was fixed and then broken again by me). Reported-by: Robert Signed-off-by: Tom Gundersen --- rc.sysinit | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'rc.sysinit') diff --git a/rc.sysinit b/rc.sysinit index 70025a1..1106503 100755 --- a/rc.sysinit +++ b/rc.sysinit @@ -30,8 +30,6 @@ mountpoint -q /dev/shm || mount -t tmpfs shm /dev/shm -o mode=1777,nosuid,nodev # log all console messages bootlogd -p /run/bootlogd.pid -status 'Configuring Virtual Consoles' /usr/lib/systemd/systemd-vconsole-setup - if [[ ! -e /run/initramfs/root-fsck ]]; then # remount root ro to allow for fsck later on, we remount now to # make sure nothing can open files rw on root which would block a remount @@ -68,6 +66,9 @@ fi # Start/trigger UDev, load MODULES and settle UDev udevd_modprobe sysinit +# this must be done after udev has loaded the KMS modules +status 'Configuring Virtual Consoles' /usr/lib/systemd/systemd-vconsole-setup + # bring up the loopback interface [[ -d /sys/class/net/lo ]] && status "Bringing up loopback interface" ip link set up dev lo -- cgit v1.2.3