Floppy won't mount with new hardware

Floppy won't mount with new hardware

Post by Gary Brain » Tue, 17 Aug 1999 04:00:00



   I recently installed some new hardware, and now can no longer mount a
floppy disk.  I'm stumped as to why; any help would be appreciated.

   I am using Caldera OpenLinux 1.3.  The changed hardware is: CPU: AMD
K6-2 350; MB: FIC PA-2013.  All other hardware is the same as my old
system.  The floppy would mount without a hitch on the old system.

   The floppy drive appears to be physically connected fine.  It works in
DOS and I used it to boot Linux in order to install.  During the
installation, there is an option to save configuration to a floppy; this
fails.

   Attempting to mount a floppy (any filesystem) gets a long and cryptic
error message.  I have copied the entry from /var/log/messages below, if
that helps.

   If anyone has a clue why this isn't working, please please please let me
know.

                        -Gary

-----Begin error message

Aug 16 00:35:50 noname kernel: floppy driver state
Aug 16 00:35:50 noname kernel: -------------------
Aug 16 00:35:50 noname kernel: now=7027 last interrupt=270 last called
handler=00175a9c
Aug 16 00:35:50 noname kernel: timeout_message=redo fd request
Aug 16 00:35:50 noname kernel: last output bytes:
Aug 16 00:35:50 noname kernel:  0  0 0
Aug 16 00:35:50 noname last message repeated 5 times
Aug 16 00:35:50 noname kernel:  8 80 270
Aug 16 00:35:50 noname last message repeated 4 times
Aug 16 00:35:50 noname kernel:  e 80 270
Aug 16 00:35:50 noname kernel: 13 80 270
Aug 16 00:35:50 noname kernel:  0 90 270
Aug 16 00:35:50 noname kernel: 1a 90 270
Aug 16 00:35:50 noname kernel:  0 90 270
Aug 16 00:35:50 noname kernel: 12 90 270
Aug 16 00:35:50 noname kernel:  0 90 270
Aug 16 00:35:50 noname kernel: 14 90 270
Aug 16 00:35:50 noname kernel: 18 80 270
Aug 16 00:35:50 noname kernel: last result at 270
Aug 16 00:35:50 noname kernel: last redo_fd_request at 6727
Aug 16 00:35:50 noname kernel: 80
Aug 16 00:35:50 noname kernel: status=80
Aug 16 00:35:50 noname kernel: fdc_busy=1
Aug 16 00:35:50 noname kernel: DEVICE_INTR=00175a9c
Aug 16 00:35:50 noname kernel: cont=001cf65c
Aug 16 00:35:50 noname kernel: CURRENT=001df9fc
Aug 16 00:35:50 noname kernel: command_status=-1
Aug 16 00:35:50 noname kernel:
Aug 16 00:35:50 noname kernel: floppy0: floppy timeout called
Aug 16 00:35:50 noname kernel: end_request: I/O error, dev 02:00, sector 0
Aug 16 00:35:53 noname kernel:
Aug 16 00:35:53 noname kernel: floppy driver state
Aug 16 00:35:53 noname kernel: -------------------
Aug 16 00:35:53 noname kernel: now=7327 last interrupt=270 last called
handler=00175a9c
Aug 16 00:35:53 noname kernel: timeout_message=redo fd request
Aug 16 00:35:53 noname kernel: last output bytes:
Aug 16 00:35:53 noname kernel:  0  0 0
Aug 16 00:35:53 noname last message repeated 5 times
Aug 16 00:35:53 noname kernel:  8 80 270
Aug 16 00:35:53 noname last message repeated 4 times
Aug 16 00:35:53 noname kernel:  e 80 270
Aug 16 00:35:53 noname kernel: 13 80 270
Aug 16 00:35:53 noname kernel:  0 90 270
Aug 16 00:35:53 noname kernel: 1a 90 270
Aug 16 00:35:53 noname kernel:  0 90 270
Aug 16 00:35:53 noname kernel: 12 90 270
Aug 16 00:35:53 noname kernel:  0 90 270
Aug 16 00:35:53 noname kernel: 14 90 270
Aug 16 00:35:53 noname kernel: 18 80 270
Aug 16 00:35:53 noname kernel: last result at 270
Aug 16 00:35:53 noname kernel: last redo_fd_request at 7027
Aug 16 00:35:53 noname kernel: 80
Aug 16 00:35:53 noname kernel: status=80
Aug 16 00:35:53 noname kernel: fdc_busy=1
Aug 16 00:35:53 noname kernel: DEVICE_INTR=00175a9c
Aug 16 00:35:53 noname kernel: cont=001cf65c
Aug 16 00:35:53 noname kernel: CURRENT=001df9cc
Aug 16 00:35:53 noname kernel: command_status=-1
Aug 16 00:35:53 noname kernel:
Aug 16 00:35:53 noname kernel: floppy0: floppy timeout called
Aug 16 00:35:53 noname kernel: end_request: I/O error, dev 02:00, sector 0
Aug 16 00:35:56 noname kernel:
Aug 16 00:35:56 noname kernel: floppy driver state
Aug 16 00:35:56 noname kernel: -------------------
Aug 16 00:35:56 noname kernel: now=7627 last interrupt=270 last called
handler=00175a9c
Aug 16 00:35:56 noname kernel: timeout_message=redo fd request
Aug 16 00:35:56 noname kernel: last output bytes:
Aug 16 00:35:56 noname kernel:  0  0 0
Aug 16 00:35:56 noname last message repeated 5 times
Aug 16 00:35:56 noname kernel:  8 80 270
Aug 16 00:35:56 noname last message repeated 4 times
Aug 16 00:35:56 noname kernel:  e 80 270
Aug 16 00:35:56 noname kernel: 13 80 270
Aug 16 00:35:56 noname kernel:  0 90 270
Aug 16 00:35:56 noname kernel: 1a 90 270
Aug 16 00:35:56 noname kernel:  0 90 270
Aug 16 00:35:56 noname kernel: 12 90 270
Aug 16 00:35:56 noname kernel:  0 90 270
Aug 16 00:35:56 noname kernel: 14 90 270
Aug 16 00:35:56 noname kernel: 18 80 270
Aug 16 00:35:56 noname kernel: last result at 270
Aug 16 00:35:56 noname kernel: last redo_fd_request at 7327
Aug 16 00:35:56 noname kernel: 80
Aug 16 00:35:56 noname kernel: status=80
Aug 16 00:35:56 noname kernel: fdc_busy=1
Aug 16 00:35:56 noname kernel: DEVICE_INTR=00175a9c
Aug 16 00:35:56 noname kernel: cont=001cf65c
Aug 16 00:35:56 noname kernel: CURRENT=001df99c
Aug 16 00:35:56 noname kernel: command_status=-1
Aug 16 00:35:56 noname kernel:
Aug 16 00:35:56 noname kernel: floppy0: floppy timeout called
Aug 16 00:35:56 noname kernel: end_request: I/O error, dev 02:00, sector 0
Aug 16 00:35:59 noname kernel:
Aug 16 00:35:59 noname kernel: floppy driver state
Aug 16 00:35:59 noname kernel: -------------------
Aug 16 00:35:59 noname kernel: now=7927 last interrupt=270 last called
handler=00175a9c
Aug 16 00:35:59 noname kernel: timeout_message=redo fd request
Aug 16 00:35:59 noname kernel: last output bytes:
Aug 16 00:35:59 noname kernel:  0  0 0
Aug 16 00:35:59 noname last message repeated 5 times
Aug 16 00:35:59 noname kernel:  8 80 270
Aug 16 00:35:59 noname last message repeated 4 times
Aug 16 00:35:59 noname kernel:  e 80 270
Aug 16 00:35:59 noname kernel: 13 80 270
Aug 16 00:35:59 noname kernel:  0 90 270
Aug 16 00:35:59 noname kernel: 1a 90 270
Aug 16 00:35:59 noname kernel:  0 90 270
Aug 16 00:35:59 noname kernel: 12 90 270
Aug 16 00:35:59 noname kernel:  0 90 270
Aug 16 00:35:59 noname kernel: 14 90 270
Aug 16 00:35:59 noname kernel: 18 80 270
Aug 16 00:35:59 noname kernel: last result at 270
Aug 16 00:35:59 noname kernel: last redo_fd_request at 7627
Aug 16 00:35:59 noname kernel: 80
Aug 16 00:35:59 noname kernel: status=80
Aug 16 00:35:59 noname kernel: fdc_busy=1
Aug 16 00:35:59 noname kernel: DEVICE_INTR=00175a9c
Aug 16 00:35:59 noname kernel: cont=001cf65c
Aug 16 00:35:59 noname kernel: CURRENT=001df9fc
Aug 16 00:35:59 noname kernel: command_status=-1
Aug 16 00:35:59 noname kernel:
Aug 16 00:35:59 noname kernel: floppy0: floppy timeout called
Aug 16 00:35:59 noname kernel: end_request: I/O error, dev 02:00, sector 0
Aug 16 00:35:59 noname kernel: FAT bread failed
Aug 16 00:36:02 noname kernel:
Aug 16 00:36:02 noname kernel: floppy driver state
Aug 16 00:36:02 noname kernel: -------------------
Aug 16 00:36:02 noname kernel: now=8227 last interrupt=270 last called
handler=00175a9c
Aug 16 00:36:02 noname kernel: timeout_message=redo fd request
Aug 16 00:36:02 noname kernel: last output bytes:
Aug 16 00:36:02 noname kernel:  0  0 0
Aug 16 00:36:02 noname last message repeated 5 times
Aug 16 00:36:02 noname kernel:  8 80 270
Aug 16 00:36:02 noname last message repeated 4 times
Aug 16 00:36:02 noname kernel:  e 80 270
Aug 16 00:36:02 noname kernel: 13 80 270
Aug 16 00:36:02 noname kernel:  0 90 270
Aug 16 00:36:02 noname kernel: 1a 90 270
Aug 16 00:36:02 noname kernel:  0 90 270
Aug 16 00:36:02 noname kernel: 12 90 270
Aug 16 00:36:02 noname kernel:  0 90 270
Aug 16 00:36:02 noname kernel: 14 90 270
Aug 16 00:36:02 noname kernel: 18 80 270
Aug 16 00:36:02 noname kernel: last result at 270
Aug 16 00:36:02 noname kernel: last redo_fd_request at 7927
Aug 16 00:36:02 noname kernel: 80
Aug 16 00:36:02 noname kernel: status=80
Aug 16 00:36:02 noname kernel: fdc_busy=1
Aug 16 00:36:02 noname kernel: DEVICE_INTR=00175a9c
Aug 16 00:36:02 noname kernel: cont=001cf65c
Aug 16 00:36:02 noname kernel: CURRENT=001df9cc
Aug 16 00:36:02 noname kernel: command_status=-1
Aug 16 00:36:02 noname kernel:
Aug 16 00:36:02 noname kernel: floppy0: floppy timeout called
Aug 16 00:36:02 noname kernel: end_request: I/O error, dev 02:00, sector 0
Aug 16 00:36:52 noname kernel: Unable to load NLS charset cp437(nls_cp437)

