MX KDE, but I am not being objective… I like MX, I dont like Ubuntu based distros. You may have different likes.
I dont know enough to be objective on that.
MX KDE, but I am not being objective… I like MX, I dont like Ubuntu based distros. You may have different likes.
I dont know enough to be objective on that.
This sounds like a Plasma version problem to me, gained the knowledge that Nvidia doesn’t play well with Wayland but not so bad with X11.
Don’t know if there’s a way to roll back to a earlier version of Plasma but that might work.
I think Cliff may have to roll back the whole OS, not kde on its own.
Since my last post, have been dabbing around with KDE Neon Plasma 6.3
Other than quirks with dual monitors, it is behaving well.
Take back my nasty remarks.
(Working under Wayland - AMD, not nVidia).
Yes, Cliffs next card should be an AMD.
I have really mixed feelings about that. My current card works just fine in Win10, Mint, Ubuntu Mate and three VMs. Should I go through the trouble and expense because a low-priority distro acts up?
But I have been shopping, and finding a card that fits the mainboard (Intel DH77EB) isn’t easy. So many variables! Plus, getting one with more than 2 GB memory is costly! (How did gamers get so damn rich?)
Finally, the most graphics intensive thing I do is edit and resize images from newspaper and magazine articles to fit in documents.
That’s why I tend to say, to hell with finicky distros!
I think wait till you buy your next computer.
They will try to push nvidia onto you, but if you use linux, insist on AMD graphics.
Ha! At my age, that day may never come!
Me too.
My last purchase was a refurbished sff desktop with onboard Intel graphics. It has been troublefree.
Linux is fine with onboard Intel graphics.
It is my spare computer. I use redundancy as a form of insurance against catastrophic failure.
An update.
I posted to both the MX and Pop! forums about Nvidia drivers for an older card.
MX said that they have legacy drivers, so their tool should be able to find, identify and install correctly.
Pop! said they only have more recent drivers, so I should download the AMD-Intel ISO and use nouveau.
So I just downloaded the MX ISO and will be installing some time this week.
Hey!
Back when I was distro hopping, I looked into KDE Neon since I love KDE Plasma. However, when I did this research, I found out two things about it.
I follow the KDE forums and Reddit frequently, and since support for explicit sync was added early this last summer there are a lot fewer compliants about Nvidia and Wayland compatibility. From what I can gather, it sounds like you have an older Nvidia card, which might mean this update hasn’t helped you. I do know Nvidia support on Linux still has issues.
A quick update. I installed MX with KDE, and it uses Kwin (X11), nouveau and version 5.27 Plasma.
On the forum, i asked about using their Nvidia driver tool, and more than one said nouveau works just fine. So i am restraining my natural curiosity to try those drivers out and let mx “just work.”
Agree. If you dont need fancy graphics and the noveau drivers work, stick with it.
Will be interested in how you react to MX?
This was posted on the thread i created on the MX forum:
https://community.kde.org/KDE_Linux#:~:text="KDE%20Linux"%20
Especially this section
Prior art
KDE neon, KDE’s first version of a self-made OS. KDE neon fulfills the “distributed by KDE” requirement, but fails on the reliability angle due to the Ubuntu LTS base that ironically becomes unstable because it needs to be tinkered with to get Plasma to build on it, breaking the LTS promise.
The poster is on the MX KDE development team, and said my issues, hinted at in this document, are the result of overly aggressive development within the Neon team.
Hi Cliff,
Thank you for the link on KDE Linux
So people know what it is, I quote
“KDE Linux” (codenamed “Project Banana”) is a work-in-progress name of a KDE-owned general-purpose Linux® distribution proposed at Akademy 2024. Not to be confused with KDE neon."
We should all have a read of Cliff’s link… there are some interesting ideas, including not supporting runtime kernel module loads
and
Your problem does seem to be due to Neon.
Regards
Neville