Announcement

Collapse
No announcement yet.

Floppy drive not recognized by new device notifier

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Floppy drive not recognized by new device notifier

    Hi all,

    In kde4.1.3, the new device notifier does not recognize the insertion of a floppy disk. It is in /etc/fstab and is mountable in command line and via KDiskfree, but that only after issuing "sudo modprobe floppy" and adding the line "floppy" to /etc/modules. I also don't have the ability to umount the drive via GUI, in KDiskfree the umount option is greyed out and will only try to mount it again. Dolphin also does not give the umount option upon right click. I know I can do this all through command line, but KDE3.5 spoiled me with its UI

    How do I get GUI floppy interaction back in 4.1.3


    #2
    Re: Floppy drive not recognized by new device notifier

    Please post your /etc/fstab file for review. My floppy is recognized when I insert a diskette.
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      Re: Floppy drive not recognized by new device notifier

      Sorry, here's the fstab

      # /etc/fstab: static file system information.
      #
      # <file system> <mount point> <type> <options> <dump> <pass>
      proc /proc proc defaults 0 0
      # /dev/sda3
      UUID=08cba1dd-5146-446c-b41f-f5ea514df244 / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid,relatime 0 1
      # /dev/sda5
      UUID=6e67b37a-45fa-4d44-aa1f-a58f804b1d1b none swap sw 0 0
      /dev/scd0 /media/cdrom0 udf,iso9660 user,atime,noauto,rw,dev,exec,suid 0 0
      /dev/fd0 /media/floppy0 vfat user,atime,noauto,rw,dev,exec,suid 0 0
      /dev/sdb1 /disk2 ext3 nouser,atime,auto,rw,nodev,nosuid,relatime 0 0

      Comment


        #4
        Re: Floppy drive not recognized by new device notifier

        Edit the /etc/fstab file (as root) and change:
        /dev/fd0 /media/floppy0 vfat user,atime,noauto,rw,dev,exec,suid 0 0
        to this:
        /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
        Save and close. Open a console and type:
        Code:
        sudo mount -a
        You should then just have to insert a diskette in and after it's read, the device notifier should pop-up and show you the diskette drive.
        Windows no longer obstructs my view.
        Using Kubuntu Linux since March 23, 2007.
        "It is a capital mistake to theorize before one has data." - Sherlock Holmes

        Comment


          #5
          Re: Floppy drive not recognized by new device notifier

          Thanks for the reply, but:
          I tried:
          Edit the /etc/fstab file (as root) and change:
          Quote
          /dev/fd0 /media/floppy0 vfat user,atime,noauto,rw,dev,exec,suid 0 0
          to this:
          Quote
          /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
          Save and close. Open a console and type:
          Code:

          sudo mount -a

          and now I can't even mount it as user from the command line.

          Anything else?

          Comment


            #6
            Re: Floppy drive not recognized by new device notifier

            Oh, and my DVD drive works as expected when a cd/dvd is inserted


            Comment


              #7
              Re: Floppy drive not recognized by new device notifier

              Check to ensure that you (as the logged on user) belong to the floppy group.

              K Menu > Applications > System > User Manager (KUser)

              Locate and click on your user name in the Users tab. That will bring up User Properties. Click on the Groups tab and ensure that floppy is checked. If it is not, check it and click on OK.

              Do a normal shutdown/restart of your system. When back on the desktop, insert a diskette. Does the Device Notifier show the drive? It should.
              Windows no longer obstructs my view.
              Using Kubuntu Linux since March 23, 2007.
              "It is a capital mistake to theorize before one has data." - Sherlock Holmes

              Comment


                #8
                Re: Floppy drive not recognized by new device notifier

                Hi,

                Yes, I was already in group floppy, and no I don't get notification upon insertion of the disk.

                Does it matter that this install is an upgrade of 3.5.10(Ithink)?

                Oh, and I get an error message if I try sudo mount -a or sudo mount /media/floppy0
                "mount: you must specify the filesystem type"



                Comment


                  #9
                  Re: Floppy drive not recognized by new device notifier

                  No, it shouldn't. Intrepid is KDE 4.1.3 (currently). When you insert the diskette, is it read - does the drive activate? If 'yes,' open a console and type:
                  Code:
                  cat /etc/mtab
                  What is the last line of the output?
                  Windows no longer obstructs my view.
                  Using Kubuntu Linux since March 23, 2007.
                  "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                  Comment


                    #10
                    Re: Floppy drive not recognized by new device notifier

                    Ohhh,

                    If I change

                    /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

                    to

                    /dev/fd0 /media/floppy0 vfat rw,user,noauto,exec,utf8 0 0

                    I get back my ability to mount on the command line, though.

                    But, the drive does not activate when the disk is inserted! It used to (I think) back in 3.5.10...

                    Ok, so not forward, but not backward and perhaps a clue...

                    Comment


                      #11
                      Re: Floppy drive not recognized by new device notifier

                      You shouldn't have had to add the floppy module to the /etc/modules file. Is this a built-in floppy drive, or connected via USB?

                      From the CLI, what is the output of:
                      Code:
                      modinfo floppy
                      Windows no longer obstructs my view.
                      Using Kubuntu Linux since March 23, 2007.
                      "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                      Comment


                        #12
                        Re: Floppy drive not recognized by new device notifier

                        modinfo floppy
                        filename: /lib/modules/2.6.27-8-generic/kernel/drivers/block/floppy.ko
                        alias: block-major-2-*
                        license: GPL
                        author: Alain L. Knaff
                        srcversion: E0938D1D0716F53CA626CFF
                        depends:
                        vermagic: 2.6.27-8-generic SMP mod_unload modversions 586
                        parm: floppy:charp
                        parm: FLOPPY_IRQ:int
                        parm: FLOPPY_DMA:int

                        Comment


                          #13
                          Re: Floppy drive not recognized by new device notifier

                          http://kubuntuforums.net/forums/inde...opic=3098557.0

                          Note Rog131's links to the kernel "bug". According to the poster in one of the bug reports, you can simply add "floppy" with no quote marks to the end of the list in /etc/modules if you want it to be always loaded at bootup.

                          I think we're experiencing the "passing of an era" here.

                          Comment


                            #14
                            Re: Floppy drive not recognized by new device notifier

                            Originally posted by Snowhog
                            Edit the /etc/fstab file (as root) and change:
                            /dev/fd0 /media/floppy0 vfat user,atime,noauto,rw,dev,exec,suid 0 0
                            to this:
                            /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
                            Save and close. Open a console and type:
                            Code:
                            sudo mount -a
                            Just to clear up a misconception here, rmallis. With the "noauto" in the fourth field of the stanza in the file system table, it won't be mounted at boot or at runtime with the mount -a option. That is the purpose of that no auto, to avoid mounting when mount -a is passed to the system. This is not an answer to your issue but to help you avoid a red herring. I think dibl pointed you at a useful link.

                            Comment


                              #15
                              Re: Floppy drive not recognized by new device notifier

                              The passing of an era. Nooooo, it's too young to die!!!!

                              Seriously, I need the floppy to interface with a piece of legacy hardware that only runs on a legacy windows box, pre-usb. I'll keep the usb-floppy in mind for future reference.

                              So, I do need to do the "sudo modprobe floppy" to get it to recognize /dev/fd0, but do I need to insert "floppy" into /etc/modules? Is that something that is helpful whenever the kernel is updated so that I don't always have to reissue the "sudo modprobe floppy"?

                              Also, in fstab, the noauto option is appropriate if I am not keeping the same floppy in the drive at all times, right? auto would result in some odd behavior/error messages at boot if no floppy is present, yes?

                              After all is said and done here, I do get recognition of the insertion of a floppy with the new device notifier upon mounting the drive the first time, but then, it does not recognize when the floppy is unmounted and ejected. Same with KDiskfree. This seems unreliable.

                              mount and umount will be necessary for the near future as the consensus thus far is that fixed 3.5" floppies are at EOL.

                              Thanks for everyone's input, not exactly resolved, but better than when I started, I think

                              Comment

                              Working...
                              X