Paul Groves composed on 2018-10-22 20:49 (UTC+0100):
I know this is old but I had to use my floppy drive
today to update a
device firmware. I actually forgot about this issue. My workaround until
now was to insert a broken floppy disk and it stopped the drive being
I used to do firmware update from floppy, but found it's more often easier to setup a
update by putting a FAT formatted DOS bootable HD in a USB device to load the update
onto, then boot the BIOS update target from the DOS HD.
Some of my most used PCs that have floppy drives have a floppy hanging out to serve as a
minimalist lift handle. If I encounter an errant floppy access attempt, I just shove it in
the issue is past.
I just tried:
echo 0 > /sys/block/sdd/events_poll_msecs
as root and this workaround sorts out the problem
udevadm monitor shows nothing before or after this
command. by default
/sys/block/sdd/events_poll_msecs is set to -1
This problem also exists on my dual boot of Ubuntu
18.04.1, on which the
same workaround is working.
How can I make this workaround permanent?
Or has this been resolved and not released yet?
Running on latest LEAP
I use floppies so rarely that I keep them disabled in BIOS except for any short periods
During installation, broken.modules=floppy is an option. Maybe it works for normal boots
Evolution as taught in public schools is religion, not science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org