Since the last Kernel-update to 6.1.19 my manjaro stopped displaying boot/shutdown-messages. I really don’t like not knowing whats going on, so I would like them back very much, but the old ways of adjusting the grub-config and removing “quiet” don’t seem do work anymore. Did something change? My current /etc/default/grub:
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="apparmor=1 security=apparmor udev.log_priority=3 intel_iommu=on vfio-pci.ids=10de:21c4,10de:1aeb,10de:1aec,10de:1aed kvm.ignore_msrs=1"
GRUB_CMDLINE_LINUX=""
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true
# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true
yes, right… I had them with the old kernel and since the update all I get are a few pre boot-messages (eg “diskfilter writes not supported”) that stay on the screen until plasma takes over but no longer the “starting XYZ…[success]”-messages
I didn’t change anything to /etc/default/grub - i left it the way it was before the update. Running update-grub doesn’t help.
Finally had the time to check it: Yes, if I boot into Kernel 5.15 the boot-messages are displayed. Booting into Kernel 6.1.19 only shows a black screen while booting/shutdown.
Since this seems to be a unique problem: Could you point me in the right direction how to solve it? I don’t know much about the linux boot process so it is hard to find the correct search terms. I’m missing the “Starting XYZ … [success]” messages during boot and shutdown. What exactly are they called and what part of the system is responsible for creating them? Maybe this would help me to find a solution.
Since I did the Kernel-update to 6.1.19 my manjaro stopped displaying boot/shutdown-messages. Instead I just see a black screen until the login-screen comes up.
My current /etc/default/grub:
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=menu
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="apparmor=1 security=apparmor udev.log_priority=5 intel_iommu=on vfio-pci.ids=10de:21c4,10de:1aeb,10de:1aec,10de:1aed kvm.ignore_msrs=1"
GRUB_CMDLINE_LINUX=""
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true
# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true
Strange thing is: If I boot back into the old kernel 5.15 the messages are displayed. Also If I boot into a USB-Livesystem with a current kernel it is also working. So there seems to be a specific option in my configuration that is not working with the newer Kernels, but I have no idea what it could be.
…which hasn’t received any answers for more than a month. Not even for my last question “Could you tell me the right terminology so I can try to google it myself?”. So I’ve concluded that most users probably don’t read a thread if it already has more than a few answers.
Thanks, I’ve tried several values for udev.log_priority but unfortunately nothing changed. It’s still completely blank… Could it be more of a “hardware-problem”? E.g. some wrong graphics setting or the output getting directed somewhere “wrong”? Anything along those lines?
Or another idea: Since it worked with the USB-livesystem - can I somehow “copy” those settings and use them for my normal boot process? Could this be a way to find the problem?
Thank you, but still no success (with rebuilding grub you mean sudo update-grub, right?).
But I might have another clue: I deliberately provoked a boot error (disconnected one hard drive) so that it should go into the rescue-shell. But still the screen stayed black.
So I’m pretty sure that it isn’t some kind of “wrong log level setting”-problem but some fundamental problem with displaying any text during the startup process.
I tried the same with the 5.15 kernel and there the rescue-shell was displayed.