[SATLUG] floppy issue

Borries Demeler demeler at biochem.uthscsa.edu
Sun Apr 12 17:21:13 CDT 2015


Craig,
thanks for the suggestions - but I am still not any further...see below:

On Sun, Apr 12, 2015 at 08:59:45AM -0500, Craig wrote:
> > On Sun, Apr 12, 2015 at 02:27:22AM -0500, Craig wrote:
> > >* Have you tried:
> *>>* sudo modprobe floppy
> *>
> > udisks --mount /dev/fd0
> > Mount failed: Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/fd0,
> ...
> 
> After doing *"sudo modprobe floppy"*, what does dmesg show?

Nothing. I checked, there is no module called floppy.* in my stock Slack 14 kernel.
(3.10.17).

> (or going for same effect, different method, is "floppy" listed in
> /etc/modules -- if not add & reboot)

There is no such module in my distro's kernel.

> *> THe floppy drive is hooked to a traditional motherboard floppy controller
> *> with the flat ribbon cable connector (slightly shorter than a PATA
> connector).
> ....
> 
> Yes, unfortunately the days where the floppy on the software side
> could exclusively look at the 8 bit fdc/isa bus and/or
> expect at most 2 floppies on a system are long gone.  The software
> side, the motherboard floppy controller is not limited
> to keeping the the floppy on the 8 bit fdc/isa bus.
> Since the device directory is populated with /dev/fd0 when a floppy
> device is detected and the command "sudo modprobe floppy"
> doesn't generate a "No such device" message; it would seem there are
> other things to look at.

So I put in the old drive that worked on the older motherboard, and 
it exhibited the same symptoms, so we can exclude the floppy drive itself.

> For me, the first thing would be to figure out if what was the legacy
> fdc was remapped to && subsequently, which different floppy
> tools are needed to match the associated "bus change". e.g. floppy can
> be mapped to /dev/idr and/or /dev/sdr in which case the traditional,
> standard floppy tools will not function and give the results/error
> messages that have been posted.
> 
> "floppy -p" was historically a quick way to do this.
> Side note: I use embedded linux -- so tend to use historical command sets.

"floppy" doesn't exist on my system:

bash: floppy: command not found

> udisk --show-info /dev/fd0 may help.

Showing information for /org/freedesktop/UDisks/devices/fd0
  native-path:                 /sys/devices/platform/floppy.0/block/fd0
  device:                      2:0
  device-file:                 /dev/fd0
    presentation:              /dev/fd0
  detected at:                 Sun 12 Apr 2015 05:09:55 PM CDT
  system internal:             0
  removable:                   1
  has media:                   0
    detects change:            0
    detection by polling:      0
    detection inhibitable:     0
    detection inhibited:       0
  is read only:                0
  is mounted:                  0
  mount paths:             
  mounted by uid:              0
  presentation hide:           0
  presentation nopolicy:       1
  presentation name:           
  presentation icon:           
  automount hint:              
  size:                        0
  block size:                  0
  job underway:                no
  usage:                       
  type:                        
  version:                     
  uuid:                        
  label:                       
  drive:                                                                                       
    vendor:                    Floppy Drive                                                    
    model:                                                                                     
    revision:                                                                                  
    serial:                                                                                    
    WWN:                                                                                       
    detachable:                0                                                               
    can spindown:              0                                                               
    rotational media:          Yes, unknown rate                                               
    write-cache:               unknown                                                         
    ejectable:                 0                                                               
    adapter:                   Unknown                                                         
    ports:                                                                                     
    similar devices:                                                                           
    media:                                                                                     
      compat:                  floppy                                                          
    interface:                 platform                                                        
    if speed:                  (unknown)                                                       
    ATA SMART:                 not available

> The following may be helpful in showing the remapping of /dev/fd0.
> udisks --enumerate

/org/freedesktop/UDisks/devices/sdc1                                                           
/org/freedesktop/UDisks/devices/sda                                                            
/org/freedesktop/UDisks/devices/sr1                                                            
/org/freedesktop/UDisks/devices/sr0
/org/freedesktop/UDisks/devices/sdc
/org/freedesktop/UDisks/devices/md127
/org/freedesktop/UDisks/devices/sda1
/org/freedesktop/UDisks/devices/sda2
/org/freedesktop/UDisks/devices/sda3
/org/freedesktop/UDisks/devices/sdb1
/org/freedesktop/UDisks/devices/sdb
/org/freedesktop/UDisks/devices/fd0

> udisks --enumerate-device-files

