On Sat, 8 Jan 2000, Soren Schmidt wrote:
> It seems Theo van Klaveren wrote:
> >
> > That helps me, but if I'm not mistaken it also disabled UDMA33 on the
> > second drive.
>
> Yup, it was more to determine is DMA really was your problem...
It was :)
> >
> > That'd be really nice, though if
It seems Theo van Klaveren wrote:
> >
> > Mode 4 is PIO4 that is no DMA, it could very well be the problem,
> > WD has made a lot of problematic drives in this area.
> > You could try to comment out the dmainit call in ata-disk.c and
> > see if that helps you.
>
> That helps me, but if I'm not
On Sat, 8 Jan 2000, Soren Schmidt wrote:
> It seems Theo van Klaveren wrote:
> >
> > I'm in doubt as to the first drive though: The BIOS says it's 'Mode 4',
> > is that the same as WDMA2? Could the harddisk be reporting the wrong
> > value, even though the BIOS is giving the correct one? I'm jus
It seems Theo van Klaveren wrote:
>
> I still can't seem to be able to boot -CURRENT with the ATA driver,
> much as I'd like to, due to the `timeout-resetting device' error, which
> I've seen more people report. I've sacrificed some dead trees to give
> you the exact boot messages:
>
> ad0: ATA
