Floppy problems with 2.1.95?

Floppy problems with 2.1.95?

Post by bill davids » Wed, 22 Apr 1998 04:00:00



I was making backup copies of old software for archival purposes,
making physical copies of the floppies used to install old Win3.1
software which runs some devices I still have to use.

I make a copy by
  dd if=/dev/fd0 of=disk1 bs=18k
where 18k is the cylinder size.

I got a solid system lockup every time I tried this, on a system
otherwise stable on 2.0.33 and 2.1.95. This is an SMP system,
haven't tried a uni yet.
--

    CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

 
 
 

Floppy problems with 2.1.95?

Post by bill davids » Mon, 27 Apr 1998 04:00:00



| I was making backup copies of old software for archival purposes,
| making physical copies of the floppies used to install old Win3.1
| software which runs some devices I still have to use.
|
| I make a copy by
|   dd if=/dev/fd0 of=disk1 bs=18k
| where 18k is the cylinder size.
|
| I got a solid system lockup every time I tried this, on a system
| otherwise stable on 2.0.33 and 2.1.95. This is an SMP system,
| haven't tried a uni yet.

Okay, I tried it on a uni and it still locks up, would someone else like
to duplicate this action and see if you have a problem, too?
--

    CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

 
 
 

Floppy problems with 2.1.95?

Post by Bill Curri » Tue, 28 Apr 1998 04:00:00



> | I make a copy by
> |   dd if=/dev/fd0 of=disk1 bs=18k
> | where 18k is the cylinder size.
> |
> | I got a solid system lockup every time I tried this, on a system
> | otherwise stable on 2.0.33 and 2.1.95. This is an SMP system,
> | haven't tried a uni yet.

> Okay, I tried it on a uni and it still locks up, would someone else like
> to duplicate this action and see if you have a problem, too?

Unless Linux supports reading both sides of the floppy in one call, the
block size should be 9k, not 18k (18 sectors * 512 bytes).

Bill
--
Leave others their otherness.

 
 
 

Floppy problems with 2.1.95?

Post by David Huggi » Wed, 29 Apr 1998 04:00:00



> | I got a solid system lockup every time I tried this, on a system
> | otherwise stable on 2.0.33 and 2.1.95. This is an SMP system,
> | haven't tried a uni yet.

> Okay, I tried it on a uni and it still locks up, would someone else like
> to duplicate this action and see if you have a problem, too?

I've been having the same problems on both my machines (actually, I
posted something about this a while back).  I get solid hangs on
2.1.94-97 when writing floppies with dd, regardless of what command-line
options I use.  2.1.91 and earlier don't do it, nor does 2.0.33.

Both are PCI, uniprocessor (P90 and 486DX33), with Symbios 53c8xx SCSI
controllers, and the floppy driver compiled as a module.

I saw something on the linux-kernel list about a patch for 2.1.98 that
seems to alleviate lockups on at least one person's dual Pentium II box.
Check out the list archives on http://www.linuxhq.com  for more info.
(I haven't tried this myself yet)

--
David Huggins-Daines

http://aix2.uottawa.ca/~s1204672

 
 
 

1. ifconfig reports bad stats with 2.1.95

On all my 2.1.95 systems I see that ifconfig reports incorrect
values for packets counts.

Example:

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Bcast:0.0.0.0  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:652 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:107620 dropped:652 overruns:0 carrier:0 coll:0
eth0      Link encap:Ethernet  HWaddr 00:00:C0:02:5D:F8  
          inet addr:192.168.4.201  Bcast:192.168.4.207  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1080 errors:0 dropped:0 overruns:0 frame:0
          TX packets:238 errors:128354 dropped:848 overruns:0 carrier:0 coll:0
          Interrupt:10 Base address:0x250 Memory:d0000-d4000

I get this on all cards, ethernet and TokenRing, on loopback, etc.
It would appear that the TX info is totally unrelated to anything
the system is doing, other than the numbers getting larger with
time.

I've tried net-tools-1.421 and 1.432, no change. Is there a later
version on another site, a patch, something? I'm using 2.1.95 in
several non-critical production machines for testing, this happens
on all of them.

This system is using the gcc-2.7.2.3 compiler, I get the same thing
with pgcc-1.0.2 on another system.
--

    CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

2. XSendEvent() and XView toolkit

3. Is TokenRing broken in 2.1.95

4. Testing Y2K?

5. crash with 2.1.95 SMP

6. External ISDN Modem with redhat 6.0 linux - help needed

7. System hangs 2.1.95/96 and Netscape

8. setgroups: Not owner ???

9. Bug report: compile error in 2.1.95

10. Linux 2.1.95 et AWE64

11. route wierdness with 2.1.95

12. TokenRing and 2.1.95

13. /dev/ttyS2 (/dev/cua2) reports "device or resource busy" on kernel 2.1.95