From owner-freebsd-current Wed Dec 15 18:22:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mppsystems.com (dslmpp.pro-ns.net [208.210.148.205]) by hub.freebsd.org (Postfix) with ESMTP id A14FF15220 for ; Wed, 15 Dec 1999 18:22:01 -0800 (PST) (envelope-from mpp@mppsystems.com) Received: (from mpp@localhost) by mppsystems.com (8.9.3/8.9.3) id TAA00949; Wed, 15 Dec 1999 19:46:04 -0600 (CST) (envelope-from mpp) Date: Wed, 15 Dec 1999 19:46:04 -0600 From: Mike Pritchard To: "D. Rock" Cc: current@FreeBSD.ORG Subject: Re: ATA problem Message-ID: <19991215194604.A887@mppsystems.com> References: <3858052D.A1298D60@dead-end.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <3858052D.A1298D60@dead-end.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 10:16:29PM +0100, D. Rock wrote: > Hi, > > The ata driver tries to enable UDMA for my controller, but fails > (this is no disk problem. The disks can do UDMA, as tested in > another machine). Perhaps UDMA should be disabled for all > VIA 82C586 chips: I have two machines with VIA 82C586 chips and they both seem to do UDMA just fine. Several days ago, one machine didn't work right with UDMA (it detected the disk as UDMA/66, but it is only a UDMA/33 disk), but today after a fresh cvsup and kernel build it seems to be working fine. See the dmesg output below. -Mike ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ad0: ATA-5 disk at ata0 as master ad0: 13029MB (26684784 sectors), 26473 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 Mounting root from ufs:/dev/ad0s2a -- Mike Pritchard mpp@FreeBSD.org or mpp@mppsystems.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message