If thats the case, whats stopping you from getting the seagate util which
enables you to set the drive to be told, its going to run in UDMA33
mode... and then maybe this error from your past might disappear. I cant
recall the prog, but its on the seagate homepages somewhere...
On Thu, 15 Mar 2001, Jeffrey Borg wrote:
> It is caused by connecting a UDMA66 Drive to a UDMA33 Controller
>
> From my experiences in a squid proxy box it seems to be pretty harmless
> And I have found no solution to the problem.
>
> On Thu, 15 Mar 2001, Sean Carmody wrote:
>
> > I also have slightly irritating (but apparently harmless) kernel
> > messages that pop up repeatedly each day:
> >
> > Mar 14 23:01:29 cardano kernel: hda: status timeout: status=0xd0 { Busy }
> > Mar 14 23:01:29 cardano kernel: hda: no DRQ after issuing WRITE
> > Mar 14 23:01:29 cardano kernel: ide0: reset: success
> >
> > The hard-disk in question is a Seagate:
> > hda: ST313021A, ATA DISK drive
> > hda: ST313021A, 12419MB w/512kB Cache, CHS=1583/255/63
>
>
>
> --
> SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
> More Info: http://slug.org.au/lists/listinfo/slug
>
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
