From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016
Description of problem:
"floppy0: not floppy controllers found" (/var/logs/dmesg)
Floppy disk is not recognized, even if the proper lines in fstab have been entered
"/dev/fd0 is not a proper block device"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Allways when booting into Linux, Windows 2000 has no problem with the floppy disk
Expected Results: Disk should be accessible, as other systems dont have this
problem. It is Asus P4T-E specific
This sounds like a kernel problem, not a problem with the boot loader
Tried to fix this problem with the following lines in grub.conf :
"kernel /boot/vmlinuz-2.4.18-18.8.0 disableapic ro root=LABEL=/"
"kernel /boot/vmlinuz-2.4.18-18.8.0 noapic ro root=LABEL=/"
"kernel /boot/vmlinuz-2.4.18-18.8.0 ro root=LABEL=/ disableapic"
"kernel /boot/vmlinuz-2.4.18-18.8.0 ro root=LABEL=/ noapic"
The result is as before, as can be read in /var/log/dmesg :
"floppy0: no floppy controllers found"
The Asus P4T-E floppy is known to be very very weird and isnt supported by Linux.
Somebody advised me to install lilo as alternative bootloader instead as this
would be a grub-problem, a rather bleak option in my view.
Still : The same motherboard does not have these problems with the floppy device
when dual-booting into Windows 2000 Professional.
I have the identical problem...RH 8.0, P4T-E MB, floppy controller is not
recognised. There are 2 other bugs open for the same issue, 75687 and 78874.
Please note that during installation the floppy WAS detected. I created a boot
Problem known with (almost all) P4-TE Asus motherboards not recognizing floppy
at boot; the bug does not depend on Rh 8.0, and is reproducible with different
linux distributions too. The floppy is OK once recognized.
I think the bug is reported with several different numbers, i lost count.
Proposed workaround: compile floppy as a module. It delays floppy recognition
and then system works reliably. Tested on RH 7.2, I am recompiling 8.0 to test
*** This bug has been marked as a duplicate of 75778 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.