Date: Sat, 8 Jan 2000 14:56:00 +0100 (CET) From: Soren Schmidt <sos@freebsd.dk> To: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren) Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA driver timeout Message-ID: <200001081356.OAA56905@freebsd.dk> In-Reply-To: <Pine.BSF.4.21.0001081414400.243-100000@Cal30B054.student.utwente.nl> from Theo van Klaveren at "Jan 8, 2000 02:19:03 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
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 mistaken it also disabled UDMA33 on the > second drive. Yup, it was more to determine is DMA really was your problem... > Ah well.. at least I can boot an ATA kernel now. > > > And yes, I'm working on a way to set this from useland... > > That'd be really nice, though if the kernel doesn't even boot to single > user mode, I don't see how this would help users with this problem, as > you'd have to do it before reboot. The idea is to boot in non-DMA mode, and then have a script setup the wanted modes from etc/rc*. That way you can always boot into singleuser mode and change the access modes... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001081356.OAA56905>