From owner-freebsd-stable Wed Aug 9 3:19:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail03.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 2828D37B6E2 for ; Wed, 9 Aug 2000 03:19:42 -0700 (PDT) (envelope-from duhring@charter.net) Received: from [24.217.4.31] (HELO dave.uhring.com) by mail03.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with ESMTP id 2620966; Wed, 09 Aug 2000 06:25:09 -0400 Date: Wed, 9 Aug 2000 05:19:37 -0500 (CDT) From: Dave Uhring X-Sender: duhring@dave.uhring.com To: jadream Cc: Andreas Persson , freebsd-stable@FreeBSD.ORG Subject: Re: Re: Strange problems installing 4.0 vs 3.2 (2-d trial) In-Reply-To: <3990F7A3.FF934E01@chat.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, jadream wrote: > Hi Andreas! > > Andreas Persson wrote: > > > Make sure you are using the ad driver instead of wd > > Yes I'm sure I am. > > ad0: at ata0-master using UDMA33 > acd0: at ata1-slave using PIO4 > > > and mail me the output of > > sysctl hw.atamodes > > failed to get to the command prompt :( > > > and dmesg after a boot. Also try to do some things which > > exhibit this behavior and check the logs/console for device timeouts. > > time to time I see a message "Probing devices that can take some time ..." in > the install script console and whole stuf hangs. > > when not so after any disk operations occur I have endlessly repeating messages > in DEBUG output console: > > ad0: WRITE command timeout - resetting > ata0: resetting devices ... done > > something wrong with VIA chipset perhaps? It might be somehow not compatible??? > strange thing it worked excellent with 3.2 ... > > Thank you in any case for attention :0) > > Alex Komratov > There appears to be something very wrong with Apollo MVP4 chipset. I installed 4.0-R on a machine with that chipset and got a steady stream of errors while the system was attempting DMA access. After about a thousand or so messages, it switched over to PIO access and the error messages ceased. I build up 4.0-S on the box and the errors continued. The problem was mentioned on this forum, but no one ever continued the discussion. I installed Slackware over FreeBSD on that box when 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message