Description of problem:
Installer and other utilities fail to see a serial ATA hard disk connected to an onboard serial
Version-Release number of selected component (if applicable):
lspci gives: 01:0d.0 Unknown mass storage controller: Silicon Image, Inc. (formerly CMD
Technology Inc) Silicon Image Serial ATARaid Controller [ CMD/Sil 3512 ] (rev 01)
Buy a Gigabyte K8NNXP-940 motherboard, or any form of the component, and attach a
Steps to Reproduce:
1. Build machine with SATA card and hard drive.
2. Boot Fedora Core 2 test3
3. Try to install.
Drive not seen.
dmesg fails to mention anything about said serial ATA card.
I am not sure wether or not sil3152 is supported by sata_sil.ko on the
2.6.5 kernel. However, I found the same problem with sil3114; the hard
drives are not detected. FC2 Test 3 does not have the sata_sil module
included in the modules.cgz file that is part of the boot cd/dvd.
I have extracted the isolinux folder from the AMD64 FC2Test3 and
modified it to work. You can get a copy at
The silicon image is widely used on amd64 motherboards, so it would be
very discouraging to fedora users if this module is not included in
the final release.
I have checked with Jose and after modifying the initrd on the cd the
controller gets recognized. Here is how you do it (for the impatient
and in case this does not make it to FC2 release):
1. You need another machine already running the distribution to obtain
the sata_sil.ko module. Make sure the kernel version and architecture
from the running version is the same as the kernel used on the boot
cd. It should be under /lib/modules/2.6.5-1.327/kernel/drivers/scsi/
If you had a FC2 Test2 machine already running you could just install
the new kernel RPM and then obtain the module from there.
2. Start with the FC2 Test 3 ISO that is adequate for your computer
(X86 or X86_64). I recommend you to use a copy of the ISO so that you
do not damage the original one. I will mount the ISO on /tmp/FC2T3:
3. cd /tmp
mount -o loop /path/to/iso/ /tmp/FC2T3
gunzip -c /tmp/FC2T3/isolinux/initrd.img > /tmp/initrd.img
mount -o loop /tmp/isolinux/initrd.img /tmp/initrdloop
Add the following entries for sil3114 and sil3512 chipsets(One line
no wrapping and use tabs instead of spaces. I have not tried sil3112
so It may also should be added like 3114 and 3512):
0x108e 0x2bad "sungem" "Sun|GEM"
0x1095 0x3114 "sata_sil" "Silicon Graphics, Inc.|SiL 3114
0x1095 0x3512 "sata_sil" "Silicon Graphics, Inc.|SiL 3512
0x10a9 0x0009 "acenic" "Silicon Graphics, Inc.|AceNIC
find the "sata_" entries and add sata_sil if missing as shown:
sata_sil: libata scsi_mod
find the "sata_" entries and add:
"Promise SATA controllers"
"Silicon Image SATA controllers"
"VIA SATA controllers"
3. mkdir /tmp/modules
gunzip -c /tmp/initrdloop/modules/modules.cgz | cpio -dvi
You should see a bunch of modules there (notice that I am working
with X86_64, so your version may just be /tmp/modules/2.6.5-1.327/x86
for the 32 bit version of Fedora).
Now you need to copy the sata_sil module here:
find 2.6.5-1.327 -print -depth| cpio -H crc -o | gzip -c > modules.cgz
Now overwrite the modules.cgz on the initrdloop/modules folder
cp /tmp/modules/modules.cgz /tmp/initrdloop/modules/
4. We can now unmount the initrd and put it back on the cd
gzip -c initrd.img > newinitrd.img
cp -rp /tmp/newinitrd.img /tmp/FC2T3/isolinux/initrd.img
5. Clean up!
rm -rf /tmp/initrdloop /tmp/initrd.img /tmp/newinitrd.img /tmp/FC2T3
6. Burn a new CD with the modified ISO and enjoy.
I tried to modify the CD as you described. But there is a small problem:
cp -rp /tmp/newinitrd.img /tmp/FC2T3/isolinux/initrd.img does not work
because the ISO9660 file system is read only by definition. So what
can I do now?
Ok, solved my problem with mkisofs :-)
Looks pretty nice now and works with all 4 S-ATA drives. Thanks.
*** Bug 123152 has been marked as a duplicate of this bug. ***
any better with the latest 2.6.9 updates ?
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.