Robert Redelmeier wrote:
>
> bug1 wrote:
> >
> > The big (and only) problem ive had with my bp6 is the fact that it has a
> > HPT366 built in that i want to use.
> > e2fsck is now causing me irq_timeouts.
>
> Well, this is a definable problem. But are you trying to use the
> UDMA/66 modes on the HPT366 [why?] or are you trying the safer[?]
> UDMA/33 modes by simply specifiying the IRQ & port on the boot prompt?
>
> If you have problems with the former, it's likely a driver issue.
> Problems with latter could have more to do with the HPT366 hardware,
> and there might be a bug that requires some code workaround.
>
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
When linux boots up though the kernel shows them all as UDMA(33).
Ive been *trying* to control the interrupts through the BIOS, i havent
tried specifying the interrupts in the command line, maybe this could
help as ive been having problems dictating what interrupts to use via
the bios, particularly for the onboard controller.
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 shouldnt be a problem should it ?
The onboard controller has a tendancy to try and use the same interrupt
as the PCI controller, so on occasions (but not all the time) ive had
all four channels sharing the one interrupt.
I guess i just use the IDE= command at the boot prompt to specify the
irq ?
Thankyou for your response, this gives me new hope.
Glenn
--
=- To unsubscribe, email [EMAIL PROTECTED] with the -=
=- body of "unsubscribe linux-abit". -=
