Date: 22 Jul 1999 14:22:03 +0200 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: Jos Vissers <jvissers@sci.kun.nl> Cc: stable@freebsd.org Subject: Re: HEADS UP: IDE breakage Message-ID: <xzpaesodgd0.fsf@flood.ping.uio.no> In-Reply-To: Jos Vissers's message of "Thu, 22 Jul 1999 14:00:23 %2B0200 (MET DST)" References: <199907221200.OAA14902@studs3.sci.kun.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Jos Vissers <jvissers@sci.kun.nl> writes: > I won't send this to the list as I am not currently behind my FreeBSD > box and cannot confirm or test anything I'll answer to the list since this is of general interest to -STABLE users, and I *can* confirm what you've experienced. > but I have been getting > that same message for a long time whenever I tried to enable DMA mode. > It might be that the VIA chipset (Asus P5A) is not properly supported. It usually occurs with UDMA disks on Aladdin chipsets (VIA use the Acer Aladdin IV/V IDE chipset). > I got loads of these messages when I did a find on the disk, so I > decided not to use DMA. Just disable UDMA in the BIOS (unless you have a fucked-up AMI BIOS which won't let you disable UDMA). Normal DMA should work fine. > I just assumed DMA didn't work properly yet but seeing this message > I assume it should work, at least in 3.2-stable which is what I am > running. DMA is supposed to work on all chipsets (AFAIK). UDMA is known to be broken on some chipsets (including the Acer Aladdin IV/V). > I checked the archives but they didn't reveal anything useful to me. Search for UDMA or UltraDMA (or variants thereof) in the -hackers and -current archives. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no 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?xzpaesodgd0.fsf>