Bug 676933 - rfkill phy0: WIreless LAN is stuck hard blocked
Summary: rfkill phy0: WIreless LAN is stuck hard blocked
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-11 21:41 UTC by Orion Poplawski
Modified: 2013-11-10 09:59 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-29 18:57:14 UTC
Type: ---


Attachments (Terms of Use)


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

Description Orion Poplawski 2011-02-11 21:41:33 UTC
Description of problem:

I cannot get phy0: Wireless lan rfkill switch to stop being in the hard blocked state.

I can toggle the hp-wifi/hp-bluetooth kill switches with the hard ware toggle:

[root@adelie ~]# rfkill list
0: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: yes
1: hp-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: yes
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: yes
[root@adelie ~]# rfkill list
0: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: hp-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: yes

Version-Release number of selected component (if applicable):
2.6.35.10-74.fc14.x86_64

Also tried kernel-2.6.35.11-83.fc14.x86_64 and kernel-2.6.38-0.rc4.git0.1.fc15.x86_64 but they were no different.

hardware:
03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
HP EliteBook 8730w Bios version F.11

I also tried disabling the hp_wmi but no help.

Comment 1 Orion Poplawski 2011-08-29 18:57:14 UTC
User error.  The BIOS was configured to disable wifi when the wired ethernet was active.


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