peter b [2010-11-26 2:44 -0000]:
> - the BIOS which is written in assembler (the fastest) detects the
> floppy presence in fractions of a second.
Please see above. In the problematic case, the linux kernel and the
BIOS detect the floppy *controller*, and thus think that a floppy is
present. This seems to be the case with a lot of motherboards, which
have a floppy controller, but no drive attached to it. Then, if you
try to speak to the floppy through the controller, you get the long
timeouts.
> - the second thought was - how comes that the proprietary os manages to
> get this type of device recognised if present and render it fully
> operational without this 20 sec delays ? I saw it myself on a friend's
> pc that uses win - the floppy device detection was almost as fast as the
> BIOS detection.
If there is an actual floppy drive, there is no problem.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
peter b [2010-11-26 2:44 -0000]:
> - the BIOS which is written in assembler (the fastest) detects the
> floppy presence in fractions of a second.
Please see above. In the problematic case, the linux kernel and the
BIOS detect the floppy *controller*, and thus think that a floppy is
present. This seems to be the case with a lot of motherboards, which
have a floppy controller, but no drive attached to it. Then, if you
try to speak to the floppy through the controller, you get the long
timeouts.
> - the second thought was - how comes that the proprietary os manages to
> get this type of device recognised if present and render it fully
> operational without this 20 sec delays ? I saw it myself on a friend's
> pc that uses win - the floppy device detection was almost as fast as the
> BIOS detection.
If there is an actual floppy drive, there is no problem.
Martin www.piware. de
--
Martin Pitt | http://
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)