Stuck on boot after update (for a few days)

Pasqui · 23 November 2024 09:00

Hi guys! For a couple of days now, if I run the update, when I reboot, it gets stuck after grub, in the screen where it loads the kernel.
I have to restore the previous snap every time
Any ideas?
Thank you!

System:
Kernel: 6.11.8-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=671de9f9-8ee6-4c92-a404-549bf7935a22 rw rootflags=subvol=@
psi=1 quiet loglevel=3 nvidia_drm.modeset=1 ibt=off
Desktop: KDE Plasma v: 6.2.3 tk: Qt v: N/A info: frameworks v: 6.8.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF GAMING X570-PLUS (WI-FI) v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 5013 date: 03/22/2024
CPU:
Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 0 microcode: 0xA20102B
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3600 min/max: 550/4851 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 3600 2: 3600 3: 3600
4: 3600 5: 3600 6: 3600 7: 3600 8: 3600 9: 3600 10: 3600 11: 3600 12: 3600
13: 3600 14: 3600 15: 3600 16: 3600 bogomips: 121603
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD104 [GeForce RTX 4070 Ti] vendor: ZOTAC driver: nvidia
v: 565.57.01 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-09) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
ports: active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3 bus-ID: 0a:00.0
chip-ID: 10de:2782 class-ID: 0300
Device-2: Microdia Dual Mode Camera (8006 VGA) driver: hid-generic,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:3
chip-ID: 0c45:8006 class-ID: 0301
Device-3: Sunplus Innovation Aukey-PC-LM1E Camera
driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 5-1:2 chip-ID: 1bcf:0215 class-ID: 0102
Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa gpu: nvidia
d-rect: 4480x2520 display-ID: 0
Monitor-1: DP-1 pos: top-right res: 2560x1440 size: N/A modes: N/A
Monitor-2: HDMI-A-1 pos: bottom-l res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: nvidia inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 565.57.01
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
memory: 11.71 GiB display-ID: :1.0
API: Vulkan v: 1.3.295 layers: 8 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 4070 Ti driver: nvidia v: 565.57.01 device-ID: 10de:2782
surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
18.1.8 256 bits) driver: mesa llvmpipe v: 24.2.7-arch1.1 (LLVM 18.1.8)
device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
Device-1: NVIDIA AD104 High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0a:00.1 chip-ID: 10de:22bc class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Sunplus Innovation Aukey-PC-LM1E Camera
driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 5-1:2 chip-ID: 1bcf:0215 class-ID: 0102
API: ALSA v: k6.11.8-zen1-2-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.6 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: Intel Wi-Fi 5 Wireless-AC 9x6x [Thunder Peak] driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0
chip-ID: 8086:2526 class-ID: 0280
IF: wlp5s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, sshd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel Wireless-AC 9260 Bluetooth Adapter driver: btusb v: 0.8
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-5:2
chip-ID: 8087:0025 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 10.01 TiB used: 612.87 GiB (6.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Smart Modular Tech.
model: SHPP41-1000GM 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: 51060A20 temp: 43.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Sabrent model: Rocket Q
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: RKT30Q.2 temp: 28.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000DM004-2CV104
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 04RL scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD40EFRX-68WT0N0 size: 3.64 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 0A82 scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 612.87 GiB (65.8%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 588 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:1
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 612.87 GiB (65.8%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 612.87 GiB (65.8%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 612.87 GiB (65.8%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 47.2 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.25 GiB used: 4.89 GiB (15.6%)
Processes: 384 Power: uptime: 9m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.45 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: 1904 pm: dpkg pkgs: 0 pm: pacman pkgs: 1896 libs: 525
tools: octopi,paru,yay pm: rpm pkgs: 0 pm: flatpak pkgs: 8 Compilers:
gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole
inxi: 3.3.36
Garuda (2.6.26-1):
System install date:     2024-01-21
Last full system update: 2024-11-17
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

SGS · 23 November 2024 09:42

Try,
Live ISO, chroot from Garuda welcome app, upd in terminal.
Exit terminal, reboot,

Pasqui · 23 November 2024 10:19

SGS · 23 November 2024 10:23

Try

sudo garuda-chroot -a
==> Detected systems:
 --> 0) Garuda_Linux
 --> 1) Garuda_Linux
==> Select system to mount [0-1] :

Check

efibootmgr

Btw. there is no need to post Screenshots from terminal text.
Images can be read worse, are not searchable and copyable for further search.

Pasqui · 23 November 2024 10:56

yes you’re right, I apologize
Anyway garuda-chroot -a answers me with:

grub-probe: error: cannot find a GRUB drive for /dev/sdd2.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdd2.  Check your device.map.
==> ERROR: No Linux partitions detected!

**efibootmgr**
BootCurrent: 0005
Timeout: 1 seconds
BootOrder: 0000,0002,0004,0005,0003
Boot0000* Garuda        HD(1,GPT,449b7fd2-e227-4e35-a6b2-bd7a4bff9ed6,0x1000,0x96000)/\EFI\GARUDA\GRUBX64.EFI
Boot0002* Windows Boot Manager  HD(1,GPT,8b7b9374-8d31-49d2-814a-03dac7d63665,0x800,0xfffc1)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI0000424f
Boot0003  UEFI OS       HD(1,GPT,449b7fd2-e227-4e35-a6b2-bd7a4bff9ed6,0x1000,0x96000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0004* UEFI:  USB DISK 3.0 PMAP, Partition 1 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x1)/USB(8,0)/HD(1,MBR,0x1bd3d81a,0x800,0xe734100)0000424f
Boot0005* UEFI:  USB DISK 3.0 PMAP, Partition 2 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x1)/USB(8,0)/HD(2,MBR,0x1bd3d81a,0xe734900,0x10000)0000424f

SGS · 23 November 2024 11:08

Live ISO, chroot,
install and update grub
Check

lsblk -f

look for /boot/efi and use /dev/sdd* it. Maybe it is sdd1 as example

grub-install /dev/
update-grub

Pasqui · 23 November 2024 11:29

ok, grub was a Ventoy related problem, flashed the ISO with Etcher but still chroot doesn’t detect any Linux partition.

lsblk -f
NAME FSTYPE FSVER LABEL                        UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
squash 4.0                                                                           0   100% /run/miso/sfs/livefs
loop1
squash 4.0                                                                           0   100% /run/miso/sfs/mhwdfs
loop2
squash 4.0                                                                           0   100% /run/miso/sfs/desktopfs
loop3
squash 4.0                                                                           0   100% /run/miso/sfs/rootfs
sda
└─sda1
ntfs         Ripostiglio                  01D75486E92A66E0
sdb
└─sdb1
ntfs         1000                         68FAE003FADFCB86
sdc
└─sdc1
ntfs         4000 RED                     EA5E01665E012CBF
sdd  iso966 Jolie GARUDA_DR460NIZED_BIRDOFPREY 2024-04-28-13-12-04-00
├─sdd1
│    iso966 Jolie GARUDA_DR460NIZED_BIRDOFPREY 2024-04-28-13-12-04-00                     0   100% /run/miso/bootmnt
└─sdd2
vfat   FAT12 MISO_EFI                     A76C-4900
zram0
[SWAP]
nvme1n1
│
├─nvme1n1p1
│    vfat   FAT32                              0220-C3D8
└─nvme1n1p2
btrfs                                     671de9f9-8ee6-4c92-a404-549bf7935a22
nvme0n1
│
├─nvme0n1p1
│    vfat   FAT32                              C760-5C28
├─nvme0n1p2
│
└─nvme0n1p3
ntfs         Windows                      0EEC3C56EC3C39F3

SGS · 23 November 2024 11:40

What are we talking about here?
Above it says stop when booting after update, now you’re talking about ventoy?

We don’t support dual boot with M$, apparently M$ deletes foreign OS, sorry @Ankur

I also no longer see any Btrfs on yours that used to be on sdd2.

I’m getting out of here.

dr460nf1r3 · 23 November 2024 12:49

This looks much like the partitions of the right drive? Might try passing it as parameter to chroot.

What’s the output when running the update? Are there any failed kernel module installations, e.g. for your Nvidia drivers?

Pasqui · 23 November 2024 17:05

that’s right, there is the block after the update.
I used Ventoy to boot the ISO from USB and I thought it was related to the problem of the undetected partitions. So I reflashed the ISO with Balena Etcher and the grub problem disappeared but not the others.
@dr460nf1r3 YEP! Now I noticed this error during the installation of the drivers:

Error! nvidia/545.29.06: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! nvidia/550.54.14: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! nvidia/550.78: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! nvidia/550.90.07: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! nvidia/555.58: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! nvidia/560.35.03: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! vboxhost/7.0.16_OSE: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! vboxhost/7.0.18_OSE: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! vboxhost/7.1.0_OSE: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!
==> dkms remove --no-depmod vboxhost/7.1.4_OSE -k 6.11.8-arch1-2

Error! nvidia/545.29.06: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! nvidia/550.54.14: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! nvidia/550.78: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! nvidia/550.90.07: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! nvidia/555.58: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! nvidia/560.35.03: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! vboxhost/7.0.16_OSE: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! vboxhost/7.0.18_OSE: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Error! vboxhost/7.1.0_OSE: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!

Pasqui · 24 November 2024 08:46

Nothing new, I tried uninstalling nvidia-dkms and virtualbox-host-dkms, removing the nvidia and vboxhost /var/lib/dkms folders and reinstalling just the nvidia drivers.
“dkms status” did not return any errors. I get to the sddm boot screen and it gets stuck.
Then I tried pacman -Syu in the tty… nothing.

Edit: looks like I’m not the only one having problems with 6.12

Jeshu · 25 November 2024 00:04

i have been having similar problems in the past with my RTX4080 card. i got two solutions you can try

RESTORE a SNAPSHOT, boot into LTS kernel if you got it. and then apply these solutions to see if that helps

Have you tried using this solution? It has worked for others with those problematic Nvidia cards

sudo pacman -R garuda-nvidia-config garuda-nvidia-prime-config && sudo pacman -S nvidia-open-dkms

The follow solution the Garuda team does not recommend, but it has saved my installation a few times already, without any other problematic issues so far.

This solution means downloading nvidia-all drivers from git, which will give you options to choose between different versions, and so try different versions than the latest one. The trick, when using this solution, is to watch your terminal while compiling the dkms modules, and if no errors are thrown up, that particular version ought to be fit for usage. You can also choose between open source or proprietary drivers.

git clone https://github.com/Frogging-Family/nvidia-all.git
cd nvidia-all
makepkg -si
sudo dracut-rebuild
sudo update-grub

cheers

Pasqui · 28 November 2024 16:52

it does not work…

Jeshu · 28 November 2024 19:28

have you tried

sudo garuda-update remote fix

Pasqui · 29 November 2024 07:41

yes, I had already tried it, I tried changing drivers, kernel, updating individually after removing the dkms… nothing.
In those few times that it managed to start (with each of the various tests) the second monitor was not recognized and the first had a resolution of 1024x768 without the possibility of choosing others.
I read on the Nvidia forum about the 565 and the 6.12 kernel and the problems are multiple.

Jeshu · 29 November 2024 07:48

Yet i got my RTX4080 to run on the linux 6.12.1.arch1-1 kernel and the latest 565 driver without any problems so far.

i reinstalled the original drivers with (for i used 560 Nvidia drivers through the nvidia-all package. To see if i could get a kernel to run like that.)

sudo pacman -Rdd lib32-nvidia-utils-tkg lib32-opencl-nvidia-tkg nvidia-dkms-tkg nvidia-egl-wayland-tkg nvidia-settings-tkg nvidia-utils-tkg opencl-nvidia-tkg

And then ran

garuda-update remote fix

worked for me, it might work for you.

LolFlasherNoobX · 29 November 2024 08:13

Perhaps try dracut --regenerate-all --force in the chroot ?

Pasqui · 29 November 2024 08:22

did you read at the beginning of the post about chroot?

LolFlasherNoobX · 29 November 2024 09:12

Sorry but I do not see any commands with dracut, might just be me. Try a different kernel as well perhaps ?

Pasqui · 29 November 2024 09:36

being quite noob, I fought until I entered the chroot, ran update, but nothing solved.
I tried with vanilla kernel, zen, cachy…