Bug 1199630 - ath9k Mac Chip Rev 0xfffc0.f is not supported by this driver
Summary: ath9k Mac Chip Rev 0xfffc0.f is not supported by this driver
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: fedora-kernel-wireless-ath
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1201661 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-06 19:46 UTC by František Zatloukal
Modified: 2015-05-14 07:18 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-09 12:45:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg from Fedora 21 (65.25 KB, text/plain)
2015-03-06 20:39 UTC, František Zatloukal
no flags Details

Description František Zatloukal 2015-03-06 19:46:03 UTC
Description of problem:
On Fedora 22 and Fedora 23 wifi doesn´t work. The error message printed to log is:

[  576.127314] ath: phy0: WB335 2-ANT card detected
[  576.127321] ath: phy0: Set BT/WLAN RX diversity capability
[  576.127342] ath: phy0: Mac Chip Rev 0xfffc0.f is not supported by this driver
[  576.127346] ath: phy0: Unable to initialize hardware; initialization status: -95
[  576.127352] ath9k 0000:02:00.0: Failed to initialize device
[  576.127385] ath9k: probe of 0000:02:00.0 failed with error -95

Version-Release number of selected component (if applicable):
Tested was kernel-4.0.0-0.rc2.git1.1.fc23 and kernel-4.0.0-0.rc2.git0.1.fc22 . 

How reproducible:
Always

Steps to Reproduce:
1.Boot Fedora 22 Alpha RC3 or Fedora 23 Rawhide 

Actual results:
Wifi doesn´t work

Expected results:
Wifi should be detected properly and work.

Additional info:
The affected device is Acer ES1-311-C9B2 with latest bios.

Comment 1 Josh Boyer 2015-03-06 20:06:46 UTC
Did this work on previous kernels?

Comment 2 František Zatloukal 2015-03-06 20:09:38 UTC
It works perfectly on Fedora 21 default kernel. Should I test different kernels?

Comment 3 František Zatloukal 2015-03-06 20:11:28 UTC
By Fedora 21 kernel, I mean the version included on Live ISO. Since this is new laptop and I haven´t installed Fedora yet.

Comment 4 Josh Boyer 2015-03-06 20:16:33 UTC
Can you provide the output of dmesg from the F21 kernel?

Comment 5 František Zatloukal 2015-03-06 20:39:21 UTC
Created attachment 998999 [details]
dmesg from Fedora 21

dmesg from Fedora 21.

Comment 6 Josh Boyer 2015-03-06 21:07:26 UTC
(In reply to František Zatloukal from comment #5)
> Created attachment 998999 [details]
> dmesg from Fedora 21
> 
> dmesg from Fedora 21.

Hm...

   20.738223] ath: phy0: WB335 2-ANT card detected
[   20.738228] ath: phy0: Set BT/WLAN RX diversity capability
[   20.746932] ath: phy0: Enable LNA combining
[   20.748196] ath: phy0: ASPM enabled: 0x43
[   20.748200] ath: EEPROM regdomain: 0x65
[   20.748202] ath: EEPROM indicates we should expect a direct regpair map
[   20.748206] ath: Country alpha2 being used: 00
[   20.748207] ath: Regpair used: 0x65
[   20.823847] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   20.824514] ieee80211 phy0: Atheros AR9565 Rev:1 mem=0xffffc90016500000, irq=18
[   20.855360] ath9k 0000:02:00.0 wls2: renamed from wlan0

So AR9565 Rev 1 should have a Mac Chip Rev of 0x2c0.1.  Which means somehow that is getting misread by 4.x?

Could you try the 3.19 kernel:

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

and see if that works?  There are some commits in 4.0-rcX that broke ACPI/PCI resource parsing on various machines.  I'd like to eliminate those before we dig much further.  The fixes for them are in the 4.0.0-0.rc2.git2.1 build that is running right now but it isn't complete yet:

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

If 3.19 works, then testing the above when it completes is the next step.  If 3.19 doesn't work we'll have to start looking at changes between 3.17 and 3.19.

Comment 7 František Zatloukal 2015-03-06 23:34:23 UTC
3.19 works. Will wait for 618697 to build and then report back.

Comment 8 František Zatloukal 2015-03-07 03:17:40 UTC
So, kernel 4.0.0-0.rc2.git2.1.fc23 works without any issues.

Comment 9 Josh Boyer 2015-03-09 12:45:04 UTC
OK, thanks for confirming both.  It seems the PCI resource issues were at fault here and have no been fixed.

Comment 10 Josh Boyer 2015-03-13 11:49:55 UTC
*** Bug 1201661 has been marked as a duplicate of this bug. ***

Comment 11 Bertrand GAMBIER 2015-05-10 18:13:26 UTC
Hi,

 I had the same issue after an update of my Fedora 21. It seems that the problem start with kernel 3.20.0-0

Exactly the same messages in dmesg.

Regards,

Comment 12 František Zatloukal 2015-05-10 18:48:51 UTC
Hi,
how did you installed kernel 3.20.0 (which is in fact non-existent - it became 4.0 very early). Anyway this issue was fixed later in 4.0 development cycle and shouldn't be present in stable kernel.

Comment 13 Bertrand GAMBIER 2015-05-13 18:49:16 UTC
Hi,
This was a mistake I use a specific kernel for a laptop (EFI 32 bits) provided with a specific repo. This kernel had a strange origin I remove it.
Sorry for this stupid post

Regards


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