-----End Error Message

|Gary Brainin                     | "...the right to be let alone--the most
|gar...@spies.com  Ramblings and  | comprehensive of rights and the right most
|anti-spam instructions at:       | valued by civilized men." Olmstead v. U.S.
|http://www.spies.com/garygm/     | (Brandeis, J., dissenting)

 
 
 

Floppy won't mount with new hardware

Post by Vilmos Sot » Tue, 17 Aug 1999 04:00:00



>    I recently installed some new hardware, and now can no longer mount a
> floppy disk.  I'm stumped as to why; any help would be appreciated.

>    I am using Caldera OpenLinux 1.3.  The changed hardware is: CPU: AMD
> K6-2 350; MB: FIC PA-2013.  All other hardware is the same as my old
> system.  The floppy would mount without a hitch on the old system.

>    The floppy drive appears to be physically connected fine.  It works in
> DOS and I used it to boot Linux in order to install.  During the
> installation, there is an option to save configuration to a floppy; this
> fails.

> Aug 16 00:35:50 noname kernel: floppy0: floppy timeout called
> Aug 16 00:35:50 noname kernel: end_request: I/O error, dev 02:00, sector 0
> Aug 16 00:35:53 noname kernel:
> Aug 16 00:35:53 noname kernel:
> Aug 16 00:35:53 noname kernel: floppy0: floppy timeout called
> Aug 16 00:35:53 noname kernel: end_request: I/O error, dev 02:00, sector 0
> Aug 16 00:35:56 noname kernel:

