On Wed, Apr 06, 2005 at 07:16:09AM +0200, Christian Perrier wrote: > > Actually, I think that it is ata_piix. I am attaching my working > > 2.6.11.5 kernel config and the output of lsmod. I am not using an > > initrd image. However, if I modprobe ata_piix and sd_mod, the > > installer still does not find the hard drive. I don't find any > > entries in /dev/scsi either. It does not help to modprobe all of the > > other sata_* modules either. > > > So, loading ata_piix should be the Right Way for discover when finding > your SATA chipset but what you say it that this is not enough with the > D-I kernel, right?
I dare to differ. IIRC `modprobe ata_piix` generates logging in /var/log/syslog with information about the chipset (disc-controller) found. So there is the clue for succesfull `modprobe ata_piix` > So, this problem is dual: > > -discover needs to load the correct module: easy to fix in pci.lst > > -the kernel module must properly handle your hardware: not easy to > fix if this fails with the current 2.6.8-2 kernel we have in D-I > > For everyone reading this: is this the correct conclusion? I agree on the fix in pci.lst. I'm not sure about the "kernel module must properly handle hardware". IMNSHO are inserting kernel modules and scanning for discs two _different_ actions. My questions: * What is the _right way_ to scan for disks in debian-installer? * How to trigger it? (which menu item?) * How to check the result? (which command in the vt2 console?) Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]