Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!cs.utexas.edu!geraldo.cc.utexas.edu!sylvester.cc.utexas.edu!not-for-mail From: vax@sylvester.cc.utexas.edu (Vax) Newsgroups: comp.os.386bsd.bugs Subject: Re: accesing rfd0a bombs (386bsd w 0.2.4) Date: 30 Jun 1993 03:02:30 -0500 Organization: The University of Texas - Austin Lines: 24 Distribution: world Message-ID: <20rham$1u7@sylvester.cc.utexas.edu> References: <20ncr8$nb9@urmel.informatik.rwth-aachen.de> NNTP-Posting-Host: sylvester.cc.utexas.edu In article <20ncr8$nb9@urmel.informatik.rwth-aachen.de> kuku@acds.physik.rwth-aachen.de writes: > >Anyway, once again, I inadvertently left a disk in the 5.25 drive, booted, the >disk was not recognized. Later - meanwhile forgotten about that fact - I >wanted to access the drive (either mount or tar - don't remember) - SOFT RESET >, black screen, reboot, no panic message, just as if someone has hit the > reset button. > I booted from hard disk and tried to use dd to copy a floppy. Further experimentation showed either reads OR writes cause a reset after 10-11 seconds of apparently normal operation. Block device works fine, only the raw device (/dev/rfd0a) seems screwy. Other raw devices (/dev/rfd0d) show the same result. Haven't tested it on 1.2MB disk or on drive 1 (B:). I have 386bsd with patch kit 0.2.3 installed. Where is everyone getting 0.2.4? I couldn't find it on agate. Is there a new home site? Seems like 0.2.3 introduced more bugs than it fixed in my case :( I may have to go back to 0.2.2 (i'd like to use my printer, thanks) Does everyone else not have a printer, or what? Nobody responded to my question about 0.2.3 breaking lpt/lpa! -- Protect our endangered bandwidth - reply by email. NO BIG SIGS! VaX#n8 vax@ccwf.cc.utexas.edu - finger for more info if you even care.