Mastodawn

Did a little adventure migrating my Debian Forky box from the in-repo nvidia (v550) drivers to extrepo nvidia driver (v595) as a work around for the kernel 6.19.x -> 7.0.x thing.

Yeah, don't do that.

I think the Debian maintainers do a bunch of work to the in repo drivers to make them 'nicer' - things like working better in multi-head. At least with my system sddm worked better. Also, the 595 drivers max the CPU under Plasma and makes it unusable (load avg ~25 on i7-11700k).

I ended up rolling back to v550 and pinning the kernel version to 6.19 for now. I'm still stuck with waiting for OpenZFS 2.4.2 for this box as well.

Nvidia drivers sure do make a mess between the number of packages required (with extra spicy things like new and interesting package name differences between in-repo and extrepo!) and the whole kernel version to module building process is a chore. I really appreciate that the teams make this work repeatably - especially when I tried going backwards to 6.19 with 595.

Anyway, rolled totally back to kernel 6.19, nv 550 and everything works as it should including OpenZFS v2.4.1 on this kernel.

One annoyance along the way was rolling back to v550 caused a sddm login loop. Deleting ~/.local/share/kscreen fixes this. Appears to undo minimal desktop tweaks, probably less noticeable on a non-multi-head host.

Things you do to avoid housework. Ha.

#Linux #Debian #Testing #Forky #Nvidia #Nvidia595 #KDE #KDEPlasma #Plasma

Carl von Lesquereux May 8

Just upgraded my #Fedora install to #Fedora44, and was almost problem-free.

Needed to downgrade the #Nvidia595 driver, because my discrete card was no longer supported. Also, I had to reconfigure the TPM for LUKS auto decrypt, and I had to modify some repo files because changes to #GNOME Software. Oh, and I need to wait for an update to the R-CoprManager, because right now no longer works.

Overall, another painless upgrade.