Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!darkstar.UCSC.EDU!news.hal.COM!decwrl!netcomsv!netcom.com!netcom4!ceb From: ceb@netcom4.netcom.com (Ch. Buckley) Subject: Re: FreeBSD, fd0d: hard error In-Reply-To: daves@gold.interlog.com's message of 5 Sep 1994 01:36:42 GMT Message-ID: <CEB.94Sep4213952@netcom4.netcom.com> Sender: ceb@netcom.com (Ch. Buckley) Organization: Mauto, Palo Alto References: <33j9hp$41l@sol.sun.csd.unb.ca> <3453os$sru@steel.interlog.com> <3486q6$dr6@pdq.coe.montana.edu> <34dsnb$78p@steel.interlog.com> Date: Mon, 5 Sep 1994 04:39:52 GMT Lines: 45 In article <34dsnb$78p@steel.interlog.com> daves@gold.interlog.com (David Shadoff) writes: Nate Williams (nate@bsd.coe.montana.edu) wrote: : I suspect a hardware problem, since I've been running FreeBSD for a long : time on a very similar combination. Aha1542B + quantum 1.8GB disk (big : brother to yours). It's not a hardware problem; other OS's work fine - DOS, Linux to name two. I also get the same problem on my Maxtor 300MB SCSI drive which didn't have any such timeout problems with FreeBSD 1.0 . I should note that my errors are from the WC FreeBSD 1.1 CD-ROM (I haven't had the opportunity to upgrade to 1.1.5.1 yet). If the 1.1.5.1 upgrade solves this problem, I'd really like to know. : Check your SCSI termination, as this is typically the problem that faces : most folks. I have. I have tried with only one drive, substituting a drive of a different size (which BTW worked flawlessly on FreeBSD1.0) I believe it's a software problem. It looks like a fiendish one, but enough people have been having this one out of the blue that the likelihood of everyone's hardware rotting in place simultaneously is just too small (only the economy does that, and it's marionnetted by the Fed). Now, I suspect that the subtext here is that the person who wrote the code is hard at work on his part of 2.0, as well as the rest of his/her life, and is not willing to take a look at it at the moment. Distributing patches to 1.1.++ is probably legalism plagued too. This may be one just to wait out, or try and fix oneself. Posted tips on how might be useful. And, at the risk of being flamed unmercilessly, wasn't there some guy named Jesus who wrote a floppy controller for 386BSD? Maybe he might offer an olive branch to the FreeBSD crowd and make his plug-compatible. At least that way, he posts less. ;'} Nah, it'll never happen. --