The following procedure worked instantly on Ubuntu 12.04:
REMARK:
The df
command shows that /dev/sdd show that d the last assigned drive in use. I need to know this to find the next available one, which is used in the subsequent sudo mount ...
command. In my case, the next drive will be /dev/sde .
You will need to determine the correct drive for your own system. For example, you might have /dev/sda, or sdb, or sdc.
So, first, to see the drive information:
df
Next, run mkdir
and mount
:
mkdir /mt/ee1
sudo mount -t vfat /dev/sde /mt/ee1 -o uid=1000
For automatic execution at boot time, I normally use Perl scripts, which detect and adapt automatically and give stable names to the partitions.
I do not need this at this point of time for floppies, and therefore I didn't optimize it. Perhaps the command "mount ...
" is not optimal....)
A more general but a bit primitive solution would be to create a bash/batch file with multiple lines as above with sudo...
, with the several probable possible variants /dev/sd...
on the specific PC.
Then there might be a call of this file in the settings of "Startup Applications".
I did not test this.
In addition, this does not deal with the aspect of removing or inserting a different floppy disk. This could be done in some automatic or at least semi-automatic manner....
I do not know if the way above is optimal. I just wanted to add helpful information, after having settled my own problem with the preceding answers.
Best Answer
Check if the floppy module is loaded:
This command should not return anything. If it returns "floppy" then you have the floppy module loaded and this answer does not solve your problem.
If you want to load the floppy module:
Try adding your username in the floppy group:
You could also try installing
fdutils
package:fdmount seems useful. Try:
sudo fdmount -l
Check if your floppy drive is listed here:
If you're still facing problems, post the output of the above commands, plus this:
Post the content of dmesg.log to a pastebin somewhere (i.e. http://www.pastebin.com ) and give us the link.
P.S. You may be suffering from this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/441835 -- Try: