From owner-freebsd-stable Wed Aug 9 6:27:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fnal.gov (heffalump.fnal.gov [131.225.9.20]) by hub.freebsd.org (Postfix) with ESMTP id 92AE837B594 for ; Wed, 9 Aug 2000 06:27:47 -0700 (PDT) (envelope-from zingelman@fnal.gov) Received: from nova.fnal.gov ([131.225.18.207]) by smtp.fnal.gov (PMDF V6.0-24 #44770) with ESMTP id <0FZ10094B1DFPX@smtp.fnal.gov> for freebsd-stable@FreeBSD.ORG; Wed, 09 Aug 2000 08:27:15 -0500 (CDT) Received: from localhost (tez@localhost) by nova.fnal.gov (8.9.3+Sun/8.9.1) with ESMTP id IAA25566; Wed, 09 Aug 2000 08:27:09 -0500 (CDT) Date: Wed, 09 Aug 2000 08:27:09 -0500 (CDT) From: Tim Zingelman Subject: Re: Re: Strange problems installing 4.0 vs 3.2 (2-d trial) In-reply-to: X-Sender: tez@nova.fnal.gov To: Dave Uhring Cc: freebsd-stable@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-Authentication-warning: nova.fnal.gov: tez owned process doing -bs Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, Dave Uhring wrote: > > something wrong with VIA chipset perhaps? It might be somehow not > > compatible??? strange thing it worked excellent with 3.2 ... > There appears to be something very wrong with Apollo MVP4 chipset. > ... DMA access ... switched over to PIO access ... > ... no one ever continued the discussion. > ... the only workaround mentioned was to replace the 80-wire cable > with a 40-wire cable. Evidently no one cares about the hardware > incompatibility. > Dave I have an MVP3C and had similar problems until I flash upgraded my bios. Now all seems fine. (Though it looks like I have a 40 pin cable...) ata0-master: DMA limitted to UDMA33, non-ATA66 compliant cable ad0: 9787MB [19885/16/63] at ata0-master using UDMA33 acd0: CDROM at ata0-slave using PIO4 afd0: 96MB [96/64/32] at ata1-master using PIO0 - Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message