Re: Re: problem with ATMEL RFMD503A driver

On Wed, 02 Jul 2003 22:12:44 +0200, Joerg Albert wrote:
> Hi Arnaud,

Hi,
 
> With a "tcpdump -i eth1" in the background the
> "arping -I eth1 192.168.0.3" must show at least the outgoing packets,
> otherwise your local network setup is broken.
> Could you please issue the following commands around the
> failed "arping ..." (you've posted them before, but maybe some prog has
> changed your network settings ?):
> 
> ifconfig eth1
> arping -I eth1 192.168.0.3
> ifconfig eth1 /* more Tx bytes/packets then above? */
> route -n

We have big loss in wire even if the AP and the usb adaptator aren't far.
The vendor sell us bad wire (rg58 instead of rg58u). We look for this...
To have an idea, when you do iwconfig, what's the quality of signal ?

I have done your command but i have nothing (certainly wire)... We will
buy some wire and test the wireless network again...
 
> If this doesn't help,
> could you try the Berlios driver (from http://at76c503a.berlios.de),
> version 0.10, instead (I know that one better) and if you got the
> same problem (iwconfig shows the MAC address of your AP but no ping
> answer etc.) set the module parameter debug=0x100013 for at76c503.o
> (e.g. in /etc/modules.conf on with manual "modprobe"). This
> will add debug output for each data packet leaving thru the WLAN driver
> to the default debug set.

I have compiled this module withou any problem but it doesn't find the AP,
contrary to the atmel driver...
 
> /Jörg

++ Arnaud