problem with a floppy

problem with a floppy

Post by Martin Klooc » Wed, 11 Mar 1998 04:00:00


I have a problem with a floppy:
I have a floppy which contains a tar-file built by an IBM under AIX. Now
I want to read on a SUN under Solaris 2.5.1. Everytime I try to find out
what this tar-file contains, there come the following messages:
With 'tar tfv /dev/fd0' comes 'device busy',
with 'tar tfv /dev/fd<any other number>' comes 'wrong blocksize' or
something like that.

Does anybody know, what's the problem?
For any answers thanks in advance!

Bye, Martin


1. Slackware 2.02 install problems / problems with floppy code?

     I tried reinstalling my Linux system with the Slackware 2.02 install
disks.  Unfortunately, the Linux kernel v1.1.54 used in Slackware 2.02
doesn't like my floppies.

Here's my setup:
   486 DLC/40 ... 8 megs RAM
   340 MB Western Digital Caviar (IDE)
   250 MB Western Digital Caviar (IDE)
   Drive A is a 1.44 MB TIAC, drive B is a 1.22 MB TIAC

What I'm doing:
   Reinstalling my Linux system after repartitioning with the adddition of
a second hard drive.  Since Slackware 2.02 just came out, I decided to
install using the new disks to catch any important upgrades since my
original Slackware 1.0 installation.

What was running before:
   Everything was fine when I had the Linux kernel v1.1.40 running.  When
I upgraded to v1.1.51, my floppies started having problems, with errors
like "Invalid device, etc...".  With v1.1.52, the drives became accessible
but the system would lock solid if I tried to write to either drive.
v1.1.53 seemed to do the same.

What happened when I tried installing Slackware 2.02:
  (Using "bare" bootdisk for 1.44 MB, 1.44 MB rookdisk)

   Everything seemed to boot okay.  I inserted the rootdisk after the
kernel loaded, the RAMDISK was initialized and I was prompted to insert
the rootdisk.  The message "VFS: Disk change detected" appeared, and the
system proceeded to lock *SOLID*, requiring my to resort to the big red
RESET key.  Same thing happened when I tried for several more attempts.
The same thing happened when I used LodLin v1.2 off my DOS partition,
using a copy of my old 1.1.45 kernel and mounting /dev/fd0 as root.

Kernels that do or do not seem to work:
  1.1.40 - Yes.
  1.1.45 - Lockups most of the time I access the floppies.
  1.1.47 - Works great for a while, but still having random lockups.
  1.1.50 - Yes.
  1.1.52 - Lockups.
  1.1.54 - Lockups.

Does ANYONE have any ideas?  I'm stuck without a running Linux system at
the moment, and would really like to get things back in order ASAP.  Could
this possibly be a hardware related problem, or has the changing state of
the Linux floppy code caught something that just doesn't work with my

Thanks in advance,

   Sunset Data Systems

P.S.  Please don't reply with something like "Well, just upgrade to
1.1.55".  Yes, if I had a working system, I would.  But that's just not an
option right now.

2. r-tools only work when I'm logged-on as root

3. floppy problems, not a mounting problem

4. More BSP MLPPP problems

5. Two problems: 1) Segmentation faults 2) floppy disk problems

6. Module rewrite 19/20: module_bound removal

7. Floppy problems and mouse problems

8. nis problems

9. rescue floppy for LS-120/ATAPI floppy drive

10. searching scsi floppy driver to read dos floppies for sol 2.4

11. use floppy when boot linux by boot floppy

12. Boot floppy/root floppy to ramdisk, add more later?

13. Making custom boot floppies without a floppy.