From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger) Subject: Re: Probleems with Linux-0.96 and 5.25" 360k diskette Date: 21 May 1992 08:30:34 GMT
In article <1992May21.032746.8899@athena.mit.edu> Epstein@DOCKMASTER.NCSC.MIL writes:
> Prior to 0.96 could use 5.25" 360 diskette as B: with new auto detect
> fd0 and fd1 mknod /dev/fd0 b 2 0 mknod /dev/fd1 b 2 1 mknod /dev/at0 b 2
> 8 mknod /dev/fd0-360 b 2 20 mknod /dev/fd1-360 b 2 5
So you have two 5.25" drives: a HD ("AT") A: and a non-HD ("PC/XT")
B: ?
When booting, the floppy driver should report:
Floppy drive(s): fd0 is 1.2M, fd1 is 360k/PC
If you get something different, you should adjust your CMOS setup.
The fd1-360 device shouldn't depend on the CMOS setup, however. I
don't know what might cause it to fail with the new driver. Does
it also happen if you don't use mtools to access the drive ? Is
anybody experiencing similar problems ?
> If place 360 in A: and mtools uses A /dev/fd0 12 80 2 15 line,
> autodetects that 360k/AT diskette but says no support for 12 40 2 9
> format
That's a sanity check. 12 80 2 15 isn't valid for a 360k disk. You have
to add a second entry
A /dev/fd0 12 40 2 9
> I also don't like the sound made when the first disk is read in A:
> drive (either 1200 or 360) under Linux [initial positioning was done
> reading Linux bootimage].
Hmm ... is this new with 0.96 or did it do that with earlier versions
too ?
- Werner
-- _________________________________________________________________________ / Werner Almesberger, ETH Zuerich, CH almesber@nessie.cs.id.ethz.ch / / IFW A44 Tel. +41 1 254 7213 almesberger@rzvax.ethz.ch / /_BITNET:_ALMESBER@CZHETH5A__HEPNET/CHADNET:_[20579::]57414::ALMESBERGER_/