Clearly a general NVIDIA issue right now

Hi guys,

Just thought I’d step in to try and highlight something that I see going on.

There is clearly a problem with NVIDIA based Garuda systems right now, regardless of kernel, that is not being acknowledged.

I think the problem might be upstream somewhere as I’ve seen a large number of kernel updates over the last couple of weeks, moreso than usual and on an install that has been fine for 2-3 years, I’m suddenly seeing a lot of problems.

I am also seeing quite a few people posting fragments of what is essentially the same problem albeit being detected in different ways.

The issue appears to be, following a reboot after a system update, people are seeing very slow boot times, no boot up at all or are being dumped into a black screen…or all three.

For me, the issues began with kernel 6.6.3…I was getting errors relating to the NVIDIA DRM module.

I ultimately performed a clean install, and the problem seemed to go away, however, not 3 to 4 days later, I’m seeing the issues creep back…I haven’t seen the DRM errors yet (that doesn’t mean they aren’t happening) but I have seen slow boot times and I have been dumped to a black screen after login.

The problem doesn’t seem to occur with other distros. This isn’t to say that the Garuda team is responsible here, far from it, but I think there is something happening upstream that isn’t being taken in account. What it is? I dunno…

All I can say for sure is that this issue isn’t affecting AMD GPUs (in as far as I can tell, I’ve seen no posts from people reporting issues with AMD GPUs and my secondary machine, which has an AMD GPU does not experience the same issues).

Currently, a clean install seems to make this issue become less of an issue, but the issue does eventually return for some reason or another. Usually not as severe.

Based on what I have seen the conditions to re-create this problem appear to be:

  1. Kernel newer than 6.6.2 (regardless of kernel type)
  2. NVIDIA GPU
  3. More than one monitor (mostly).
  4. Doesn’t happen immediately after a clean reinstall, but does happen eventually.

The common symptoms are:

  1. Slow boot up time with DRM errors.
  2. Booting to a black screen and then going no further.
  3. Logging in and seeing a black screen with an X mouse cursor.

Fixes that seem to temporarily fix the problem:

  1. Clean install. Seems to get you about a week.
  2. Reverting to a previous snapshot.
  3. Using a different distro (in my case, EndeavourOS and Manjaro do not seem have the same issue).

Fixes that don’t work (permanently):

  1. Freezing the kernel version to 6.6.2 (not sure why, doesn’t help).
  2. Reinstalling the NVIDIA driver.
  3. Switching to a different kernel.
  4. Updating your BIOS.
  5. Setting the DRM flag to 0 or 1 in your Grub config.
  6. Clean install (works for a while, but will ultimately start glitching again).
  7. Unplugging extra monitors.
  8. Holding packages unrelated to the GPU / Kernel.

Factors I have yet to discern:

  1. Whether it is AMD or Intel CPU specific.
  2. Whether it is only affecting new GPUs.

I am currently writing this on an NVIDIA based PC with Garuda fully up to date, but rebooting is a coin toss. Sometimes it works first time, sometimes it doesn’t.

To be crystal clear, I don’t think the Garuda team is responsible for this problem and I don’t want this post to come off that way, I think the issue is likely coming from upstream…but we need to acknowledge that there is a general problem…there are lots of people going in circles over this issue and some proper investigation needs to be done…something is being missed and it’s causing people to waste a lot of time.

I don’t have enough machines here with enough variety of components to be able to build a clearer picture.

I hope we can bring more clarity to this issue and get everyone fixed swiftly!

Cheers and Merry Xmas!

2 Likes

Ive alsp been getting errors on bootup related to nvidia. For me ive still been able to boot and log into my DE but on shutdown and reboot im getting errors. Cant post them at the moment but will try to once I have time

Yes, it is clear! There must be a hundred posts in the forum recently. Who is not acknowledging it? :face_with_monocle:

Though, I am not sure how Garuda Linux is implicated here. Garuda doesn’t provide Nvidia drivers or anything, nor modify them in any way. They come from upstream, and get installed in whatever state they are provided.

That is to say: the issues folks experience with Nvidia drivers on Garuda Linux should be identical to the issues on Arch Linux.

I recall reading this article over the summer where it was mentioned the infrastructure for Nvidia modules was going to change starting with the 6.6 kernel, and it was anticipated there would be issues for Nvidia users:

I did not follow the news closely and I’m not actually sure what happened with that so it could just be a coincidence, but I definitely have noticed a major uptick in Nvidia-related issues posted here in the forum since 6.6 came out.

6 Likes

You’re not alone man!

I think what we need is a proper in depth look at this issue rather than just superficial “post your inxi” and “which packages were updated” stuff. The basic troubleshooting stuff is clouding the issue and doesn’t help us to understand the problem at hand.

