Arch Linux

FrostedCookies

Member

Registered: 2015-12-14

Posts: 11

Unable to achieve a silent boot

I have read and followed silent boot but I still have a huge number of messages during boot that even overwrite when I'm trying to log in.
Please see image of some of the messages. Most don't appear to be an error. For instance I get a lot of wlan0 messages about limiting TX power to 30 dBm as advertised, authenticating, sending auth etc.
https://i.imgur.com/Twlnxyy.jpg

I have updated my

/etc/default/grub

To have:
GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3"  (the default that came with arch was loglevel=3 quiet. However, switching this order did not make a difference)
I also have GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p3:root".
I then ran grub-mkconfig -o /boot/grub/grub.cfg
when I type cat /proc/cmdline
My output is:
BOOT_IMAGE=/vmlinuz-linux root=UUID=<many numbers/letters> rw rootflags=subvol=@ cryptdevice=/dev/nvme0n1p3:root quiet loglevel=3
So it seems like the kernel is getting the correct parameters sent including quiet, but it still has a lot of messages (see image above, can attach even more). The messages will also write-in even over the login-prompt as I'm typing (though they don't affect the inputted characters). I have even tried putting the cryptdevice= line in the default line at the end just in case the ':' character was causing some issue, but that didn't seem to affect things either.

Is there something else I'm missing besides those two parameters? I don't have the systemd hook in my hooks for /etc/mkinitcpio.conf the line is HOOKS=(base udev autodetect modconf block encrypt filesystems keyboard fsck)

Mod Edit - Replaced oversized image with link.
CoC - Pasting pictures and code

Last edited by Slithery (2022-08-27 20:37:39)

kermit63

Member

Registered: 2018-07-04

Posts: 372

Re: Unable to achieve a silent boot

You are probably looking in the wrong place. I'm from the opposite side of the spectrum in the sense that I like to see messages during the boot process so I can be warned of potential problems with my install. Anyway, upon reading this post, I decided to add "quiet" into /etc/default/grub, regenerated grub.cfg and rebooted.

Aside from the initial kernel loading message and the passphrase prompt, there were no messages leading to user login. I guess it's safe to say that your effort to achieve silent boot is not the problem since it didn't really take much for me to get there.

My hunch is there are problems with your installation that triggered the display of error messages. Instead of trying to hide those messages, you should use those messages to try and diagnose the problem. However "enormous number of messages" doesn't exactly offer much info for people here to help you.  How about posting what those messages really are?

If you are using a display manager like sddm, lightdm, etc. to log-in, you may want to disable it in the meantime so you can at least get a glimpse of the tail-end of the messages. It also removes one possible source of error.

I'm no expert at troubleshooting stuff, but I''m hoping that by improving the quality of your original post, you can persuade the more knowledgeable experts of this forum to take the time to help you.

Last edited by kermit63 (2022-08-26 09:23:15)

---

Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.

jl2

Member

From: 47° 18' N 8° 34' E

Registered: 2022-06-01

Posts: 1,395

Re: Unable to achieve a silent boot

What messages are you complaining about? It sounds like you do not have errors. In case they are colored try to get some obvious or red ones.

If the boot messages look something like:

[OK] started something
....

they should actually go away if you add the boot parameters quiet loglevel 3

In case you get something like this

starting arch 251.4-1
root: clean a number/number blocks, number files

or something like that then i guess the only way to hide then is with plymouth

Last edited by jl2 (2022-08-27 06:48:26)

---

Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...

Upload longer text output like this

FrostedCookies

Member

Registered: 2015-12-14

Posts: 11

Re: Unable to achieve a silent boot

Thank you both for your reply. Apologies Kermit for not including enough information. I have updated my original post to include a screenshot of some of the messages. Many if not most don't appear to be errors though. A lot are "audit: " messages, as you can see one is "mousedev: PS/2 mouse device common for all mice" so most don't strike me as a warning. Jl2 there aren't any green messages for example that say [OK] or [Failed] like I've seen when I boot Fedora for example. Some of the messages do mention systemd but most do not, and I don't have the systemd hook in place. Any idea what these messages are and if they indeed are important?

Last edited by FrostedCookies (2022-08-26 17:23:32)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,171

Re: Unable to achieve a silent boot

output of

$ sysctl kernel.printk
$ cat /proc/cmdline

?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky