[SOLVED] [14.2] Only certain programs broke after nVIDIA proprietary driver switch

Richard Cranium · 02-28-2018, 01:46 PM

Maybe we can start talking about systemd instead in order to calm things down.

enorbet · 02-28-2018, 06:13 PM

FWIW Richard, I'm quite calm and harbor no bad feelings for kingbeowulf or anyone here. Misinterpretation of raw text is "just another day at the office" on the webz for me after all these years

RadicalDreamer · 02-28-2018, 07:35 PM

Quote:

Originally Posted by elcore

I'm familiar with the *glx.so conflict, and it's not 'fixed' by replacing mesa components with a blob and tainting the kernel in the process. It is fixed by a clean kernel and clean mesa package.
If you keep repeating that mesa is at fault for breaking glx, some newb will read that, replace the glx, and proceed to compile SBo packages which don't work on slackware unless it's tainted.
And then you will have bug reports where crucial information is left out, and nobody will know what the problem is, because the OP assumed mesa broke something and he fixed it.

Then tell them not to use the NVIDIA blob because it will "taint" their install. I'll tell them that elcore said that NVIDIA blob has cooties so they better not use it. I WILL IN ALL CAPS TELL THEM THAT ITS NVIDIA'S FAULT WHEN THEY INSTALL MESA OVER IT AND NOTHING WORKS. This is ridiculous I'm describing a conflict between two packages. Its no ones fault. I don't get why you are going all Richard Stallman on me. Maybe that is how these packages are designed. Maybe mesa was designed to be used with open source drivers. Maybe just maybe. Bare with me on this. People bought NVIDIA cards and they want good performance in games. The only way to do that currently is through the NVIDIA blob. Is it the fault of nouveau? No its not. Its the consumers fault for allowing NVIDIA to maintain closed source drivers.

OP forget what I said. I know nothing. Good day. Maybe that will end the zealotry aimed at me.

elcore · 03-01-2018, 03:42 AM

I use it once or twice a week, I just keep it way over there on a separate partition, away from any compilers and shared libraries.
Fact is, it makes the kernel worthless for any debugging, which you'd already know if you had read the documentation.
It's nothing personal mate, just saying it's your own fault if mesa updates break your files, because you put them there in the first place.