I've just done a fresh install of factory to see how systemd behaves. At first I ran with init=/bin/systemd configured in lilo.conf. With this I get hardly any console output? After an fsck of the /home volume, nothing happens until I get the login prompt. Is intentional?
Then I tried just adding init=/bin/systemd at the lilo prompt, and now I got a lot more of the usual output, although it seems to be a bit garbled. Lines are overwritten, seems to jump up and down.
On Sun, 2011-06-12 at 14:58 +0200, Per Jessen wrote:
I've just done a fresh install of factory to see how systemd behaves. At first I ran with init=/bin/systemd configured in lilo.conf. With this I get hardly any console output? After an fsck of the /home volume, nothing happens until I get the login prompt. Is intentional?
Remove 'quiet' from the command line?
Kay
Kay Sievers wrote:
On Sun, 2011-06-12 at 14:58 +0200, Per Jessen wrote:
I've just done a fresh install of factory to see how systemd behaves. At first I ran with init=/bin/systemd configured in lilo.conf. With this I get hardly any console output? After an fsck of the /home volume, nothing happens until I get the login prompt. Is intentional?
Remove 'quiet' from the command line?
Duh. Yeah. I obviously removed that too when I was revising lilo.conf.
The bit about the output being garbled still holds though. I don't know how else to explain it.
Am Sun, 12 Jun 2011 15:13:40 +0200 schrieb Per Jessen per@opensuse.org:
The bit about the output being garbled still holds though. I don't know how else to explain it.
I also have seen this, but only since a few days. Might be a regression in either systemd or the kernel.
(After logging out of a text console, the screen is also no longer cleared but overwritten. I'd guess this is the same bug)