Bug 498662
| Summary: | Thinkpad Wireless (Atheros) does not work: can't ping gateway | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hubert Figuiere <hub+rhbz> |
| Component: | kernel | Assignee: | Michal Schmidt <mschmidt> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | dcbw, itamar, kernel-maint, kmcmartin, linville, phalenor, tim |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-06-28 12:19:32 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
Hubert Figuiere
2009-05-01 18:39:11 UTC
lspic -vvnn 13:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212 802.11abg NIC [168c:1014] (rev 01) Subsystem: IBM ThinkPad 11a/b/g Wireless LAN Mini Express Adapter (AR5BXB6) [1014:058a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 19 Region 0: Memory at a7f00000 (64-bit, non-prefetchable) [size=64K] Capabilities: <access denied> Kernel driver in use: ath5k Kernel modules: ath5k *** This bug has been marked as a duplicate of bug 498502 *** (In reply to comment #2) > > *** This bug has been marked as a duplicate of 498502 *** I don't want to be picky but my problem is with an ath5k. Ooops... Is there an earlier kernel version where this was working? as far as I know, ath5k has never worked with it. This is my first Fedora install though. openSUSE 11.1 does not work either (that's what was just before I installed Fedora and the kernel was 2.6.27.7-9-pae). They made me try the compat-wireless on that kernel with no success. Before ath5k I was forced to use MadWifi (and that was on Ubuntu, and for a while this laptop was only on wire as it was secondary). OK -- I'm not sure what I can offer you right now. You may want to try a rawhide (i.e. fc12) kernel? http://koji.fedoraproject.org/koji/buildinfo?buildID=100421 This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Closing optimistically based on lack of response from comment 7... The problem is that changing kernel means changing X as I understand the X driver are now highly dependent on this (I could be wrong though). All in all, I risk, in order to test that, to totally foobar my ONLY system. I'd rather have partial functionality than no functionality. So no I have not tested. This is just closed following defeatism. If you guarrantee that I don't have to touch the i915 X driver, I'll try it. (maybe the resolution should be "INSUFFICIENT_HARDWARE"?) I installed it but bug 514386 prevent me from doing anything: NM does not seem to see it, etc. And the network does not seem to be up. I'll retry when bug 514386 is addressed. Seeing this on F11 on a Thinkpad t23 with a Cisco AIR-CB21AG-A-K9: Aug 7 19:19:42 magrathea kernel: ath5k phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43) Aug 7 19:19:42 magrathea kernel: ath5k phy0: RF5112B multiband radio found (0x36) Kernel: kernel-PAE-2.6.29.4-167.fc11.i686 With messages like these: Aug 7 19:20:14 magrathea kernel: ath5k phy0: noise floor calibration timeout (5520MHz) Aug 7 19:20:15 magrathea kernel: ath5k phy0: noise floor calibration timeout (5525MHz) Aug 7 19:20:15 magrathea kernel: ath5k phy0: noise floor calibration timeout (5530MHz) and the system becomes essentially unusable, using 100% CPU. Xorg display updates about once per second. The card seems to associate, but the system was so unusable that I didn't have a chance to even see if it was passing packets or not. Andy, that sounds like something completely different -- please open a new bug instead of hijacking this one...thanks! I need bug 533601 to be resolved first before being able to test this on F12 Seems to work with 2.6.31.5-127.fc12.i686.PAE bug 533601 is the proof that the kill switch is supported too (but not reported by NM) This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |