Rod Butcher wrote:
Isn't PIIX the Intel driver ? I understand you need the driver appropriate to your board / controller. In my case it's CONFIG_SCSI_SATA_VIA=y ... or have I not understood something here ? In fact, I believe my first compile included all the drivers, still no dice.
My comments was in relation t yours re: libata. libata is used with the specific driver.
I am assuming a few things, here. I was assuming you are examing your /var/log/messages and the output of your dmesg.
Your /var/log/messages should show some lines like:
snipped .....
Dec 7 17:33:30 hdtv kernel: SCSI subsystem initialized
Dec 7 17:33:30 hdtv kernel: ACPI: PCI interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 18
Dec 7 17:33:30 hdtv kernel: ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 18
Dec 7 17:33:30 hdtv kernel: ata2: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 18
Dec 7 17:33:30 hdtv kernel: ata1: dev 0 ATA, max UDMA/133, 312579695 sectors: lba48
Dec 7 17:33:30 hdtv kernel: ata1: dev 0 configured for UDMA/133
Dec 7 17:33:30 hdtv kernel: scsi0 : ata_piix
Dec 7 17:33:30 hdtv kernel: ata2: SATA port has no device.
Dec 7 17:33:30 hdtv kernel: scsi1 : ata_piix
Dec 7 17:33:30 hdtv kernel: Vendor: ATA Model: ST3160827AS Rev: 3.03
Dec 7 17:33:30 hdtv kernel: Type: Direct-Access ANSI SCSI revision: 05
Dec 7 17:33:30 hdtv kernel: SCSI device sda: 312579695 512-byte hdwr sectors (160041 MB)
Dec 7 17:33:30 hdtv kernel: SCSI device sda: drive cache: write back
Dec 7 17:33:30 hdtv kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
Look for a line like I have above, namely: scsi0:ata_piix
What do you have after scsi0 or scs1 ?
That is the driver that you have to modprobe.
So, say:
# modprobe ata_piix
And you will be on your merry way.
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
