Problem when upgrade to kernel 2.4.24
 

Hi, recently I upgrade to kernel 2.4.24. I download it recompiled from slackware.com it upgrade fine, but every time I boot my machine i get this messages in all the boot proccess:

Note: /etc/modules.conf is more recent than /lib/modules/2.4.24/modules.dep

I got those messages in all modules dependencies boot. I don't think thats Ok, maybe is not a big, big problem. but there is a way to resolve this?

hmm... did you do make dep while recompiling the kernel?

No i didn't do that because i download the package kernel-2.4.24.tgz from slackware.com for install those packages you just have to do:

upgradepkg kernel

I did it before whit version 2.4.23 and didn't have problem at all. So it surprise me that now, did that. I didn't download the kernel source, because i haven't need it upgrading the kernel the way i say before. anyway if someone had the same problem and know any solution for this bug?? maybe could reply.

run 'depmod' as root.

I run it depmod as root, but nothing happens it doesn't say nothing to me. I restart my box and still have the message:

Note: /etc/modules.conf is more recent than bla bla

Someone told me that this was a modutils bug, I don't know my worried is that this problem could leave a bug in my box than other people could used to hack me. If this doesn't make any problem like a big bug or something, I don't mind continue receiving this message, cause my Box still works fine, I haven't had any problem at all.

Someone else jump in here, since I've never used
this way to upgrade a kernel before ....

Will upgradepkg touch his lilo-configuration
and actually make the machine boot the new
kernel without manual interaction?

Little_ball, what output does
uname -r
give you?


Cheers,
Tink

Hello, I got this on:

root@Marian:/home/marian# uname -a
Linux Marian 2.4.24 #6 Turs Jan 8 13:44:46 PST 2004 i586 unknown unknown GNU/Linux
root@Marian:/home/marian# uname -r
2.4.24

K, so it does pick up the right kernel.

what does
ls -l /etc/modules.conf
and
ls -l /lib/modules/2.4.24/modules.dep
give you?

Maybe your problem is a
/etc/modules.conf
with a creation date in the future?


Cheers,
Tink

did you also install the kernel-modules package for 2.4.24 ?

root@Marian:/home/marian# ls -l /etc/modules.conf
-rw-r--r-- 1 root root 0 Sep 24 2003 /etc/modules.conf
root@Marian:/home/marian# ls -l /lib/modules/2.4.24/modules.dep
-rw-r--r-- 1 root root 136201 Jan 8 03:08 /lib/modules/2.4.24/modules.dep


Excuse me, but what is a creation date? I'm a little lost here. :cry: anyway I hope you people could help me, like you already had before :)

By the way, I think that yes is true, is the date :cry: I know look at my date, and it was Jan 1 1999 I update it know but the modules kernel still old look:

root@Marian:/home/marian# ls -l /lib/modules/2.4.24/modules.dep
-rw-r--r-- 1 root root 136201 Jan 1 1999 /lib/modules/2.4.24/modules.dep

how can I update it too? does I have to download it again? and install it :(

goto
ftp://slackware.at/slackware-9.1/patches/packages
and download
kernel-modules-2.4.24-i486-1.tgz
the do an
upgradepkg kernel-modules-2.4.24-i486-1.tgz
this could solve your problem
if it's still naggin you...
<everybody insert the sentence he knows i wanna say> ^^

I can't do that, because I already have upgrade kernel package, And when i tried to upgrade it again, it skip the package because is installed :( Well I guess i would have to wait to next kernel release and update it whit the correct date. Thanks by the way.

could you issue the following command ->
ls /var/log/packages/|grep kernel

and post the output ?

root@Marian:/home/marian# ls /var/log/packages/|grep kernel
kernel-headers-2.4.22-i386-1
kernel-ide-2.4.24-i486-1
kernel-modules-2.4.24-i486-1

thats give me.

strange...it seems sane... :confused:
well there's one thing that _always_ works...
recompiling your kernel...if you dare ^^
download
kernel-source-2.4.24-noarch-1.tgz

install the source ->
installpkg kernel-source-2.4.24-noarch-1.tgz

then, copy the configuration file over, be absolutuly sure nothing goes wrong at this point...
cp /boot/config-ide-2.4.24 /usr/src/linux/.config

then compile your kernel->
cd /usr/src/linux/
make oldconfig dep clean bzImage modules modules_install

install your kernel image ->
cp System.map /boot/
cat arch/i386/boot/bzImage > /boot/vmlinuz

update lilo ->
lilo

if you do....be careful that you type everything without errors...otherwise you are in danger you have to boot from CD...
sorry...I don't have any other suggestions =(

regards

That's what i was afraid off poison, I prefer to wait the next release of the kernel than compiling the source and maybe something goes wrong :S, I compile kernel 2.6 to slackware and try it 4 times and never obtain my internet or sound to work, that what you suggest is the best way for me I know but i don't want to go trough that, I will wait, and next time that wont happen to me.

My doubt is now, if modules.conf is newer than lib/modules.conf of kernel 2.4.24 what modules does my Box are using right now the one that cames whit 2.4.24 kernel or the one that was whit the old kernel 2.4.23?

hmmm...thats the strange part...
you seem to have the 2.4.24 modules installed...so it should have upgraded your modules.conf
...
don't be afraid too much of compiling you're first kernel =)
2.6 still isn't mature enough yet in my opinion and there still is some missing stuff...I've changed back to 2.4 because I had problems with my GFX card...
after the 3rd recompile you'll say something like..."damned this is boring..." ^^
the steps I posted above will recreate the original configuration used by the stock 2.4.24 slackware kernel...so you don't have to configure it....and the things that worked before will also work...

To make a file/dir become current u just touch it, like ..
# touch /lib/modules/2.4.24/modules.dep

Dear god :D thank you all. it works very fine the stuff of

touch /lib/modules/2.4.25/modules.dep

I am so happy now, i reboot my machine and i don't see anymore the stuff of the modules.conf newer :D I'm so glad of all of you people here helping newbies like me, going on whit slackware. If it wasn't for this forum, and all the good people who help my simple doubts Probably I will give up using slackware, but instead i'm learning to love it with all your good help. Thank you very much, to poison for his advice an for the user who open my eyes showing me that my error was because of the date stuff. I'm so glad whit all of you guys, :) keep the good working On.