Bug 551720 - ath5k gives error "Invalid EEPROM checksum" after kernel update
Summary: ath5k gives error "Invalid EEPROM checksum" after kernel update
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-01 14:33 UTC by Juhani Jaakola
Modified: 2010-11-04 06:20 UTC (History)
11 users (show)

Fixed In Version: 2.6.32.4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-04 06:20:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 14874 0 None None None Never

Description Juhani Jaakola 2010-01-01 14:33:02 UTC
Description of problem:
After update to kernel 2.6.31.9-174.fc12.i686 my WLAN card does not work any more. It works if I boot with kernel 2.6.31.6-145.fc12.i686

Version-Release number of selected component (if applicable):
kernel-2.6.31.9-174.fc12.i686

How reproducible:
Always

Steps to Reproduce:
1. Boot with kernel 2.6.31.9-174.fc12.i686
  
Actual results:
WLAN does not work. dmesg displays:

ath5k 0000:04:05.0: PCI INT A -> Link[LNK2] -> GSI 20 (level, high) -> IRQ 20
ath5k 0000:04:05.0: registered as 'phy0'
ath5k phy0: Invalid EEPROM checksum 0x8fdb
ath5k phy0: unable to init EEPROM
ath5k 0000:04:05.0: PCI INT A disabled
ath5k: probe of 0000:04:05.0 failed with error -5

Expected results:
WLAN should work. When I boot with kernel 2.6.31.6-145.fc12.i686 dmesg shows:

ath5k 0000:04:05.0: PCI INT A -> Link[LNK2] -> GSI 19 (level, high) -> IRQ 19
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)

Additional info:
lspci -v displays (with kernel 2.6.31.6-145.fc12.i686):

04:05.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)
	Subsystem: AMBIT Microsystem Corp. Device 0418
	Flags: bus master, medium devsel, latency 168, IRQ 19
	Memory at c3000000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [44] Power Management version 2
	Kernel driver in use: ath5k
	Kernel modules: ath5k

Comment 1 Natxo Asenjo 2010-01-04 22:03:37 UTC
I have the same problem with my atheros AR2413 chip. Using the older kernel solves the issue.

Comment 2 Anonymous account 2010-01-08 13:41:31 UTC
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.

Comment 3 Juan Castro 2010-01-14 06:56:35 UTC
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)

Comment 4 Juhani Jaakola 2010-01-18 09:46:47 UTC
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.

Comment 5 Natxo Asenjo 2010-01-22 07:46:41 UTC
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)

Comment 6 John W. Linville 2010-01-22 15:59:47 UTC
Please try a 2.6.32-based kernel...

http://koji.fedoraproject.org/koji/buildinfo?buildID=152350

Comment 7 Juhani Jaakola 2010-01-22 18:10:41 UTC
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.

Comment 8 Juhani Jaakola 2010-01-22 19:05:53 UTC
I erased kmod-nvidia and installed akmod-nvidia, and now I have kernel 2.6.32.4 with working network and nVidia graphics!

Comment 9 Bug Zapper 2010-11-04 02:06:07 UTC
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


Note You need to log in before you can comment on or make changes to this bug.