At 11:26 17/11/2000, Alan Cox wrote:
> > drive problem, considering that another ide drive on the same controller
> > works fine with DMA enabled (a QUANTUM TRB850A) while the Conner
> > Peripherals 1275MB - CFS1275A fails with DMA enabled. They are in fact
> both
>
>And the Conner drives work fi
On Fri, 17 Nov 2000, Alan Cox wrote:
> > Then I need to fix that to prevent the bypass that should not happen.
>
> No you need to fix the PIIX tuning hangs people keep reporting 8)
You can't fix was the docs claim is broken and issuing a channel reset is
the only way out. Unfortunate, this is
> drive problem, considering that another ide drive on the same controller
> works fine with DMA enabled (a QUANTUM TRB850A) while the Conner
> Peripherals 1275MB - CFS1275A fails with DMA enabled. They are in fact both
And the Conner drives work fine on a VIA MVP3 it seems. You need to try
th
At 10:52 17/11/2000, Alan Cox wrote:
> > I tried adding the string that is output for the bad drive by hdparm -i
> > into drivers/ide/ide-dma.c::drive_blacklist and
> > drivers/ide/ide-dma.c::bad_dma_drives but the kernel still says that it is
> > using DMA and the kernel hangs after displaying:
>
> Then I need to fix that to prevent the bypass that should not happen.
No you need to fix the PIIX tuning hangs people keep reporting 8)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.o
> I tried adding the string that is output for the bad drive by hdparm -i
> into drivers/ide/ide-dma.c::drive_blacklist and
> drivers/ide/ide-dma.c::bad_dma_drives but the kernel still says that it is
> using DMA and the kernel hangs after displaying:
The black list is for drives with problems
On Fri, 17 Nov 2000, Anton Altaparmakov wrote:
> I am sure you knew this perfectly well already but just in case it is helpful:
>
> the offending code is in:
>
> drivers/ide/piix.c::piix_dmaproc [starts on line 402 in 2.4.0-test11-pre5]
>
> It calls piix_config_drive_for_dma and only then call
I am sure you knew this perfectly well already but just in case it is helpful:
the offending code is in:
drivers/ide/piix.c::piix_dmaproc [starts on line 402 in 2.4.0-test11-pre5]
It calls piix_config_drive_for_dma and only then calls ide_dmaproc.
It is ide_dmaproc that does the good/bad test
Then I need to fix that to prevent the bypass that should not happen.
On Fri, 17 Nov 2000, Anton Altaparmakov wrote:
> The drive was being added to the black lists fine it's just that I had PIIX
> tuning enabled which caused the good/bad dma tables check to be bypassed
> completely. - So disa
The drive was being added to the black lists fine it's just that I had PIIX
tuning enabled which caused the good/bad dma tables check to be bypassed
completely. - So disabling PIIX tuning made my PC boot fine.
Regards,
Anton
At 00:13 17/11/2000, Anton Altaparmakov wrote:
>Hello all,
>
>I have
Hello all,
I have an ide hard drive that misbehaves when the option "enable DMA at
boot time" (2.4.x kernel) is selected (this is on a on board ide
controller). But on the other hand I have a Promise Ultra-ATA-100
controller with an IBM ATA-100 drive that, according to the menuconfig
informat
11 matches
Mail list logo
