Hello, im newbie in the tux world, now im trying to compile a new kernel 2.6.10, the old version is the 2.4.27, i have a sata hdd, and my mother asus p4s800d with sata controller SIS 180.
My problem is:
When i make the initrd image, display this error:
mkinitrd -o /boot/initrd.img-2.6.10-v2 /lib/modules/2.6.10/
/usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
FATAL: Module sata_sis not found.
FATAL: Module sd_mod not found.
WARNING: This failure MAY indicate that your kernel will not boot!
but it can also be triggered by needed modules being compiled into
the kernel.

in google found that sata_sis is SiS 964/180 SATA support and sd_mod is SCSI disk support. Both modules, i mark as built in, then i try put them as built in, and the initrd image, goes ok. but when i reboot to start my new kernel, this error appears:

VFS: Cannot open root device "sda1" or unknown-block (0,0).
Please append a correct "root" boot options

Google again, and say that for sata disk i must have in built in the follow items:
SCSI device support
SCSI disk support
SCSI generic support
Serial ATA (SATA) support
and my SIS 180.

But again, when i make the initrd image, my problem is the same that at the beggining.
FATAL: Module sata_sis not found.
FATAL: Module sd_mod not found.

Somebody can help me?.

Thanks.

Excuse my poor english.
See ya.

is sata turned on on your mkinitrd.conf?

I dont know how i turned on sata in the .conf, here is my conf file:

# /etc/mkinitrd/mkinitrd.conf:
# Configuration file for mkinitrd(8). See mkinitrd.conf(5).
#
# This file is meant to be parsed as a shell script.

# What modules to install.
MODULES=most

# The length (in seconds) of the startup delay during which linuxrc may be
# interrupted.
DELAY=0

# If this is set to probe mkinitrd will try to figure out what's needed to
# mount the root file system. This is equivalent to the old PROBE=on setting.
ROOT=probe

# This controls the permission of the resulting initrd image.
UMASK=022

# Command to generate the initrd image.
MKIMAGE='mkcramfs %s %s > /dev/null'

# Set this to yes if you want to use busybox(1).
BUSYBOX=no

# Set this to no if you want to disable /usr/share/initrd-tools/scripts.
PKGSCRIPTS=yes

# This is the value for LD_LIBRARY_PATH when deciding what goes onto the
# image.
INITRD_LD_LIBRARY_PATH=$LD_LIBRARY_PATH

# Hardcode partition to resume from so it doesn't have to be specified
# on the command line. The command line will override this setting.
# RESUME=

what i must do? thanks.

Hello, the problem is solved, i put all modules as built in, and dont create an initrd image. The new kernel boots ok. See ya.

Thanks for the help.
Gabriel

thank's for the update.

I had some issue with initrd and my modules initially. It took me a bit to figure it out and get it sorted. I think I was actually missing initrd support in the kernel, or something.

yes, is a little hard that thing of modules and initrd, i read in forums that some users dont use initrd, so i said, i will try without initrd, and it works!!!. I don't know if is recommendable dont use initrd, but well, now works. Although i really want to know the way to use initrd with sata modules, but well i had too many headache for this week, Next target is the Project Looking Glass . Thanks 4 help.

And on the 8th day, God created Google. And it was good. And the people now had a resource to search for answers to all of their problems. There was much rejoycing. ---- Excellent!!!!!!