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=/