You are not logged in.
Pages: 1
Up until yesterday, my boot up process was clean. Just informing me about things being loaded with [DONE] next to it.
Yesterday, however, it became very cluttered with unneccessary stuff like what it is running in each second. How can I make it what it was before?
My current boot entry is:
title Arch
root (hd0,2)
kernel /vmlinuz26 root=/dev/sda2 resume=/dev/sda2 resume_offset=1748992 ro quiet vga=785 sr0=ide-scsi
initrd /kernel26.img
Offline
Check out files:
/var/log/boot
/var/log/dmesg.log
/var/log/messages.log
Offline
For what purpose?
Offline
Change the "initrd /kernel26.img" to "initramfs-linux.img" and the "/vmlinuz26" to "/vmlinuz-linux"
Proud Arch Linux user since 2007.
Offline
Add the loglevel kernel boot parameter maybe? e.g. loglevel=4
See https://www.kernel.org/doc/Documentatio … meters.txt
This silver ladybug at line 28...
Offline
Add the loglevel kernel boot parameter maybe? e.g. loglevel=4
See https://www.kernel.org/doc/Documentatio … meters.txt
I never used loglevel=4 and it was always fine. It started literally with no apparent reason. The kernel line is the same as before.
Offline
The apparent reason is you updated the kernel. I said "maybe" because I thought it was a behavior already reverted in the latest kernel, but why don't you just try and see if my suggestion works for you?
This silver ladybug at line 28...
Offline
I got
[2011-07-31 18:35] warning: /etc/rc.conf installed as /etc/rc.conf.pacnew
[2011-07-31 18:35] VERBOSE= in rc.conf no longer has any effect.
[2011-07-31 18:35] Please append 'quiet' to your kernel command line.
in my pacman output when doing an update.
http://mailman.archlinux.org/pipermail/ … 21114.html
http://mailman.archlinux.org/pipermail/ … 21160.html
Last edited by karol (2011-08-30 13:48:24)
Offline
but why don't you just try and see if my suggestion works for you?
It didn't. Exactly the same cluttered output. And I don't think I updated the kernel when it went south.
Offline
lolilolicon wrote:but why don't you just try and see if my suggestion works for you?
It didn't. Exactly the same cluttered output. And I don't think I updated the kernel when it went south.
If loglevel=4 doesn't silence them, try loglevel=3.
Offline
Lockheed wrote:lolilolicon wrote:but why don't you just try and see if my suggestion works for you?
It didn't. Exactly the same cluttered output. And I don't think I updated the kernel when it went south.
If loglevel=4 doesn't silence them, try loglevel=3.
Won't make a difference because even 4 allowed things it should silence by definition. It looks like kernel parameters are being simply ignored or they changed...
Offline
Some users reported similar problems, maybe you should file a bug report upstream.
https://bbs.archlinux.org/viewtopic.php?id=123776
https://bbs.archlinux.org/viewtopic.php?pid=970935
Offline
Pages: 1