Bug 436876
Summary: | Activation (ath0/wireless): association took too long, asking for new key | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Siim Käba <siim.kaba> |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | cesar.alvernaz, dcbw, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-20 14:56:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Siim Käba
2008-03-10 20:58:41 UTC
Did you try the shiny new ath5k driver? It does not support this chipset (AR5418). Livna has also old version of this driver. Open question as to if this is Madwifi's issue or Network manager. I've seen this problem with madwifi where the mode is setup to either 802.11A or Auto. I set the mode to B/G at startup and it eliminates this issue. /sbin/iwpriv ath0 setmode 3 Also make sure that ath5k is blacklisted in modprobe. Maybe the livna rpms do this already? ath5k is blacklisted. "/sbin/iwpriv ath0 mode 3" did the job. Thanks. Not too much that can be done with madwifi, it's not upstream and not included in Fedora. ath9k in 2.6.27 supports the 5418 and uses the standard mac80211 stack. |