Heres the deal. I installed a new hard drive on my existing Slack system, installed Slack 10 on it. I am using lilo on the existing Hard drive to boot either the existing drive or the new one from the lilo boot prompt. I can boot the new drive, Slack is good and gnome starts up. The problem I am having is none of the modules load no matter what I do. When modprobe runs I get an error saying cannot find module so and so. I cannot connect to the internet, load nvidia drivers or load alsa on the new drive. I did notice that in the boot directory all the files have a kernel 2.4.26 but in the /lib/modules directory the kernel is 2.4.27 I tried to make lilo boot the new drive with 2.4.26 and 2.4.27 but it will not. I have already used pkgtool to setup the network, ran rc.inet1 and 2 to start it and nothing. Any ideas on what I should try next. Am I missing a config file that just needs edited? Thanks for any help.

Well if you didn't updated your "fresh" install 2.4.27 modules shouldn't be there so I assume you did it. It won't load anything because kernel 2.4.26 will search for it's modules on /lib/modules/2.4.26 not 27. So if you updated it, be sure to update the kernel too.

Hi
Sounds like you tried to recompile the kernel source and changed the version number in your Makefile under the /usr/src/linux dir.

1st check the symbolic linc to your src it should be
linux -> linux-2-4-26

2nd check in the first 4 or 5 lines in the Makefile for a line with 2.4.27 <<<<this could be the prob if so change it to 2.4.26

3rd i think you could just do a $make modules here to recreate the modules (else you will have to recompile and do the normal procedure that you normally do)

4th do make modules_install, this will create the /lib/modules/2.4.26 dir with all the modules

Do you have 2 different distros on each hd ?
Have you configured lilo.conf properly

Maybe if there are 2 different distros upon loading the modules for each distro are being confused.

mm anyway hope it helps
cheers

I didnt compile or try to upgrade kernel or anything like that, I just installed slack like normally from CDs. I think your both correct, somehow modprobe is looking for one kernel but the other is there, at least the kernel number is different. They are both slack 10 the only difference is the existing one I upgraded to 10 with swaret and the new HD has Slack 10 from downloaded ISO`s. I havent had time to play around with it today, probably wont be until weekend. I did try linux -> linux-2-4-26 and all I get is command not found as user and root.