It seems Hans Ottevanger wrote:
> Tried this patch, and the system does not hang any more. Even better,
> I/O to this disk is still quite fast, at least way faster than using the
> "standard" interface on this board (and even that is not really slow).
> I'll run a "buildworld" as torture test this evening.
Aha, yet another UDMA66 unable disk type :(
> > Trying another disk is also an option, I know that the IBM's
> > work just fine, and that some of the Quantums and WDC's are broken.
>
> I'll try a WD from my other BP6 one off these days. Maybe I had better
> buy IBM in the future.
I've had _very_ good experience with IBM, being over Quantums, WDC and
Maxtors with various bad experiences...
> BTW, would it be possible to modify sysctl() to switch between UDMA66
> and UDMA33, or maybe use "flags" like the old wd driver had. I fear that
> a lot of "broken" hardware is around, and once FreeBSD 4.0 hits the
> streets, you may expect a lot of problem reports.
This is on my list of things, its just not so simple as it sounds
unfortunately. Ideally one shoul dbe able to specify the exact mode
one wants to use, but some of the controllers has bugs in regard
to what sequence the modes can be set...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
