Date: Mon, 14 May 2001 12:09:57 +0100 From: "Mark Hughes" <mark@dvdnews.co.uk> To: "Ted Mittelstaedt" <tedm@toybox.placo.com>, "Salvo Bartolotta" <bartequi@inwind.it> Cc: <freebsd-questions@FreeBSD.ORG> Subject: Re: Read command timeout Message-ID: <076e01c0dc66$6dc006d0$0200a8c0@mark2> References: <008901c0dc47$3ff84d80$1401a8c0@tedm.placo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'd be happy to, unfortunately over a 56k modem link it would take me two straight days to download it - which in and of itself isn't too bad, however not using the modem for those two days while it's downloading is... Thanks for the suggestion tho, and if I can find someone with a fast internet link to D/L it for me then I'll give it a shot. Regards, Mark > 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" <mark@dvdnews.co.uk> 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. > > > > > > > ><snip> > > > > > > > >> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?076e01c0dc66$6dc006d0$0200a8c0>