Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!sal.wisc.edu!rat!cindy!satmech
From: satmech@ecst.csuchico.edu (satmech)
Subject: Re: fdprobe() returns 0
Message-ID: <1992Sep10.000731.5529@ecst.csuchico.edu>
Keywords: fdc wdc patch fdprobe
Sender: news@ecst.csuchico.edu (no news is good news)
Nntp-Posting-Host: cscihp.ecst.csuchico.edu
Organization: California State University, Chico
References: <1992Sep7.192540.10143@Urmel.Informatik.RWTH-Aachen.DE>
Date: Thu, 10 Sep 1992 00:07:31 GMT
Lines: 23
In article <1992Sep7.192540.10143@Urmel.Informatik.RWTH-Aachen.DE> kuku@acds.physik.rwth-aachen.de writes:
>
>I installed the 2nd drive (updated) patch from Tom Helbekkmo
>(tih@barsoom.nhh.no) and since then (?) I cannot access my fd drive any longer.
>
>I peeked into fdprobe() with a printf() and find that fdprobe() does
>not even see the FD controller (at 3f0).
>
>I'm baffled. I will now successively go back in steps to see at which kernel
>configuration I can see my floppies again.
>
>It does not seem to be hardware - a different IDE controller gave the same
>bad result and I can still boot dist.fs (I'm using a 386SX 16MHz Morse Motherboard with 8MB, two disks). It's really strange, maybe too strange
>to post it here - but if anyone has a vague idea what I could also look for or check I'd be thankful.
>
This seems to be a problem with all IDE controllers (mine too). It doesn't
respond to the NE7CMD_SPECIFY command in fdprobe(). I just commented this
part out, the if(out_fdc(NE7CMD_SPECIFY) < 0 ) { ... } lines 125-128 in
/sys/i386/isa/fd.c and it recognized both my 1.44m and 1.2m floppies and
mtools works great...
If anyone has a better fix than this quick hack, please tell me about it.