floppy disk drive not detected (module not loaded) in Intrepid and Jaunty

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

I can confirm this with Intrepid kernel 2.6.27-2-generic.

There is no floppy icon neither in Places nor in Computer.

There is no entry for floppy in /etc/fstab.
In /dev/ there is no fd0 device but there is a fd folder with 4 link files within, 0, 1, 2 and 255, all pointing to /dev/pts/0.

This problem occurs on Intrepid Alpha 5 64bit - kernel 2.6.27-2-generic with all 102 updates today 06/09/08.

I am running Ibex Alpha 5 and I am unable to access my floppy drive (/dev/fd0). I added /dev/fd0 to /etc/fstab and I am still unable to mount the floppy drive. My mount point is /media/floppy0.

You don't need to add anything in your fstab.
As a workaround you just need to load floppy module:

sudo modprobe floppy

in a terminal does the trick.

I have the same problem: I need to modprobe the floppy module by hand in order to get floppy disk drive working.

Using latest Intrepid, fully updated until 2008-10-13.

Ditto here, need to modprobe floppy.

ASUS P5QL-PRO

Still affects 2.6.27-7.12

Idem ditto.

Same here. Had to sudo modprobe floppy. Clean install of Intrepid rc1 and all updated.

Right after I did this, there was a kernel update. On reboot, the floppy was gone again. 2.6.27-7 32 bit.
Again, sudo modprobe floppy brought it back.

installed ubuntu release 8.10, and the floppy drive is not detected, running sudo modprobe floppy works but after reboot it's gone.

Still unable to mount /dev/fd0. The floppy module is not loaded and you need to run sudo modprobe floppy to get it to run. Is this going to be fixed soon since I hate having to type sudo modprobe floppy each and everytime I start Ubuntu 8.10.....

Same problem here. The floppy module is not loaded automatically.

As a workaround, add "floppy" to /etc/modules

Ubuntu 8.10 still does not detect itself the floppy drive!

It is not a beta nor a candidate release anymore. Which it's still more odd as this OS is intended to be installed in older computers, also, in most all computers indeed.

It's a bit confusing, because although we of course always do love the newer features, the bug fixes and that it is now more stable, but with the new Ubuntu features and bug fixes... Sometimes also come with unexpected (basic?) new bugs.

Otherwise, the workaround indeed works... Thanks for the advice.

Gfloppy still does not work, anyway.

I just had to actually use my floppy drive, not just detect it, to generate some driver disks for a windows XP box. I tried using a live CD for Ubuntu 7.10 and an installed 8.10 for comparison purposes.

Of course 7.10 detects the floppy just fine. But also the entire process of accessing the drive and moving files to it in 7.10 works as expected. Where in 8.10 it is still a bit buggy.

In 7.10, insert a disk and click on the floppy drive in Places > Computer and a dialog box opens asking you to wait while the drive is loaded.
In 8.10 you get an error message that the drive can't be mounted, while in the background, it mounts anyway.

In 7.10, when you unmount the drive, the icon in Places > computer goes back to the generic floppy drive icon and label.
In 8.10 the label stays whatever it decided to call the contents of the last floppy it read.

One function seems to be improved:
7.10 waits to do the actual file copying till you unmount the drive, at which time a dialog box pops up asking you to wait till it's done. This is followed by an "ok to remove media" popup.

8.10 seems to copy the files as soon as they are dragged to the drive, so on unmount, it is ready to remove right away.

I am confirming that adding the module floppy to /etc/modules works for me in Ubuntu 8.10 final. Added it and then modified the fstab file to auto mount floppy if a disk was present. Rebooted system and upon reload the floppy loaded itself.

Alienexplorers said:
"modified the fstab file to auto mount floppy if a disk was present"

Interesting. What was the command line you added to fstab? This works if you just popped a floppy into the drive?

Martin G Miller wrote:
> Alienexplorers said:
> "modified the fstab file to auto mount floppy if a disk was present"
>
> Interesting. What was the command line you added to fstab? This works
> if you just popped a floppy into the drive?
>
>

