You are not logged in.
A month or so ago (I don't remember when, exactly) I started getting all of the kernel boot messages appearing on my startup screen. In between all of the 'normal' startup messages (like daemon's starting) and also over the top of my console login on TTY1. I can still type my username/password, but the prompt is obscured by all of the other messages appearing (usually network driver/startup info by that point).
My /etc/inittab is default. I saw the other forum post where someone had something other than 'wait' in this line: 'rm:2345:wait:/etc/rc.multi', but mine says wait.
I have 'quiet' appended to my grub boot line:
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/bbc83434-90b8-413c-8050-afd00dad5d9e ro quiet nomodeset vga=791 nohz=offI've also tried adding 'loglevel=4' to the boot line but that didn't help either.
I just made a live USB with archiso and it doesn't show the kernel messages...both /etc/inittab's are identical and it also boots (using syslinux instead of grub) without the quiet parameter!
What am I missing here?
Thanks!
Scott
Offline
Check your inittab https://bbs.archlinux.org/viewtopic.php … 5#p1034095
Last edited by karol (2012-01-18 18:12:04)
Offline
My /etc/inittab is default. I saw the other forum post where someone had something other than 'wait' in this line: 'rm:2345:wait:/etc/rc.multi', but mine says wait.
From my first post ![]()
Scott
Offline
It's been a few days.... polite <bump> ? Any ideas? With the stock kernel....what else besides boot parameters in menu.lst or /etc/inittab could affect showing those messages??
Scott
Offline
I had the same thing happen, but more than a couple of weeks ago now (from memory). I already had quiet in my kernel line, adding "loglevel=3" restored the normal message levels...
Offline
Adding "loglevel=3" didn't work either
This is really baffling, because I have another Arch machine (desktop) that works fine with just the 'quiet' setting! It appears to be mostly networking messages by the time it hits the tty login screen ( [19.12345 b43-pyh0: Loading firmware.......], [23.156072 wlan0: associated], etc etc etc).
Any other ideas?
Scott
Offline
I background my network (@wicd), but foregrounding made no difference.
Perhaps do a little bit of experimenting in your daemons line to see if you can isolate the issue?
Offline
Well....I emptied the daemons line except for syslog-ng and dbus. Same result. Tried syslinux instead of grub. Same result. Tried loglevel=2. Same result.
This is really strange!! Any more ideas where to look? I don't know if it matters, but the HOOKS line in my mkinitcpio.conf is:
HOOKS="base udev autodetect pata scsi sata uresume filesystems usbinput"I just don't know what else to check!!
Thanks,
Scott
Offline