I'll try CentOS, but it won't fix the problem.

And actually I only have a 34 pin floppy disk drive connector to USB adapter, I don't have an external USB Floppy drive.

Hi fellow floppy enthusiasts

Sorry for bumping this old thread, but I thought you'd be interested to know that I too am encountering exactly this same problem.

I separately acquired an internal floppy drive and a USB→34-pin adapter for it. After inspecting the output of lsusb, I can confirm that the adapter is the same TEAC chipset which both of you have mentioned previously (I assume the person I bought it from must have ripped it out of a TEAC USB external drive).

I did discover one way to deactivate the drive from software, using the Disks application (I'm currently running Ubuntu 16.04). The Disks app includes an option to 'power off' the Floppy drive. Clicking this causes the drive to stop making that noise and the LED to go off. Unfortunately, it also makes it disappear completely from the list of storage devices and the list of USB devices. The only way to get it back is to unplug and re-plug the USB cable. This won't really do for me as I ideally want to have the floppy as an internal drive, with the USB connected internally. The floppy drive otherwise functions as normal and I have had no trouble reading or writing disks with it.

I'll definitely subscribe to/register my interest in that launchpad bug you linked earlier, glad to know I'm not the first to experience this problem!

Regards

I've found a somewhat course solution I found in securing my desktop which can work in a specific circumstance. I am assuming most distros have this as a module but if you compile your own set usb_storage as a module and blacklist it unless you need your floppy drive and assuming you have no other storage device connected via USB.

That's interesting to know. With this system, is there a way to re-activate the floppy drive once you've deactivated it?

If you manually insert the usb_storage module the system should recognize the floppy drive atleast after a few seconds or so. I dont have my floppy on hand as write this but I tested on a few usb thumb drives which also use the same module and are detected immediately.

Sorry duplicate post#

When I as doing my DietPi (Debian Buster) PI4 + aliexpress usb floppydrive (TEACV0.0) DOSBOX project I came across several
threads and posts on the Internet.

My initial situation was that I used the regular mount commandline to mount the usb floppydrive.
Like mentioned in this thread it had the side effect of the drive constantly polling every second
when the floppy was removed.

The cumbersome solution to this problem
I've ended up installing autofs:
(automatically starts after (re)boot)

I edited "/etc/auto.misc" and added this line at the end:
Restarted autofs:
Autofs will automatically mount the drive only when the user explicitly do a file or folder change/check..
Also any changes to a file are directly written to the floppy, so it will not be cached and waiting for the user to unmount like a memorystick.

Now the cumbersome part is to hack the usb drive in a way that when there is no disk inserted, you just cut off the power. When insertnig a disk, the power should be connected. I had to cut the red wire and hook it up in the floppy eject lever (right side of the case) in a way it makes only contact when the floppy is inserted.
This works fine with autofs, since you have to LS or open location with a filemanager to the mountfolder to trigger the autofs automount.



The only downside for my project is that autofs will not be triggered when doing ie. A:\dir within DOSBOX mount, so
if I really wanted to use my USB floppydrive within DOSBOX, then I have to switch back to the regular mount command and disable autofs.