During bootup, the following messages appear: fdc0: <floppy drive controller (FDE)> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 It is not possible to mount or use the floppy after the system is booted. This problem does NOT exist in FreeBSD 4.11. Fix: Solution not known exactly, other than to say that FreeBSD 4.11 does not exhibit this behavior when running on MS Virtual Server 2005 R2. How-To-Repeat: 1. Install MS Virtual Server 2005 R2 on a machine. 2. Create a new Virtual Machine, and accept the defaults for the configuration. 3. Install FreeBSD in the virtual machine. Accept the defaults during install. 4. Once the system boots, the messages will appear during boot time, and the floppy will not be mountable or otherwise accessible.
This is probably the same issue as already described in problem report kern/79944. Apply the patch below and compile and install a new kernel. Regards Björn # cd /usr/src # patch -p1 -i fdc.c-2005010801.diff # make buildkernel # make installkernel # reboot --- fdc.c-2005010801.diff begins here --- --- src/sys/dev/fdc/fdc.c.orig Sun Jan 8 06:55:49 2006 +++ src/sys/dev/fdc/fdc.c Sun Jan 8 06:56:12 2006 @@ -1621,8 +1621,6 @@ */ fdout_wr(fdc, 0); fdout_wr(fdc, 0); - if (fdsts_rd(fdc) != 0) - return (ENXIO); /* * Clear the reset and see it come ready. --- fdc.c-2005010801.diff ends here ---
Responsible Changed From-To: freebsd-i386->freebsd-bugs This does not sound i386-specific.
State Changed From-To: open->feedback To submitter: Are you able to confirm if the patch in the PR audit trail fixes the problem you are seeing? If so,I'll mark one as a duplicate of the other.
Responsible Changed From-To: freebsd-bugs->gavin Take
I'm getting the same kernel messages from fdc as described in this report 10 years ago, and can't access to the virtual floppy image. But I'm using FreeBSD 10.3 now (FreeBSD-10.3-RELEASE-i386), running under a freshly installed VirtualBox 5.0.16 (running on Windows Server 2008R2). There is also a forum report from 2011 citing the same messages and access problem using FreeBSD 8.2 running in VirtualBox 4.1 (on Windows Vista 32-bit). https://forums.freebsd.org/threads/25289/ There is also a more detailed answer to the same questioner in the VirtualBox forum, saying the cause is that the FreeBSD fdc driver can't handle floppy interrupts coming back too quickly from VirtualBox when reading. https://forums.virtualbox.org/viewtopic.php?f=4&t=43288
batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Keyword: patch or patch-ready – in lieu of summary line prefix: [patch] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>