dmesg :

PCI: Setting latency timer of device 0000:03:00.0 to 64
MadWifi: ath_attach: Switching rfkill capability off.
wifi0: Atheros AR5418 chip found (MAC 12.10, PHY SChip 8.1, Radio 13.0)
ath_pci: wifi0: Atheros 5418: mem=0xefef0000, irq=169

iwconfig
[root <at> localhost network-scripts]# iwconfig 
lo        no wireless extensions.

eth0      no wireless extensions.

sit0      no wireless extensions.

wifi0     no wireless extensions.

wlan0     IEEE 802.11g  ESSID:"xxxx"  Nickname:"localhost.localdomain"
          Mode:Managed  Frequency:2.462 GHz  Access Point: Not-Associated   
          Bit Rate:1 Mb/s   Tx-Power:14 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:A7A7-A7A7-A7   Security mode:open
          Power Management:off
          Link Quality=76/70  Signal level=-20 dBm  Noise level=-96 dBm
          Rx invalid nwid:112  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

any idea ?

---
Reza ISSANY
Ingénieur Systèmes

ZA Les Playes - Jean Monnet Sud
Avenue de Lisbonne
83500 La Seyne sur Mer
Mail : issanyr <at> olympecti.fr
Tél : + 33 (0)4 13 41 63 24
Fax : + 33 (0)4 13 41 63 25

-----Message d'origine-----
De : Pavel Roskin [mailto:proski <at> gnu.org] 
Envoyé : jeudi 4 septembre 2008 19:20
À : reza
Cc : madwifi-users <at> lists.sourceforge.net
Objet : RE: [Madwifi-users] connection/deconnection with AR5418

On Thu, 2008-09-04 at 09:37 +0200, reza wrote:
> When I load the madwifi driver, I start a ping to the AP :
...
> 364 packets transmitted, 60 received, +210 errors, 83% packet loss, time 409882ms
> rtt min/avg/max/mdev = 2.907/4034.577/44098.390/7048.882 ms, pipe 11
... 	
> #Turbo mode
> WIRELESS_CARD_MODE=3
> WIRELESS_TURBO_MODE=1
> WIRELESS_RATE=auto

I don't think it has any effect.
	
> #Special commands sent directly to wifi tool
> #IWCONFIG=
> IWPRIV="bgscan 0"

Why are you disabling background scanning?  I don't think if would
affect latency too much, but it could prevent reconnect.

The configuration files don't matter that much.  What matters is the
actual state of the interface.  It would be more useful if you post the
output from iwconfig and the parts of the kernel log after the driver
was loaded (use dmesg to display it).

> ps : when I try to compile the 2.6.27 kernel on redhat ws 4 (to use the ath9k driver), the boot stopped at
storage initialisation.
> All the ata and sata modules are present. any idea ?

That should be asked elsewhere.

-- 
Regards,
Pavel Roskin

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/