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.
The SBo slackbuild file(s) should be editable to accompany the 367.xx drivers, or any of them really.
This did not work for me (slackware 64 14.2)! I changed the driver version in the slackbuilds nvidia-kernel.SlackBuild and nvidia-driver.SlackBuild from 361.45.11 to 367.44, recompiled both packages and upgraded with upgradepkg. At reboot the X server did not start at all. From the log file it seems the system was not able to load nvidia kernel module properly.
The way in which I fixed the problem was to downgrade to driver version 361.45.11 (in my case this was quite easy because I kept the old SBo) and from there I upgraded to the new nvidia driver just running the NVIDIA-Linux-x86_64-367.44.run installer.
As mentioned in my previous post, currently, I'm running the last nvidia driver (version 367.44). Up to now I'm not having any freezing issues and the system seems quite stable. Anyway thanks for the info. In case of problems I know what to do.
For the nvidia scripts in Slackbuilds.org, since I do not use the nvidia-installer (haven't yet parsed all the CLI options...ugh...), each slackbuild is hand crafted due to Nvidia's habit of changing/adding libs right-and-left. In particular we now have GLVND, non-GLNVD (incompitable with EGL), Vulcan and wayland libs creeping in. In the 367.44 release, there is another kernel module as well.
In short, no you can't just "VERSION=<something> ./nvidia-{driver | kernel}.Slackbuild" No, I say. Bad, Slackers!
Also, if you run the NVIDIA-*.run script, you have to be VERY careful in selecting options. Installing the wrong set can be "exciting".
Please make a note of the following installation procedure (We assume a CLEAN, FULL Slackware installation). sbopkg and such automated tools are contraindicated. nvidia-switch is a stupid, one-trick-pony.
Quote:
$ su -
# cd <appropriate path(s)>
# ./nvidia-kernel.SalackBuild
# ./nvidia-driver.SlackBuild
# installpkg /tmp/nvidia-kernel....tgz /tmp/nvidia-kernel...tgz
# reboot
If you need to remove or upgrade Mesa | Xorg, etc, you will need to fully re-install nvidia-driver
Quote:
$ su -
# nvidia-switch --remove
# removepkg nvidia-driver
# upgradeplg mesa...txz xorg-server...txz
# installpkg /tmp/nvidia-kernel...tgz
** WARNING: there must be NO GL, EGL, GLES file changes in the new Mesa.
If you upgrade ONLY the kernel, you just need to re-run nvidia-driver.Slackbuild and upgradepkg only.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.