The problem goes deeper than that I think…it’s clearly more than “it’s your setup bro”.

It is possible to reliably recreate the issue regardless of superficial packages etc, as highlighted in my OP, a clean install seems to resolve the issue, but it does eventually return…which is why I doubt the problem is config related or due to dodgy additional packages and so on. The kind of troubleshooting going on will get you a workaround, which will work for a while, but it won’t get an actual reliable fix that will work permanently.

The confusing part is that the issue seems to manifest itself in subtly different ways, but it is clearly the same problem…so we have multiple posts in here troubleshooting the same problem but from different angles and each angle is being treated as a different problem.

At this point, we know what the problem is, how to recreate it and when it occurs but we don’t know why it’s happening or who can fix it!

The “who”, in my opinion, is probably upstream…but I don’t know for sure. We’ve had 5 kernel updates in 2 weeks which is considerably more than usual…I would usually expect one kernel update a week at most in normal times…so something is going on upstream!

As for the “why” aspect…I’m not 100% certain there either…but there have been patches rolled out to plug the “logoFAIL” bug that was disclosed in mid-November…which coincides with the flurry of kernel updates.

See here: NVD - CVE-2023-40238

Seems like a weird coincidence that these booting problems starting occurring not long after that disclosure.

The CVE says it only affects Lenovo devices…but there are other resources that suggest it is far wider reaching than that.

Therefore, I think there are efforts underway upstream to deal with this and it is having knock on effects downstream.

I haven’t tested yet to see if disabling UEFI boot helps here, but I strongly suspect it will…anecdotally, I disabled boot logos on my machine and it did appear to help a bit…it didn’t fix the problem entirely, but it trimmed some time off the “slow boot” effect.

This is also why I tried updating my BIOS, in case the kernel was expecting some kind of fix to be in place for this bug that is required for a smooth boot.

Users are definitely acknowledging it, but each case is being handled as an isolated problem…not a problem in general!

Edit: As I mentioned in my OP, I don’t think Garuda is to blame here. I think the problem is upstream…but I think a stickied post or something acknowledging the issue and outlining some common workarounds that help might be a good step rather than having hundreds of people posting separate posts and taking up your time!

The problem needs to be tracked…otherwise you’re just fighting a fire that you can’t put out!

Nvidia was getting a lot better, too…even working on Wayland a little bit!

I feel like we are going back to the old days of Nvidia support being a mostly-broken crap shoot…:game_die:

Linus, what do you say?

Linus Torvalds Linus GIF - Linus Torvalds Linus Nvidia GIFs|518x291.2449799196787

[“Blur spoiler” applied due to an obscene gesture in the GIF :face_with_hand_over_mouth:]

9 Likes

Have you tried this fix yet? Seems to be helping people that other fixes aren’t

1 Like

I couldn’t agree more!

It needs to float to the top and be acknowledged as a general problem though rather than existing in a mist of hacks and workarounds, take the problem to NVIDIA, blame them…there are people being led to believe that their system has a specific problem which is not the case.

I’m fine for the time being, I can work around it, but I came to my solution following loads of fragmented threads…and I see lots of other people with the same issue that aren’t fine that are experiencing the same problem and they are being given lots of different solutions.

What I’m trying to get at here is that we need a sticky post acknowledging the general problem that has all the potential workarounds in one place…it’s for the benefit of the Garuda Team as well as the users…everyone wants a peaceful Christmas!

Why would the team want to firefight hundreds of posts when they can centralise around a single sticky post and funnel the issue through there?

1 Like

So, is there an issue to this issue thread or not? :confused:
If you have feedback for the forums, there is a section for it https://forum.garudalinux.org/c/feedback/forum-feedback/18

3 Likes

I agree, it may be best to move it since it’s intended to be a discussion thread. Feedback seems fine, or maybe Garuda Community?

Edit: I moved it to Garuda Community and kept the Nvidia tag.

3 Likes

It was actually intended to be a central thread resolving the issue at hand. Oh well. Perhaps you can open a single sticky? :man_facepalming:

I too have been plagued with little errors and have reverted back to lts kernel at times. I cannot pin down a specific error and have been on this forum reading and trying little fixes here and there.

I have been actively looking for my next laptop and am thinking of moving from nvidia to AMD for my next gpu. Nvidia is still king imho, but AMD (from my understanding) having gpu drivers in the kernel is sure appealing at this point. Last time I chose an AMD gpu and had regrets.

I saw in your other post someone mentioned having multiple displays made the boot times slower and a third monitor was acting janky. For me im running on a laptop single monitor and still getting shit boot times. I did notice that once logged in that restarted actually boots much faster than a shutdown and power on. Thankfully my rig at home has a RX6800 so shouldnt be a problem there.

