I guess this is the same problem I have, but I'm not 100% sure. I'm on 10.10/amd64 and I (still) use my floppy drive semi-regularly because I dumpster dive and thus prepare BIOS updates for older machines. Anyway, I noticed that under my current installation, being 10.10/amd64 my floppy does not work.
I booted the machine under Windows XP Home and the floppy is readable there. The most surprising, though, is that I booted the 10.10/i386 LiveCD on the same machine and the floppy then works! All on the same machine. I can rule out hardware problems fairly certainly. In /var/log/messages, I get the following when accessing the floppy (either by using Gnome or by manually executing "mount /dev/fd0 /mnt): Apr 19 20:18:50 tiger kernel: [10226.990059] Apr 19 20:18:50 tiger kernel: [10226.990071] floppy driver state Apr 19 20:18:50 tiger kernel: [10226.990075] ------------------- Apr 19 20:18:50 tiger kernel: [10226.990123] now=4295959995 last interrupt=4294946147 diff=1013848 last called handler=main_command_interrupt Apr 19 20:18:50 tiger kernel: [10226.990128] timeout_message=lock fdc Apr 19 20:18:50 tiger kernel: [10226.990131] last output bytes: Apr 19 20:18:50 tiger kernel: [10226.990136] 8 81 4294946073 Apr 19 20:18:50 tiger kernel: [10226.990140] f 80 4294946073 Apr 19 20:18:50 tiger kernel: [10226.990144] 0 90 4294946073 Apr 19 20:18:50 tiger kernel: [10226.990148] 1 91 4294946073 Apr 19 20:18:50 tiger kernel: [10226.990151] 8 81 4294946073 Apr 19 20:18:50 tiger kernel: [10226.990155] 4 80 4294946075 Apr 19 20:18:50 tiger kernel: [10226.990158] 0 90 4294946075 Apr 19 20:18:50 tiger kernel: [10226.990162] f 80 4294946075 Apr 19 20:18:50 tiger kernel: [10226.990165] 0 90 4294946075 Apr 19 20:18:50 tiger kernel: [10226.990169] 0 91 4294946075 Apr 19 20:18:50 tiger kernel: [10226.990172] 8 81 4294946075 Apr 19 20:18:50 tiger kernel: [10226.990176] e6 80 4294946109 Apr 19 20:18:50 tiger kernel: [10226.990180] 0 90 4294946109 Apr 19 20:18:50 tiger kernel: [10226.990184] 0 90 4294946109 Apr 19 20:18:50 tiger kernel: [10226.990187] 0 90 4294946109 Apr 19 20:18:50 tiger kernel: [10226.990191] 1 90 4294946109 Apr 19 20:18:50 tiger kernel: [10226.990194] 2 90 4294946109 Apr 19 20:18:50 tiger kernel: [10226.990200] 12 90 4294946109 Apr 19 20:18:50 tiger kernel: [10226.990204] 1b 90 4294946109 Apr 19 20:18:50 tiger kernel: [10226.990207] ff 90 4294946109 Apr 19 20:18:50 tiger kernel: [10226.990211] last result at 4294946610 Apr 19 20:18:50 tiger kernel: [10226.990214] last redo_fd_request at 4295811797 Apr 19 20:18:50 tiger kernel: [10226.990231] status=77 Apr 19 20:18:50 tiger kernel: [10226.990233] fdc_busy=1 Apr 19 20:18:50 tiger kernel: [10226.990242] do_floppy=reset_interrupt Apr 19 20:18:50 tiger kernel: [10226.990247] cont=ffffffffa0046060 Apr 19 20:18:50 tiger kernel: [10226.990250] current_req=(null) Apr 19 20:18:50 tiger kernel: [10226.990254] command_status=-1 Apr 19 20:18:50 tiger kernel: [10226.990256] Apr 19 20:18:50 tiger kernel: [10226.990266] floppy0: floppy timeout called Hope this helps someone Regards Jorg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/441835 Title: Clicking on floppy gives "no device media found" -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
