[OpenSUSE 11.1] modprobe: FATAL: Could not load /lib/modules

noir911 · 04-30-2009, 07:39 PM

I'm getting "modprobe: FATAL: Could not load /lib/modules/2.6.27.7-9-pae/modules.dep: No such file or directory" in /var/log/messages

This is a OpenSUSE 11.1 box and I haven't modified/ updated/ upgraded anything related to kernel. I use this box only for apache, bind and dhcp servers.

I looked around the system and there is no /lib/modules/2.6.27.7-9-pae/modules.dep
but there is /lib/modules/2.6.27.21-0.1-pae/modules.dep

uname -a shows 2.6.27.7-9-pae #1 SMP

/etc/sysconfig/bootloader shows

default name as DEFAULT_NAME="openSUSE 11.1 - 2.6.27.7-9"

In /boot/grub directory it shows two files have been changed/ created recently: menu.lst.old and menu.lst - both the files have been modified at the exact same time!

menu.lst.old

Code:

# Modified by YaST2. Last modification on Wed Apr 29 11:03:02 2009
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,1)/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1 - 2.6.27.21-0.1
    root (hd0,1)
    kernel /vmlinuz-2.6.27.21-0.1-pae root=/dev/disk/by-id/ata-ST3160828AS_5MT3MBZH-part1 resume=/dev/disk/by-id/ata-ST3160828AS_5MT3MBZH-part3 splash=silent showopts vga=0x31a
    initrd /initrd-2.6.27.21-0.1-pae

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.1 - 2.6.27.21-0.1
    root (hd0,1)
    kernel /vmlinuz-2.6.27.21-0.1-pae root=/dev/disk/by-id/ata-ST3160828AS_5MT3MBZH-part1 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
    initrd /initrd-2.6.27.21-0.1-pae


###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1 - 2.6.27.7-9
    root (hd0,1)
    kernel /vmlinuz-2.6.27.7-9-pae root=/dev/disk/by-id/ata-ST3160828AS_5MT3MBZH-part1 resume=/dev/disk/by-id/ata-ST3160828AS_5MT3MBZH-part3 splash=silent showopts vga=0x31a
    initrd /initrd-2.6.27.7-9-pae


###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.1 - 2.6.27.7-9
    root (hd0,1)
    kernel /vmlinuz-2.6.27.7-9-pae root=/dev/disk/by-id/ata-ST3160828AS_5MT3MBZH-part1 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
    initrd /initrd-2.6.27.7-9-pae

menu.lst

Code:

# Modified by YaST2. Last modification on Wed Apr 29 11:03:02 2009
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,1)/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1 - 2.6.27.21-0.1
    root (hd0,1)
    kernel /vmlinuz-2.6.27.21-0.1-pae root=/dev/disk/by-id/ata-ST3160828AS_5MT3MBZH-part1 resume=/dev/disk/by-id/ata-ST3160828AS_5MT3MBZH-part3 splash=silent showopts vga=0x31a
    initrd /initrd-2.6.27.21-0.1-pae

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.1 - 2.6.27.21-0.1
    root (hd0,1)
    kernel /vmlinuz-2.6.27.21-0.1-pae root=/dev/disk/by-id/ata-ST3160828AS_5MT3MBZH-part1 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
    initrd /initrd-2.6.27.21-0.1-pae

Looks like menu.lst has been modified and the old version is in menu.lst.old - but who would change it? Yast? How? And how can I fix this mess?

Thanks.

JZL240I-U · 05-11-2009, 06:48 AM

Hmm. Why don't you try and create a symbolic link /lib/modules/2.6.27.7-9-pae/modules.dep -> /lib/modules/2.6.27.21-0.1-pae/modules.dep? If all your woes are gone you might simply leave it at that.

The reason for all this might be that you have automatic updates via YAST enabled(forgot the name SuSE / Novell uses for that). That might have gotten you a new kernel (as it should) with no update of the modules.dep (buggy?). You might try to download / update those possibly by installing the kernel sources.

noir911 · 05-20-2009, 04:16 AM

rebooting the box fixed the issue. The kernel was updated automatically after a power failure. Also: creating a symlink wouldn't have been a good idea.

Thanks.

JZL240I-U · 05-20-2009, 05:50 AM

Quote:

Originally Posted by noir911

rebooting the box fixed the issue. The kernel was updated automatically after a power failure.

Aha.

Quote:

Originally Posted by noir911

Also: creating a symlink wouldn't have been a good idea.

Why? Where would it have been dangerous?