On Sun, Nov 26, 2000 at 08:17:42PM -0800, kmself@ix.netcom.com wrote: > on Sat, Nov 25, 2000 at 11:50:15PM -0600, Joseph Anthony ([EMAIL PROTECTED]) > wrote: > > I just installed Debian 2.2 and compiled the 2.2.17 kernel on a 3.2 gig > > Quantum Fireball EX. The drive is a slave on the primary IDE cable and > > both drives are jumpered correctly. I did bad block scans when > > initializing all partitions and nothing bad came up. This is the error: > > > > Starting deferred execution scheduler: atdhdb: dma_intr: status=0x51 { > > DriveReady SeekComplete Error } > > hdb: dma_intr: error=0x84 { DriveStatusError BadCRC } > > hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > hdb: dma_intr: error=0x84 { DriveStatusError BadCRC } > > hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > hdb: dma_intr: error=0x84 { DriveStatusError BadCRC } > > hdb: timeout waiting for DMA > > hdb: irq timeout: status=0x59 { DriveReady SeekComplete DataRequest Error > > } > > hdb: irq timeout: error=0x84 { DriveStatusError BadCRC } > > hdb: DMA disabled > > ide0: reset: success > > > > Can anyone tell me what I can do to fix this? > > You may have a bad drive. Or you could have problems with DMA, though I > don't particularly understand it.
Check the kernel documentation for notes on DMA. Or if you're using the menu configurator for configuring a kernel, look at the help notes within. I recall seeing notes on an option to be used with one of the IDE drivers in cases like the above.