Re: SV: After an update som modules points to the old kernel

On Thu, 16 Sep 2004 20:40:45 +0200, Henrik Grevelund wrote:

> Hi Michael
> 
> depmod -ae says:
> depmod: Can't open /lib/modules/2.4.20-8/modules.dep
> 
> /boot
> Contains:
> config-2.4.20-31.9
> config-2.4.20-31.9smp
> 
> initrd-2.4.20-31.9.img
> initrd-2.4.20-31.9smb.img
> 
> module-info-2.4.20-31.9
> module-info-2.4.20-31.9smp
> module-info -> module-info-2.4.20-31.9
> 
> system.map-2.4.20-31.9
> system.map-2.4.20-31.9smp
> system.map -> system.map-2.4.20-31.9
> 
> vmlinux-2.4.20-31.9
> vmlinux-2.4.20-31.9smp
> 
> vmlinuz-2.4.20-31.9
> vmlinuz-2.4.20-31.9smp
> vmlinuz -> vmlinuz-2.4.20-31.9
> 
> boot.b
> chain.b
> grub
> kernel.h
> message
> message.ja
> os2_d.b
> 
> 
> /lib/modules
> contains 2 dirs:
> 2.4.20-31.9
> 2.4.20-31.9smp
> 
> What does the smart man do ?

Did you specify a modules path in /etc/modules.conf maybe?
I wonder where it takes the 2.4.20-8 version from? uname -r
does return 2.4.20-31.9 or 2.4.20-31.9smp, doesn't it?
 
-- 
Fedora Core release 2 (Tettnang) - Linux 2.6.7-1.494.2.2
loadavg: 1.15 1.07 1.04


-- 
Shrike-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/shrike-list