System fails to load after update

Hello Garuda Forum

Please go easy on me

System:    Kernel: 5.12.12-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0 
parameters: BOOT_IMAGE=/timeshift-btrfs/snapshots/2021-07-02_00-18-49/@/boot/vmlinuz-linux-zen 
root=UUID=3da14aaf-cef6-4bda-9bc1-b175d6ed4910 quiet splash rd.udev.log_priority=3 
vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 
resume=UUID=4019ab13-02ed-4dc3-892e-81ce8c46b230 loglevel=3 
rootflags=defaults,noatime,space_cache,autodefrag,compress=zstd,subvol=timeshift-btrfs/snapshots/2021-07-02_00-18-49/@ 
Desktop: KDE Plasma 5.22.2 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM 
Distro: Garuda Linux base: Arch Linux 
Machine:   Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF serial: <filter> 
Mobo: Gigabyte model: X570 AORUS ELITE v: x.x serial: <filter> UEFI: American Megatrends LLC. 
v: F33c date: 02/17/2021 
CPU:       Info: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 family: 17 (23) 
model-id: 71 (113) stepping: 0 microcode: 8701021 cache: L2: 6 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 182055 
Speed: 3592 MHz min/max: 2200/3800 MHz boost: disabled Core speeds (MHz): 1: 3592 2: 3596 
3: 3587 4: 3587 5: 3584 6: 3596 7: 3591 8: 3588 9: 3201 10: 3572 11: 3657 12: 3590 13: 3592 
14: 3372 15: 3586 16: 3581 17: 3620 18: 3597 19: 3594 20: 3588 21: 3667 22: 3040 23: 3033 
24: 3584 
Vulnerabilities: Type: itlb_multihit status: Not affected 
Type: l1tf status: Not affected 
Type: mds status: Not affected 
Type: meltdown status: Not affected 
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
Type: spectre_v2 
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling 
Type: srbds status: Not affected 
Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP104 [GeForce GTX 1070 Ti] vendor: Micro-Star MSI driver: nvidia v: 465.31 
alternate: nouveau,nvidia_drm bus-ID: 08:00.0 chip-ID: 10de:1b82 class-ID: 0300 
Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: nvidia 
unloaded: modesetting alternate: fbdev,nouveau,nv,vesa display-ID: :0 screens: 1 
Screen-1: 0 s-res: 1920x1080 s-dpi: 93 s-size: 524x292mm (20.6x11.5") s-diag: 600mm (23.6") 
Monitor-1: DVI-D-0 res: 1920x1080 dpi: 94 size: 521x293mm (20.5x11.5") diag: 598mm (23.5") 
OpenGL: renderer: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 465.31 
direct render: Yes 
Audio:     Device-1: NVIDIA GP104 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel 
v: kernel bus-ID: 08:00.1 chip-ID: 10de:10f0 class-ID: 0403 
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel 
bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403 
Device-3: Logitech [G533 Wireless Headset Dongle] type: USB 
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-4:3 chip-ID: 046d:0a66 class-ID: 0300 
Sound Server-1: ALSA v: k5.12.12-zen1-1-zen running: yes 
Sound Server-2: JACK v: 0.125.0 running: no 
Sound Server-3: PulseAudio v: 14.2 running: yes 
Sound Server-4: PipeWire v: 0.3.30 running: yes 
Network:   Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel port: f000 
bus-ID: 04:00.0 chip-ID: 8086:1539 class-ID: 0200 
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 651.49 GiB (69.9%) 
SMART Message: Unable to run smartctl. Root privileges required. 
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Gigabyte model: GP-ASM2NE6100TTTD size: 931.51 GiB 
block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 rotation: SSD 
serial: <filter> rev: EGFM13.0 scheme: GPT 
Partition: ID-1: / raw-size: 914.06 GiB size: 914.06 GiB (100.00%) used: 651.49 GiB (71.3%) fs: btrfs 
dev: /dev/nvme0n1p2 maj-min: 259:2 
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 546 KiB (0.2%) fs: vfat 
dev: /dev/nvme0n1p1 maj-min: 259:1 
ID-3: /home raw-size: 914.06 GiB size: 914.06 GiB (100.00%) used: 651.49 GiB (71.3%) fs: btrfs 
dev: /dev/nvme0n1p2 maj-min: 259:2 
ID-4: /var/log raw-size: 914.06 GiB size: 914.06 GiB (100.00%) used: 651.49 GiB (71.3%) 
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2 
ID-5: /var/tmp raw-size: 914.06 GiB size: 914.06 GiB (100.00%) used: 651.49 GiB (71.3%) 
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2 
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100) 
ID-1: swap-1 type: partition size: 17.19 GiB used: 0 KiB (0.0%) priority: -2 
dev: /dev/nvme0n1p3 maj-min: 259:3 
ID-2: swap-2 type: zram size: 666.9 MiB used: 21.2 MiB (3.2%) priority: 32767 dev: /dev/zram0 
ID-3: swap-3 type: zram size: 666.9 MiB used: 19.3 MiB (2.9%) priority: 32767 dev: /dev/zram1 
ID-4: swap-4 type: zram size: 666.9 MiB used: 19.2 MiB (2.9%) priority: 32767 dev: /dev/zram2 
ID-5: swap-5 type: zram size: 666.9 MiB used: 17.6 MiB (2.6%) priority: 32767 dev: /dev/zram3 
ID-6: swap-6 type: zram size: 666.9 MiB used: 17.7 MiB (2.7%) priority: 32767 dev: /dev/zram4 
ID-7: swap-7 type: zram size: 666.9 MiB used: 21 MiB (3.2%) priority: 32767 dev: /dev/zram5 
ID-8: swap-8 type: zram size: 666.9 MiB used: 17.4 MiB (2.6%) priority: 32767 dev: /dev/zram6 
ID-9: swap-9 type: zram size: 666.9 MiB used: 17.5 MiB (2.6%) priority: 32767 dev: /dev/zram7 
ID-10: swap-10 type: zram size: 666.9 MiB used: 17.6 MiB (2.6%) priority: 32767 dev: /dev/zram8 
ID-11: swap-11 type: zram size: 666.9 MiB used: 18.9 MiB (2.8%) priority: 32767 dev: /dev/zram9 
ID-12: swap-12 type: zram size: 666.9 MiB used: 17.5 MiB (2.6%) priority: 32767 
dev: /dev/zram10 
ID-13: swap-13 type: zram size: 666.9 MiB used: 19.5 MiB (2.9%) priority: 32767 
dev: /dev/zram11 
ID-14: swap-14 type: zram size: 666.9 MiB used: 17.9 MiB (2.7%) priority: 32767 
dev: /dev/zram12 
ID-15: swap-15 type: zram size: 666.9 MiB used: 17.1 MiB (2.6%) priority: 32767 
dev: /dev/zram13 
ID-16: swap-16 type: zram size: 666.9 MiB used: 18.7 MiB (2.8%) priority: 32767
dev: /dev/zram14
ID-17: swap-17 type: zram size: 666.9 MiB used: 18.4 MiB (2.8%) priority: 32767
dev: /dev/zram15
ID-18: swap-18 type: zram size: 666.9 MiB used: 16.3 MiB (2.4%) priority: 32767
dev: /dev/zram16
ID-19: swap-19 type: zram size: 666.9 MiB used: 17.7 MiB (2.7%) priority: 32767
dev: /dev/zram17
ID-20: swap-20 type: zram size: 666.9 MiB used: 19.7 MiB (3.0%) priority: 32767
dev: /dev/zram18
ID-21: swap-21 type: zram size: 666.9 MiB used: 17.8 MiB (2.7%) priority: 32767
dev: /dev/zram19
ID-22: swap-22 type: zram size: 666.9 MiB used: 20.8 MiB (3.1%) priority: 32767
dev: /dev/zram20
ID-23: swap-23 type: zram size: 666.9 MiB used: 18.3 MiB (2.7%) priority: 32767
dev: /dev/zram21
ID-24: swap-24 type: zram size: 666.9 MiB used: 20.3 MiB (3.0%) priority: 32767
dev: /dev/zram22
ID-25: swap-25 type: zram size: 666.9 MiB used: 20.2 MiB (3.0%) priority: 32767
dev: /dev/zram23
Sensors:   System Temperatures: cpu: 36.2 C mobo: 16.8 C gpu: nvidia temp: 35 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 44%
Info:      Processes: 466 Uptime: 5m wakeups: 0 Memory: 15.63 GiB used: 3.39 GiB (21.7%) Init: systemd
v: 248 tool: systemctl Compilers: gcc: 11.1.0 Packages: apt: 0 pacman: 1645 lib: 488
Shell: fish v: 3.2.2 running-in: konsole inxi: 3.3.04


