From owner-freebsd-hackers Fri Sep 12 06:51:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA04305 for hackers-outgoing; Fri, 12 Sep 1997 06:51:27 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA04296 for ; Fri, 12 Sep 1997 06:51:18 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA05405; Fri, 12 Sep 1997 15:51:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id PAA15022; Fri, 12 Sep 1997 15:48:15 +0200 (MET DST) Message-ID: <19970912154815.HN39525@uriah.heep.sax.de> Date: Fri, 12 Sep 1997 15:48:15 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: grog@lemis.com (Greg Lehey) Cc: hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: Do *you* have problems with floppies? References: <19970912101014.37786@lemis.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970912101014.37786@lemis.com>; from Greg Lehey on Sep 12, 1997 10:10:14 +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Greg Lehey wrote: > I've seen a lot of reports recently about problems with floppies under > FreeBSD. Now I can understand a lot of that: floppies must be the > most unreliable data storage medium I can think of, not to mention the > most expensive per byte. But I'm getting the feeling that there is > more to it than that, that possibly there's a bug in the floppy driver > and that we're blaming it on the inherent unreliability of the medium. Oh, Greg is going to take over maintenance of the FDC driver! Congratulations! :-) > I'm looking for indications which would point towards the driver. One > of these might be: > > 1. Floppy formatted under on the same machine. > 2. FreeBSD runs into hardware problems with the floppy (typically > things like checksum errors). > 3. can read the entire floppy with no trouble. There's exactly one unexplained record open where 1 - 3 does fit, and i have yet to see more user input data for this case (or have to get the drive and floppy controller myself for debugging). Greg, please think a little more about reported problems before starting this kind of postings. What has been triggering this was plainly and clearly something where a user had a problem with *the BIOS* reading the floppy. This should say enough about the media quality... > In addition, if you have any other evidence I haven't thought of which > would also point to an error in the floppy driver, please contact me. Good luck for fixing these errors... And don't forget to verify your changes on at least half a dozen of drives and controllers. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)