On Mon, 4 Sep 2000, Lars Knudsen wrote:
> I have have serious problems using a specific Quantum disk connected
> to a Promise ATA/100 controller. The disk causing problems is the
> QUANTUM FIREBALLlct10 30. The disk simply locks up the machine solid
> during boot at the point where it should repo
> Lars,
> Did you add your drives to
> const char *pdc_quirk_drives[] = {
> };
My current quirk_drives from pdc202xx.c
const char *pdc_quirk_drives[] = {
"QUANTUM FIREBALLlct08 08",
"QUANTUM FIREBALLlct10 30",
"QUANTUM FIREBALLlct15 30",
"QUANTUM FIREBALLP KA6.4",
On Tue, 5 Sep 2000, Lars Knudsen wrote:
> > > PDC20267: (U)DMA Burst Bit DISABLED Primary PCI Mode
> > Secondary PCI Mode.
> > ^
> > You have to force the driver into action.
> > You have no way to get UltraDMA enabled.
>
> OK, I removed the CD-rom, and the d
> > PDC20267: (U)DMA Burst Bit DISABLED Primary PCI Mode
> Secondary PCI Mode.
> ^
> You have to force the driver into action.
> You have no way to get UltraDMA enabled.
OK, I removed the CD-rom, and the driver states upon boot:
PDC20267: (U)DMA Burst Bit ENA
On Tue, 5 Sep 2000, Lars Knudsen wrote:
> I tried in two different boxes. I have 3 of the 'QUANTUM FIREBALLlct10 30' drives
>and one
> 'QUANTUM FIREBALLlct15 30' all having the same problem. I tried the IBM-DPTA-373420
> and a Seagate ST38431A on the controllers and cables, without problems. Any
> "QUANTUM FIREBALLlct10 30"
>
> Just add this ti the pdc_quirks_list and see if it fixes the problem.
> It is an nIEN problem.
Horst von Brand, you suggested it could be bad cabling or some other physical problem.
I have tried several cables (yes, UDMA66 cables), I have tried two Promise
cont
"QUANTUM FIREBALLlct10 30"
Just add this ti the pdc_quirks_list and see if it fixes the problem.
It is an nIEN problem.
Cheers,
On Mon, 4 Sep 2000, Lars Knudsen wrote:
> Hi,
>
> I have have serious problems using a specific Quantum disk connected to a Promise
>ATA/100 controller. The disk
7 matches
Mail list logo
