Bug 551720
Summary: | ath5k gives error "Invalid EEPROM checksum" after kernel update | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Juhani Jaakola <juhani.jaakola> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | altobone, anton, dougsland, gansalmon, itamar, jccyc1965, kernel-maint, linville, M8R-7fin56, natxo, pikachu.2014 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.6.32.4 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-11-04 06:20:55 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
Juhani Jaakola
2010-01-01 14:33:02 UTC
I have the same problem with my atheros AR2413 chip. Using the older kernel solves the issue. Same problem with Atheros Communications Inc. AR2413 802.11bg NIC (rev 01): Linux 2.6.32.2 #1 SMP Wed Dec 30 17:18:07 CET 2009 i686 GNU/Linux ath5k 0000:0a:03.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ath5k 0000:0a:03.0: registered as 'phy0' ath5k phy0: Invalid EEPROM checksum 0x94fb ath5k phy0: unable to init EEPROM ath5k 0000:0a:03.0: PCI INT A disabled ath5k: probe of 0000:0a:03.0 failed with error -5 The module seems to work in 2.6.28 with poor link quality: Linux 2.6.28-17-generic #58-Ubuntu SMP Tue Dec 1 18:57:07 UTC 2009 i686 GNU/Linux ath5k_pci 0000:0a:03.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ath5k_pci 0000:0a:03.0: registered as 'phy0' ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Currently I'm using 2.6.32.2 with handcompiled madwifi-drivers (ath_pci,...). The card works with them. I confirm this bug in kernel-PAE-2.6.31.9-174.fc12.i686: ath5k 0000:0a:03.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ath5k 0000:0a:03.0: registered as 'phy0' ath5k phy0: Invalid EEPROM checksum 0xe082 ath5k phy0: unable to init EEPROM ath5k 0000:0a:03.0: PCI INT A disabled ath5k: probe of 0000:0a:03.0 failed with error -5 In an older kernel (kernel-PAE-2.6.31.5-127.fc12.i686) it works: ath5k 0000:0a:03.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ath5k 0000:0a:03.0: registered as 'phy0' ath: EEPROM regdomain: 0x63 ath: EEPROM indicates we should expect a direct regpair map ath: Country alpha2 being used: 00 ath: Regpair used: 0x63 phy0: Selected rate control algorithm 'minstrel' ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) I added reference to Linux Kernel bug #14874. There is a patch for this bug, but I don't know whether it is only for kernel 2.6.32.2 and later. If the patch is only for 2.6.32.2 and later, please build one for Fedora 12. Or if we must stick with 2.6.31.*, please revert the buggy checksum patch. With the new upgraded kernel pushed to fedora 12 systems it does not work either (downgrading from 2.6.31.12-174.2.3.fc12.i686 to 2.6.31.6-166.fc12.i686) Please try a 2.6.32-based kernel... http://koji.fedoraproject.org/koji/buildinfo?buildID=152350 The card works with kernel-2.6.32.4-30.fc12.i686: ath5k 0000:04:05.0: PCI INT A -> Link[LNK2] -> GSI 20 (level, high) -> IRQ 20 ath5k 0000:04:05.0: registered as 'phy0' ath: EEPROM regdomain: 0x63 ath: EEPROM indicates we should expect a direct regpair map ath: Country alpha2 being used: 00 ath: Regpair used: 0x63 ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) However, I need kmod-nvidia - how can I get kmod-nvidia for kernel-2.6.32.4-30.fc12.i686? Will kernel 2.6.32 replace 2.6.31 soon in the main yum update stream? If I can't get kmod-nvidia for this kernel then I would prefer reverting the buggy checksum patch for kernel 2.6.31. I erased kmod-nvidia and installed akmod-nvidia, and now I have kernel 2.6.32.4 with working network and nVidia graphics! This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 |