From owner-freebsd-questions Mon May 14 0:27: 7 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id F215937B423 for ; Mon, 14 May 2001 00:27:02 -0700 (PDT) (envelope-from tedm@toybox.placo.com) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f4E7Qsk40144; Mon, 14 May 2001 00:26:55 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Salvo Bartolotta" , "Mark Hughes" Cc: Subject: RE: Read command timeout Date: Mon, 14 May 2001 00:26:53 -0700 Message-ID: <008901c0dc47$3ff84d80$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <20010513.21552800@bartequi.ottodomain.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What about just trying a install of FreeBSD 3.5.1 which uses the wd driver, and seeing if this one works? That would at least confirm the problem is in the ad driver. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Salvo >Bartolotta >Sent: Sunday, May 13, 2001 2:55 PM >To: Mark Hughes >Cc: freebsd-questions@FreeBSD.ORG >Subject: Re: Read command timeout > > >>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< > >On 5/13/01, 10:13:22 PM, "Mark Hughes" wrote regarding >Read command timeout: > > >> Hello all, > >> After trial and error, I have managed to get freebsd to install (see >"Panic on Install - >> page fault syncing discs"), however on the first boot at the end of the >boot sequence I >> get: > >> ad0: read command timeout >> ata0: resetting devices .. done >> ad0: WRITE command timeout >> ata0: resetting devices .. done >> ad0: read command timeout >> ata0: resetting devices .. done > >> looping for ages, eventually ending in a > >> /: bad dir ino 12611 > >> and a panic which I didn't catch before it reset the system. Now it won't >boot at all, the >> whole file system has been screwed it seems. > >> I'm attempting to install 4.1-Release. My system is detailed below. > > > > > > > >> System spec: >> Biostar M7MIA motherboard, using AMD761 north bridge and VIA 686B south >> bridge ^^^^^^^^^^^^^^ > ^^^^^^^^^^^^^^ > > > > >IIRC, another person has met with difficulties with the VIA south bridge >recently (and NO installation) -- it was an ASUS AM7266 mobo, "featuring" >the same south bridge. Actually, the problems seem to be connected with >IDE disks; AFAIR, SCSI disks work correctly. > >AFAIK, there are no solutions (yet), but I would be happy if I were wrong >(erm, I've got IDE HDs & I'd very much like to get the ASUS mobo) :-)) > > > > >> 128MB Crucial 2.5CAS DDR PC2100 memory >> AMD Duron 750MHz CPU >> IBM Deskstar 6.5GB ATA33 Hard Disk Drive (partitioned as 4.5GB FAT32 >> Win2K, rest FreeBSD)^^^^^^^^^^^^^^^^^^^^^ > ^^^^^^^^^^^^^^^^^^^^^ > > > >Best regards, >Salvo > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message