this post was submitted on 31 Oct 2023
85 points (100.0% liked)
Linux
1258 readers
95 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah it's absolutely ridiculous. The "stable" release is out in the
extra-testing
repo for Arch, and I just had an absolute nightmare trying to get it to work. Installed it, added the suggestednvidia-drm.modeset=1 nvidia-drm.fbdev=1
kernel parameters to systemd-boot, ensured all of the Nvidia kernel modules were present in initrd to do early KMS loading - tried to start a KDE Wayland session and the desktop ran no more than maybe 5 FPS and I wish I were exaggerating that. A very similar issue was reported on their forums but the error I'm getting fromkwin_wayland_drm
is slightly different.Tried install GNOME, but its Wayland session wouldn't even launch at all. Loaded into its X11 session and it seemed to not be using accelerated graphics whatsoever.
Now of course, part of the blame goes to me for opting into the testing repo... but at the same time, I shouldn't have to go through those hoops just to potentially get a working Wayland desktop (and I suspect even if I had succeeded, the same issues will have still been present). As far as I understand, AMD/Intel's drivers are just part of mesa and are included in the kernel - no modifying your initrd, no worrying about DKMS, no trying to mess with
.run
files...I have a Windows partition on one of my SSDs for the few occasions that I need to do something that can only be done from Windows, and I think I'm just going to use that till my GPU comes in. Funnily enough, Nvidia's drivers aren't even that great on Windows either - I still get a screen flicker issue whenever (I believe) the power state of the GPU changes, so for example playing a YouTube video, or even Steam popping a toast notification saying that a friend has launched some game. And plenty of my friends have tales of nightmares with trying to install and manage the Nvidia driver on Windows.
I would've never bought an Nvidia GPU in the first place if I had known how bad it was on Linux, and my current Nvidia GPU (a 2080) wasn't actually purchased by me, but handed down by a very gracious friend at the beginning of the year since times have been really tough for me. Thankfully this last month I was able to put in some extra hours to be able to set aside some money for a used 6700xt because if I have to deal with this any longer I'm going to lose my sanity.
Its a lost cause, I've wasted several weeks in August and September trying to make Nvidia and Wayland and hardware video decoding work on every distro imaginable, GNOME or KDE. I would have bought a card from Team Red outright if I knew how deep the rabbit hole went.