My fstab looks like this:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sdb6
UUID=182c66b4-ed87-4eec-9bd9-afebae097ee3 / ext3
relatime,errors=remount-ro 0 1
# /dev/sdb7
UUID=74d55a7f-49eb-4a65-b1b8-12db46dc75c5 /home ext3
relatime 0 2
# /dev/sdb5
UUID=2eac46be-ff76-48e4-bbd2-9e8e14c97699 none swap
sw 0 0
# /dev/sdb1
UUID=11e5a808-45f5-41fb-8b43-5f2a8af9016d /media/disk ext3
relatime 0 2
# /dev/sdb2
UUID=9f76cfa0-091f-4940-8be3-fc46fe85e283 /media/disk-1 ext3
relatime 0 2
# /dev/sda1
UUID=4CA7-E543 /media/windows vfat
relatime 0 2
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8
0 0
/dev/scd1 /media/cdrom1 udf,iso9660 user,noauto,exec,utf8
0 0
/dev/fd0 /media/floppy0 auto rw,auto,user,sync
0 0

The methods used by alienexplorers works in Jaunty Jackalope 2.6.27-7. I've edited both /etc/modules and my fstab file.

I spoke too soon. Now get Cannot mount the volume - mount point /media/floppy0 does not exist, followed by DBus error org.freedesktop.DBus.Error.NoReply.

You have to create the mount point directory first ( sudo mkdir /media/floppy0 ) giving full write/read access to the plugdev group (" sudo chgrp plugdev /media/floppy0 " and " sudo chmod g +rwx /media/floppy0 ") for the mount command to work correctly.

I also confirm this bug, adding that on my floppy drive I have the activity led always on.

Error on my last comment: the last command is really " sudo chmod g+rwx /media/floppy0 " - you can also add a " sudo chmod o-rx /media/floppy0 " if you want to uniform with other folders' privileges, giving access rights only to members of the plugdev group.

Damiano says:
"I also confirm this bug, adding that on my floppy drive I have the activity led always on."

This is usually an indication that the data cable on the floppy drive is installed backwards. Try unplugging the data cable and turning it around the other way. Unlike IDE drives, it is easy to plug this in backwards. There may be a small label on the drive telling you which end has "pin 1". This is the side of the connector that has the black stripe on the wire.

Make sure the computer is turned off and you are grounded before working inside the case.

I'll try checking the data cable of the floppy drive, however it's strange it did not happen with Ubuntu 7.04LTS nor does it happen with Windows XP - they both recognize correctly the floppy drive, correctly use it (writing/reading), and with both the led is not always on (only with activity, as it should be). I think there should be errors on drive activity, with a cable plugged backwards - there are no errors at all with the above OSes nor using the drive on 7.10 enabling the floppy module and manually mounting the device.

I didn't know that you were successfully using the floppy in other OS's without the light staying on. I suspect the cable is correct and you may have uncovered a different issue.

I can confirm that I can successfully load and use the floppy drive but
it is not detected automatically.

Martin G Miller wrote:
> I didn't know that you were successfully using the floppy in other OS's
> without the light staying on. I suspect the cable is correct and you
> may have uncovered a different issue.
>
>

I have had the same problem on two desktops. Both had Ubuntu 8.04LTS and neither would mount the floppy drive and the light stayed on all the time for both of them. On one of the desktops I have upgraded to 8.10 and I still have the problem I initially tried the floppy cable in each of the four different configurations without any success. I now know that the cable is connected correctly and that it is the OS. On the desktop that still has 8.04LTS the floppy icon does show up in the [Places] menu, but not on the 8.10 desktop.

I am hoping that the developers will find a solution for all of us in this matter.

I can verify this... wasn't detected automatically on my system either.

"sudo modprobe floppy" fixes (thank you kindly!)

i have used this command: "sudo modprobe floppy" but the problem persists.

this is actually happening.

excuse me: this is actually happening to me too in ubuntu 8.10 final release

Mark F ..

I can confirm this Using - Ubuntu 8.10 -- K = 2.6.27-7-generic

After install of Ubuntu 8.10, I Had no floppy.
Floppy light was on all the time, but could not mount / access floppy.
Checked - /etc/fstab and had entry - /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

Tried lots of things mentioned on forums, but could not get it to work.

Then found the "second" bug report page on no floppy and came here via link from that page.

I created folder under /media - floppy0
In terminal - Did - " sudo chmod g+rwx /media/floppy0 " and " sudo chmod o-rx /media/floppy0 "
in terminal - Did - " sudo modprobe floppy "

My floppy is now (fixed) mountable and the light is no longer on. Extra details are for someone (like me) who is looking for help with this problem.

