From owner-freebsd-stable Tue Aug 8 23:12:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from head.lvl.ru (head.lvl.ru [194.67.189.100]) by hub.freebsd.org (Postfix) with ESMTP id 1AE1737B696 for ; Tue, 8 Aug 2000 23:12:31 -0700 (PDT) (envelope-from jadream@chat.ru) Received: from chat.ru (p22.gw.lvl.ru [194.67.189.22]) by head.lvl.ru (8.10.0/8.10.0.Beta12) with ESMTP id e796BwK15564; Wed, 9 Aug 2000 10:11:59 +0400 (MSD) Message-ID: <3990F7A3.FF934E01@chat.ru> Date: Wed, 09 Aug 2000 10:18:12 +0400 From: jadream X-Mailer: Mozilla 4.72 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Andreas Persson Cc: freebsd-stable@freebsd.org Subject: Re: Re: Strange problems installing 4.0 vs 3.2 (2-d trial) References: <37ACA2FF.828914B7@chat.ru> <20000808101044.A29953@sophocles> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message