I've compiled a new kernel in Debian sarge, 2.6.6. The kernel compiles, installs but when i try to make th initrd.img file I get this error.

command:
mkinitrd -o initrd.img-2.6.6 2.6.6


error:

/usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
FATAL: Module sd_mod not found.


If I try to load the kernel without the initrd.img I get this error:


kernel panic: VFS: unable to mount root fs on unknown-block (0,0)


This is what I've done with the kernel config.

I removed the 1394 support, parallel support, sound support, raid support, and nic drivers that are not needed. All of these are not needed on the computer so I removed them. I then added scsi support and scsi-emulation support for cd burning. The compile goes fine but when I try to make the initrd.img it fails with the above error.

I can make the initrd.img without error if I don't try to cut down the things that aren't needed. If I try to get rid of drivers that aren't needed I get the error.

What did I do wrong and what do I need to put back to solve this error?

You dropped support for scsi disks (scsi disk module = sd_mod).
You need it if you need support for:
-firewire disks (eg. HD:s with fw connector)
-usb storage (eg. memory sticks, compact flash/ camera readers, usb hds)
-scsi disks.
-some others.

You have to either put it back (recommended), or
-modify your /etc/mkinitrd/mkinitrd.conf to not scan everything (change "MODULES=most" to "MODULES=dep")
-and explicitly say what modules are needed to boot the system up in /etc/mkinitrd/modules.

For example I have lines
in my modules -file, because I have my root in reiserfs filesystem, piix ide chipset, Adaptec scsi controller having one hd there for root and Silicon image raid controller having software raid and lvm.

Actually I chose to have scsi disk support in the kernel instead of a module. I wanted it in there for the scsi emulation for my atapi dvd writer. Does it need to be left as a module? And not included in the kernel? Seems so.

have you looked at kernel-package? It's a package of scripts that allows you to make a .deb image of a kernel. After going through the process, you then type dpkg -i <kernel package name.deb> and you have a new kernel installed . Check it out.

I've got kernel-package installed and when I'm done I get the .deb file for my kernel, and dpkg installs it. Those are none of the problems I'm having in any way what so ever.

The problem is that when I choose to have scsi support put into my kernel rather than leaving it as modules I get an error.

Thanks for the suggestion, though it does not relate to the problem I'm having.

sorry, I'm fairly new, and, well, I try to help people. But I guess I didn't read the thread thoroughly enough. Sorry again

It's not a problem, I just wanted to be clear on what the issue is so people aren't wasting their time with solutions that don't address the problem.

Thanks.

i would leave the scsi as amodule and redefine you kernel to only include
your filesysem, IDE Chip Support and eliminate support for initrd.....this
way you can boot without the need for initrd...

see the following:
http://www.desktop-linux.net/debkernel.htm
http://myrddin.org/howto/debian-kernel-recompile.php
http://www.digitalhermit.com/linux/K...ild-HOWTO.html

Did your command to compile the kernel include --intird? Like: make-kpkg --initrd --append-to-version=-051104 kernel_image
You'll get a warning about initrd, you can just continue. When compiling is done and you install the new kernel dpkg -i blablabla it will install the new initrd aswell. No need to do anything extra, just reboot to your new kernel......

When I do it that way I get a kernel panic. The problem is that I included scsi in the kernel and it's still trying to load them as modules. That's where I'm getting the FATAL: Module sd_mod not found error.

I'm going to just have to leave scsi out of the kernel and use it only as modules. My attempts without scsi in the kernel have worked. I just want it in there.