This bug does not exist in 2.6.17 (Edgy kernel) since it's a madwifi-old issue and Edgy uses madwifi-ng.
This bug does not exist in 2.6.17 (Edgy kernel) since it's a madwifi-old issue and Edgy uses madwifi-ng.