Could not load /lib/modules/2.6.12.5/modules.dep
Renaud Vernet
renaud.vernet at cern.ch
Thu Aug 18 16:06:20 UTC 2005
Michael R Head wrote:
> On Thu, 2005-08-18 at 11:40 +0200, Renaud Vernet wrote:
>
>>Hi
>>I have just compiled 2.6.12.5 kernel, but I can't boot with it ; I get
>>something like :
>>
>>Could not load /lib/modules/2.6.12.5/modules.dep : no such file or directory
>>Could not load /lib/modules/2.6.12.5/modules.dep : no such file or directory
>>Could not load /lib/modules/2.6.12.5/modules.dep : no such file or directory
>>....
>>
>>and then a "kernel panic : attempted to kill init" or something like that.
>>
>>But the file /lib/modules/2.6.12.5/modules.dep DOES exist, and seems ok.
>>What can cause such a behaviour ??
>>Any idea ??
>
>
> Are you sure you've got built an initrd? Ubuntu loads the
> modules/drivers out of the kernel's inird before mounting the root
> filesystem (correct me if I'm wrong), so if you haven't got an initrd
> for the kernel, it won't find modules.dep.
>
> (just a guess, I haven't built my own kernel in a while... since I
> started using the 2.4 kernel on debian a few years ago)
> mike
>
>
>>Thanks a lot,
>> Renaud
>>
>>
>>==============================
>>My grub's menu.lst entries :
>>
>>title Ubuntu, kernel 2.6.12.5
>>root (hd0,4)
>>kernel /boot/vmlinuz-2.6.12.5 root=/dev/sda5 ro quiet splash
>>initrd /boot/initrd.img-2.6.12.5
>>savedefault
>>boot
>>
>># THIS IS THE DEFAULT ONE :
>>title Ubuntu, kernel 2.6.10-5-386
>>root (hd0,4)
>>kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/sda5 ro quiet splash
>>initrd /boot/initrd.img-2.6.10-5-386
>>savedefault
>>boot
>>===============================
>>my /boot directory :
>>
>>vernet at sbgat83:~$ ll /boot/
>>total 13M
>>-rw-r--r-- 1 root root 826K May 20 19:22 System.map-2.6.10-5-386
>>-rw-r--r-- 1 root root 863K Aug 18 01:09 System.map-2.6.12.5
>>-rw-r--r-- 1 root root 59K May 20 15:47 config-2.6.10-5-386
>>-rw-r--r-- 1 root root 50K Aug 18 01:09 config-2.6.12.5
>>drwxr-xr-x 2 root root 4.0K Aug 18 01:12 grub
>>-rw-r--r-- 1 root root 4.3M Jun 7 13:32 initrd.img-2.6.10-5-386
>>-rw-r--r-- 1 root root 4.3M Aug 18 01:11 initrd.img-2.6.12.5
>>-rw-r--r-- 1 root root 93K Mar 31 13:08 memtest86+.bin
>>-rw-r--r-- 1 root root 1.2M May 20 19:22 vmlinuz-2.6.10-5-386
>>-rw-r--r-- 1 root root 1.2M Aug 18 01:09 vmlinuz-2.6.12.5
>>==================================
>>my /lib/modules :
>>
>>vernet at sbgat83:~$ ll `find /lib/modules/*/modules.dep`
>>-rw-r--r-- 1 root root 254K Aug 17 19:17
>>/lib/modules/2.6.10-5-386/modules.dep
>>-rw-r--r-- 1 root root 94K Aug 18 01:09 /lib/modules/2.6.12.5/modules.dep
>>
>>
>>
>
>
Well, I tried without initrd, and it did not boot either. There was also
a kernel panic, but a different error message that I'll post later, when
I reboot.
The thing is that the default Ubuntu kernel image (2.6.10-5-386 in my
case, which comes without the source) is installed WITH an initrd.
At first I tried with the 2.6.10 kernel, which I supposed to be the
corresponding sources of the default installed image, so as to be able
to use the same config file.
So I copied the /boot/config-2.6.10-5-386 in /usr/src/linux/.config, I
compiled and installed the new kernel, and created the initrd : I got
exactly the same error messages (could not load etc.)
I don't know exaclty why/when the initrd is needed, but I guess if the
same options of my .config file is the same as the default
config-2.6.10-5-386, it should work... am I wrong ?
Anyway, I'll try again without the initrd in the meantime.
Thanks for your answer,
Renaud
More information about the ubuntu-users
mailing list