Unable to boot into the default kernel

I believe I may be affected by this problem. After running garuda-update, I am unable to boot into the default kernel (linux-zen); However, I am able to boot into linux-amd-zen3.

I’m also not able to fully boot into my snapshots: I’m able to get into a tty, but journalctl shows that the display sever fails to launch, giving the same “failed to read display number from pipe” error that was identified by BluishHumility.

What should I do?

here’s the garuda-inxi output for my system.

System:
Kernel: 6.8.7-AMD-znver3 arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-amd-znver3
root=UUID=d79509aa-f1eb-4406-9a67-13190c3cd0a6 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.1.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: PRO B550M-VC WIFI (MS-7C95) v: 3.0
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: H.81 date: 06/09/2023
CPU:
Info: model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA50000D
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 2128 high: 2994 min/max: 400/4464 scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 400 2: 400 3: 400
4: 2994 5: 2991 6: 400 7: 2994 8: 2993 9: 2994 10: 2994 11: 2994 12: 2993
bogomips: 93463
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: DP-3,HDMI-A-1 empty: DP-1,DP-2,Writeback-1
bus-ID: 12:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.6
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu d-rect: 3840x1080 display-ID: 0
Monitor-1: DP-3 pos: primary,left res: 1920x1080 size: N/A modes: N/A
Monitor-2: HDMI-A-1 pos: right res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.6-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6800 (radeonsi navi21
LLVM 17.0.6 DRM 3.57 6.8.7-AMD-znver3) device-ID: 1002:73bf
memory: 15.62 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 10 device: 0 type: discrete-gpu name: AMD
Radeon RX 6800 (RADV NAVI21) driver: mesa radv v: 24.0.6-arch1.2
device-ID: 1002:73bf surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.0.6-arch1.2 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 12:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Renoir Radeon High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.1 chip-ID: 1002:1637
class-ID: 0403
Device-3: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.6 chip-ID: 1022:15e3
class-ID: 0403
API: ALSA v: k6.8.7-AMD-znver3 status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 29:00.0 chip-ID: 14c3:0608
class-ID: 0280
IF: wlp41s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8168 v: 8.053.00-NAPI modules: r8169 pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 2a:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp42s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:6 chip-ID: 0e8d:0608
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 1.36 TiB used: 1.01 TiB (73.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV2S500G
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: ELFKAN.2 temp: 20.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABD100
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 5J scheme: GPT
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 322.49 GiB (69.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 322.49 GiB (69.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 322.49 GiB (69.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 322.49 GiB (69.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.52 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 31.0 C mobo: 24.0 C gpu: amdgpu temp: 31.0 C
mem: 30.0 C
Fan Speeds (rpm): fan-1: 1346 fan-2: 0 fan-3: 851 fan-4: 861 fan-5: 561
fan-6: 0 fan-7: 0 fan-8: 0 fan-9: 0 fan-10: 0 gpu: amdgpu fan: 0
Info:
Memory: total: 16 GiB available: 15.52 GiB used: 3.99 GiB (25.7%)
Processes: 301 Power: uptime: 40m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.19 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1810 libs: 562 tools: octopi,pamac,paru
Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi default: Bash
v: 5.2.26 running-in: konsole inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2023-06-15
Last full system update: 2024-05-01
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

May you please share any and all logs you think might be relevant to help us investigate this issue? Depending on those, your comment may be split into a separate thread, however. Please note that logs from a successful system boot are not useful for us, since they do not help. As the last question, what leads you to the conclusion that you are having the same issue as @Elmar?

2 Likes
Garuda inxi
System:
  Kernel: 6.6.29-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
    root=UUID=9bdc1bb8-710e-4a2b-a1fc-d771d79d9fb1 rw rootflags=subvol=@
    quiet resume=UUID=3de67b4e-0081-4321-8b87-d6348302d4da loglevel=3 ibt=off
  Desktop: Cinnamon v: 6.0.4 tk: GTK v: 3.24.41 wm: Muffin v: 6.0.1 tools:
    avail: cinnamon-screensaver,xautolock dm: LightDM v: 1.32.0 Distro: Garuda
    base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: CROSSHAIR VI HERO v: Rev 1.xx
    serial: <filter> part-nu: SKU UEFI: American Megatrends v: 7704
    date: 12/16/2019
CPU:
  Info: model: AMD Ryzen 9 3900X socket: AM4 bits: 64 type: MT MCP arch: Zen 2
    gen: 3 level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
    family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701013
  Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
    L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
    L3: 64 MiB desc: 4x16 MiB
  Speed (MHz): avg: 2400 high: 3800 min/max: 2200/4672 boost: enabled
    base/boost: 3800/4650 scaling: driver: acpi-cpufreq governor: schedutil
    volts: 1.1 V ext-clock: 100 MHz cores: 1: 2200 2: 2200 3: 2200 4: 2200
    5: 2200 6: 2200 7: 2200 8: 2200 9: 2200 10: 2200 11: 2200 12: 2200
    13: 3800 14: 2200 15: 2200 16: 2200 17: 2200 18: 3800 19: 3800 20: 2200
    21: 2200 22: 2200 23: 2200 24: 2200 bogomips: 182449
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: ASUSTeK driver: nvidia
    v: 550.76 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current
    (as of 2024-04; EOL~2026-12-xx) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: DVI-D-1,HDMI-A-1,HDMI-A-2 empty: DP-1,DP-2
    bus-ID: 0b:00.0 chip-ID: 10de:1b81 class-ID: 0300
  Display: server: X.Org v: 21.1.13 with: Xwayland v: 23.2.6 driver: X:
    loaded: nvidia gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5760x1080 s-dpi: 92 s-size: 1590x301mm (62.60x11.85")
    s-diag: 1618mm (63.71")
  Monitor-1: DVI-D-1 mapped: DVI-D-0 note: disabled pos: primary,center
    model: BenQ GL2450H serial: <filter> built: 2015 res: 1920x1080 hz: 60
    dpi: 92 gamma: 1.2 size: 531x298mm (20.91x11.73") diag: 609mm (24")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  Monitor-2: HDMI-A-1 mapped: HDMI-0 note: disabled pos: right
    model: Dell SE2422H serial: <filter> built: 2022 res: 1920x1080 hz: 60
    dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  Monitor-3: HDMI-A-2 mapped: HDMI-1 note: disabled pos: left
    model: Dell SE2422H serial: <filter> built: 2022 res: 1920x1080 hz: 60
    dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.76
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2
    memory: 7.81 GiB
  API: Vulkan v: 1.3.279 layers: 4 device: 0 type: discrete-gpu
    name: NVIDIA GeForce GTX 1070 driver: nvidia v: 550.76 device-ID: 10de:1b81
    surfaces: xcb,xlib
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 0b:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0d:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.6.29-1-lts status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.5 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 05:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
Drives:
  Local Storage: total: 7.28 TiB used: 749.24 GiB (10.1%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO with
    Heatsink 1TB size: 931.51 GiB block-size: physical: 512 B logical: 512 B
    speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QGXA7
    temp: 37.9 C scheme: GPT
  SMART: yes health: PASSED on: 19d 2h cycles: 446
    read-units: 31,300,161 [16.0 TB] written-units: 26,712,026 [13.6 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 1TB
    family: based SSDs size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.3 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 2B6Q temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 240d 12h cycles: 820
    written: 15.33 TiB
  ID-3: /dev/sdb maj-min: 8:16 vendor: Hitachi model: HUA723020ALA641
    family: Ultrastar 7K3000 size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B sata: 2.6 speed: 6.0 Gb/s tech: HDD rpm: 7200
    serial: <filter> fw-rev: A840 temp: 39 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 101d 12h cycles: 1658
  ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD10EFRX-68PJCN0 family: Red size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s tech: HDD
    rpm: 5400 serial: <filter> fw-rev: 0A82 temp: 32 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 2y 33d 10h cycles: 2876
    Old-Age: UDMA CRC errors: 38136 alert: Bad cable/connection?
  ID-5: /dev/sdd maj-min: 8:48 vendor: Western Digital
    model: WD10EADS-00M2B0 family: Caviar Green size: 931.51 GiB block-size:
    physical: 512 B logical: 512 B sata: 2.6 speed: 3.0 Gb/s tech: N/A
    serial: <filter> fw-rev: 0A01 temp: 35 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 2y 290d 20h cycles: 4287
  ID-6: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 860 EVO 1TB
    family: based SSDs size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 1B6Q temp: 31 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 312d 11h cycles: 2305
    written: 63.47 TiB
  ID-7: /dev/sdf maj-min: 8:80 vendor: SanDisk model: SSD PLUS 1000GB
    family: Marvell based SSDs size: 931.52 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 00RL temp: 34 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 223d 3h cycles: 803
Partition:
  ID-1: / raw-size: 896.82 GiB size: 896.82 GiB (100.00%)
    used: 749.24 GiB (83.5%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 896.82 GiB size: 896.82 GiB (100.00%)
    used: 749.24 GiB (83.5%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-4: /var/log raw-size: 896.82 GiB size: 896.82 GiB (100.00%)
    used: 749.24 GiB (83.5%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-5: /var/tmp raw-size: 896.82 GiB size: 896.82 GiB (100.00%)
    used: 749.24 GiB (83.5%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 34.39 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
  ID-2: swap-2 type: zram size: 31.27 GiB used: 6.14 GiB (19.6%)
    priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 56.0 C mobo: 30.0 C gpu: nvidia temp: 54 C
  Fan Speeds (rpm): cpu: 1415 case-1: 0 case-2: 1201 case-3: 0 gpu: nvidia
    fan: 0%
  Power: 12v: 12.29 5v: N/A 3.3v: N/A vbat: 3.16
Info:
  Memory: total: 32 GiB available: 31.27 GiB used: 12.61 GiB (40.3%)
  Processes: 573 Power: uptime: 9h 58m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.47 GiB services: csd-power,upowerd
    Init: systemd v: 255 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 2083 libs: 615 tools: paru,yay Compilers:
    clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi (sudo) default: Bash v: 5.2.26
    running-in: gnome-terminal inxi: 3.3.34
Garuda (2.6.26-1):
  System install date:     2024-01-20
  Last full system update: 2024-05-01
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Yes
  Failed units:            vmware.service 

I don’t think I haven’t the same Problem as @Elmar I haven’t install dracut I think. If I boot it doesn’t load after selecting the default boot option. With the LTS Kernel it is no Problem.

Is there a option to look where it failed to boot? With Ubuntu I can see what Linux load at boot. Because, I could post where it failed.

If it were me, I’d try the LTS kernel.

1 Like

I always use the LTS kernel, unless I really have a good reason for using something else (which I never do).

1 Like

As for why I thought I may have the same, or a related, problem, is for a few reasons:

  • The time frame is the same; I had no issues until I updated a few days ago; and I hadn’t used the PC (and therefore hadn’t updated it) for about 3 weeks, so it seems likely that the same update was responsible for both problems
  • The symptoms of the problem are the same (new kernel can’t boot, also unable to boot into snapshots to roll back to a previous, working version)
  • When booting into a snapshot, the display manager fails to start, giving an error that matched an earlier error log that had been posted

It seems that this has now been split into a separate issue, so I should have made a separate post to begin with. Apologies, I didn’t want to create a duplicate post, if the issues had the same solution.

As for relevant logs, I don’t know which ones will be helpful. I don’t know how to recover logs from an unsuccessful boot into linux-zen as the boot process fails before I’m able to get into a TTY.
Edit: Note, that I’ve tried running journalctl --system -b -1 after an unsuccessful boot to recover logs, but it does not give the log from the unsuccessful boot into linux-zen. Rather, it produces logs from the last successful boot.

I have added linux-lts to my list of kernels, but I haven’t tried booting into it yet, as the system is currently running fine on linux-amd-znver3. I’ll give that a shot and report back.
Result: LTS boots perfectly.

I’ll also boot into one of my snapshots to get the logs of the display manager failing in that case, and add them to this post.
Edit: I’m actually not sure how to get these logs out of the snapshot TTY session. when I boot back into a working kernel, eg. LTS, journalctl doesn’t show logs from the boot into the snapshot. Of course, I’m able to see the logs when I’m in the snapshot TTY, but I can’t copy and paste them. The only thing I can think of would be to attach a USB stick and write the output of the journal to a file on that usb stick, which I could then access from a working desktop environment, and from there I could upload them here. I’ll give that a try, but it is definitely pushing the limits of my comfort zone in terms of navigating with just the terminal.

OK, I have managed to get the output of journalctl --system -b -lines=all -e into a file on to a usb disk. There are 2,154 lines of output, and I’m not sure that they will be of any help, as this was a “successful” boot; that is, I was able to get into a TTY. I’m only attaching the part that I think is the most relevant here, which are lines 1840-1906, where the display server fails to start (thus failing to start the desktop environment, if I’m understanding correctly). However, I’ve got the full file, so I can upload more of it if it would help. I’ve removed my actual name from the file and replaced it with “myname” but haven’t made any other changes.

May 04 17:29:55 myname-tower-cstm systemd[1]: Finished Terminate Plymouth Boot Screen.
May 04 17:29:55 myname-tower-cstm systemd[1]: Reached target Multi-User System.
May 04 17:29:55 myname-tower-cstm systemd[1]: Started Simple Desktop Display Manager.
May 04 17:29:55 myname-tower-cstm systemd[1]: Reached target Graphical Interface.
May 04 17:29:55 myname-tower-cstm avahi-daemon[823]: Server startup complete. Host name is myname-tower-cstm.local. Local service cookie is 4107554292.
May 04 17:29:55 myname-tower-cstm sddm[1034]: Initializing...
May 04 17:29:55 myname-tower-cstm sddm[1034]: Starting...
May 04 17:29:55 myname-tower-cstm sddm[1034]: Logind interface found
May 04 17:29:55 myname-tower-cstm sddm[1034]: Adding new display...
May 04 17:29:55 myname-tower-cstm sddm[1034]: Loaded empty theme configuration
May 04 17:29:55 myname-tower-cstm sddm[1034]: Xauthority path: "/run/sddm/xauth_DXylMV"
May 04 17:29:55 myname-tower-cstm sddm[1034]: Using VT 2
May 04 17:29:55 myname-tower-cstm sddm[1034]: Display server starting...
May 04 17:29:55 myname-tower-cstm sddm[1034]: Writing cookie to "/run/sddm/xauth_DXylMV"
May 04 17:29:55 myname-tower-cstm sddm[1034]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_DXylMV -noreset -displayfd 16
May 04 17:29:56 myname-tower-cstm systemd-coredump[852]: Removed old coredump core.kdenlive.1000.e681aacf48304287ab89f585065573a1.39535.1713202327000000.zst.
May 04 17:29:56 myname-tower-cstm NetworkManager[980]: <info>  [1714865396.1876] device (wlp41s0): set-hw-addr: set MAC address to 0A:BA:FD:87:EC:FF (scanning)
May 04 17:29:56 myname-tower-cstm dbus-daemon[825]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.10' (uid=0 pid=980 comm="/usr/bin/NetworkManager --no-daemon")
May 04 17:29:56 myname-tower-cstm systemd[1]: Starting WPA supplicant...
May 04 17:29:56 myname-tower-cstm dbus-daemon[825]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
May 04 17:29:56 myname-tower-cstm wpa_supplicant[1038]: Successfully initialized wpa_supplicant
May 04 17:29:56 myname-tower-cstm systemd[1]: Started WPA supplicant.
May 04 17:29:56 myname-tower-cstm sddm[1034]: Failed to read display number from pipe
May 04 17:29:56 myname-tower-cstm sddm[1034]: Display server stopping...
May 04 17:29:56 myname-tower-cstm sddm[1034]: Attempt 1 starting the Display server on vt 2 failed
May 04 17:29:56 myname-tower-cstm NetworkManager[980]: <info>  [1714865396.3614] device (wlp41s0): supplicant interface state: internal-starting -> disconnected
May 04 17:29:56 myname-tower-cstm NetworkManager[980]: <info>  [1714865396.3614] Wi-Fi P2P device controlled by interface wlp41s0 created
May 04 17:29:56 myname-tower-cstm NetworkManager[980]: <info>  [1714865396.3616] manager: (p2p-dev-wlp41s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
May 04 17:29:56 myname-tower-cstm NetworkManager[980]: <info>  [1714865396.3617] device (p2p-dev-wlp41s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
May 04 17:29:56 myname-tower-cstm NetworkManager[980]: <info>  [1714865396.3619] device (wlp41s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
May 04 17:29:56 myname-tower-cstm NetworkManager[980]: <info>  [1714865396.3622] device (p2p-dev-wlp41s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
May 04 17:29:56 myname-tower-cstm pamac[851]: Number of versions of each package to keep in the cache: 3
May 04 17:29:56 myname-tower-cstm pamac[851]: To delete: 0 files
May 04 17:29:56 myname-tower-cstm systemd[1]: pamac-cleancache.service: Deactivated successfully.
May 04 17:29:56 myname-tower-cstm systemd[1]: Finished Clean packages cache.
May 04 17:29:57 myname-tower-cstm systemd-coredump[852]: Removed old coredump core.kdenlive.1000.e681aacf48304287ab89f585065573a1.40016.1713202361000000.zst.
May 04 17:29:57 myname-tower-cstm systemd-coredump[852]: Process 835 (preload) of user 0 dumped core.
                                                         
                                                         Stack trace of thread 835:
                                                         #0  0x00007a9bd55d1f18 g_log_structured_array (libglib-2.0.so.0 + 0x5ef18)
                                                         #1  0x00007a9bd55d2213 g_log_default_handler (libglib-2.0.so.0 + 0x5f213)
                                                         #2  0x00007a9bd55d2485 g_logv (libglib-2.0.so.0 + 0x5f485)
                                                         #3  0x00007a9bd55d2754 g_log (libglib-2.0.so.0 + 0x5f754)
                                                         #4  0x0000575a59042552 n/a (preload + 0x4552)
                                                         #5  0x0000575a59041053 n/a (preload + 0x3053)
                                                         #6  0x00007a9bd53b6cd0 n/a (libc.so.6 + 0x25cd0)
                                                         #7  0x00007a9bd53b6d8a __libc_start_main (libc.so.6 + 0x25d8a)
                                                         #8  0x0000575a59041275 n/a (preload + 0x3275)
                                                         ELF object binary architecture: AMD x86-64
May 04 17:29:57 myname-tower-cstm systemd[1]: preload.service: Main process exited, code=dumped, status=5/TRAP
May 04 17:29:57 myname-tower-cstm systemd[1]: preload.service: Failed with result 'core-dump'.
May 04 17:29:57 myname-tower-cstm systemd[1]: [email protected]: Deactivated successfully.
May 04 17:29:58 myname-tower-cstm sddm[1034]: Display server starting...
May 04 17:29:58 myname-tower-cstm sddm[1034]: Writing cookie to "/run/sddm/xauth_DXylMV"
May 04 17:29:58 myname-tower-cstm sddm[1034]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_DXylMV -noreset -displayfd 16
May 04 17:29:58 myname-tower-cstm sddm[1034]: Failed to read display number from pipe
May 04 17:29:58 myname-tower-cstm sddm[1034]: Display server stopping...
May 04 17:29:58 myname-tower-cstm sddm[1034]: Attempt 2 starting the Display server on vt 2 failed
May 04 17:29:59 myname-tower-cstm ModemManager[997]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.1/0000:16:00.2/0000:20:09.0/0000:2a:00.0': not supported by any plugin
May 04 17:29:59 myname-tower-cstm ModemManager[997]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.1/0000:16:00.2/0000:20:08.0/0000:29:00.0': not supported by any plugin
May 04 17:30:00 myname-tower-cstm sddm[1034]: Display server starting...
May 04 17:30:00 myname-tower-cstm sddm[1034]: Writing cookie to "/run/sddm/xauth_DXylMV"
May 04 17:30:00 myname-tower-cstm sddm[1034]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_DXylMV -noreset -displayfd 16
May 04 17:30:00 myname-tower-cstm sddm[1034]: Failed to read display number from pipe
May 04 17:30:00 myname-tower-cstm sddm[1034]: Display server stopping...
May 04 17:30:00 myname-tower-cstm sddm[1034]: Attempt 3 starting the Display server on vt 2 failed
May 04 17:30:00 myname-tower-cstm sddm[1034]: Could not start Display server on vt 2

As for a solution to the problem, I think it makes sensefor me to switch to the LTS kernel as my primary kernel. How do I change it to be the default, without just removing my other kernels outright? Thanks for your help.

Para trocar o kernel na inicialização, use o Garuda Boot Options

Boot to… Kernel (zen or LTS)

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.