This might sound silly, but couldn’t you just get a better connection? You are using bandwidth for lemmy so your internet can’t be that bad. In the worst case you can just go to your local library.
Not much really. It is great, but slow as shit and makes me want to toss my computer across the room. I just want to install one tiny 5 kb package, I don’t want you to take 10 minutes checking all the RPM fusions repos and go to the moon and back then install my package. No, just install the damn thing. I’ll ask you when I need you to check that long list of repos. 😂
I actually did install it. I hate to judge it in a virtual machine, but I’ve noticed a small difference. It’s still slow, but not as slow as the other one. Fun fact, the only reason why I don’t use fedora is that I hate their installer. I have 3 drives on my PC, and I’m so scared that I’d mess things up and lose my photos/videos/games etc 😂 The installer is so confusing. I remember figuring it out once then just forgot it again.
I custom install every time, partially to preserve my user data partition, partially because I don’t like the defaults (I like mirroring my disks and leaving space to grow into later if I want)
Same here, that’s why I have 3 different drives in my PC, 512GB nvme ssd for root, 1TB SATA SSD for home, and 2 TB SATA SSD just for games/emulation and steam
Because people will never agree on a single one, and it’s FOSS so nothing is forced. I for one am glad I don’t have to use apt because I prefer pacman, just as I am glad someone who doesn’t want to use an Arch-derivative has Debian and apt to fall back on.
Arch btw: it is much stable that many Linux users think, there are a ton of guide to do/repair things thanks to Arch Wiki, and, last but not least, it has the AUR repository in which you can find basically all software you will ever need; the only malus the AUR repository has is that you have to compile every software you install with it (even if sometimes they are precompiled).
P.S. if you want a “ready-to-go” arch distro, install EndevourOs and set the btrfs file system with timeshift. Here’s a guide.
Some package managers do have differences that justify a separate project (nix, gentoo’s portage, etc).
For others, sometimes package managers are very similar feature-wise. But some developers would rather remake the thing because they would understand their code a lot better than someone else’s. Or because it would be far easier for them to customize rather than extend another project.
Imo it is developer laziness. Being able to use other people’s work is a valuable skill. But then again, this is open source, and people are free to develop the software they want the way they want.
I tried out the beta version of 545 last week, I swear it made the render issue with XWayland apps worse. Even if it’s back to the 535 state, it still makes using Wayland on Nvidia very difficult unless every application you plan to use is Wayland native. It’ll be a while before that’s the case for me.
I plan to just pick up a 6700 XT next week. I’m tired of being a second class citizen in Nvidia’s eyes.
That being said, I appreciate the devs themselves who’ve been working on improving what they can (there’s a couple that I’ve even seen participating in the Freedesktop GitLab). I assume the lackluster Linux support comes from the management side of things. I may not like the company, but I obviously don’t have disdain for every single person there.
I replaced my 3080 Ti with a 7900 XTX, reinstalled Tumbleweed to start fresh, and KDE on Wayland has been running great so far. Before, visual glitches galore, GPU refusing to output a signal if iGPU is not blacklisted, hardware video decoding outright does not work, etc.
Now, with AMD, I have not yet experienced graphics-related issues in weeks, fingers crossed.
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 suggested nvidia-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 from kwin_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.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.