Hi,

While I am in no way expert in this, but from the symptoms (works with
DOS but not with Linux) and from the errorlog I would say your floppy
drive uses some nonstandard settings. Of course DOS can use it since
your BIOS is adjusted to the changes and DOS uses BIOS. But Linux has
its own device drivers and ignores the BIOS for the most part. So, I
would look in this direction.

Vilmos

--
Looking for a job in British Columbia.
http://members.home.net/vilmossoti/resume.html

 
 
 

Floppy won't mount with new hardware

Post by Gary Brain » Tue, 17 Aug 1999 04:00:00




Quote:> While I am in no way expert in this, but from the symptoms (works with
> DOS but not with Linux) and from the errorlog I would say your floppy
> drive uses some nonstandard settings. Of course DOS can use it since
> your BIOS is adjusted to the changes and DOS uses BIOS. But Linux has
> its own device drivers and ignores the BIOS for the most part. So, I
> would look in this direction.

   I'm not completely sure I understand this.  I mean, the actual
floppy drive is the same one I was using before; the difference is the
motherboard.  If Linux is ignoring the BIOS, what else is there that
could be a problem?

                        -Gary

|Gary Brainin                     | "...the right to be let alone--the most

|anti-spam instructions at:       | valued by civilized men." Olmstead v. U.S.
|http://www.spies.com/garygm/     | (Brandeis, J., dissenting)

 
 
 

