On Sun, Jan 16, 2000 at 06:41:25PM -0500, Tom Diehl wrote:
> On 16 Jan 2000, Harry Putnam wrote:
>
> > Tom Diehl <[EMAIL PROTECTED]> writes:
[...]
> My understanding and limited experience with this tells me that in
> order to really do UDMA66 you need a motherboard that specifically
> supports UDMA66. In my limited experience with this (2 different
> computers) the machines were clearly marked to support UDMA66 and
> there were 4 IDE interface plugs on the Motherboard. 2 to support
> normal IDE (UDMA33 if you will) and 2 to support UDMA66. I have had
> vendors tell me that their board would support UDMA66 but that in
> order to plug it in I had to drill out the plugged hole in the
> ribbon special 80 conductor ribbon cable. Since the book for the
> motherboard specifically said it was good only to UDMA33 I made them
> exchangs it for one that the manufacturer said would do 66. That is
> how I ended up with the Abit with the HPT366 controller.
Tom -- I think Harry's main problem is the BIOS does not want to
recognize the drive and takes a long time to timeout on boot. Once
things get to the kernel, all is OK. Also, I don't think Harry seems
to care whether the drive functions as UDMA33 or 66.
Since I've run out of other suggestions, I can only now suggest to
Harry that he not reboot ;)
FWIW, I have a WD 13G UDMA66 on a BP6 with the std controller, and
never had any problems at all -- either BIOS or Linux. Running UDMA33,
but I don't really care.
--
Hal B
[EMAIL PROTECTED]
--
Linux helps those who help themselves
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
