3 ms·
I think you're looking at two issues here. One, your GPU has a really small VRAM pool and will probably exhaust it within a few windows. Two, your GPU is likely
by bigyabai 11mo ago
I think you're looking at two issues here. One, your GPU has a really small VRAM pool and will probably exhaust it within a few windows. Two, your GPU is likely not supported by the recent Nvidia drivers that majorly improved Wayland (550-series onward). So you're running into an OOM state that doesn't get handled gracefully and results in a crash.
My 3070Ti reports similar memory usage at idle, but even when my VRAM is exhausted I don't get an OOM crash. The only time I'd ever had my GPU OOM panic was with my 1050 Ti on very old Nvidia drivers. You'll probably want a newer GPU for Wayland stuff.
- nickjj 11mo agoThanks. Which driver version are you using? NVIDIA's official stance is the DKMS 580 series drivers do support my card. The 590 series do not but I didn't try those. Basically the 75X, 8XX, 9XX and 10XX cards all use the 580 series driver. I don't know about 6XX or less (I didn't check). Getting a newer GPU is going to be sketchy I think. It's a machine I built up from parts in 2014. The motherboard is an ASRock H97M with PCIe 3.0 x16. I don't think the PSU can even power a 1080 and even then, a 1080 would use the same 580 series drivers as this card so it might have the same problem, just with a higher ceiling (8 GB instead of 2 GB). It's also disgusting that this card is over $200 used in 2025. Using someone else's 10 year old card in itself is a massive gamble. When the instability starts to happen due to high GPU memory usage I get this in journalctl: Dec 28 12:41:10 kaizen kernel: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to allocate NVKMS memory for GEM object Closing out windows to reclaim GPU memory isn't enough to bring things back to operational. I often get compositor freezes and other weird artifacts like windows taking up space but not being there until I reboot. It's like niri gets in an unrecoverable state that it doesn't recover from. I say reboot but logging out and back in also works, but this is quite disruptive to be doing a few times a day and hinders me from recording videos since I often run into issues while doing my day to day stuff. I really wonder how to resolve it if it's even possible. This box is my main dev / media creation box and it was super good and stable on Windows for 11 years.