Floppy won't mount with new hardware

Post by Jon Aker » Tue, 17 Aug 1999 04:00:00





> > While I am in no way expert in this, but from the symptoms (works with
> > DOS but not with Linux) and from the errorlog I would say your floppy
> > drive uses some nonstandard settings. Of course DOS can use it since
> > your BIOS is adjusted to the changes and DOS uses BIOS. But Linux has
> > its own device drivers and ignores the BIOS for the most part. So, I
> > would look in this direction.

>    I'm not completely sure I understand this.  I mean, the actual
> floppy drive is the same one I was using before; the difference is the
> motherboard.  If Linux is ignoring the BIOS, what else is there that
> could be a problem?

Just because the floppy drive is the same, the addresses that it is set at in the
memory of the computer when it starts up can differ when you change peripherals
or motherboards. For instance, I have seen Windows 98 detect new floppy drive
controllers when I have started it up without connecting a PS/2 mouse, simply
because the memory address that the floppy controller was on when the PS/2 mouse
was connected changed due to the movement of the mouse. It isn't the drive itself
that you are worried about, but the floppy drive controller on the motherboard
that is important.
 
 
 

Floppy won't mount with new hardware

Post by Gary Brain » Wed, 18 Aug 1999 04:00:00




Quote:>Just because the floppy drive is the same, the addresses that it is set at
in the
>memory of the computer when it starts up can differ when you change
peripherals
>or motherboards. For instance, I have seen Windows 98 detect new floppy
drive
>controllers when I have started it up without connecting a PS/2 mouse,
simply
>because the memory address that the floppy controller was on when the PS/2
mouse
>was connected changed due to the movement of the mouse. It isn't the drive
itself
>that you are worried about, but the floppy drive controller on the
motherboard
>that is important.

   You know, I kept wondering if I should mention that the mouse moved
from COM1: to the PS/2 port.  Thanks for the tip.

   It appears, though, that the controller is my problem.
Unfortunately, that probably means that I have to get a new
motherboard, no?

                        -Gary

|Gary Brainin                     | "...the right to be let alone--the most

|anti-spam instructions at:       | valued by civilized men." Olmstead v. U.S.
|http://www.spies.com/garygm/     | (Brandeis, J., dissenting)

 
 
 

1. Floppy directory structure won't update when new floppy is mounted

Hi:

Can anyone explain this.  I mount a floppy disk on device
/dev/fd0 using "mount -t ext2 /dev/fd0 /mnt". I then cd into
/mnt and perform an ls to get the directory.  Sure enough
the directory structure reflects what is actually on the disk.

Now I unmount the disk "umount /dev/fd0" and then mount
a different disk containing a different directory
structure (using the same mount command as before).
Then I cd into /mnt and do an ls to get the directory.
The directory structure reported by the ls command is
wrong.  The directory listing is the same as the first disk
that I mounted!.  If I then cd into directories that
are NOT on the second disk BUT are on the first, the
system comes back with something like "doesn't exist"
(which is very re-assuring)

I can mount any number of floppies on /dev/fd0, the
results are the same.  NOW if I use /dev/fd0H1440, the
directory structure will indeed be correct BUT, from
this point onward, I cannot mount a different floppy on
/dev/fd0H1440 and expect to see the correct directory
structure - it will always show the structure of the
FIRST floppy that I mounted on the device.  (I realize
that the difference between /dev/fd0 and /dev/fd0H1440
is the minor device number, but their is a bigger
mystery here for me).

Obviously re-booting the system seems to clear this -
any new floppies mounted on these devices will report
the directory structure correctly - for the first
floppy mounted.

Another problem related to this - I have on a few
occasions inadvertently issued the mount command
for /dev/fd0 without the disk in the drive.  Instead
of rejecting the command, the system mounts the
drive as read-only.  If I umount then mount, the floppy
still is mounted read only.  This seems to be similar to
the first problem - the FIRST floppy mounted on the
device since the last reboot was read-only (by mistake),
so this device will be read-only until the system is
rebooted.

If anyone can shed some light on this I would be
most grateful.

Jeffrey Smith

2. Info on 3.3

3. Zdisk floppy's won't mount

4. Networking Utilities

5. Floppy won't mount on ThinkPad 770ED

6. DLT4000 problems

7. Floppy won't mount ...

8. rsh between RH6.1 & RH 5.2 not working??

9. Newbie - File System Manager won't mount cdrom/floppy

10. My floppy won't mount

11. sol 2.5 x86 won't mount cdrom or floppy

12. floppy won't mount at install time

13. floppy drive won't mount