I can confirm 1 & 2, i have the same problems on my aspire one.
Also wrt: 1
The reported signal strength is much lower than running say madwifi on
the same hardware/os.
On 1 Jun 2009, at 21:43, Maxim Levitsky wrote:
Hi,
Just like ath9k thread, here is the list of bugs, I have seen on my
aspire one (with ath5k).
This is an AR2425 device.
#1) - Data transfer often stalls, sometimes for few seconds, sometimes
for much longer periods.
Transfer rate doesn't affect this, nether does network load (happens
much more often when it is high, but also happens, while it is
medium to
low).
I observed that, resetting the phy by triggering a scan, sometimes
help,
although running the scan inside a 2 second per iteration loop,
doesn't
prevent this stall to occur.
Also encryption doesn't play any role in this, I have seen same
scenario on open network configuration as well.
#2) - Driver sometimes doesn't wake the device up, after resume from
ram/disk. It happens not much often, but when it does, only a power
cycle (reboot or poweroff) helps to recover the device, and nether
s2ram
nor s2disk do anything.
#3) Ath5k often panics the kernel when it is in ibss/ap mode. This
reported to be fixed, but I use latest wireless-testing (less that 3
day
old, on average)
#4) Ath5k doesn't send beacons, when hostapd is run for the first
time.
#5) Can't send any frames between AP (ath5k) and a client.
But If I create a second monitor iface (in addition to the one hostapd
have created) I do see the frames from client on AP.
I especially hate bug #1, and would be happy to see bug #2 fixed.
I don't use AP mode much yet, but it would be nice if it were in
working
state.
Best regards,
Maxim Levitsky
--
To unsubscribe from this list: send the line "unsubscribe linux-
wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
