On Thu, Oct 11 2001 at 11:23:06 -0400, der Mouse wrote:
> > Could people with NetBSD running on a sparc10 with a floppy drive see
> > if they can access floppies?  Just tar something to the device and
> > back again should be enough...
> 
> I've got a 10.  My floppy drive shows up as
> 
> fdc0 at obio0 slot 0 offset 0x700000 level 11 softpri 4: chip 82077
> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> 
> Running fdformat produces:
> 
> # fdformat
> Ready to format /dev/rfd0a with 80 cylinders, 2 tracks, 18 sectors of
> 512 bytes
> (1440 KB) Yes/no [y]?y
> EEEEEEE^C
> 
> to the accompaniment of console messages
> 
> fd0a: hard error reading fsbn 0
> fd0: controller status: state 17 (st0 70<abnrml,seek_cmplt,drv_chck>
> cyl 0)
> fd0: timeout: state 10
> fd0: timeout: state 4
> fd0: timeout: state 4
> fd0: timeout: state 4
> fd0: timeout: state 4
> fd0: timeout: state 4
> fd0: timeout: state 4
> 
> "eject fd0" produces more console messages
> 
> fd0: timeout: state 10
> fd0: timeout: state 13
> fd0: timeout: state 13
> fd0: timeout: state 13
> fd0: timeout: state 13
> fd0: timeout: state 13
> fd0c: hard error reading fsbn 0
> fd0: controller status: state 13
Does eject work from the openboot console?

If not, it's a hardware problem.

Maybe this helps:

Last year I got two sun4cs (IPC+IPX), both with floppy drives which appeared
to be non functional (error messages like yours, eject from openprom didn't
work), but I discoverd the following  (or similar - from memory) procedure 
which brought them back to life:

1. disconnect power from the floppy drive, but leave the data cable connected
2. put a disk into the drive
3. power up the machine and enter openboot
4. issue eject (nothing will happen)
5. reconnect the power cable -> the floppy disk should eject now

Somehow this "unjammed" the disk drives - they have been working fine since then.

No guarantees and use at your own risk!
-- 
Dies ist Thilos Unix Signature! Viel Spass damit.