I can also confirm this, floppy icon doesn't appear, i did sudo modprobe floppy, but that is just temporary, because when when you re-boot again the floppy icon is not there.And by the the way the floppy icon was in 8.04 by default on my system.

Edmond Thiebaud wrote:
> I can also confirm this, floppy icon doesn't appear, i did sudo modprobe
> floppy, but that is just temporary, because when when you re-boot again
> the floppy icon is not there.And by the the way the floppy icon was in
> 8.04 by default on my system.
>
>
I seem to have the fix for this problem - it works for me anyway. Would
you like me to send details to fix it ?

D.

I would expect the correct work around is the one listed in the summary, adding floppy to /etc/modules, and then rebooting. I would then expect /media/floppy0 to appear automatically etc.

Added floppy to /etc/modules and the floppy is added to the /dev directory. I insert a floppy before starting up the computer and it auto mounts the floppy. If I add the floppy after bootup I have to sudo /dev/fd0 /media/floppy0.

Sure, please. Would you?

Mark L. Kachel
Executive Sale Rep./Webmaster
TSM Group 2 - www.tsmgroup2.biz
Coupon TSM - www.coupontsm.com
Going green by asking for and servicing your old computers
and electronics to save you even more money, ask about
our services today!

-- Derek Bollam <email address hidden> wrote:
Edmond Thiebaud wrote:
> I can also confirm this, floppy icon doesn't appear, i did sudo modprobe
> floppy, but that is just temporary, because when when you re-boot again
> the floppy icon is not there.And by the the way the floppy icon was in
> 8.04 by default on my system.
>
>
I seem to have the fix for this problem - it works for me anyway. Would
you like me to send details to fix it ?

D.

--
floppy disk drive not detected (module not loaded) in Intrepid Alpha 4 kernel 2.6.27-2
https://bugs.launchpad.net/bugs/255651
You received this bug notification because you are a direct subscriber
of a duplicate bug.

Status in “linux” source package in Ubuntu: Triaged

Bug description:
Trying out intrepid daily-live: There is no floppy in "Computer" and no "/dev/fd0. The "floppy" module has not been loaded. This is maybe a bug in initramfs-tools or udev, but I file it here for now.

WORKAROUND: add "floppy" to /etc/modules, for instance this way:
 echo "floppy" | sudo tee -a /etc/modules

____________________________________________________________
Domain Registration - Click Here
http://thirdpartyoffers.juno.com/TGL2131/fc/PnY6rbuwwa2yacEGdQZMrxKrfHOTsRSKVGYdfOIenO34bqK7wCAeA/

The same is here. I had been forced to add floppy to /etc/fstab to make my floppy work.

The fix for the floppy driver is in my GIT tree, and I've requested that the kernel team pull from it:

http://kernel.ubuntu.com/git?p=scott/ubuntu-jaunty.git;a=commitdiff;h=92c7c6aafabb109a9f3e97ddfe5f632ffa37e430

It also contains various other auto-loading and option fixes I found at the same time.

I'll rebase these against linux-2.6 and send to lkml as well

This bug was fixed in the package linux - 2.6.28-8.28

