SlackwareThis Forum is for the discussion of Slackware Linux.
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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
1 Slackwareold, a stock 2.4.26 kernel
2 Slackware2.6, my own 2.6.6 kernel that sort of works
3 Slackwaretest, my 2.6.6 that I've compiled about 10 times, trying to get all my funky and odd h/w to work.
The problem is whenever i switch between kernel's (if i need to burn a cd i have to use Slackware old, or if i want to have another go at getting my raid card working i use Slackwaretest etc) i have to reinstall the nvidia drivers, now this doesn't take too long but it is becoming tedious.
I notice it compiles a kernel module, is there no way i can just put this somewhere and call it up, so i dont have to faff around every time i switch as its driving me mad!
dunno...I noticed the same thing. luckily I got rid of the thing by changing card why don't you just build one working one and use it? and if you really need a "test-kernel", compile one but don't use X with it (so you don't need to fight with nvidia things), but use it from shell and test your hw and stuff from there until you get it work..that's what I'd do, rather than installing nvidia drivers all the time (yes, it is annoying)
Q: I just upgraded my kernel, and now the NVIDIA kernel module will not
load. What is wrong?
A: The kernel interface layer of the NVIDIA kernel module must be
compiled specifically for the configuration and version of your kernel.
If you upgrade your kernel, then the simplest solution is to reinstall
ADVANCED: You can install the NVIDIA kernel module for a non
running kernel (for example: in the situation where you just built
and installed a new kernel, but have not rebooted yet) with a command
line such as this:
sh NVIDIA-Linux-x86-1.0-5336-pkg1.run --kernel-name='KERNEL_NAME'
Where 'KERNEL_NAME' is what `uname -r` would report if the target
kernel were running.