Jan Engelhardt composed on 2015-04-02 12:27 (UTC+0200):
On Sunday 2015-03-29 20:24, Stefan Seifert wrote:
Some time in the last month Tumbleweed lost the ability to boot into runlevel 3 (command line with no X server running) by appending a 3 to the kernel line in the grub menu. I guess that's because with systemd there are no numbered runlevels anymore, but I wonder, what the replacement is?
Does it still occur for you and have you not changed klog units since? If so, run and paste
systemctl status klog
Welcome to openSUSE 20150329 "Tumbleweed" - Kernel \r (\l). Linux gx150 3.19.3-1-desktop #1 SMP PREEMPT Thu Mar 26 17:34:34 UTC 2015 (f10e7fc) i686 i686 i386 GNU/Linux â klog.service - Early Kernel Boot Messages Loaded: loaded (/usr/lib/systemd/system/klog.service; enabled; vendor preset: disabled) Active: active (exited) since Thu 2015-04-02 06:38:26 EDT; 2min 30s ago Process: 753 ExecStart=/bin/sh -c test -c /dev/tty10 && /usr/sbin/klogconsole $KLOGCONSOLE_PARAMS -r10 || : (code=exited, status=0/SUCCESS) Process: 751 ExecStart=/bin/sh -c test -s /dev/shm/initrd.msg && /bin/cat /dev/shm/initrd.msg >> /var/log/boot.msg || : (code=exited, status=0/SUCCESS) Process: 748 ExecStart=/bin/sh -c /bin/dmesg -r > /var/log/boot.msg (code=exited, status=0/SUCCESS) Process: 723 ExecStart=/bin/sh -c test -s /var/log/boot.msg && /bin/mv -f /var/log/boot.msg /var/log/boot.omsg || : (code=exited, status=0/SUCCESS) Main PID: 753 (code=exited, status=0/SUCCESS) CGroup: /system.slice/klog.service Apr 02 06:38:25 gx150 systemd[1]: Starting Early Kernel Boot Messages... Apr 02 06:38:26 gx150 systemd[1]: Started Early Kernel Boot Messages. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org