Bug 606249 - Intel Wireless 4965 AG or AGN Fails in Fedora 13
Summary: Intel Wireless 4965 AG or AGN Fails in Fedora 13
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-21 08:46 UTC by Matt Healy
Modified: 2013-01-10 08:09 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-27 18:40:22 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Output of "/sbin/rfkill event" (194 bytes, text/plain)
2010-06-21 22:19 UTC, Matt Healy
no flags Details
/sbin/rfkill event with hp_wmi unloaded (296 bytes, text/plain)
2010-06-22 23:08 UTC, Matt Healy
no flags Details
/sbin/rfkill event with hp_wmi blacklisted and iwlagn loaded with debug (425 bytes, text/plain)
2010-06-23 22:53 UTC, Matt Healy
no flags Details

Description Matt Healy 2010-06-21 08:46:00 UTC
Description of problem:

I'm having issues with F13 and this wireless card. The card worked
perfectly in F12. In my case, NetworkManager reports that wireless is disabled
even though the wireless hardware switch is on. 

I have upgraded my kernel to: 

[root@kookaburra ~]# uname -rs

I have tried removing NetworkManager altogether and manually configuring the
wireless - I get an error about RF-kill:

[root@kookaburra ~]# /sbin/ifconfig wlan0 up
SIOCSIFFLAGS: Operation not possible due to RF-kill

If I do restart NetworkManager, /var/log/messages reports:

