new fdc(4) and new fdcontrol(8) behavior (5.3-BETA5)

Poul-Henning Kamp phk at
Tue Sep 21 05:42:39 PDT 2004

In message <20040921122354.73480.qmail at>, Rostislav Kras
ny writes:

>dmesg fragment from 5.3-BETA5 (verbose):
>fdc0: ic_type 90 part_id 80
>fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5 irq 6 drq 2 on

>Why the 3F7h port isn't used by new fdc(4) on my system? Is it a
>hardware detection bug?

Warner is working on this issue.

>2. fdcontrol cannot access /dev/fd0 when there is no diskette inserted
>When no diskette is inserted then running 'fdcontrol [anyflag]
>/dev/fd0' produce following error message:
>fdcontrol: open(/dev/fd0): Device not configured

We don't have a specific errno for "No media in drive".  It would have
been nice, but defining errno's is a tricky business.

>What is inspected behavior of fdcontrol(8) in 5.3-BETA5? Isn't its
>current behavior buggy? Is it concerned with 3F7h port that is not used
>on my system by the new fdc(4) driver?

The 0x3f7 is a bug, and as I said Warner is working on that.

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

More information about the freebsd-current mailing list