Kernel 6.1.19 doesn't display boot messages, booting into older kernel does

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

you mean:
with this kernel you don’t get them, but with older kernels you do?

update-grub
after any change to /etc/default/grub …

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.

… but my question also was:
Is there a difference between different kernels that you are booting?

You could boot with an older one - or with the most recent one you installed.

Is there a difference between those - in terms of whether or not you get the console messages?

… that would be weird - but that is what I was asking about …

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.

1 Like

Uncomment GRUB_TERMINAL_OUTPUT=console in /etc/grub/default

Thank you, but that only changed the way the GRUB-Menu is displayed but didn’t enable the boot-messages

Since you confirmed it works with previous kernel it seems the problem is in the kernel.

can you report

inxi -Fza
System:
  Kernel: 6.1.19-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=/dev/mapper/VolumeGroup-root rw 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
  Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: H170-PRO v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 3805
    date: 05/16/2018
CPU:
  Info: model: Intel Core i7-6700 bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 3700 min/max: 800/4000 scaling: driver: intel_pstate
    governor: powersave cores: 1: 3700 2: 3700 3: 3700 4: 3700 5: 3700 6: 3700
    7: 3700 8: 3700 bogomips: 54417
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional,
    RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Micro-Star MSI
    driver: nvidia v: 470.161.03 alternate: nouveau,nvidia_drm non-free:
    series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Fermi 2
    code: GF119/GK208 process: TSMC 28nm built: 2010-16 pcie: gen: 2
    speed: 5 GT/s lanes: 8 bus-ID: 01:00.0 chip-ID: 10de:128b class-ID: 0300
  Device-2: NVIDIA TU116 [GeForce GTX 1660 SUPER] vendor: Gigabyte
    driver: vfio-pci v: N/A alternate: nouveau,nvidia_drm,nvidia
    non-free: 525.xx+ status: current (as of 2023-02) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 4
    link-max: lanes: 16 bus-ID: 07:00.0 chip-ID: 10de:21c4 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,vfio-pci
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.70x13.46")
    s-diag: 692mm (27.26")
  Monitor-1: DVI-D-0 res: 2560x1440 hz: 60 dpi: 109
    size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 470.161.03 renderer: NVIDIA GeForce GT
    710/PCIe/SSE2 direct-render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170
    class-ID: 0403
  Device-2: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 10de:0e0f class-ID: 0403
  Device-3: C-Media CMI8788 [Oxygen HD Audio] vendor: ASUSTeK CMI8786
    driver: snd_oxygen v: kernel bus-ID: 03:04.0 chip-ID: 13f6:8788
    class-ID: 0401
  Device-4: NVIDIA TU116 High Definition Audio vendor: Gigabyte
    driver: vfio-pci alternate: snd_hda_intel pcie: speed: Unknown lanes: 63
    link-max: gen: 6 speed: 64 GT/s bus-ID: 07:00.1 chip-ID: 10de:1aeb
    class-ID: 0403
  Sound API: ALSA v: k6.1.19-1-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.22 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.65 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: c000 bus-ID: 06:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: br0 state: down mac: <filter>
  IF-ID-2: virbr0 state: down mac: <filter>
  IF-ID-3: virbr1 state: up speed: 10 Mbps duplex: unknown mac: <filter>
  IF-ID-4: virbr2 state: up speed: 10 Mbps duplex: unknown mac: <filter>
  IF-ID-5: virbr3 state: down mac: <filter>
  IF-ID-6: vnet0 state: unknown speed: 10 Mbps duplex: full mac: <filter>
  IF-ID-7: vnet1 state: unknown speed: 10 Mbps duplex: full mac: <filter>
  IF-ID-8: vnet2 state: unknown speed: 10 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 5.49 TiB used: 3.07 TiB (56.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 QVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1B6Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD30PURZ-85GU6Y0 size: 2.73 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0A80 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital
    model: WD My Passport 264F size: 931.48 GiB block-size: physical: 512 B
    logical: 512 B type: N/A serial: <filter> rev: 2005 scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Olympus model: E-M10MarkII
    size: 29.72 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 150 GiB size: 146.59 GiB (97.72%) used: 45.85 GiB (31.3%)
    fs: ext4 dev: /dev/dm-2 maj-min: 254:2 mapped: VolumeGroup-root
  ID-2: /boot/efi raw-size: 401 MiB size: 400.2 MiB (99.79%)
    used: 336 KiB (0.1%) fs: vfat dev: /dev/sda2 maj-min: 8:2
  ID-3: /home raw-size: 1000 GiB size: 983.23 GiB (98.32%)
    used: 590.73 GiB (60.1%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: VolumeGroup-home
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 31.06 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda8 maj-min: 8:8
Sensors:
  System Temperatures: cpu: 67.0 C mobo: N/A gpu: nvidia temp: 61 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 52%
Info:
  Processes: 301 Uptime: 1h 55m wakeups: 0 Memory: 62.73 GiB
  used: 19.27 GiB (30.7%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
  pkgs: 1789 libs: 411 tools: pamac pm: flatpak pkgs: 0 Shell: Zsh v: 5.9
  default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.25

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.

System:
  Kernel: 6.1.26-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=/dev/mapper/VolumeGroup-root rw 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
  Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.9 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: H170-PRO v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 3805
    date: 05/16/2018
CPU:
  Info: model: Intel Core i7-6700 bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 1775 high: 3400 min/max: 800/4000 scaling:
    driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 3400 7: 3400 8: 3400 bogomips: 54417
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional,
    RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Micro-Star MSI
    driver: nvidia v: 470.182.03 alternate: nouveau,nvidia_drm non-free:
    series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Fermi 2
    code: GF119/GK208 process: TSMC 28nm built: 2010-16 pcie: gen: 2
    speed: 5 GT/s lanes: 8 bus-ID: 01:00.0 chip-ID: 10de:128b class-ID: 0300
  Device-2: NVIDIA TU116 [GeForce GTX 1660 SUPER] vendor: Gigabyte
    driver: vfio-pci v: N/A alternate: nouveau,nvidia_drm,nvidia
    non-free: 530.xx+ status: current (as of 2023-05) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 4
    link-max: lanes: 16 bus-ID: 07:00.0 chip-ID: 10de:21c4 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,vfio-pci
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.70x13.46")
    s-diag: 692mm (27.26")
  Monitor-1: DVI-D-0 res: 2560x1440 hz: 60 dpi: 109
    size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 470.182.03 renderer: NVIDIA GeForce GT
    710/PCIe/SSE2 direct-render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170
    class-ID: 0403
  Device-2: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 10de:0e0f class-ID: 0403
  Device-3: C-Media CMI8788 [Oxygen HD Audio] vendor: ASUSTeK CMI8786
    driver: snd_oxygen v: kernel bus-ID: 03:04.0 chip-ID: 13f6:8788
    class-ID: 0401
  Device-4: NVIDIA TU116 High Definition Audio vendor: Gigabyte
    driver: vfio-pci alternate: snd_hda_intel pcie: speed: Unknown lanes: 63
    link-max: gen: 6 speed: 64 GT/s bus-ID: 07:00.1 chip-ID: 10de:1aeb
    class-ID: 0403
  API: ALSA v: k6.1.26-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 0.3.70 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 16.1 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: c000 bus-ID: 06:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: br0 state: down mac: <filter>
  IF-ID-2: virbr0 state: down mac: <filter>
  IF-ID-3: virbr1 state: up speed: 10 Mbps duplex: unknown mac: <filter>
  IF-ID-4: virbr2 state: up speed: 10 Mbps duplex: unknown mac: <filter>
  IF-ID-5: virbr3 state: down mac: <filter>
  IF-ID-6: vnet0 state: unknown speed: 10 Mbps duplex: full mac: <filter>
  IF-ID-7: vnet1 state: unknown speed: 10 Mbps duplex: full mac: <filter>
  IF-ID-8: vnet2 state: unknown speed: 10 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 6.43 TiB used: 2.88 TiB (44.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 QVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM000-1F2168
    size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5900 serial: <filter> fw-rev: CC54 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD My Passport 264F size: 931.48 GiB block-size: physical: 512 B
    logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
    tech: N/A serial: <filter> fw-rev: 2005 scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 vendor: Innostor model: N/A size: 59.08 GiB
    block-size: physical: 512 B logical: 512 B type: USB rev: 2.1 spd: 480 Mb/s
    lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 150 GiB size: 146.59 GiB (97.72%) used: 48.05 GiB (32.8%)
    fs: ext4 dev: /dev/dm-2 maj-min: 254:2 mapped: VolumeGroup-root
  ID-2: /boot/efi raw-size: 401 MiB size: 400.2 MiB (99.79%)
    used: 336 KiB (0.1%) fs: vfat dev: /dev/sda2 maj-min: 8:2
  ID-3: /home raw-size: 1000 GiB size: 983.23 GiB (98.32%)
    used: 493.95 GiB (50.2%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: VolumeGroup-home
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 31.06 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda8 maj-min: 8:8
Sensors:
  System Temperatures: cpu: 33.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 282 Uptime: 8m wakeups: 0 Memory: available: 62.73 GiB
  used: 17.68 GiB (28.2%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
  pkgs: 1814 libs: 418 tools: pamac pm: flatpak pkgs: 0 Shell: Zsh v: 5.9
  default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.27

You already have one thread open with the same problem: Kernel 6.1.19 doesn't display boot messages, booting into older kernel does

…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.

You can bump the old thread instead of opening a new one.

Unfortunately I’m not very helpful in the matter. I couldn’t figure out any reason for that behavior.

Topics merged. Please do not create duplicate threads.

This silences a lot of the output.

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?

Remov udev.log_priority from the grub default and rebuild grub

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.