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.
Thanks Richard,
Doesn’t work . . .
I did it over and over again and I keep getting the same ‘error’.
ERROR: unable to load the kernel module ‘nvidia.ko’. This happens most frequently when this kernel module was built against the wrong or improperly configured kernel sources, with a version of gcc that differs from the one used to build the target kernel, or if another driver, such as nouveau, is present and prevents the NVIDIA kernel module from obtaining ownership of the NVIDIA GPU(s) , or no NVIDIA GPU installed in this system is supported by this NVIDIA Linux graphics driver release.
Please see the log entries ‘Kernel module load error’ and ‘Kernel messages’ at the end of the file ‘/var/log/nvidia-installer.log’ for more information.
You can't load any Kernel module/driver without knowing something about the sources that the module was built against. Whatever the nvidia modules are, I suspect that you're trying to load into Kernel 4.4 (the Slackware-14.2 kernel) and this is too old now. For now, install this 5.4 LTS kernel and see if nvidia.ko loads.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,803
Rep:
Quote:
Originally Posted by slackerz
You can't load any Kernel module/driver without knowing something about the sources that the module was built against. Whatever the nvidia modules are, I suspect that you're trying to load into Kernel 4.4 (the Slackware-14.2 kernel) and this is too old now. For now, install this 5.4 LTS kernel and see if nvidia.ko loads.
Just out of curiosity: Is this a problem with the specific nVidia driver the OP mentioned? What is the latest 4.x kernel known to work?
Back on topic: I would extend the suggestion someone else made about level "3" by setting that up in the "id" record in /etc/inittab until such time as the nVidia driver is loading/working when "startx" is used to bring up X11. Once it's working, change /etc/inittab back to use level "4". If for no other reason than to avoid having to manually kill a non-functioning X11 time after time.
Just out of curiosity: Is this a problem with the specific nVidia driver the OP mentioned? What is the latest 4.x kernel known to work?
Back on topic: I would extend the suggestion someone else made about level "3" by setting that up in the "id" record in /etc/inittab until such time as the nVidia driver is loading/working when "startx" is used to bring up X11. Once it's working, change /etc/inittab back to use level "4". If for no other reason than to avoid having to manually kill a non-functioning X11 time after time.
You can load the module at boot or do it manually. It doesn't matter either way. The point being that the module has to be compatible with the kernel.
Again, this has nothing to do with X11.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,803
Rep:
Quote:
Originally Posted by slackerz
You can load the module at boot or do it manually. It doesn't matter either way. The point being that the module has to be compatible with the kernel.
Again, this has nothing to do with X11.
Ah. I got the impression that there was a build problem that was resulting in a bad module that wasn't loading for some reason. I've stuck with stock kernels for ages and rebuild the driver via nVidia's ".run" file when the kernel is updated. For me, working in level 3 is more convenient and then change the run level when all the sausage making is done.
Am I right in assuming that when you use the NVIDIA-foo.run installer from Runlevel 3 it completes without error? If that is true then it would appear the installer may be installing to the wrong kernel, not the one actually in use. It would not complete if it didn't build the nvidia.ko module and place it in "/lib/modules/<kernel version>.
So can you verify that your bootloader (or the boot item you select) points to a kernel that has the source (and headers if you don't build your own kernel) in "/usr/src/linux" and also the same kernel version in "/lib/modules"? I know it seems a bit of a pain, but I think there must be some mismatch for the module to build and install but not be found afterwards. In any case it would be worth eliminating that possibility.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.