udisks --enumerate-device-files
/dev/sdc1
/dev/disk/by-id/ata-ST3400832AS_4NF0473Q-part1
/dev/disk/by-uuid/eb4e4a35-eb3f-4427-b1b4-02d51155bed5
/dev/disk/by-path/pci-0000:07:00.0-sas-0x0600000000000000-lun-0-part1
/dev/sda
/dev/disk/by-id/ata-TOSHIBA_DT01ACA200_Y3CN4NGAS
/dev/disk/by-id/wwn-0x5000039ff3e557ec
/dev/disk/by-path/pci-0000:07:00.0-sas-0x0400000000000000-lun-0
/dev/sr1
/dev/disk/by-id/ata-HL-DT-ST_DVDRAM_GH22NS50_K0029Q74916
/dev/disk/by-id/wwn-0x5001480000000000
/dev/sr0
/dev/disk/by-id/ata-HL-DT-ST_DVDRAM_GH22NS40_K4P9C793024
/dev/disk/by-id/wwn-0x5001480000000000
/dev/sdc
/dev/disk/by-id/ata-ST3400832AS_4NF0473Q
/dev/disk/by-path/pci-0000:07:00.0-sas-0x0600000000000000-lun-0
/dev/md127
/dev/sda1
/dev/disk/by-id/ata-TOSHIBA_DT01ACA200_Y3CN4NGAS-part1
/dev/disk/by-id/wwn-0x5000039ff3e557ec-part1
/dev/disk/by-uuid/c8aff971-d67a-481c-9561-bfe50819e95c
/dev/disk/by-path/pci-0000:07:00.0-sas-0x0400000000000000-lun-0-part1
/dev/sda2
/dev/disk/by-id/ata-TOSHIBA_DT01ACA200_Y3CN4NGAS-part2
/dev/disk/by-id/wwn-0x5000039ff3e557ec-part2
/dev/disk/by-path/pci-0000:07:00.0-sas-0x0400000000000000-lun-0-part2
/dev/sda3
/dev/disk/by-id/ata-TOSHIBA_DT01ACA200_Y3CN4NGAS-part3
/dev/disk/by-id/wwn-0x5000039ff3e557ec-part3
/dev/disk/by-uuid/5c0bf862-ca9f-48ed-b4ea-a681726a22af
/dev/disk/by-path/pci-0000:07:00.0-sas-0x0400000000000000-lun-0-part3
/dev/sdb1
/dev/disk/by-id/ata-ST3400620AS_5QH029JH-part1
/dev/disk/by-path/pci-0000:07:00.0-sas-0x0500000000000000-lun-0-part1
/dev/sdb
/dev/disk/by-id/ata-ST3400620AS_5QH029JH
/dev/disk/by-path/pci-0000:07:00.0-sas-0x0500000000000000-lun-0
/dev/fd0

> There are other things to check out, given there are mainstream
> distros that have dropped floppy support and/or automatically
> block floppy access.

The same distro install (no mods except video driver) worked fine with the 
older AMD motherboard and same floppy drive.

> Knowing the distro/version would be helpful.

Slack 14

> Knowing the specific motherboard model number would be helpful.

ASRock 990 FX Extreme4
http://www.asrock.com/mb/AMD/990FX%20Extreme4/

I checked the manual and there is nothing special about the floppy drive mentioned.

Still stumped...

So far I have to conclude the floppy controller is broken or not recognized by
the 3.10.17 kernel. No other ideas right now.

-b.

> 
> On Sun, Apr 12, 2015 at 2:27 AM, Craig <sargonemail at gmail.com> wrote:
> 
> > Have you tried:
> > sudo modprobe floppy
> > and then
> > udisks --mount /dev/fd0
> >
> > On Sun, Apr 12, 2015 at 1:46 AM, Craig <sargonemail at gmail.com> wrote:
> >
> >> Borries Demeler demeler at biochem.uthscsa.edu on Sat Apr 11 17:25:57
> >> CDT 2015 wrote:
> >> > Finally got back to this.
> >> > Here is what I find:
> >> >
> >> > * I can boot an old dos/windows95 floppy from the drive just fine
> >> ..
> >> > * mounting the old or newly formatted floppies under Linux is
> >> impossible:
> >>   ...
> >> >
> >> > * formatting the floppies under Linux with any filesystem seems to
> >> succeed at
> >> > first, including all Linux or windows or msdos file systems, at least
> >> there is
> >> > no error message.
> >> >
> >> > * mounting such formatted filesystems under Linux returns the same
> >> exact error
> >> > as above:
> >>   ...
> >> >
> >> > Any idea?
> >> ...
> >>
> >> It sounds like the floppy controller for /dev/fd0 is not associated with
> >> the traditional floppy controller (could be ata, ide/eide, pata, usb, scsi,
> >> etc)
> >> In not totally correct technical terms, need to figure out first which
> >> bus/controller /dev/fd0 is being associated with.
> >> (e.g. hard drive bus example: ata, ide, eide, scsi, usb.
> >>  Tools for each are different, so just saying /dev/harddrive would NOT
> >> indicate if ata, ide, eide, scsi or usb hard drive tools/modules are
> >> needed!)
> >> e.g. fdutils will not work with a usb floppy!
> >> The output of the command: floppy -p
> >> would provide appropriate information to figure out what's going on.
> >>
> >> Craig
> >>
> >>
> >
> -- 
> _______________________________________________
> SATLUG mailing list
> SATLUG at satlug.org
> http://alamo.satlug.org/mailman/listinfo/satlug to manage/unsubscribe
> Powered by Rackspace (www.rackspace.com)


More information about the SATLUG mailing list