this post was submitted on 24 Aug 2023
112 points (78.6% liked)
Linux
48212 readers
2094 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
Which GPU are you using?
I spent a good 10-20 hours just trying to get it to boot to a largely error-free experience with SDDM and KDE. I set out to daily drive Hyprland and what a shit show that turned out for me on Nvidia GPU and Alder Lake CPU.
The basic gist is you have add nvidia, nvidia_uvm, nvidia_modeset and nvidia_drm to your mikinitcpio conf, regenerate your initramfs, then adding kernel boot parameters nvidia-drm.modeset=1 and i915.modeset=0 before it can even boot to a usable state. Apparently since 6.0, the igpu grabs the display and refuses to give it back. I don’t know how the fuck any “normal” user is going to figure out how to do all of that. Then I spent another evening trying to figure out how to get VAAPI working properly. There’s lots of outdated info in the wiki and not much else to go on, but I figured it out eventually.
BUT, having said this, I do recognise when you go Arch, you’re asking for all of these jank. And, for science, I wiped and tried out endeavouros, and it was surprisingly painless, mostly just worked out of the box (I didn’t check if it was nouveau but it might have been, I also didn’t check if VAAPI was working).
In the end after what seems like 400 wipes and reinstalls, I got it working just right. But it wasn’t painless and it certainly isn’t meant for the faint hearted.
Yes I know the fault largely lies with Nvidia and their shitty proprietary drivers, and so on. But the exact same machine worked just fine in W11, without a single jank or terminal command (not 100% true because I did run OOBE\BYPASSNRO to skip the online junk).
Moral of the lesson: go vanilla Arch if you are comfortable with figuring out shit on your own. Otherwise, stay the hell away and pick a starter distro like Fedora or Pop!_OS that is mostly jank-free.
obligatory I use Arch btw.
I think your experience is more to do with nvidia + Wayland than anything OS specific. Although I think other distros have done a lot of patching and coding around nvidia's incompetence to get Wayland to work better and I think Arch doesn't really do this sort of thing. Definitely seems like you unwittingly took on a project.
I also use nvidia but I have no desire to move to Wayland any time soon. X11 works just fine unless you get into esoteric setups like multiple monitors with different refresh rates. My first boot into KDE with Arch was completely broken and I thought "okay, here comes the hard part" until I realized it was defaulting to Wayland. Changed it to X11 in sddm and it's perfect. I use my ForceCompositionPipeline script on login and set kwin to force lowest latency and it's smooth as butter.
Wayland is the future but nvidia is definitely gatekeeping that future. I've got a 3080 in this machine that is going to last a pretty long time I suspect, but unless nvidia can manage to remove head from ass I see AMD in my future.