On Sun, 4 Jun 2000, Dan Hollis wrote:
> On Sun, 4 Jun 2000, James Sutherland wrote:
> > On Sun, 4 Jun 2000, Dan Hollis wrote:
> > > http://www.promise.com/Products/idecards/u66.htm
> > > Im using one on a BP6 in place of the broken onboard HPT366.
> > When you say "broken", what do you mean? When I use a generic IDE driver,
> > it's too slow, but works OK - even with DMA. When I use the HPT366 driver,
> > it's even slower, and enabling DMA fscks the CMOS RAM. This looks like a
> > driver problem from here.
> I mean broken as in, when you run the HPT366 in UDMA mode it locks the
> hardware up harder than a rock requiring hardware reset to reboot. Even
> PIO mode is unstable on the damned thing.
A hardware reset doesn't cure this problem - the CMOS RAM is fscked. Also,
the hardware works fine (but slowly) using DMA with the generic driver;
only the HPT366 driver fscks up. It could be due to the specific driver
exercising something the generic one doesn't - but enabling DMA works with
one, but fscks up with the other. Why??
> It happens under windoze as well as linux so its not a driver problem.
Not the same problem. DMA works with one driver but not the other.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:18 EST