I am a newbie to Linux (windows for 20 years) and Garuda is my first distro, I am running 2 machines that I built and I have been doing ok over the last 12 months learning as I go, and usually I am able to resolve any issues I encounter.

For the last month or so my second PC , would not load after the latest updates, so I used a snapshot to restore then I would update again and the same issue would return - stuck at loading. I have been putting off fixing this, but I couldn't leave it...

So today after loading the latest snapshot I used the commands

sudo mkinitcpio -P
sudo grub-mkconfig -o /boot/grub/grub.cfg

And rebooted.

I think I have made the problem worse and now the recent snapshots will not load at all - only the oldest one, which is over 5 months old and now there is no network ....

I'm not sure where to start any assistance would be appreciated.

EDIT: To be clear - I have been trying to fix this for weeks, and I am ok with that - I was able to load any snapshot before today but now I think I have made it worse, and so decided to ask for help.

1 Like

image :grinning:
boot from live iso and open garuda chroot to chroot into system. update the system(sudo pacman -Syu) and try opening garuda boot repair and try reinstalling grub.

1 Like

One more thing I forgot to include,

at the loading screen I can login using ALT + CTRL +F2 and gain access , and here it is Kernel: 5.14.6-zen1-1-zen and not Kernel: 5.12.12-zen1-1-zen