---------------
linux (2.6.28-8.28) jaunty; urgency=low

  [ Alexey Starikovskiy ]

  * SAUCE: ACPI: EC: Limit workaround for ASUS notebooks even more
    - LP: #288385

  [ Scott James Remnant ]

  * SAUCE: Auto-load esp module when device opened.
  * SAUCE: Auto-load bridge module when socket opened.
  * SAUCE: Auto-load af_netlink module when socket opened.
  * SAUCE: Auto-load wanrouter module when socket opened.
  * SAUCE: Auto-load ip_queue module when socket opened.
  * SAUCE: Auto-load ip6_queue module when socket opened.
  * SAUCE: Auto-load cn module when socket opened.
  * SAUCE: Auto-load scsi_transport_iscsi module when socket opened.
  * SAUCE: Auto-load ftl module when device opened.
  * SAUCE: Auto-load pcd module when device opened.
  * SAUCE: Auto-load pf module when device opened.
  * SAUCE: Auto-load nftl module when device opened.
  * SAUCE: Auto-load mousedev module when psaux device opened.
  * SAUCE: Auto-load mousedev module when /dev/input/mice opened.
  * SAUCE: Auto-load rng-core module when device opened.
  * SAUCE: Auto-load openprom module when device opened.
  * SAUCE: Auto-load applicom module when device opened.
  * SAUCE: Auto-load toshiba module when device opened.
  * SAUCE: Auto-load cyclades module when device opened.
  * SAUCE: Auto-load riscom8 module when device opened.
  * SAUCE: Auto-load specialix module when device opened.
  * SAUCE: Auto-load videodev module when device opened.
  * SAUCE: Auto-load i2c_dev module when device opened.
  * SAUCE: Auto-load mtdchar module when device opened.
  * SAUCE: Auto-load pt module when device opened.
  * SAUCE: Auto-load pg module when device opened.
  * SAUCE: Auto-load cdc_acm module when device opened.
  * SAUCE: Auto-load msr module when device opened.
  * SAUCE: Auto-load cpuid module when device opened.
  * SAUCE: quickcam: Enable double-buffering by default
  * SAUCE: libata: Ignore HPA by default.
  * SAUCE: hostap: Change initial operation mode to managed (infra)
  * SAUCE: floppy: Provide a PnP device table in the module.
    - LP: #255651
  * SAUCE: Auto-load mwave module when device opened.
  * Build CONFIG_FUSE_FS into kernel, not as module.

  [ Stefan Bader ]

  * Enable build of ext4 as a module on LPIA
    - LP: #331848

  [ Tim Gardner ]

  * Update configs to fix LPIA FTBS

 -- Tim Gardner <email address hidden> Thu, 05 Mar 2009 10:43:24 -0700

Any chance of a Intrepid backport?

apw is already working on an Intrepid backport

I have pulled this patch back to the Intrepid kernel and have built some test kernels. If you could test those kernels and report back here that would be very helpful. These kernels are available at the URL below:

    http://people.ubuntu.com/~apw/lp255651-intrepid/

For me works it like a charm - Ubuntu 8.10 amd64

Accepted intrepid into linux-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

proposed worked great! thanks!!

oops! I spoke too soon. I have the floppy drive back, but now when I remove the floppy, the files remain and I cannot close them. Finally deleted all, and cannot open a new floppy disc. The only way to open a new disc is to reboot and the circle starts anew. Any ideas?

On Sun, 2009-03-22 at 18:33 +0000, Rick Keever wrote:

> oops! I spoke too soon. I have the floppy drive back, but now when I
> remove the floppy, the files remain and I cannot close them. Finally
> deleted all, and cannot open a new floppy disc. The only way to open a
> new disc is to reboot and the circle starts anew. Any ideas?
>
Always unmount a disk before removing it.

Scott
--
Scott James Remnant
<email address hidden>

thanks Scott, that was what I wasn't doing. I've got to get my old windows ways gone; bear with a new Linux user!

I have read through this "bug" thread and I sure am confused as to the fix. I have not been able to use a floppy drive with Ubuntu 8.04, 8.10 and now 9.04.

Would someone publish the "fix" so that the floppy drives will work.

In the thread I read that someone else has the floppy drive light on all the time. The response was that the cable is backwards. That is not the truth, as I have two desktops with floppy drive lights that are "on" all the time. I have tried the cable in all four ways and it stays on. I have made sure the red indicator strip is towards the number one terminal. In short I have done all the physical things one can do and I still have the led staying on, in two (2) different desktops.

I tried to add Floppy to my /etc/modules file and I got a message that I did not have authorization to make a change. So I know I was not doing it correctly. Some instructions in that area would help me. Thanks.

I think the reason the floppy stops working is there is a conflict with either java jre or the plug in or the adobe flash for firefox. prior to adding adobe flash the floppy 1,5 media was showing up and working but after it now just shows floppy and it will not mount, and will not open. So something conflicted with it.
It was OK prior to the latest upgrade in 9.04
Never had any trouble with it in 8.10 or 8.04 however the java plug in did not work in 8.10 as it does in 9.04 but unlike 8.04 now the floppy drive is not working. Hope that helps....

This bug was fixed in the package linux - 2.6.27-14.33

---------------
linux (2.6.27-14.33) intrepid-proposed; urgency=low

  [Stefan Bader]

  * Fix FTBS due to a mysteriously missing ABI directory.

linux (2.6.27-14.32) intrepid-proposed; urgency=low

  [Stefan Bader]

  * Rebuild of 2.6.27-14.30 with 2.6.27-11.31 security patches applied

