Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!library.ucla.edu!csulb.edu!csus.edu!netcom.com!jmonroy From: jmonroy@netcom.com (Jesus Monroy Jr) Subject: Re: FreeBSD, fd0d: hard error Message-ID: <jmonroyCvozLK.5q9@netcom.com> Organization: NETCOM On-line Communication Services (408 261-4700 guest) X-Newsreader: TIN [version 1.2 PL1] References: <33j9hp$41l@sol.sun.csd.unb.ca> Date: Tue, 6 Sep 1994 05:08:08 GMT Lines: 56 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 : : :: [deleted stuff] :: : : Any thoughts? : For those of you keeping score, here is a list of my reference material tonight on this subject: NEC Microcomputers, Inc. 1981 Catalog Intel Peripheral Components 1991 Please note that the orignal FDC specs come from NEC and the Intel dat guide is the latest FDC guide I have in my possesion. To the errors: ST0 is the register -- STATUS REGISTER 0 44 is the hex value 0x44 The message returned is an incorrect status of the error. The high nibble is 4, which indicates that the FDC received an invalid command. The low nibble is 4, which indicates on *some* controllers that the drive is not ready. To make this short, it is quite possible that one of the applications you ran decided that it could read 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. Are there any other questions? Or do I need to elaborate on this more? -- Jesus Monroy Jr jmonroy@netcom.com Zebra Research /386BSD/device-drivers /fd /qic /clock /documentation ___________________________________________________________________________