-------------- Original message ---------------------- From: Tejun Heo <htejun@xxxxxxxxx> > Luiz Fernando N. Capitulino wrote: > > Em Wed, 08 Aug 2007 11:21:08 +0900 > > Tejun Heo <htejun@xxxxxxxxx> escreveu: > > > > | Alan Cox wrote: > > | >>> I'd rather know what is going on here. A drive can legitimately > > | >>> support LBA48 and HPA and refuse READ_NATIVE_MAX_EXT. > > | >> READ_NATIVE_MAX_EXT is mandatory if HPA && LBA48, no > > | > > > | > Ok the report in that thread is different. The offending Maxtor simply > > | > aborts the read_native_max_ext > > | > > | I'll resend sans ata_id_has_hpa() change. Does that sound okay? I > > | don't really think we can do anything other than blacklisting it. > > > > Does that make your patch invalid or is it still ok? > > You controller being ICH ahci, I don't think the chance of the > controller messing things up is pretty slim but, just in case, do you > have another SATA controller to cross check? If not, can you put the > controller into IDE mode so that ata_piix can drive it and test whether > the problem persists? > Hi, Unfortunately, I do not have any machine with a different controller. Whichever I pick in the BIOS between ATA and AHCI, it seems that the drive is always handled by the ahci module, and the boot process goes the exact same way. Is there a way to force the IDE mode? -- kk1 - 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
