Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#27452 - [netcfg] always reports "radio is disabled on wlan0" with RFKILL=hard on Thinkpad X201
Attached to Project:
Arch Linux
Opened by janis (Stalafin) - Sunday, 04 December 2011, 21:54 GMT
Last edited by Jouke Witteveen (jouke) - Monday, 15 October 2012, 08:48 GMT
Opened by janis (Stalafin) - Sunday, 04 December 2011, 21:54 GMT
Last edited by Jouke Witteveen (jouke) - Monday, 15 October 2012, 08:48 GMT
|
DetailsDescription:
Using a Thinkpad X201, I have configured the RFKILL support according to netcfg's wiki entry in /etc/network.d/interfaces/wlan0 to read: RFKILL=hard RFKILL_NAME='phy0' However, when I try to establish a connection with these settings, netcfg _always_ returns: > radio is disabled on wlan0 My switch is definitly not disabling the connection. rfkill reports: $ rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: no Hard blocked: no This would red yes in all cases if the switch was enabled (checked and confirmed on my machine). Additional info: netcfg 2.6.8-1 Network I am trying to connect to has _no_ encryption! All necessary info given above; if needed, I can provide files (if you tell me which). Steps to reproduce: Configure RFKILL support for the interface, try to connect to a network > fails. |
This task depends upon
Closed by Jouke Witteveen (jouke)
Monday, 15 October 2012, 08:48 GMT
Reason for closing: No response
Additional comments about closing: 8de50 updates the rfkill implementation.
Monday, 15 October 2012, 08:48 GMT
Reason for closing: No response
Additional comments about closing: 8de50 updates the rfkill implementation.
Comment by Dmitry Korzhevin (dkorzhevin) -
Tuesday, 29 May 2012, 10:39 GMT
What driver are you use?