-   Slackware (
-   -   Where is the modules dir for stock 2.6.18 (Slackware 11) (

cygnus-x1 10-16-2006 01:31 PM

Where is the modules dir for stock 2.6.18 (Slackware 11)
We just installed Slackware 11 and chose the stock.2.6.18 kernel (test not bigmem). We realized that the toshiba mousepad was not working so I had him do an lsmod. Nothing. So I guess its all built in so I ask him to do a modprobe psmouse and then we get an error saying that /lib/modules/2.6.18/modules.dep could not be found.

Upon further inspection I see that there is only a directory for 2.4.33 under /lib/modules not one for 2.6.18.

What happened or why is this. Am I going to have to build the 2.6.18 kernel from source to get the modules?

We were trying to avoid this at the moment (time constraint)


Alien Bob 10-16-2006 01:44 PM

Did you actually read what is on screen when you select the test26 kernel?
Did you actually read the RELEAS_NOTES README.txt BOOTING.TXT or whatever?
Your question is simply answered with:

installpkg /testing/packages/linux-2.6.18/kernel-modules-2.6.18-i486-1.tgz

cygnus-x1 10-16-2006 02:09 PM

No I did not and I appologize. Sorry I am assisting a complete newbie and I did not read / install anything myself. I assumed (incorrectly) that if he chose a 2.6 kernel that the modules dir would have been installed.

I am not a complete newbie but I am very green when it comes to installing Slackware as it requires a lot more wide ranging knowlege than I currently posess.

I have only installed Slack 10.1 and 10.2 and had a friend walk me through upgrading to the 2.6 kernel by downloading the kernel headers and source and building it from scratch. Since he knows the hardware really well he knew what options to change in the .config to get things to work.

Would you entertain a few simple questions?

1) Would you advise us to try and use the stock (test) 2.6.18 (A), the stock (huge) 2.6.17(B) or go get the latest and build it from scratch(C)?

2) if suggestion A or B are the modules in the package "source for the modules" or "compiled modules"? I assume its compiled (sorry I don't have the disks in front of me and the new machines network is not running)


Alien Bob 10-16-2006 02:25 PM

If you're not using bleeding edge hardware I would prefer the kernel from "extra" over the 2.6.18 kernel in "testing".
Also, what I usually do (whatever kernel I used for installing) is "installpkg" the kernel-generic- and kernel-modules- packages. The "kernel-generic" kernel is a kernel just like the huge26.s bootkernel from the CD, but it does not have all those drivers compiled-in like the huge26.s kernel has. It's modules are in the corresponding kernel-modules package (these modules can also be used by the huge26.s kernel as I explained to you in my previous post).
After installing these two packages, you will have to add some lines to the lilo configuration file /etc/lilo.conf, like these:

image = /boot/vmlinuz-generic-
  root = /dev/hda1
  label = linux26
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking

You should adapt the "/dev/hda1" to where your root partition resides of course, and you can choose another label name than "linux26".
If you want to make this new kernel the default that LILO starts, then place the above lines in front of all other " Linux bootable partition config" sections, or add "default = linux26" somewhere high up in the file in the global section.
After editing /etc/lilo.conf, you have to run the command "lilo" to install the changes into the disk boot sector.

If you want to play with the kernel and compile your own tweaked version based on the Slackware default kernel, then also install the "/extra/linux-" package, which places the kernel sources in /usr/src/linux-
Then, copy the Slackware kernel config file to this location as well and run "make oldconfig":

cp /boot/config-generic- /usr/src/linux-
cd /usr/src/linux-
make oldconfig

After that, you can run

make xconfig
or "make menuconfig" and tweak the configurations, where the default choices will be those from the Slackware kernel you installed. This gives you a head start in generating a customized kernel.


cygnus-x1 10-16-2006 02:45 PM

Thank you. We got the 2.6.18 kernel working.

All times are GMT -5. The time now is 04:37 AM.