linux (2.6.27-14.30) intrepid-proposed; urgency=low

  [ Alexey Starikovskiy ]

  * SAUCE: ACPI: EC: Limit workaround for ASUS notebooks even more
    - LP: #288385

  [ Huaxu Wan ]

  * SAUCE: report rfkill changes event if interface is down
    - LP: #193970

  [ Scott James Remnant ]

  * SAUCE: floppy: Provide a PnP device table in the module.
    - LP: #255651

  [ Steve Beattie ]

  * fix apparmor memory leak on deleted file ops
    - LP: #329489

  [ Stefan Bader ]

  * Revert "ACPI: Fix compiler warnings introduced by 32 to 64 bit acpi
    conversions"
    - LP: #337019
  * Revert "ACPI: Change acpi_evaluate_integer to support 64-bit on 32-bit
    kernels"
    - LP: #337019

  [ Upstream Kernel Changes ]

  * KVM: MMU: Add locking around kvm_mmu_slot_remove_write_access()
    - LP: #335097, #333409
  * ricoh_mmc: Handle newer models of Ricoh controllers
    - LP: #311932

linux (2.6.27-13.29) intrepid-proposed; urgency=low

  [ Colin Ian King ]

  * SAUCE: Bluetooth USB: fix kernel panic during suspend while streaming
    audio to bluetooth headset
    - LP: #331106, #322082

  [ Stefan Bader ]

  * Revert "SAUCE: Work around ACPI corruption upon suspend on some Dell
    machines." (replaced by stable update)
    - LP: #330200
  * Revert "SAUCE: Add back in lost commit for Apple BT Wireless Keyboard"
    (replaced by stable update)
    - LP: #330902

  [ Upstream Kernel Changes ]

  * Revert "vt: fix background color on line feed"
    - LP: #330200
  * ti_usb_3410_5052: support alternate firmware
    - LP: #231276
  * fuse: destroy bdi on umount
    - LP: #324921
  * fuse: fix missing fput on error
    - LP: #324921
  * fuse: fix NULL deref in fuse_file_alloc()
    - LP: #324921
  * inotify: clean up inotify_read and fix locking problems
    - LP: #324921
  * mac80211: decrement ref count to netdev after launching mesh discovery
    - LP: #324921
  * sysfs: fix problems with binary files
    - LP: #324921
  * x86, mm: fix pte_free()
    - LP: #324921
  * alpha: nautilus - fix compile failure with gcc-4.3
    - LP: #324921
  * it821x: Add ultra_mask quirk for Vortex86SX
    - LP: #324921
  * libata: pata_via: support VX855, future chips whose IDE controller use
    0x0571
    - LP: #324921
  * rtl8187: Add termination packet to prevent stall
    - LP: #324921
  * serial_8250: support for Sealevel Systems Model 7803 COMM+8
    - LP: #324921
  * SUNRPC: Fix a memory leak in rpcb_getport_async
    - LP: #324921
  * SUNRPC: Fix autobind on cloned rpc clients
    - LP: #324921
  * USB: fix char-device disconnect handling
    - LP: #324921
  * USB: storage: add unusual devs entry
    - LP: #324921
  * USB: usbmon: Implement compat_ioctl
    - LP: #324921
  * ALSA: hda - add another MacBook Pro 4, 1 subsystem ID
    - LP: #324921
  * ALSA: hda - Add quirk for HP DV6700 laptop
    - LP: #324921
  * ALSA: ...

Ok, how do I get the floppy drive to work? I tried the fix in miketan63 post without success. I am using kernel Linux 2.6-28-11-generic (i686).

I can confirm this bug in 9.10 prerelease as of 8th July 2009.

Does not autodetect flopp. Necessary to add floppy to /etc/modules.

Regarding the last comment, I believe the machine has an FX chipset. In which case, I suppose it is so old as to not be worth investigating.
I found the auto-loading works for the i810 based machines.

I tried using Miketan63 procedure and got as far as step 4. Step four
failed. I got the following message: "Cannot Initialize Device",
"unable to open any device formatting cannot continue"

That is it. I do not have a floppy icon in my Places> computer:/// file.

I have been trying to get my floppy drive to work through three
different upgrades of Ubuntu (9.04, 8.10, & 8.04) without any success.
I would really like to get it working.

If anyone can help or want more info on my computer let me know.

Thanks
John Hart

Are we saying that Ubuntu cannot access floppy drives without a degree in computer technology? This is plain nonsense, it has to work out of the box. How can I help test any possible solutions please?

