From owner-freebsd-current Sun Apr 30 0:53:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8B60337B88A for ; Sun, 30 Apr 2000 00:53:07 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA74288; Sun, 30 Apr 2000 09:52:44 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004300752.JAA74288@freebsd.dk> Subject: Re: MVP3 problems - current state? In-Reply-To: <20000429164027.A7708@cichlids.cichlids.com> from Alexander Langer at "Apr 29, 2000 04:40:27 pm" To: alex@big.endian.de (Alexander Langer) Date: Sun, 30 Apr 2000 09:52:44 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alexander Langer wrote: > 20000320: > * * * W A R N I N G * * * > The ata driver has some issues with the Apollo MVP3 chipset. > Drives work only in pio mode and must be set to pio mode early > int the boot process. Do not upgrade. If you must upgrade > in the face of this, add > /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio > to the start of /etc/rc.conf. Even if you do this, any and > all damage to your system is at your own risk. You have been > warned. > * * * W A R N I N G * * * > > > Of _course_ I own such a thing. Ehm, is that a warning you have written or ?? I certainly havn't issued this warning as the maintainer/author of the ata driver... > FreeBSD 5.0-CURRENT #0: Fri Mar 31 16:52:11 CEST 2000 > alex@cichlids.cichlids.com:/usr/src/sys/compile/cichlids > > pcib0: on motherboard > pci0: on pcib0 > pcib2: at device > 1.0 on pci0 > atapci0: port 0xe000-0xe00f at device > 7.1 on pci0 > > Two things: As you can see, my -current is from Mar 31,though I don't > know exaclty if I've taken sourcs from Mar 31, but I'm kinda sure. > > Question is: Does the problem affect all versions? > It doesn't seem so, since I'm running two disks at UDMA33 without > problems: > > ad0: 4133MB [8959/15/63] at ata0-master using UDMA33 > ad2: 6197MB [12592/16/63] at ata1-master using UDMA33 > > There still is a little chance that my sources wasn't from pre-03/20, > so - is this problem fixed? I have not changed anything in the ata driver related to the VIA'586 in a long time, its works with all disks and ATAPI devices I have access to on the MVP3 chaintec board I have... But knowing VIA and their funny way of versioning the silicon, it could be that they have made a newer version of the '586 that behaves differently than the old (they have done that with the '596) and that will probably cause problems.. So, I need a verbose boot from a working kernel, and the same from a system that shows the problem from a newer kernel to be able to tell if there is an issue here... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message