dma error on startup

[catastrofe]

I get all those errors too, I experienced hem with RH9 and now with
Fedora. I still do not know why I get them, I have always wondered if it
got something to do with the file system of the hard disk (the drive
that gives all the errors is a NTFS file system) ¿is this your case?
My secondary controller is enabled in the BIOS, and I still get the
errors...

Best regards.

El mar, 02-12-2003 a las 08:02, Corey Taylor escribió:
> Thanks, I do believe that the secondary controller may be disabled in
> the BIOS, I will try and enable it and see what happens. Thanks.
> 
> Corey
> 
> On Tue, 2003-12-02 at 01:53, Iain Buchanan wrote:
> > On Tue, 2003-12-02 at 14:22, Corey Taylor wrote:
> > > Hi all. I get the following message on startup:
> > >  
> > > Journalled Block Device driver loaded
> > > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> > [etc]
> > >  
> > > Is this a cause for concern. Does this mean I have a bad hard drive?
> > 
> > I used to get this all the time with RH9.  It turned out that my bios
> > settings had something to do with it.  In my bios I had the secondary
> > controller disabled, or something like that, so I re-enabled it, and the
> > messages went away.
> > 
> > Sorry I can't be more specific, it was a while ago!
> > 
> > HTH,
> 
> 
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list