System stuck in boot screen

Issues & Assistance
1

I just did "garuda-update", after the downloading part finished I typed "shutdown -r 10" into a new window and then I went afk to eat dinner. After I got back my system was stuck on a black screen with the error message 'setfont: KDFONTOP: Function not implemented'.

I was shutting off my pc and turned it back on, after I selected a boot option my system ever just returned to the error screen. Snapshot recovery are resulting in the same outcome. 'GRUB Commandline' and 'Garuda Linux, with Linux linux-zen (recovery mode)' are the only working things, but I don't know what to do with it. The error message 'setfont: KDFONTOP: Function not implemented' already appeared before today and ignoring it wasn't causing any problems til now.

garuda-inxi:

driver: rtu89 8852ae v: kernel modules: rtu_8852ae pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e888 bus-ID: 04:08.8 chip-ID: 18ec:8852 class-10: 8288

IF: ulp4s8 state: down mac:

Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d888 bus-10: 85:88.8 chip-10: 18ec:8168 class-ID: 8280

IF: enp5s8 state: down mac: Bluetooth:

Device-1: Realtek Bluetooth Radio driver: btusb v: 8.8 type: USB rev: 1.8 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-18:6 chip-ID: 8bda: 4852 class-ID: e001 serial: Report: bt-adapter ID: hci0 rfk-id: 1 state: up address:

Drives: Local Storage: total: 477.88 GiB used: 385.33 GiB (88.6%)

ID-1: /dev/nvme8n1 maj-min: 259:8 vendor: Samsung model: MZVL2512HCJQ-88BL7 size: 476.94 GiB block-size: physical: 512 B logical: 512 8 speed: 63.2 Gb/s lanes: 4 tech: SSD serial: fu-rev: AL206XA7 temp: 41.9 C scheme: GPT SMART: yes health: PASSED on: 17d 18h cycles: 495 read-units: 32,422,874 [16.6 TB]

written-units: 9,314,458 [4.76 TB]

ID-2: /dev/sda maj-min: 8:0 vendor: Generic model: Flash Disk size: 968 MiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.8 spd: 488 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: fu-rev: 8.87 scheme: MBR

SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?

Partition:

ID-1: /raw-size: 128 GiB size: 128 GiB (188.88%) used: 48.48 618 (48.4%) fs: btrfs block-size: 4096 B dev: /dev/nvmeBnip3 maj-min: 259:3

block-size: 512 B dev: /dev/nvme@nip1 maj-min: 259:1 ID-3: /home raw-size: 348.6 618 size: 348.6 GiB (188.88%) used: 336.85 GiB (98.9%) fs: btrfs

ID-2: /boot/efi rau-size: 512 MiB size: 511 MiB (99.88%) used: 576 KiB (8.1%) fs: vfat block-size: 4896 8 dev: /dev/nvme8n1p3 maj-min: 259:3 ID-5: /var/tmp rau-size: 128 GiB size: 128 GiB (188.88%) used: 48.48 GiB (48.4%) fs: btrfs block-size: 4896 B dev: /dev/nvme8n1p3 maj-min: 259:3

block-size: 4896 B dev: /dev/nvme8n1p4 maj-min: 259:4 ID-4: /var/log rau-size: 128 GiB size: 128 GiB (188.88%) used: 48.48 GiB (48.4%) fs: btrfs

Swap:

Kernel: swappiness: 133 (default 68) cache-pressure: 180 (default) ID-1: swap-1 type: zran size: 15.46 GiB used: 8 KiB (0.8%) priority: 100 dev: /dev/zramB ID-2: swap-2 type: partition size: 15.83 GiB used: 8 KiB (0.8%) priority: -2 dev: /dev/nvae8n1p2 maj-min: 259:2 Sensors:

System Temperatures: cpu: 54.2 C mobo: N/A gpu: nvidia temp: 33 C Fan Speeds (RPM): N/A Info:

Processes: 242 Uptime: 8n wakeups: 2 Memory: available: 15.46 GiB used: 720.9 MiB (4.6%) Init: systemd v: 253 default: graphical tool: systemctl Compilers: gcc: 13.1.1 clang: 15.8.7 Packages: 1762 pm: pacman pkgs: 1756 libs: 586 tools: octopi,paru pm: flatpak pkgs: 6 Shell: Bash v: 5.1.16 running-in: tty 1 inxi: 3.3.27 Garuda (2.6.16-1):

System install date: 2822-12-28 Last full system update: 2823-86-28

Is partially upgraded: No

Relevant software:
snapper akinitcpio nvidia-dkes

Windows dual boot:
No/Undetected

Failed units:

