2.4.29 kernel showing up as 2.4.26

gitnrdun1115 · 06-26-2005, 04:03 PM

I have just installed the slackware 10.1 distro and when booting it says that it is using 2.4.26 kernel... the networking wont work because it is getting the message:

modprobe: Can't open dependencies file /lib/modules/2.4.26/modules.dep (No such file or directory)

I have a /lib/modules/2.4.29 directory and its not reading out of it...

when i type uname -r it says that it is using 2.4.26 kernel when the 2.4.29 is on the hd.

how can i fix this?

jailbait · 06-26-2005, 04:27 PM

"when i type uname -r it says that it is using 2.4.26 kernel when the 2.4.29 is on the hd.

how can i fix this?"

Look in /boot and see what kernels you have installed. Look in your boot loader configuration file and see what kernel you are actually booting. Then you can probably straighten things out by changing your boot loader to boot the kernel you want.

---------------------------
Steve Stites

egag · 06-26-2005, 04:29 PM

strange thing....
how did you manage that ?

i guess you can boot your sys. from cd with the right boot options.
( there are instructions on screen howto do that )
then install the 2.4.29 kernel ( it's in /a )
don't forget to rerun lilo and check the output before you reboot.

egag

gitnrdun1115 · 06-26-2005, 04:30 PM

everything in boot has a 2.4.29 taged on the end of it

in the lilo.conf file it says:

image = boot/vmlinuz
root = /dev/hda1
label = Linux

gitnrdun1115 · 06-26-2005, 04:32 PM

this is what the slackware installation did,,, everywhere on the hd it says i have 2.4.29 installed... but i cant find out why it is saying that 2.4.26 is loaded. i have installed twice with the same results and a clean install

Tinkster · 06-26-2005, 04:42 PM

Did you do a clean install or an upgrade?

gitnrdun1115 · 06-26-2005, 05:00 PM

in the installer i had it format the destiniation drive.... so i am assuming that constitutes a clean install

egag · 06-26-2005, 05:24 PM

could it be that you've also Slack 10.0 cd's laying around there,
and when you picked a kernel, you slipped in the wrong cd ?
any other thing i can think of besides a " joker's " iso image...

egag

gbonvehi · 06-26-2005, 06:10 PM

Which kernel did you select during installation? I only can thing of some old kernel being left in Slackware 10.1.

gitnrdun1115 · 06-26-2005, 06:11 PM

i downloaded the images from linuxiso.org and burned them right before i installed it, i havent had slack 10.0 cds in a long time. I dont know what the heck is going on

gitnrdun1115 · 06-26-2005, 06:12 PM

i picked the basic or bare or whatever the standard kernel is... i thought that would be 2.4.29 since that was one of the big deals with this release.

gbonvehi · 06-26-2005, 06:18 PM

Well I don't know how you got a 2.4.26, maybe you've a spare /boot partition and the proper symlink couldn't be done..
Anyways, you can install a kernel from the CD, just copy the kernel and it's System.map file and re-run lilo (check /etc/lilo.conf points to it).

egag · 06-26-2005, 06:28 PM

better use "installpkg" to install the cd's kernelpackage.
it will also set the symlink /boot/vmlinuz

or edit lilo.conf to point to /boot/vmlinuz-ide-2.4.29 before you run lilo.

egag

gitnrdun1115 · 06-28-2005, 09:43 PM

well, i re-fdisked my hd and made sure it was a fresh install, and it worked on the third installation attempt... i guess i had a /boot/ partition link that was bad. thanks for all the help guys, you guys respond fast and have some great ideas.... keep up the good work