FTP, "EMI?" message, and SCP

Hello,

  This is my first message to the members of this mailing list,
so the very first thing I want to do is to thank Jorg Albert
for making his wonderful Linux Atmel drivers freely available

  You have made it possible for me to experiment with wireless
networking for the first time, and this has really opened my eyes to
many new ideas. In fact, nothing else has ever had such a big impact on
my thinking about what it is possible to do with computers since I
learned about Borland/PDC Turbo Prolog (in 1985!).

  Now, to the business at hand.

  My current network consists of 2 PC's connected by Xterasys x2122b USB
wireless adapters.

  One of these PCs (herein, the "host") is connected to the internet via
dialup PPP.

   The host is running RedHat Fedora RC2 on the other PC (herein, the
"client) I have
Gentoo, Fedora RC2, WIndows2000, and Win98se,

  I have for several weeks been using the Berlios at76c503a Linux
drivers to do such things as update my client systems and transfer small
files p2p by various means without any problems.

  Yesterday it so happens that I wanted to transfer a 16MB Redhat RPM
from my host Linux machine to my client Linux machine.

  My first thought was to use FTP in passive mode on the client to log
onto the host FTP server
and "download" the file, but every time I tried this, I would see on the
host console a message saying

      hub 1-0:1.0: port 1 disabled by hub (EMI?), re-enabling ...

at which point PING on the client says the host is unreachable and PING
in the host just sits there and says nothing.

  It also happens that the client I am speaking about is a "new"
computer that I am in the process of putting together from old parts
using a new ATX mobo in a new chassis, so when I saw the "EMI?" in the
message I naturally thought that maybe the new mobo
and case are causing the problem.

   Maybe they are, I don't know, but my point is that after several of
these failed attempts,  I decided to check what would happen if I tried
to transfer the file from the Linux host  to the same client running
WinSCP on Win2000 -- et voila, 16MB transferred in a matter of seconds
  without any problems.

  So, today I am wondering, what explains this difference? I am using
exactly the same hardware *and* software on the host side in both cases,
and I am using the exactly the same hardware on the client side in both
cases, so it seems to me that the explanation must lie in the difference
between the WinSCP/WIn2000 software and FTP/Linux software on
the client side, but at this stage I am too naive in these matters to
take that idea
any farther, so I would very much appreciate hearing any ideas that
others might have to offer.

   I am compiling the Berlios at76c503 package directly from your CVS
repository.

   Here are some lines from my bootup dmesg today:

/opt/VAR/at76c503-cvs/at76c503a/at76c503.c: $Id: at76c503.c,v 1.72 2004/1
0/19 20:45:25 jal2 Exp $ compiled Nov 13 2004 17:34:00
/opt/VAR/at76c503-cvs/at76c503a/at76c503.c: firmware version 1.101.0 #86
(fcs_len 4)
/opt/VAR/at76c503-cvs/at76c503a/at76c503.c: device's MAC 00:0d:2f:01:4d:0
2, regulatory domain FCC (U.S) (id 16)
/opt/VAR/at76c503-cvs/at76c503a/at76c503.c: registered wlan0

  I hope this information is sufficient to identify the software I am using.

  Thank you.

  Bill Hogan