The user specification is:
----------------
If a floppy drive is fitted to a computer and correctly configured in the BIOS setup then it should be found by the operating system at boot and shown in Places.

When the user clicks on 'Floppy Drive' in Places the system should show the folders/files of the 'Floppy Drive' in a normal nautilus window, similar to the contents of a cd when placed in the cdrom drive.
----------------

Can this be done?

I think the problem is that older BIOSs don't "know" whether or not a floppy drive is present (floppy drives still use an old technology designed back in 1981 or such) and loading the floppy driver module when there is no floppy drive (by adding it to /etc/modules) for everybody would probably slow down booting and result in lots of error messages (and might in some cases even cause harm to other hardware?).

Maybe adding the floppy driver to the hardware dialog that also has the closed source drivers for video cards etc. is a possible way to make it easier to enable this for "normal" users?

My BIOS has the floppy drive selected, so it should know that a floppy drive is present. Also my OS has loaded the floppy kernel on my desktop (the computer with a floppy drive), The same OS has not loaded the floppy kernel on my laptop. That indicated to me that the OS detects the floppy drive, and when found loads the kernel for it, but the OS cannot for some reason access it.

I know floppy disks are "old" technology, but it should not be that much of a problem to get them to work with a modern OS. Of course as soon as I can access my floppy disks, I will move the data to CD-R's and be done with it. I just want to get my old data files (image files, documents, and other files)

Since I have two desktops that exhibit the same lack of being able to access the floppy drive, one PC being over 5 years old the other newer, at least one of them should be able to access the floppy drive.

I am sure the older Linux distros could access the floppy drive, so why can't that access be recreated?

please do not change bug states without explanation.

@David
Again, please don't change bug statu without explanation.
This bug has been fixed long time ago, if you have an issue please open a new bug report.

I keep seeing that this bug has been fixed. I would like to see the fix so that I can "FIX" it on my computer. Maybe someone can help me with it as I have tried most all of the suggested fixes and none have worked yet.

Maybe a ask me to look at "X" and report what I have, then offer the next step based on the response. Somehow it has to be made to work.

Thanks.

@John Hart

This bug was about the floppy drive not detected on boot.
Giving "sudo modprobe floppy" (which loads floppy module) in a terminal was a workaround to make it works.

If you tried using that command in a terminal and it didn't work, It's because you have a different bug from this one.
So have a look on launchpad if another bug is already opened about your bug.
If not, open a new one.

Thanks.

please don't change bug status without explanation.

As far as I can tell, all the bug reports regarding floppy disk drives have been marked as duplicates of this one, and this is marked "Fix Released." But, there's still a bug, somewhat different from the original description in this bug report. The icon for a floppy drive appears in Nautilus, but the disk cannot actually be read: it's indicated that there is no media in the drive.

See this thread: http://ubuntuforums.org/showthread.php?t=1511446

@Brian Vaughan,

pls take a look at

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/441835?comments=all

for more on the floppy subject on karmic and lucid. there are well over 200 posts. sometimes I ask myself, how many bugs and posts would be required to get this/these issue/es solved once and for all in ubuntu releases ? I mean, is it acceptable to see users turned off and give up on ubuntu because of its inability to mount floppy media and see win fly through it ? is it a reason to not make work a basic computer device because of rants that it is an obsolete technology ? I know quite a few people and fairly large offices after experimenting with ubuntu for a while that went back to win after it was discovered this issue.

I agree. How am I going to flash my bios? I'm using a windows VM for just this purpose, but the first time I need it ...

For older motherboards that require a floppy to update the BIOS, it's easily done from a bootable floppy disk. Back in the days when I used to run Windows, I always did it that way because I didn't trust having Windows running while doing something as critical as a BIOS update. The OS installed on the HDD is irrelevant. As long as all the hardware is correct and properly recognized by the motherboard, you don't even have to have an OS installed to do a BIOS update and in fact, many system builders will argue that it's a good idea to update the BIOS prior to installing the OS.

I don't mean this to be a dismissal of the need for floppy support. It's still needed by people for other use cases with devices that only read/write their data to floppy. It's just that for BIOS management, it's simply not needed.

If you read through the link provided in #108 above, you will find several mentions of (relatively) simple cli solutions for mounting and unmounting the floppy. These can be semi-automated to 1 click solutions as launchers on the top panel. Not ideal, but a usable workaround till this (hopefully) gets fixed.