Edit1:
I dont have my laptop on hand but if I remember correctly it also looked like during boot I was getting an error for usb/bt and that I may have had an error with the igpu (vega) but cant remember at the moment.

If this thread is able to accomplish that, then great. :slightly_smiling_face:

I think the topic should not be in Issues & Assistance because that category is intended for addressing a single, specific issue. Relevant logs related to that one issue can be studied, troubleshooting relevant to that specific issue can be attempted, etc.

Trust me: if you make this topic a repository for all Nvidia issues, it will just turn into a jumbled mess of tons of different logs and error messages, issues that may or may not be related, a fix that works on one machine but not another, etc.

I understand your theory that all the recent Nvidia issues have a common underlying problem, but still at this point the thread is only a discussion topic.

I do not know what this means.

2 Likes

“The most profound truth I’ve encountered today”

1 Like

I think it may have been easier back when they were nVidia. Sure, I recall having to hand-install them (drivers) into SuSE, but then they worked. And maybe everyone expected that perhaps a little hackery was normal–Linux wasn’t fire-and-forget. :wink:

But I also recall there came a time when that was no longer so.

It seems to be functioning as an emotional unsupport thread. Not badly, either. Folks taking out their angst against a legendary uncooperative hardware manufacturer–I get that.

It’s part of the grieving process. Like listening to sad, my dog died and girlfriend run off with my horse songs.

5 Likes

What they said:

I am a carbon copy of this posts issues and items tried. I just do not update without making sure I have snap shot at this moment. Its been this way for a few weeks now. I keep watching for a newer build of the nvidia-dkms, currently 545.29.06-1 was introduced along with Zen kernel 6.6.7.zen1-1 still emplify the same issues.

I try to update once week, get the same and just roll back the snap shot and life is good again. I will try the other distros as well, as I am curious now. Time for a tripple boot ;-).

To add I have tried the following as well:

Booted without any external drives attached
booted without any kernel settings for QEMU
booted with a 1050ti same issue
booted with a 2080 same issue
Removed everything from the PC withe excpetion of keyboard and mouse
reinstalled (worked great till I updated)

