bug1 wrote:
> I got the drivers for my various hdd to put them permanently on udma/33
> mode, however one of my drives is still detected as UDMA/66 by the
> HPT366 BIOS
This is normal. The BIOS asks the drives what they can do. Then
Linux ignores it. But it sounds like you're using the HPT366 Linux
driver. This may have bugs in it. AFAIK, the Bootprompt method
uses the standard EIDE drivers&kernel, and just tells Linux where
to find the HPT366. I would consider this method most reliable
until the HPT366 driver is fully debugged.
> Both the onboard and PCI card HPT366 use the same interrupt for two
> channels. I have interrupt shareing compiled into the kernel though,
So this isn't a BP6 or other board with an on-mobo HPT366.
Another hint: Fast EIDE is hard on cables. Keep them short
and messy (don't block airflow). IIRC 14" is spec, but I often
cut off the last connector. And never leave a dangling connector
at the end but unused connector in the middle is OK. Always use
a UDMA/66 cable if the card/socket expects one (HPT366 controller).
Furthermore, for an EIDE disk farm I'd look into possibly
resetting the interrupt priorities. Some old serial ports
had trouble with too low a priority. That may be coming back
for fast EIDE disks if the buffers/transfers are small (512-1024B)
--
=- To unsubscribe, email [EMAIL PROTECTED] with the -=
=- body of "unsubscribe linux-abit". -=
