I'm very pleased to see ath5k support for my EeePC (AR2425) in
2.6.27-rc2. That said, there seems to be a regression with suspend to
ram. This is relative to the version I tested from Nicks
compat-wireless-2008-07-03-ath5k snapshot.
The driver doesn't blow up; it just doesn't behave as expected. This
might be a generic issue; it might even be a bad interaction with
eeepc-laptop being moved to rfkill support. But I'm asking you guys
about this first :-).
Expected behaviour (as seen previously):
After resume, a scan is performed automatically. Unpriviledged users
can run "iwlist ath0 scan" to see the results. NetworkManager (0.6.6)
presumably picks up the scan results, and reconnects without user
intervention.
Actual behaviour:
After resume, no scan is performed. Unpriviledged users running "iwlist
ath0 scan" are told "no results". It is necessary to run "iwlist ath0
scan" *as root*; only then will NetworkManager reconnect.
Thanks
Alan
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
