> So why are the IBM drives picked on? I thought this was a hpt366 problem,
> and possibly has only shown up with IBM drives so far.
> It sounds like the proper fix would be to not enable ata66 by default.
It's a combination of chipset and drive that causes the problems. I've
been using ata66 with the same controller on a different drive
(FUJITSU MPE3136AT) for some time now, and it's been rock solid. It's only
the IBM DTLA drive that's been a problem on this controller.
There may be other drives which show the same problems, and perhaps we
should have an ata66 whitelist rather than a blacklist. But it's not just
a simple case that the controller can't do ata66 properly.
Highpoint made changes in their 1.26¹ BIOS to correctly support the IBM
DTLA drives. If we can get access to information about what they had to
change, we ought to be able to get it to work on those drives reliably.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org Please read the FAQ at http://www.tux.org/lkml/