Boot issue after update

[fnt]

Hello!

I've been reading the forum for the past couple hours and noticed some people having similar issues to mine, regarding booting afther updating the system. However, some people couldn't solve it and some others did but the issue was slightly different. So, to go into detail...

I did a full update two days ago (july 4), shut off my pc after work and today it wouldn't boot past:

"Loading Linux linux-zen
Loading initial ramdisk"

After a quick google search I restored the system from a previous snapshot and everything seems normal now. However, I got a notification asking to update the system again, after restoring from the snapshot. My question is: wouldn't that make the booting issue come back?

Granted, my last update was 2 days ago, maybe whatever was broken is now fixed, but I just don't want to go into unnecesary risks.

Here's my inxi:

System:
Kernel: 6.3.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=4f8eb6de-fef8-4543-880e-2f2c837257bc rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=2e046cc7-773f-462e-8451-57e8d63aa103 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 1
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: AB350M-HDV serial: <superuser required>
UEFI: American Megatrends v: P4.40 date: 01/03/2018
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M280/320/275
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 3 2200G with Radeon Vega Graphics bits: 64 type: MCP
arch: Zen level: v3 note: check built: 2017-19 process: GF 14nm
family: 0x17 (23) model-id: 0x11 (17) stepping: 0 microcode: 0x8101004
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB
desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
desc: 1x4 MiB
Speed (MHz): avg: 1980 high: 2300 min/max: 1600/3500 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1875 2: 2076
3: 1669 4: 2300 bogomips: 27948
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 730] vendor: eVga.com. driver: nvidia
v: 470.182.03 alternate: nouveau,nvidia_drm non-free: series: 470.xx+
status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx
process: TSMC 28nm built: 2012-18 pcie: gen: 2 speed: 5 GT/s lanes: 8
bus-ID: 10:00.0 chip-ID: 10de:1287 class-ID: 0300
Device-2: AMD Raven Ridge [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm
built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 38:00.0
chip-ID: 1002:15dd class-ID: 0300 temp: 34.0 C
Device-3: Generalplus GENERAL WEBCAM driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:3
chip-ID: 1b3f:2247 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: nvidia,amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 81 s-size: 602x343mm (23.70x13.50")
s-diag: 693mm (27.28")
Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 82
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 470.182.03 renderer: NVIDIA GeForce GT
730/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: NVIDIA GK208 HDMI/DP Audio vendor: eVga.com. driver: snd_hda_intel
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 10:00.1
chip-ID: 10de:0e0f class-ID: 0403
Device-2: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 38:00.1
chip-ID: 1002:15de class-ID: 0403
Device-3: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 38:00.6
chip-ID: 1022:15e3 class-ID: 0403
Device-4: Generalplus GENERAL WEBCAM driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:3
chip-ID: 1b3f:2247 class-ID: 0102 serial: <filter>
API: ALSA v: k6.3.8-zen1-1-zen status: kernel-api tools: N/A
Server-1: 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 RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: e000 bus-ID: 25:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp37s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:4 chip-ID: 0bda:8771
class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 1 TiB used: 33.33 GiB (3.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 70.5 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37120G
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: B1E1 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: HD502HJ
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 0001 scheme: MBR
Partition:
ID-1: / raw-size: 102.69 GiB size: 102.69 GiB (100.00%)
used: 33.33 GiB (32.5%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 102.69 GiB size: 102.69 GiB (100.00%)
used: 33.33 GiB (32.5%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 102.69 GiB size: 102.69 GiB (100.00%)
used: 33.33 GiB (32.5%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 102.69 GiB size: 102.69 GiB (100.00%)
used: 33.33 GiB (32.5%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 6.7 GiB used: 537 MiB (7.8%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sdb3 maj-min: 8:19
Sensors:
System Temperatures: cpu: 34.1 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: nvidia screen: :0.0 temp: 52 C fan: 40% device: amdgpu
temp: 34.0 C
Info:
Processes: 245 Uptime: 43m wakeups: 11 Memory: available: 6.7 GiB
used: 3.13 GiB (46.7%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 13.1.1 Packages: pm: pacman pkgs: 1342
libs: 412 tools: octopi,paru 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:     2023-05-17
Last full system update: 2023-06-20
Is partially upgraded:   Yes
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

Thanks in advance!

[Bro]

I don't recall exactly what the "recommended" fix is, but it sounds like a possible kernel regression (it can happen--this is leading edge stuff). What I would do are three things, assuming you're still in the restored session and haven't done anything else, yet.

• I would go ahead and update, so I didn't end up in a possible partial update situation.
• Then I would install the LTS kernel and headers:
  # pacman -S linux-lts linux-lts-headers
• I don't have anything Nvidia, so if you normally have to bring in anything regarding them, you'll either have to await further guidance from an Nvidia aficionado, or hoof it yourself.

When you are done, reboot, choose Advanced and boot into the Linux LTS kernel and see what happens. But I do believe it's the LTS kernel folks have been installing/running. And, who knows, it may have been fixed by now. It can happen that fast in Archlandia.

regards

[filo]

I think we have good chances to solve the issue with the linux-lts.
See all the recent comments in the AUR package site. A patch is also suggested in the second page, but there are so many comments after to read... I hope the maintainer will take care of this.
https://aur.archlinux.org/packages/nvidia-470xx-dkms
Don't forget to install also the headers:

sudo pacman -S linux-lts linux-lts-headers

And to select that kernel in the GRUB, normally under Advanced options.

[NaN]

@fnt

quiet quiet splash

Remove the splash kernel parameter from grub and you will be able to boot. To make the change permanent upon booting into the system goto garuda boot options and remove the parameter from there as well.

To learn more on how to do that visit here:

Booting and input issues after update

We still don't know if that's your problem, so I suggest that you first test the removed splash on a single boot (not permanent). This should be done when your system is updated, so unbootable, of course. When you are in the grub line that you want to use, press button E, go to the line starting with linux and remove splash, then CTRL+x If it works (you can boot), you can easily set this as permanent with the Garuda Boot Options tool in the Kernel parameters field. Or, at that point, you can …

[fnt]

Thank you for answering!

I'm updating right now, I'll try the splash solution first and if that doesn't do it, I'll install the LTS-Kernel.

I'll update you as soon as I can. Thanks again!

[filo]

When the system is updated the removal of splash is now performed by the garuda-migrations package.
You should see a message about it.

garuda-linux/packages/stable-pkgbuilds/garuda-migrations/-/blob/master/garuda-migrations-runner#L114

[fnt]

This did it! I'm booted into the LTS right now, and everything seems to be working just fine.

One more question before I marked this as solved. From now on, will I boot directly into the LTS or do I have to manually select it each time?

[filo]

You will have to select it manually.
Or you can apply this procedure:

How do you set a kernel to default

Defining a new default kernel has some known bugs with btrfs (if you search in the forum you'll find several topics about it). So, you should edit /etc/default/grub and change GRUB_DEFAULT=0 (which is the first line you see in the GRUB main menu, numbering starts from 0 in GRUB) to e.g. GRUB_DEFAULT=1 (second line in GRUB main menu) or whatever else. If you need to select an entry into a "sub-menu" you can use e.g. GRUB_DEFAULT="1>2" which means go into the submenu in line 2 of the main GRUB me…

Or you can use the tool garuda-boot-options, field “Boot to”, don’t ue field “Enable saving last boot choice”.

[fnt]

Thank you so much! I'll get to it