Modprobe fatal

[njin1]

I've installed from usb by unetbootin in sdb.
At the boot it show me

modprobe FATAL could not load /lib/modules/2.6.29.4/modules.dep

and go on but i've not internet connection (i cant ping my router)
The file exist and it appear ok.
The md5sum match.
Intrepid work well on this pc.
What i can do ?

[ZEROF]

Some people use this :

I had the same error message, so I suppose, it's the same problem.

I solved it by using initramfs instead of initrd.

I read the previous error messages, befor "modprobe: FATAL: Could not load /lib/modules". I saw, that this error might have occured because the file system couldn't be mounted.

On hxxp://de.wikipedia.org/wiki/Initramfs]initramfs – Wikipedia(this is a german article, in the English wikipedia, this article is missing) I found, that initrd only works, if the drivers for the file system are fix compiled into the kernel. Initrd will not work, if the needed drivers are compiled as modules - and compiling as modules is the standard in most kernels, I learnt.

Initramfs is the successor of initrd. It works independently from this question. So I installed the debian-package "inintramfs-tools".
Within the folder, where my kernel-sources are (don't know, if this is nessecary), I did
Code:

update-inintramfs -c -k 2.6.20

-c says: create (a inintramfs)
-k XYZ says, for whitch Kernel the initramfs should be created.
(Note: There is an other tool named "mkinintramfs". I didn't use it, because it's recommended only for advanced users. "update-inintramfs" is recommended for people like I am.)

Then, I found a new file named "initrd.img-2.6.20" in /boot/.
I inserted
Code:

initrd /boot/initrd.img-2.6.20

into my file /boot/grub/menu.1st

- and it worked.

[Mexicant]

Tried that and it didn't work...couldn't even find the package actually. Anyway, I remember from one of xCPPx's guides on the Luks encrypted volume he unpacked and repacked the initrd image and that did it for me. Just kind of followed what he did in the relavant areas.

cd /boot
cp initrd.img-2.6.29.4 initrd-2.6.29.4.old (Just making a backup)
depmod -a
update-initramfs -k all -c
cd /tmp
gzip -dc /boot/initrd.img-2.6.29.4| cpio -id
touch lib/modules/2.6.29.4/modules.dep
find ./ | cpio -H newc -o > /boot/initrd.img-2.6.29.4.new
gzip /boot/initrd.img-2.6.29.4.new
mv initrd.img-2.6.29.4.new.gz initrd.img-2.6.29.4

Reboot and it should be gone. You can double check your UUID while you're in there to make sure resume works before repacking (sts). If it breaks you can use the .old image through grub to get back into the machine to fix it.

Good luck.

[forix]

@ Mexicant:

Kernel panic...

P.S.

My fault I take that back. I made a mistake on the touch command.. I used /lib/modules/.... instead of lib/modules.

You are correct that this fixes the problem. Thanks!

[rakzhodekams]

Hi,

well i have same problem at boot time, but for now is nothing to worry about. The wicd-server/client can't connect to wireless lan until I reboot.

[syale]

Originally Posted by Mexicant

gzip /boot/initrd.img-2.6.29.4.new
mv initrd.img-2.6.29.4.new.gz initrd.img-2.6.29.4

I changed the above to this to get it to work:

gzip /boot/initrd.img-2.6.29.4.new
cd /boot
mv initrd.img-2.6.29.4.new.gz initrd.img-2.6.29.4

Stephen

[rakzhodekams]

cd /boot
cp initrd.img-2.6.29.4 initrd-2.6.29.4.old (Just making a backup)
depmod -a
update-initramfs -k 2.6.29.4 -c
cd /tmp
gzip -dc /boot/initrd.img-2.6.29.4| cpio -id
touch lib/modules/2.6.29.4/modules.dep
find ./ | cpio -H newc -o > /boot/initrd.img-2.6.29.4.new
gzip /boot/initrd.img-2.6.29.4.new
cd /boot
mv initrd.img-2.6.29.4.new.gz initrd.img-2.6.29.4

Reboot and it should be gone.

Many thanks. It is working very well.

[di2co]

I felt like gambling so I figured I'd give the "easy mode" solution a try.

The "update-grub" command executed as root after removing the install media and rebooting worked for me. You can leave the install media in but the idea is to boot into your new environment.

I apologize I'm not on a linux box or I would paste the code but I don't really think it would be necessary.

edit: Although this fixes the aforementioned issue you'll still need to fix the splash screen manually. In conclusion.. RTFM < WTFV. Just use fix-splash after rebooting into the fresh install (as root).
V/r

[kinchyle]

Originally Posted by rakzhodekams

cd /boot
cp initrd.img-2.6.29.4 initrd-2.6.29.4.old (Just making a backup)
depmod -a
update-initramfs -k 2.6.29.4 -c
cd /tmp
gzip -dc /boot/initrd.img-2.6.29.4| cpio -id
touch lib/modules/2.6.29.4/modules.dep
find ./ | cpio -H newc -o > /boot/initrd.img-2.6.29.4.new
gzip /boot/initrd.img-2.6.29.4.new
cd /boot
mv initrd.img-2.6.29.4.new.gz initrd.img-2.6.29.4

Reboot and it should be gone.

Many thanks. It is working very well.

This fixed me up as well. Thanks!
I started getting this error after reinstalling madwifi.