New (minor) gotcha with the new 4.14.11 kernel and Nvidia driver
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
New (minor) gotcha with the new 4.14.11 kernel and Nvidia driver
I just installed the new kernel tonight, and when I tried to build the 384.89 Nvidia driver, the kernel module failed. But all was not lost. Nvidia just happened to release an update this evening, 384.111. I was able to build that with no problem, and so far it works fine. For those who don't have the URLs:
MY rant to Pat. https://www.linuxquestions.org/quest...ml#post5801492 the 384.111 is not latest not stable so that is why My progrma did not like it. .
Simple log from pat would would help. He runs Nvidia.
Yes I am pissy I read loggs. Thank you for your Post.
works for you great give me the link to Nvida download. This is not slackbooks.
I Re write the the code to build not a patch. you show me on the nvidia site the 384.111.
That said do not confuse people.
190.42
Ignore the first link, that is my bad, it was the wrong link. see the other two. This is fixed.
when you have a nvidia link. let me know I fixed the build not a hobby to me. Extract the installer now edit the code for a newer gcc. KISS.
Give me a link to nvidida. Not Ponce.
Fair enough, if you are wanting a fix from nvidia then I guess you will have to wait for the next driver release, but if you look at the patch its a only a few lines of code in one file. You could just extract the .run executable and apply the patch yourself, or just add the few lines of code yourself then run the installer, or last, just download the slackbuilds from ponce and buld, done. Shouldn't take more than a few minutes, but to each his own, I am just trying to help you out.
Fair enough, if you are wanting a fix from nvidia then I guess you will have to wait for the next driver release, but if you look at the patch its a only a few lines of code in one file. You could just extract the .run executable and apply the patch yourself, or just add the few lines of code yourself then run the installer, or last, just download the slackbuilds from ponce and buld, done. Shouldn't take more than a few minutes, but to each his own, I am just trying to help you out.
next driver does not support multi lib read the nvidia log
in the meantime I updated it in the unofficial repository for current to 384.111 (it wasn't out when I pushed the previous update).
I don't know if Edward feels like pushing this update to SBo yet: it's up to him and SBo supports only stable, so the version that's there is fine.
I don't know if Edward feels like pushing this update to SBo yet: it's up to him and SBo supports only stable, so the version that's there is fine.
True, that was just an assumption on my part. Thanks for this update though, do you know if this version is a short term dev version or is it considered a stable release?
do you know if this version is a short term dev version or is it considered a stable release?
according to the page where the lead developer announces the new releases, the 384.x branch is listed as long-lived: also, I suppose the released 384.111 in a rush to avoid breakage with the newers Spectre-safe-kernels so they haven't got the time to update that page yet with the necessary data.
according to the page where the lead developer announces the new releases, the 384.x branch is listed as long-lived: also, I suppose the released 384.111 in a rush to avoid breakage with the newers Spectre-safe-kernels so they haven't got the time to update that page yet with the necessary data.
You know, maybe I do nitpicking, BUT...
Nothing protects our sorry asses against Spectre, the KPTI is literally protection against Meltdown.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.