Re: Re: Re: problem with ATMEL RFMD503A driver

On Thu, 03 Jul 2003 13:01:36 +0200, joerg wrote:

> Sorry, I don't understand. We are talking about _wireless_ only, your
> desktop (with Atmel WLAN adapter) and an AP and no traffic between both.
> The commands I mentioned should be executed on the desktop after the
> WLAN driver had joined the AP (i.e. iwconfig shows the AP's MAC
> address). eth1 is the wireless interface. IMHO any wire quality has no
> influence.

Hi,

Excuse me for this later answer but i have no time this days. People who
lend me this card have modified the belkin usb adaptor to put an better
antenna than the original. But they didn't do that correctly so i modify
this wire between antenna and card and now i ping without any problem with
the two drivers.

> The driver lists all APs found during scan in the syslog. Be aware that
> it only runs
> after you have opened the netdevice, e.g. by "ifconfig wlan0 <some ip
> addr>".
> If the problem remains, please post the syslog.

Now, the two drivers lists all APs found during scan and i can ping after
i do ifconfig and configured properly the card. Before, i have following
that you say (opened the netdevice after the driver found the APs) 
so the problem comes from wire between antenna and Atmel WLAN
adaptor.

I would like to thanks you a lot for your help... I would also
to know what's the major difference between the atmel and the berlios
driver ? Why do you say that the berlios driver are better ? ;)
 
> /Jörg

Arnaud