[root@stk-98rc88f4ge "1#

2

I accidentally typed exit because I didn't knew how to get out of the recovery-screen and it so happened that it caused my PC to boot normally (I got into the login screen).

I immediately rebooted to see if the problem was fixed, but it wasn't. Apparently I can go around my problem by going to recovery -> exit but the normal boot doesn't work.

But now I can at least show a proper garuda-inxi output (as before I had to make a picture of my screen and let Google Lens help me...)

System:
Kernel: 6.3.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=b7f5747e-8e0d-4c8c-a714-9103e07d590b rw single
rootflags=subvol=@
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: LENOVO product: 90RC00F4GE v: Legion T5 26AMR5
serial: <superuser required> Chassis: type: 3 serial: <superuser required>
Mobo: LENOVO model: 3716 serial: <superuser required> UEFI: LENOVO
v: O4MKT1DA date: 04/14/2021
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
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: 0xA50000B
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: 3519 high: 3900 min/max: 1400/3900 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3214 2: 3076
3: 3179 4: 3900 5: 3900 6: 3204 7: 3900 8: 2993 9: 3900 10: 3900 11: 3167
12: 3900 bogomips: 93426
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060] vendor: Lenovo driver: nvidia
v: 535.54.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
status: current (as of 2023-05) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.0 chip-ID: 10de:2503
class-ID: 0300
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x1080 s-dpi: 91 s-size: 1003x301mm (39.49x11.85")
s-diag: 1047mm (41.23")
Monitor-1: DP-0 pos: primary,right res: 1920x1080 hz: 60 dpi: 93
size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
Monitor-2: HDMI-0 pos: left res: 1680x1050 hz: 60 dpi: 267
size: 160x90mm (6.3x3.54") diag: 184mm (7.23") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 535.54.03 renderer: NVIDIA GeForce RTX
3060/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: NVIDIA GA106 High Definition Audio vendor: Lenovo
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: 01:00.1 chip-ID: 10de:228e
class-ID: 0403
Device-2: AMD Renoir Radeon High Definition Audio vendor: Lenovo
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: 07:00.1 chip-ID: 1002:1637
class-ID: 0403
Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo 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: 07:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-4: Generalplus Usb Microphone
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-2:3 chip-ID: 1b3f:2008 class-ID: 0300
API: ALSA v: k6.3.9-zen1-1-zen 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: 0.3.71 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: Realtek RTL8852AE 802.11ax PCIe Wireless Network Adapter
vendor: Lenovo driver: rtw89_8852ae v: kernel modules: rtw_8852ae pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 04:00.0
chip-ID: 10ec:8852 class-ID: 0280
IF: wlp4s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:6 chip-ID: 0bda:4852
class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
Local Storage: total: 477.88 GiB used: 385.34 GiB (80.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVL2512HCJQ-00BL7 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: AL2QGXA7 temp: 39.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Generic model: Flash Disk
size: 960 MiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.0
spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter> fw-rev: 8.07
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 120 GiB size: 120 GiB (100.00%) used: 48.49 GiB (40.4%)
fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 576 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 340.6 GiB size: 340.6 GiB (100.00%)
used: 336.85 GiB (98.9%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
ID-4: /var/log raw-size: 120 GiB size: 120 GiB (100.00%)
used: 48.49 GiB (40.4%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-5: /var/tmp raw-size: 120 GiB size: 120 GiB (100.00%)
used: 48.49 GiB (40.4%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.46 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 15.83 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p2 maj-min: 259:2
Sensors:
System Temperatures: cpu: 44.0 C mobo: N/A gpu: nvidia temp: 33 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 32%
Info:
Processes: 354 Uptime: 2m wakeups: 2 Memory: available: 15.46 GiB
used: 4.08 GiB (26.4%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7 Packages: 1762
pm: pacman pkgs: 1756 libs: 506 tools: octopi,paru pm: flatpak pkgs: 6
Shell: fish v: 3.6.1 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.27
Garuda (2.6.16-1):
System install date:     2022-12-28
Last full system update: 2023-06-28
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:
3

For this, you could try this:

But there might be something else.
If necessary, try also this:

3 Likes
4

Thx for your help, I solved the setfont-issue, but the boot still wasn’t working.
I then tried your second suggestion and the first part (removing splash) worked fine.
But could you please specify what you mean by

“You can replace plymouth-git with plymouth and not remove splash.”

1 Like
5

Please search the forums, this has been solved and addressed in multiple threads. Here is one example that explains plymouth vs plymouth-git: System wont start after update - #12 by Kottonballs

3 Likes
6

Sorry I just was confused a lot since I'm not into this stuff. Actually never heard plymouth or plymouth-git ever before today. I just read that I might not even have plymouth-git installed and as I checked it, I realised I haven't.
So for me removing splash from the Garuda Boot Options is the solution.

2 Likes
7

I completely understand and no need to apologize. I just wanted you to be aware of the other discussions. :slight_smile:

Removing splash or changing to pymouth can be a solution. I'm stubborn and wanted to help the devs so I stuck it out and gave some logs. We'll see. :slight_smile:

1 Like
8

Can you forward those logs to the plymouth devs as well? I am just saying because there doesn't seem to be an active issue registered on their gitlab repo regarding this which is weird... (Or I am just wrong about it :expressionless:)

1 Like
9

Correct. But there is this one in sddm which seems to be related.
Issues always occurred to sddm users. Not necessarily a sddm 0.20 issue, but probably in how Plymouth interacts with sddm, either due to a recent commit only or also due to changes in the sddm update.

3 Likes
10

I'd be happy to forward the logs if you want me to, or I can attach my log to that SDDM case, up to you guys. I'm not sure how to do either but can try to figure it out.

11

I guess since the log is plymouth related we should open an issue in plymouth's gitlab repo (link above). Tell them that the recent update of plymouth-git renders us unable to boot into the system give them the log, our inxi and tell them that it's reproduce able for atleast all garuda linux users since I have yet to see any complaints on this package's AUR repo except maybe this

https://aur.archlinux.org/packages/plymouth-git#comment-919951

4 Likes
12

My first ever issue report in Git. I hope I didn’t screw it up (still learning): https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/215

7 Likes
13

Looks fine :+1:

3 Likes
14

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