garuda-inxi
System:
Kernel: 6.6.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=85d10ba7-1da5-4b61-a934-a0dd37c75c5e rw rootflags=subvol=@
rd.driver.pre=vfio-pci intel_iommu=on rd.udev.log_priority=3
vt.global_cursor_default=0 loglevel=3 vfio_pci.ids=10de:1c82,10de:0fb9
pcie_acs_override=downstream,multifunction video=efifb:off iommu=pt
ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING Z590-PLUS WIFI v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1801
date: 12/26/2022
Battery:
Device-1: hid-0003:256F:C62E.0001-battery model: 3Dconnexion SpaceMouse
Wireless serial: N/A charge: N/A status: discharging
CPU:
Info: model: 11th Gen Intel Core i9-11900KF bits: 64 type: MT MCP
arch: Rocket Lake gen: core 11 level: v4 note: check built: 2021+
process: Intel 14nm family: 6 model-id: 0xA7 (167) stepping: 1
microcode: 0x5D
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 825 high: 1155 min/max: 800/5300 scaling:
driver: intel_pstate governor: powersave cores: 1: 801 2: 800 3: 800 4: 800
5: 798 6: 800 7: 800 8: 800 9: 1155 10: 800 11: 852 12: 800 13: 803
14: 800 15: 800 16: 800 bogomips: 112128
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: ZOTAC
driver: nvidia v: 545.29.02 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2023-10; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s
lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1e87 class-ID: 0300
Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI
driver: vfio-pci v: N/A alternate: nouveau,nvidia_drm,nvidia
non-free: 545.xx+ status: current (as of 2023-10; EOL~2026-12-xx)
arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 3
speed: 8 GT/s lanes: 4 link-max: lanes: 16 bus-ID: 04:00.0
chip-ID: 10de:1c82 class-ID: 0300
Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-2:3
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,vfio-pci display-ID: :0
screens: 1
Screen-1: 0 s-res: 8320x1440 s-dpi: 92 s-size: 2297x393mm (90.43x15.47")
s-diag: 2330mm (91.75")
Monitor-1: DP-1 pos: 2-4 res: 1920x1080 hz: 60 dpi: 82
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
Monitor-2: DP-3 pos: 2-2 res: 1920x1080 hz: 60 dpi: 82
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
Monitor-3: DP-4 pos: primary,1-3 res: 2560x1440 dpi: 93
size: 698x392mm (27.48x15.43") diag: 801mm (31.52") modes: N/A
Monitor-4: None-1-1 size-res: N/A modes: N/A
Monitor-5: USB-C-0 pos: 2-1 res: 1920x1080 dpi: 163
size: 300x260mm (11.81x10.24") diag: 397mm (15.63") modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2
memory: 7.81 GiB
API: Vulkan v: 1.3.269 layers: 1 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 2080 driver: nvidia v: 545.29.02
device-ID: 10de:1e87 surfaces: xcb,xlib
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:43c8 class-ID: 0403
Device-2: NVIDIA TU104 HD Audio vendor: ZOTAC driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:10f8 class-ID: 0403
Device-3: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI
driver: vfio-pci alternate: snd_hda_intel pcie: speed: Unknown lanes: 63
link-max: gen: 6 speed: 64 GT/s bus-ID: 04:00.1 chip-ID: 10de:0fb9
class-ID: 0403
Device-4: SteelSeries ApS Arctis 7
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-7.2:10 chip-ID: 1038:12ad class-ID: 0300
Device-5: GN Netcom Jabra Engage 75 driver: jabra,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7.4.4:14
chip-ID: 0b0e:1112 class-ID: 0300 serial: <filter>
Device-6: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-2:3
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
API: ALSA v: k6.6.2-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 0.3.85 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 Tiger Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:43f0 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 07:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:16 chip-ID: 8087:0026
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 25.14 TiB used: 137.75 GiB (0.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung model: SSD 970 EVO 1TB
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: 2B2QEXE7 temp: 38.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:9 model: PCIe SSD 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: EHFM60.0 temp: 34.9 C scheme: MBR
ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Western Digital
model: WDS100T2B0C-00PXH0 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: 233010WD temp: 31.9 C scheme: MBR
ID-4: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.52 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 00RL scheme: MBR
ID-5: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.52 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 00RL scheme: GPT
ID-6: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SDSSDH3 512G
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1000 scheme: MBR
ID-7: /dev/sdd maj-min: 8:48 vendor: ASMedia model: T ASM236X NVME
size: 119.24 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter>
scheme: GPT
ID-8: /dev/sde maj-min: 8:64 vendor: Seagate model: Expansion Desk
size: 7.28 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: 0915 scheme: GPT
ID-9: /dev/sdf maj-min: 8:80 vendor: Seagate model: Expansion SW
size: 7.28 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: 1801 scheme: GPT
ID-10: /dev/sdg maj-min: 8:96 vendor: Seagate model: Backup+ Hub BK
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: D781 scheme: GPT
ID-11: /dev/sdh maj-min: 8:112 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 0001 scheme: GPT
ID-12: /dev/sdi maj-min: 8:128 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 0001 scheme: GPT
ID-13: /dev/sdj maj-min: 8:144 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: TB08 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-14: /dev/sdk maj-min: 8:160 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: TB08 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 159.23 GiB size: 159.23 GiB (100.00%)
used: 137.72 GiB (86.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:8
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 25.9 MiB (27.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:4
ID-3: /home raw-size: 159.23 GiB size: 159.23 GiB (100.00%)
used: 137.72 GiB (86.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:8
ID-4: /var/log raw-size: 159.23 GiB size: 159.23 GiB (100.00%)
used: 137.72 GiB (86.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:8
ID-5: /var/tmp raw-size: 159.23 GiB size: 159.23 GiB (100.00%)
used: 137.72 GiB (86.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:8
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.15 GiB used: 1024 KiB (0.0%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 39.5 C mobo: 31.0 C gpu: nvidia temp: 37 C
Fan Speeds (rpm): fan-1: 0 fan-2: 1461 fan-3: 0 fan-4: 0 fan-5: 0
fan-6: 3383 fan-7: 0 gpu: nvidia fan: 33%
Info:
Processes: 418 Uptime: 8h 20m wakeups: 0 Memory: total: 32 GiB note: est.
available: 31.15 GiB used: 7.75 GiB (24.9%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 1854 libs: 461
tools: gnome-software,octopi,pamac,paru Shell: fish v: 3.6.1
running-in: konsole inxi: 3.3.31
Garuda (2.6.19-2):
System install date:     2023-08-25
Last full system update: 2023-12-10
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:            preload.service

Screenshot_20231216-213232~2

Heres something interesting. Ive been having the same issue on my laptop which has an nvidia gpu. Just now after being gone for 2 weeks I update my rig at home which has a 5800x and rx6800. I was greeted with this error after updating and a reboot. Not sure if this is related. Im pretty noob but it seems like both problems stems from kvm?¿

Guess I got lucky then because since switching to Wayland on Garuda with my RTX 3070 earlier this year, I’ve had zero problems with the nvidia proprietary driver driving two identical 4K monitors and gaming (native only, I haven’t set up WINE or proton/steam at all). I have an AMD CPU.