> >
> > I have been trying to install yesterday's 4.0 snap on a no-name brand
> > motherboard with the VIA chipset, but I'm running in some problems. I
> > suspect there is a problem with the DMA. The error I'm getting when the
> > disk is newfs'ed is a repeating:
> >
> > ad0: WRITE command timeout - resetting
> > ata0: resetting devices .. done
> > ad0: WRITE command timeout - resetting
> > ata0: resetting devices .. done
> > ...
> >
> > It seems that it is just going on and on. Shouldn't it back down to non
> > DMA mode after a while? Is there a way to disable the DMA on the install
> > floppies?
>
> It should back down after 3 retries... But is is 3 retries pr request,
> so say it gets through on the 2 retry each time this will continue..
> I dont know if there is access to the sysctl knobs from the emergency
> shell, but that would be a solution...
Well it is been doing fsck for more than an hour now. :-) This is
before the emergency shell is opened, but if I remember correctly,
sysctl is not part of tools available.
>
> > Part of the probe looks like this: (written down by hand)
> >
> > atapci0: <VIA 82C586 ATA33 controller> port 0xe000 - 0xe00f at device 7.1 on pci0
> > ata0: at 0x1f0 irq 14 on atapci0
> > ...
> > ad0: 6204MB <ST36531A> [13446/15/63] at ata0-master using UDMA33
>
> Hmm, wierd, did this hardware run FreeBSD before ??
A similar system did run FreeBSD-3.4, but I never enabled DMA on it. I'll
try to install 3.4 on this one and see.
John
--
John Hay -- [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
