Date: Tue, 17 Oct 2000 20:02:16 -0700 From: Greg Lehey <grog@lemis.com> To: "Jose M. Alcaide" <jose@we.lc.ehu.es> Cc: Marc Albers <freebsd@oblomow.demon.nl>, freebsd-stable@FreeBSD.ORG Subject: Re: Via KT133 chipset and DMA diskaccess Message-ID: <20001017200216.D1250@sydney.worldwide.lemis.com> In-Reply-To: <39EC7AAA.642D480@we.lc.ehu.es>; from jose@we.lc.ehu.es on Tue, Oct 17, 2000 at 06:13:30PM %2B0200 References: <E13lWjn-000LqP-00@post.mail.nl.demon.net> <39EC7AAA.642D480@we.lc.ehu.es>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 17 October 2000 at 18:13:30 +0200, Jose M. Alcaide wrote: > Marc Albers wrote: >> >> I'm have not been able to get DMA disk access to work ( DMA33 or >> DMA66 ) on my new Abit KT7. I have heard of several people having it >> working perfectly on their KA133 based motherboards. >> >> Therefore I am curious: Is there anyone who has this working on an >> VIA KT133 based motherboard? If so, can this person assist me in taming my >> beast? >> > > Works here: > > atapci0: <VIA 82C686 ATA66 controller> port 0xffa0-0xffaf at device 7.1 on pci0 > [...] > ad0: 9768MB <ST310212A> [19846/16/63] at ata0-master using UDMA66 > acd0: CDROM <CRD-8482B> at ata1-master using WDMA2 > > The MB is a Gigabyte GA-7ZX. However, I had problems when the CD-ROM > was connected as primary slave: it was not detected, and the ATA probe > routine reported that the cable is not ATA66 compatible (but it > *is*). No, ATA-66 can only connect one device. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001017200216.D1250>