Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!agate!tfs.com!julian From: julian@tfs.com (Julian Elischer) Subject: Re: FreeBSD, fd0d: hard error Message-ID: <Cvp1s7.JCM@tfs.com> Organization: TRW Financial Systems, Oakland, CA References: <33j9hp$41l@sol.sun.csd.unb.ca> <jmonroyCvozLK.5q9@netcom.com> Date: Tue, 6 Sep 1994 05:55:19 GMT Lines: 30 In article <jmonroyCvozLK.5q9@netcom.com>, Jesus Monroy Jr <jmonroy@netcom.com> wrote: >Peter Howlett (b6ps@jupiter.sun.csd.unb.ca) wrote: >: Howdy, > >: Has anyone ever seen this? > >: fd0d: hard error reading fsbn 62 of 64-71 >: (ST0 44<abnrml,top_head> ST1 20<bad_crc> ST2<bad_crc> cyl 1 hd 1 sec 15 > more than 15 sectors on a track, which on a 1.2 meg > diskette is not possible. This is pointed to by > the remaining registers that point to the last > successfully completed transfer, a side effect of > most FDC controllers. Jesus's analysis sounds 'possible.' the driver under 1.x does get some information from the cmos.. have you the correct information in the cmos setup? I doubt this is what's wrong however because your error sounds sporadic and not at all repeatable, which whould not be the case if it were trying to use the wrong geometry (in which case it would fail the same way each time) it Is possible something else is making it go wild, but I can't imagine what... any chance of grafting the 1.0 fd.c into the kernel and trying that? julian