Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!ihnp4.ucsd.edu!swrinde!pipex!sunic!trane.uninett.no!eunet.no!nuug!EU.net!uunet!fonorola!interlog.com!gold!daves From: daves@gold.interlog.com (David Shadoff) Newsgroups: comp.os.386bsd.bugs Subject: Re: FreeBSD, fd0d: hard error Date: 5 Sep 1994 01:36:42 GMT Organization: Interlog Internet Services -Voice (416) 975-2655 -Data 515-1414 Lines: 46 Message-ID: <34dsnb$78p@steel.interlog.com> References: <33j9hp$41l@sol.sun.csd.unb.ca> <3453os$sru@steel.interlog.com> <3486q6$dr6@pdq.coe.montana.edu> NNTP-Posting-Host: gold.interlog.com X-Newsreader: TIN [version 1.2 PL2] 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). : No problems whatsoever. 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. : > It's really bugging me, because the drive/controller : > combo works, if gen'd for DOS. : This means nothing. Dos doesn't push hardware to specifications, and : so it's really easy to run with the hardware completely and utterly : screwed up. (My box was totally mis-configured when I first installed : 386BSD years ago). Perhaps the way *most* people use DOS doesn't push hardware to spec. I have had enough opportunities to see problems emerge, however. The non-problematic installation of Linux (and FreeBSD 1.0 on the same drives, and the same problems happening with multiple config's on 1.1) gives me the opinion that it's not the hardware. : 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), one drive with CD-rom internal, Cd-rom external, different cables, different juxtapositions of drives, moving the drives away from the power supply, even removing the termination on each end... no combination even seemed to reduce the problem. I therefore conclude an AHA1542 driver problem as pressed on the WC1.1 disk. This is why I posted to the group - because I felt I had made a reasonable attempt at solving the problem myself, and wondered if (a) anybody else had similar problems (uh, yes they did...) and (b) if anybody knew what the problem was. I don't mean to sound harsh, but I am frustrated by this problem. I just haven't been following this group for a few months.