Graphic drivers and boot issues

Hello, I'm currently experiencing an issue as I update the system.

It happened to me that after doing an update and booting Garuda it would load as usual until it asks me to select what to boot, then a full black screen appeared with a prompt to insert login and password, I managed to login but then I couldn't do much.

Doing some generic research I found it might be an issue where some drivers don't load, but I'm not sure if that's the case.

Here I'll insert the inxi of a snapshot I did, this is the latest working version for me, updating it gives me issues at login where the display where I'd type my password doesn't appear...

System:
Kernel: 6.2.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=1b38e87f-3760-49b3-866d-731b5f0b0a33 rw [email protected]
quiet
cryptdevice=UUID=9074fab6-463a-46ea-a0e4-f3e75f597eae:luks-9074fab6-463a-46ea-a0e4-f3e75f597eae
root=/dev/mapper/luks-9074fab6-463a-46ea-a0e4-f3e75f597eae quiet splash
rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.3 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING WIFI II
v: Rev X.0x serial: <superuser required> UEFI: American Megatrends v: 0309
date: 08/16/2021
CPU:
Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 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: 4691 min/max: 2200/4850 boost: enabled scaling:
driver: acpi-cpufreq governor: performance cores: 1: 4691 2: 4691 3: 4691
4: 4691 5: 4691 6: 4691 7: 4691 8: 4691 9: 4691 10: 4691 11: 4691 12: 4691
13: 4691 14: 4691 15: 4691 16: 4691 bogomips: 121367
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3080 Ti] vendor: ASUSTeK driver: nouveau
v: kernel non-free: 525.xx+ status: current (as of 2023-02) arch: Ampere
code: GAxxx process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1
empty: DP-2,DP-3,HDMI-A-2 bus-ID: 09:00.0 chip-ID: 10de:2208
class-ID: 0300
Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
compositor: kwin_x11 driver: X: loaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: nouveau display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1015x571mm (39.96x22.48")
s-diag: 1165mm (45.85")
Monitor-1: DP-1 pos: primary model: Samsung U28H75x serial: <filter>
built: 2018 res: 3840x2160 hz: 60 dpi: 161 gamma: 1.2
size: 607x345mm (23.9x13.58") diag: 698mm (27.5") ratio: 16:9 modes:
max: 3840x2160 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-1 model: Samsung built: 2014
res: 1920x1080 hz: 60 dpi: 55 gamma: 1.2 size: 885x498mm (34.84x19.61")
diag: 801mm (31.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.7 256 bits)
direct-render: Yes
Audio:
Device-1: NVIDIA GA102 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 09:00.1 chip-ID: 10de:1aef 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: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
Sound API: ALSA v: k6.2.6-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.67 running: yes
Network:
Device-1: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 14c3:0608
class-ID: 0280
IF: wlp3s0 state: up mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 04:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp4s0 state: down mac: <filter>
Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 05:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp5s0 state: down mac: <filter>
Bluetooth:
Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8
bus-ID: 3-6:5 chip-ID: 0e8d:0608 class-ID: e001 serial: <filter>
Report: bt-adapter note: tool can't run ID: hci0 rfk-id: 0 state: down
bt-service: disabled rfk-block: hardware: no software: no address: N/A
Drives:
Local Storage: total: 5.74 TiB used: 1.84 TiB (32.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM008-2FR102
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: 0001 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM008-2FR102
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: 0001 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1B6Q scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST2000DM008-2FR102
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: 0001 scheme: GPT
ID-5: /dev/sde maj-min: 8:64 type: USB model: USB Disk 3.0 size: 57.99 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
rev: 8.01 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 57.68 GiB size: 57.68 GiB (100.00%)
used: 28.91 GiB (50.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-9074fab6-463a-46ea-a0e4-f3e75f597eae
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 752 KiB (0.2%) fs: vfat dev: /dev/sde1 maj-min: 8:65
ID-3: /home raw-size: 57.68 GiB size: 57.68 GiB (100.00%)
used: 28.91 GiB (50.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-9074fab6-463a-46ea-a0e4-f3e75f597eae
ID-4: /var/log raw-size: 57.68 GiB size: 57.68 GiB (100.00%)
used: 28.91 GiB (50.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-9074fab6-463a-46ea-a0e4-f3e75f597eae
ID-5: /var/tmp raw-size: 57.68 GiB size: 57.68 GiB (100.00%)
used: 28.91 GiB (50.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-9074fab6-463a-46ea-a0e4-f3e75f597eae
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 62.71 GiB used: 2 MiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 43.0 C mobo: 26.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 319 Uptime: 24m wakeups: 0 Memory: 62.71 GiB
used: 3.03 GiB (4.8%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
pkgs: 2001 libs: 563 tools: octopi,paru Shell: fish v: 3.6.0 default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.25
Garuda (2.6.15-1):
System install date:     2023-04-22
Last full system update: 2023-03-16
Is partially upgraded:   Yes
Relevant software:       snapper NetworkManager mkinitcpio
Windows dual boot:       Probably (Run as root to verify)
Failed units:

When I posted in a past thread my inxi I was told I had the proprietary Nvidia drivers, but when I checked in the hardware settings of my GPU it tells me I have enabled the video-linux options for the drivers, and using the button to auto install open source drivers says I already have them installed.

What am I supposed to do to fix the issue? Is someone able to tell me from the inxi if I have the open source drivers and, if not, how do I install them and remove the proprietary ones?

I have seen a thread here about frogging family Nvidia-all (hope I wrote it right), am I supposed to grab that for my system?

Thanks in advance

Oh, right, that's the thread I had seen about drivers issues. So, am I just supposed to try those commands after trying to update, or like the command 'sudo dkms autoinstall' I can run it in my current snapshot to see if it has issues?

Because, in the hardware configuration panel I tried to install the package video-nvidia-dkms, but it wasn't marked as open source, it didn't have the check, so I thought those were the proprietary drivers... Did I get it wrong maybe?

I've tried following your suggestions, but I've found out I am in a weird situation, I'm not able to restore any of my old snapshots anymore, if I try restoring them I just end up in an emergency shell, but I can't run the commands as I think wifi is disabled, is there a way I can connect to internet from the console? trying to reset dkms tells me the file doesn't exist, so I don't have those drivers

Use live ISO, chroot from Garuda-Welcome app, or chroot, try update or install dkms or nvidia driver ...

1 Like

I'm trying to chroot the system, but I'm currently running into a little issue. When I input the command

sudo garuda-chroot /mnt/broken/@

I get an error

Can't create chroot on non-directory /mnt/broken/@

The previous command in the line worked fine. How should I behave now?

ls /mnt/ | grep broken
drwxr-xr-x - root  4 Jan 09:05  broken

did you create

sudo mkdir -p /mnt/broken

?
did you try?

App, use/click the icon.

1 Like

I did it first thing, following the guide you linked, should I run it again?

Was working all in terminal, I will try from Garuda-Welcome

Use only the first line, it check if /mnt/broken exist.

Yeah, try the app :slight_smile:

1 Like

Alright, thanks!

damn, I'm running the live garuda on a laptop with Mint on it, chroot app targets linux mint boot files...
can the garuda boot repair app be of use? I can manually select the partitions there

Switching boot priority didn't help unfortunately...

This is shown for example if you mount onto /mnt/broken the wrong partition, e.g. the EFI partition instead of the system partition (the btrfs formatted one).
Can you recap the exact commands you tried and the outputs you got?

2 Likes
lsblk -f

sudo mkdir -p /mnt/broken

sudo mount /dev/sdc1 /mnt/broken

These are all the commands I write before attempting the chroot command, none of them give either errors or other type of message in the terminal

Alright, then I might have a issue, with the lsblk I found the partitions of my garuda install, but I only see a vfat or FAT32 partition (the one I'm attempting to chroot) and a crypto partition, I see nowhere a partition marked as btrfs, is that an issue?

If I try to mount the crypted partition is says it doesn't recognize the filesystem type 'crypto-LUKS'

Hold on, that's the culprit.
You need to unlock the crypto partition before chrooting.
I've never used that configuration but I'm sure there are good examples in the forum. And relevant users :wink:

2 Likes

By unlocking it you mean opening it in the file explorer and then chrooting it? That didn't work for me.

Or do I need a specific command to do so?

I'm not at all an expert on encryption but I guess you could try something like

sudo cryptsetup open /dev/sdc2 crypto_LUKS

Substitute sdc2 with your encrypted partition.
It will unlock the device into /dev/mapper/crypto_LUKS and this can be used to mount before chrooting

sudo mount /dev/mapper/crypto_LUKS /mnt/broken
4 Likes