On Fri, Jan 22, 2010 at 8:29 PM, infernix <infernix@xxxxxxxxxxxx> wrote: > On 23/01/10 02:23, Robert Hancock wrote: >> >> From what I can gather from the ICH7 datasheet, when using AHCI the IDE >> controller is supposed to show up as device 1f.1 and the SATA controller >> as 1f.2. It seems like for some reason your BIOS is disabling the IDE >> controller entirely in that mode, which appears rather wrong. > > Well kind of, but not completely since that old IDE PIIX driver does work > when its set to Enhanced AHCI. It's just that it doesn't show up on the PCI > bus, or so it seems at least. > >> Do you have the latest BIOS for that board? > > Yes, but it's a SOHO NAS box by Intel; the SS4200-E is the branded one that > comes with some kind of EMC NAS software, and the ESW is the OEM version > which is sold under various names, without the software. I've got the > latter. > > In either case, there's no BIOS upgrades, only "firmware" which is the EMC > NAS stuff that gets shipped with the -E version, and Intel put up a notice > on Jan 10th that the product is discontinued since Dec '09. So that's a dead > end. > > Can we force ata_piix to pick up the IDE controller? I mean the old IDE PIIX > driver can do it (albeit terribly slow), so why can't ata_piix? I won't lose > sleep if I have to pass an option to the kernel or modprobe for this to > happen as it's an uncommon case. I don't think it actually is the IDE PIIX driver that's picking it up, it's the generic IDE driver which detects it by banging ports randomly, and doesn't know anything about DMA support, which is likely why it's so slow. ata_piix doesn't know about anything that doesn't show up on the PCI bus. Since the chipset does have open documentation, one might be able to develop a PCI quirk that would re-enable the disabled IDE interface so that ata_piix can access it. That would likely be the best option, albeit still rather ugly and highly system-specific.. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