Can I try to repair grub from there?

If it's a driver mismatch, then Computer doesn’t boot, boots to a black screen, or stops at a message

If you're using SDDM and NVIDIA, there seems to be an issue with 470.74's Wayland implementation.

Yes, though if you can boot then GRUB isn't the issue.

2 Likes

@broisthisfake thanks for this advice I am planning to do this this as a last resort

If it's a driver mismatch, then Computer doesn’t boot, boots to a black screen, or stops at a message

@jonathon thankyou, Ok I have tried the advice in the link, and after

sudo reflector -a6 -f5 --save /etc/pacman.d/mirrorlist

sudo pacman -Syyu

there was a conflict with ananicy as per this thread

I followed the instructions and was able to update, but after the restart the issue remains and back at loading initial ram disk.

I tried startx , the result -

xinit: giving up
xinit: unable to connect to x server: connection refused
xinit: server error

I tried the DKMS , the result -

error! could not locate dkms.conf file
File: /var/lib/dkms/nvidia456.24 02/source/dkms.conf does not exist

This is likely separate to the actual issue (SDDM and Wayland), but you can clean out old DKMS drivers and links and fix that error message:

1 Like

Sorry for the format, I had to copy this across..

ls -l /var/lib/dkms/*
.rw-r--r-- 6 root 13 Sep 04:32  /var/lib/dkms/dkms_dbversion

/var/lib/dkms/nvidia:
drwxr-xr-x - root 1 May 13:58  465.24.02
drwxr-xr-x - root 04 Oct 10:42  465.31
lrwxrwxrwx 35 root 24Apr 10:43  kernel-5.11.11-zen1-1-zen-x86_64 -> 465.24.02/5.11.11-zen1-1-zen/x86_64
drwxr-xr-x - root 16 Aug 14:23  original_module

/var/lib/dkms/zenpower:
drwxr-xr-x - root 04 Oct 10:42  0.1.12
lrwxrwxrwx 31 root 04 Oct 10:42  kernel-5.14.8-zen1-1-zen-x86_64 -> 0.1.12/5.14.8-zen1-1-zen/x86_64

Is the only solution to get a working desktop to wait until October 11th for the new driver?

Is there a way to downgrade driver whilst in TTY? or is there a way to install another kernel so that I can get the desktop back again?

From the tty I followed the advice again in the link and was able to do a full system update after using the command

update

After a reboot the DM will still not start although I can see now the kernel has updated to
5.14.9-zen2-1-zen

@jonathon I have followed the advice in the thread you linked, but I was unable to remove the drivers in ls -l /var/lib/dkms/*

sudo rm -fr 465.24.02 465.31 kernel-5.11.11-zen1-1-zen-x86_64 -> 465.24.02/5.11.11-zen1-1-zen/x86_64

but they are still there

ls -l /var/lib/dkms/*
/var/lib/dkms/nvidia:
drwxr-xr-x - root 1 May 13:58  465.24.02
drwxr-xr-x - root 04 Oct 10:42  465.31
lrwxrwxrwx 35 root 24Apr 10:43  kernel-5.11.11-zen1-1-zen-x86_64 -> 465.24.02/5.11.11-zen1-1-zen/x86_64
drwxr-xr-x - root 16 Aug 14:23  original_module

After this i tried

sudo pacman -R nvidia-dkms

and received this

target not found:nvidia-dkms

Im not sure how to proceed from here - I could chroot in but I would like to try to solve the problem.

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

3 Likes

That command won't do anything useful. Look at its components and trace through what you're asking it to do.

Or, use this instead:

cd /var/lib/dkms/nvidia
sudo rm -fr 465.24.02 kernel-5.11.11-zen1-1-zen-x86_64

If you don't have the Nvidia driver version 465.31 installed then you could also delete that directory, but check that before you do.

3 Likes

@filo thankyou for your reply, I have installed that ok and it updated the nvidia drivers but im still back at tty2

@jonathon thankyou for your reply and for being patient, I realized when I read your reply back what I was doing wrong, I didn't change the directory -

Here is the output below -it removed both the entries
rwxr-xr-x - root 1 May 13:58  465.24.02
drwxr-xr-x - root 04 Oct 10:42  465.31

ls -l /var/lib/dkms/*

drwxr-xr-x - root 16 Aug 14:23  original_module

/var/lib/dkms/zenpower:
drwxr-xr-x - root 04 Oct 10:42  0.1.12
lrwxrwxrwx 31 root 04 Oct 10:42  kernel-5.14.8-zen1-1-zen-x86_64 -> 0.1.12/5.14.8-zen1-1-zen/x86_64

I was reading in this thread,is this maybe related to my problem?

To me this seems to be a desktop manager issue? KDE?

Or are there some cleaning commands I could try on Xorg?

Actually, the more incorrect part was trying to delete a file called

which is indicating a symbolic link.

Given you now don't have any Nvidia DKMS drivers on the system, I'd try reinstalling the package

sudo pacman -Syu nvidia-dkms

and pay attention to any messages in the output.

3 Likes

Thankyou!

I get the message :

nvidia-utils and nvidia-utils-tkg are in conflict . Remove nvidia-utils-tkg? Y

nvidia-dkms and nvidia-dkms-tkg are in conflict. remove?Y

error :failed to prepare transaction(could not satisfy dependencies)
removing nvidia-dkms-tkg breaks dependency " nvidia-dkms-tkg" required by lib32-nvidia-dkms-tkg
removing nvidia-dkms-tkg breaks dependency " nvidia-dkms-tkg" required by nvidia-egl-wayland-tkg
removing nvidia-dkms-tkg breaks dependency " nvidia-dkms-tkg>=465.31 required by nvidia-settings-tkg

1 Like

OK, so the nvidia-dkms-tkg driver will only work with the linux-tkg kernel - it won't work with linux-zen.

So, let's force removal to replace with a working driver package:

sudo pacman -Rdd nvidia-utils-tkg nvidia-dkms-tkg lib32-nvidia-dkms-tkg nvidia-egl-wayland-tkg nvidia-settings-tkg
sudo pacman -S nvidia-dkms
6 Likes

first command threw an error with

lib32-nvidia-dkms-tkg : not found

so , it was removed and ran again with success

second command was a success

there are new .pac files , to me this looks the most promising so far , I will now reboot

Ok Success!!!!

Edit:

Thankyou @jonathon sincerely for your time and patience.

Thankyou to everyone in the Garuda Project for what you have created

1 Like

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