How to disable verbose log messages at boot

thant · 2023-09-25 06:08:07

My current grub kernel parameter is:

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet cryptdevice=UUID=**************:cryptlvm root=UUID==**************"

For verbose message, I mean something like this: http://freedesktop.org/wiki/Software/sy … 17boot.png (not my image, just an example).
Is the above order incorrect? Should I add something? Do I need splash parameter after quiet?

seth · 2023-09-25 06:40:03

That's not "verbose", that's normal and regardless of how clever it is to hide that for whatever stupid reason so you cannot see where things go wrong if they ever do: https://wiki.archlinux.org/title/Silent_boot

thant · 2023-09-25 06:45:20

seth wrote:

That's not "verbose", that's normal and regardless of how clever it is to hide that for whatever stupid reason so you cannot see where things go wrong if they ever do: https://wiki.archlinux.org/title/Silent_boot

And how do I disable it? I have already read this wiki post but quiet parameter does not seem to change anything as I have it above at least.

seth · 2023-09-25 07:13:01

That depends on what you're *actually* seeing there - and whether its the same messages in the generic picture you linked.
Also post

cat /proc/cmdline

- the UUIDs there are btw. for collision prevention and not of privacy concern.

Edit:

the wiki btw wrote:

Note that this only seems to work if both quiet and loglevel=level are both used, and they must be in that order (quiet first).

Last edited by seth (2023-09-25 07:14:23)

thant · 2023-09-25 07:18:54

seth wrote:

That depends on what you're *actually* seeing there - and whether its the same messages in the generic picture you linked.
Also post
cat /proc/cmdline
- the UUIDs there are btw. for collision prevention and not of privacy concern.
Edit:
the wiki btw wrote:
Note that this only seems to work if both quiet and loglevel=level are both used, and they must be in that order (quiet first).

BOOT_IMAGE=/vmlinuz-linux root=UUID=cda70d36-b4c3-4b83-adc5-84af1ec0d4e6 rw loglevel=3 quiet cryptdevice=UUID=05111410-cf75-49b2-b1bc-c4419f747b24:cryptlvm root=UUID=cda70d36-b4c3-4b83-adc5-84af1ec0d4e6

The above is the output of the command you sent.
The messages are not exactly that but they are in this type with green ok and they appear exactly after I enter password of encrypted volume.

seth · 2023-09-25 07:27:40

Did you read the wiki quote?

thant · 2023-09-25 07:36:25

seth wrote:

Did you read the wiki quote?

Yes, I changed the above to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 cryptdevice=UUID=05111410-cf75-49b2-b1bc-c4419f747b24:cryptlvm root=UUID=cda70d36-b4c3-4b83-adc5-84af1ec0d4e6"

but the same is happening. I have again those messages.
I of course updated grub with this command

grub-mkconfig -o /boot/grub/grub.cfg

Last edited by thant (2023-09-25 07:37:08)

seth · 2023-09-25 07:54:58

Post an actual shot of the actual messages.

thant · 2023-09-25 09:21:05

seth wrote:

Post an actual shot of the actual messages.

Sorry for the bad quality but it's difficult to capture.

seth · 2023-09-25 14:28:47

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Short of a feature bug in systemd I don't see how you'd end up w/ that output for those parameters…

thant · 2023-09-25 14:36:01

seth wrote:

Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Short of a feature bug in systemd I don't see how you'd end up w/ that output for those parameters…

...

This is happening from first install. I remember this to happen when installing kde plasma as display manager from the iso.

Last edited by thant (2023-09-25 15:33:15)

seth · 2023-09-25 15:11:10

systemd.show_status=false

There also seems to be an attempt to use plymouth, but there's no "splash" in the kernel parameters - and did you add the plymouth hook to the initramfs?

Maybe try to de-install plymouth for the moment to make sure this isn't just a consequence of its failure.

thant · 2023-09-25 15:21:45

seth wrote:

systemd.show_status=false
There also seems to be an attempt to use plymouth, but there's no "splash" in the kernel parameters - and did you add the plymouth hook to the initramfs?
Maybe try to de-install plymouth for the moment to make sure this isn't just a consequence of its failure.

So for now just uninstall plymouth without changing anything? I do not see it in hook. Though I cannot remove it as there are modules that depend on it (breeze-plymouth, plymouth-kcm).

Last edited by thant (2023-09-25 15:23:53)

seth · 2023-09-25 15:28:12

Just remove those as well.
If that doesn't help, force the systemd.show_status value in the kernel commandline.
If it however is because of plymouth, you might simply need the splash parameter (idk. I've never used plymouth)

thant · 2023-09-25 15:32:48

Messages disappeared completely after uninstalling. Thanks!

Arch Linux

#1 2023-09-25 06:08:07

How to disable verbose log messages at boot

#2 2023-09-25 06:40:03

Re: How to disable verbose log messages at boot

#3 2023-09-25 06:45:20

Re: How to disable verbose log messages at boot

#4 2023-09-25 07:13:01

Re: How to disable verbose log messages at boot

#5 2023-09-25 07:18:54

Re: How to disable verbose log messages at boot

#6 2023-09-25 07:27:40

Re: How to disable verbose log messages at boot

#7 2023-09-25 07:36:25

Re: How to disable verbose log messages at boot

#8 2023-09-25 07:54:58

Re: How to disable verbose log messages at boot

#9 2023-09-25 09:21:05

Re: How to disable verbose log messages at boot

#10 2023-09-25 14:28:47

Re: How to disable verbose log messages at boot

#11 2023-09-25 14:36:01

Re: How to disable verbose log messages at boot

#12 2023-09-25 15:11:10

Re: How to disable verbose log messages at boot

#13 2023-09-25 15:21:45

Re: How to disable verbose log messages at boot

#14 2023-09-25 15:28:12

Re: How to disable verbose log messages at boot

#15 2023-09-25 15:32:48

Re: How to disable verbose log messages at boot

Board footer