>Number:         6157
>Category:       port-amiga
>Synopsis:       floppy driver does not always recognize HD disks
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Sep 14 12:50:01 1998
>Last-Modified:
>Originator:     Ingolf Koch
>Organization:
Jena-Optronik GmbH
>Release:        1.3.2
>Environment:
System: NetBSD maus.rz.uni-jena.de 1.3.2 NetBSD 1.3.2 (MAUS) #2: Thu Jun 11 20:03:43 MEST 1998 ingolf@maus.rz.uni-jena.de:/usr/src/sys/arch/amiga/compile/MAUS amiga
A4000 w/ internal 3.5" HD floppy drive
>Description:
	After booting with a HD floppy disk in disk drive #0 (I'm
    not sure if this is still needed to use HD disks), the
    driver does not recognize newly inserted HD disks as such
    every second or third time, e.g.

    ingolf@maus% cat /dev/fd0b > /dev/null
    cat: /dev/fd0b: Input/output error

    (Yes, the disk was MSDOS formatted)
    It seems that these problems are more likely to occur if
    the drive's head has been moved to the innermost cylinder
    before (e.g. by a similar `cat' as above). For determining
    the drive type, it is AFAIK necessary to move the head to
    the outermost cylinder (or even beyond it), so the reason
    might be that the head is not moved enogh steps.

    Another anomaly I noticed was that keyboard input is often
    duplicated during floppy activity. But maybe this is another
    PR...
>How-To-Repeat:
	0. Use an Amiga4000 with an internal HD floppy drive.
    1. Boot it with (not "from") a HD disk in drive #0.
    2. Read the whole disk.
    3. Insert another HD disk.
    4. Try to read it (the whole disk).
    If step 4 succeeded, repeating 3 and 4 should lead to a
    read error after a few retries.
>Fix:
	Maybe the head is not moved far enough to be able to
    determine the disk type.
>Audit-Trail:
>Unformatted: