Exploring CPUs, motherboards, overclocking, building your own PC, case mods, PC brands, handhelds, peripherals of all types, DVDs, CD burners, hardware-specific software, device drivers, and anything else related to hardware.
The The Restaurant at the Edge of the Universe, previously known as The Water Cooler, is a place to post stuff that has absolutely nothing at all to do with computers, broadband, Scot's Newsletter, or anything that's "supposed" to be here.
Man! This is a widespread issue with many distributions. LQ.org has been fairly burning up with posts regarding this kernel upgrade/Nvidia failure issue. Turns out that Nvidia has been a little slow to update their legacy drivers to be compatible with newer kernels. This is EXACTLY the problem I was having this past week in my Slackware. I'm finding that there are no easy solutions to this because it's in Nvidia's ballpark and they're not hopping to fix anything, it doesn't seem.
Those of us with older Nvidia cards (mine GeForce 560) are going to be screwed in a short while due to Nvidia's EOL of legacy drivers. It's all about the $$$. They want us to buy the spiffy new Nvidia cards... that we don't really need. Oh, well... for me, I'll just have to figure out how to get Nouveau to work on my system once the next Slackware version is released. I'll worry about it then.
They did it again.
I am currently using Ubuntu Mate 18.04.3 LTS and during a routine upgrade it updated to kernel 126.96.36.199 and upon reboot went to a blank screen. Others who are well versed in getting nvidea drivers to work are saying this kernel is not compatible with nvidea.
Warning: kernel 188.8.131.52 can ruin your day!
Well, after quite a bit of reading at LQ.org and other places, I'm finding that the issue with Nvidia on the newer kernel that I was trying upgrade is being experienced by MANY folks and not just in Slackware. It seems that Nvidia has been a bit remiss in keeping their legacy drivers updated, so there are Xs crashing all over the place. Unfortunately, there doesn't seem to be just one common fix, but many work-arounds; some successful, some not.
I guess I'll just keep things as they are (working properly) for the time being. I'll worry about all this Nvidia carp when I do a clean install of the next version of Slack... whenever that comes out.
It is what it is...