Jun 19 10:26:48 kookaburra NetworkManager[2321]: <info> found WiFi radio
killswitch rfkill2 (at
(driver <unknown>)
Jun 19 10:26:48 kookaburra NetworkManager[2321]: <info> found WiFi radio
killswitch rfkill0 (at /sys/devices/platform/hp-wmi/rfkill/rfkill0) (driver
Jun 19 10:26:48 kookaburra NetworkManager[2321]: <info> WiFi disabled by radio
killswitch; disabled by state file
Jun 19 10:26:48 kookaburra NetworkManager[2321]: <info> (wlan0): driver
supports SSID scans (scan_capa 0x01).
Jun 19 10:26:48 kookaburra NetworkManager[2321]: <info> (wlan0): new 802.11
WiFi device (driver: 'iwlagn' ifindex: 3)
Jun 19 10:26:48 kookaburra NetworkManager[2321]: <info> (wlan0): exported as
Jun 19 10:26:48 kookaburra NetworkManager[2321]: <info> (wlan0): now managed
Jun 19 10:26:48 kookaburra NetworkManager[2321]: <info> (wlan0): device state
change: 1 -> 2 (reason 2)
Jun 19 10:26:48 kookaburra NetworkManager[2321]: <info> (wlan0): bringing up
Jun 19 10:26:48 kookaburra NetworkManager[2321]: <info> (wlan0): deactivating
device (reason: 2).

If I switch the wireless switch on or off, this appears in /var/log/messages:

Jun 19 10:25:20 kookaburra kernel: HP WMI: Unknown response received

[root@kookaburra ~]# ls -la /sys/class/rfkill/rfkill*
lrwxrwxrwx 1 root root 0 Jun 19 10:23 /sys/class/rfkill/rfkill0 ->
lrwxrwxrwx 1 root root 0 Jun 19 10:23 /sys/class/rfkill/rfkill1 ->
lrwxrwxrwx 1 root root 0 Jun 19 10:23 /sys/class/rfkill/rfkill2 ->

[root@kookaburra ~]# cat /sys/class/rfkill/rfkill*/state

Version-Release number of selected component (if applicable):

[root@kookaburra ~]# uname -rs

[root@kookaburra ~]# /sbin/lspci | grep Wireless
07:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

How reproducible:

Wireless connection cannot be established at any time seemingly due to an rfkill problem.

Steps to Reproduce:
1. Upgrade Fedora 12 to Fedora 13 
2. Wireless connection does not start automatically. Restarting NetworkManager does not solve problem. Removing NetworkManager entirely and manually setting wireless connection does not work.

[root@kookaburra ~]# /sbin/ifconfig wlan0 up
SIOCSIFFLAGS: Operation not possible due to RF-kill

Actual results:

Intel 4965 Wireless card does not work in F13 

Expected results:

Intel 4965 Wireless card worked perfectly "out of the box" in earlier releases of Fedora (confirmed in 11 and 12)

Additional info:

- Laptop is a HP Pavilion dv2000 series.
- May be related to https://bugzilla.redhat.com/show_bug.cgi?id=595931
- May be related to

Comment 1 John W. Linville 2010-06-21 14:27:47 UTC
Please attach the output of running 'rfkill event' and then manipulating the rfkill switch on the laptop.  If there are both a physical switch (e.g. a slider along the front edge) and a "soft" switch (e.g. a key or a combination of keys on the keyboard) then please included both sets of manipulations and indicates which part of the output from rfkill corresponds to which manipulation.

Matthew and Reinette, any idea why we are seeing so many variations on this theme lately?

Comment 2 Matt Healy 2010-06-21 22:19:28 UTC
Created attachment 425765 [details]
Output of "/sbin/rfkill event"

Comment 3 Matt Healy 2010-06-21 22:24:01 UTC
Output of "rfkill event" attached.

Manipulating the physical wireless switch on the laptop produces no output at all in "rfkill event". 

There is no software switch for wireless on this hardware.

Comment 4 reinette chatre 2010-06-22 22:06:40 UTC
Can you repeat the test with hp-wmi unloaded?

Comment 5 Matt Healy 2010-06-22 23:08:31 UTC
Created attachment 426106 [details]
/sbin/rfkill event with hp_wmi unloaded

Comment 6 Matt Healy 2010-06-22 23:10:06 UTC
I have removed hp_wmi and again performed /sbin/rfkill event (output attached).

The output is different to earlier, but toggling the hardware switch produces no further output.

Comment 7 reinette chatre 2010-06-23 17:17:44 UTC
Could you please try the following:

- set up your system not to load hp_wmi at all ... you can do this by blacklisting it in your modprobe files
- ensure driver is compiled with debug support (CONFIG_IWLWIFI_DEBUG) and load driver module with "modprobe iwlagn debug=0x63fff"

Please send debugging output when you repeat the above tests.

Comment 8 Matt Healy 2010-06-23 22:53:55 UTC
Created attachment 426409 [details]
/sbin/rfkill event with hp_wmi blacklisted and iwlagn loaded with debug

Comment 9 Matt Healy 2010-06-23 22:55:51 UTC

Following the above steps has got the wireless connection working perfectly.

Thank you for your help with this and hope this allows you to fix the bug.
Let me know if you need any further testing done.


Comment 10 reinette chatre 2010-06-23 23:26:16 UTC
The log you provide does not contain any driver debugging ... but I do not believe just enabling driver debugging will just make things work so I assume it was the action of blacklisting hp_wmi.

John ... I don't know what to say ... here it the third case now where getting the platform driver out of the way makes rfkill work. Any chance that one of your platform folks can take a look at this?

Comment 11 John W. Linville 2010-06-24 13:30:22 UTC
Reinette, I'm inclined to agree that it seems like something has 'gone pear-shaped' (is that the right expression?) with platform drivers and rfkill.  FWIW, there doesn't seem to be much activity in net/rfkill/.

As for platform folks, Matthew is on the Cc: list already.  Hopefully he has some insight?

Comment 12 Ricardo 2010-08-03 18:22:06 UTC
Reinette, John,

I have an HP-dv2625 laptop. Under F10 I had no problem whatsoever with the Intel Pro 4965. The card was recognized and activated without any problems or human intervention at boot-time.

I installed F13 on an external USB drive (leaving F10 on the internal drive) and came across the problem with the 4965.

So, I rebooted with F10 (from the internal drive) and to my surprise the wireless card was NOT activated and the hardware switch led remained orange. Rebooted again with F10, and again no wireless and an orange led. So I turned off the switch and then on again and voilá the led turned blue and the wireless was activated. I then disconnected the USB external drive, rebooted with F10 and now to activate the wireless card I had to cycle off-on the hardware switch. I did NOT have to do this switch cycling in F10 BEFORE installing F13. Could it be that F13 messed up something WITHIN the card firmware itself?

So, I started googling and came across this bug report. I booted the laptop with F13 (from the external drive), followed the steps (i.e. blacklisting the hp-wmi module and rebooting) and the switch led remained orange. So, I cycled the switch and the led immediately turned blue and got a working wireless card.

In summary:

1. Before installing F13, in F10 I did NOT have to cycle the wireless hardware switch to activate the wireless card. Now, after installing F13 on the external drive, I have to cycle the switch even when I boot with F10 from the internal drive.

2. Blacklisting the hp-wmi module did in fact solve the problem in F13 (albeit I have to cycle the wireless hardware switch to get the wireless card working).

Just wanted to share my experience with you in hope that it might help you debug and fix the problem.

Best Regards,


P.S. Booting with the wireless hardware switch in the ON position:

Before cycling the switch, "rfkill list" shows:

0: phy0: Wireless LAN
        Soft blocked no
        Hard blocked yes

After cycling the switch it shows:

0: phy0: Wireless LAN
        Soft blocked no
        Hard blocked no
1: hci0: Bluetooth
        Soft blocked no
        Hard blocked no

Notice how cycling the switch ALSO activates bluetooth (which was not activated before cycling the switch)

With respect to "rfkill event", just issuing the command (without moving the switch) results in:

1280859054.384801: idx 0 type 1 op 0 soft 0 hard 1

Moving the switch to the OFF position does NOT result in any output.

Moving back the switch to the ON position results in:

1280859079.096430: idx 0 type 1 op 2 soft 0 hard 0
1280859079.964645: idx 1 type 2 op 0 soft 0 hard 0
1280859079.967222: idx 1 type 2 op 2 soft 0 hard 0

Comment 13 Matt Healy 2010-08-05 08:25:25 UTC
I'd like to mention that I'm experiencing issues similar to Ricardo - recently I had to boot my laptop back in to Windows Vista and the wireless failed to work at all (it worked prior to my upgrade from Fedora 12 to Fedora 13). I could not find any way in Vista to activate the wireless - it was as if the laptop did not have a wireless card. Toggling the hardware switch had no effect on the WiFi (although Vista was able to activate and deactivate Bluetooth - just no WiFi).

I have no idea how to retrieve debugging information about the card in Windows Vista and whether it would be any help to you.


Comment 14 Robert Story 2010-08-26 23:24:12 UTC
Add me to the list too... wireless was working out of the box on F11, but not after I installed f13. The only difference is that my laptop is not an hp, so hp-wmi wasn't loaded and I didn't have to blacklist it. I did have to cycle the keyboard radio switch, though.

Comment 15 Bug Zapper 2011-06-01 16:02:43 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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: 

Comment 16 Bug Zapper 2011-06-27 18:40:22 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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