Bug 483735
Summary: | iwl3945 driver stopped by RF kill switch on boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew John Hughes <ahughes> |
Component: | kernel | Assignee: | John W. Linville <linville> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | andreas.utterberg, davidz, kernel-maint, quintela |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-04 16:42:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrew John Hughes
2009-02-03 12:58:28 UTC
I have also after update no wireless, have worked perfectly before. This must have very high priority!! Wireless is broken on all my Fedora 10 systems now. Breakout from messages: Mar 3 18:58:40 localhost kernel: firmware: requesting iwlwifi-3945-1.ucode Mar 3 18:58:40 localhost kernel: iwl3945: Radio disabled by HW RF Kill switch From messages: Mar 3 18:57:10 localhost kernel: fuse init (API version 7.9) Mar 3 18:57:30 localhost kernel: nepomukservices[3130]: segfault at 4 ip 047168a2 sp bfafdc40 error 4 in libQtCore.so.4.4.3[46ce000+21e000] Mar 3 18:58:30 localhost NetworkManager: <info> (wlan0): now unmanaged Mar 3 18:58:30 localhost NetworkManager: <info> (wlan0): device state change: 2 -> 1 Mar 3 18:58:36 localhost kernel: iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26kds Mar 3 18:58:36 localhost kernel: iwl3945: Copyright(c) 2003-2008 Intel Corporation Mar 3 18:58:36 localhost kernel: iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Mar 3 18:58:36 localhost kernel: iwl3945: Detected Intel Wireless WiFi Link 3945ABG Mar 3 18:58:36 localhost kernel: iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels Mar 3 18:58:36 localhost NetworkManager: <info> wlan0: driver is 'iwl3945'. Mar 3 18:58:36 localhost NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). Mar 3 18:58:36 localhost NetworkManager: <info> Found new 802.11 WiFi device 'wlan0'. Mar 3 18:58:36 localhost NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_1c_bf_51_35_24 Mar 3 18:58:40 localhost NetworkManager: <info> (wlan0): device state change: 1 -> 2 Mar 3 18:58:40 localhost NetworkManager: <info> (wlan0): bringing up device. Mar 3 18:58:40 localhost kernel: iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Mar 3 18:58:40 localhost kernel: firmware: requesting iwlwifi-3945-1.ucode Mar 3 18:58:40 localhost kernel: iwl3945: Radio disabled by HW RF Kill switch Mar 3 18:58:40 localhost NetworkManager: <WARN> nm_device_hw_bring_up(): (wlan0): device not up after timeout! Mar 3 18:58:40 localhost NetworkManager: <info> (wlan0): deactivating device (reason: 2). What kernel version worked? What was the first version to fail? Are you absolutely sure that the RF kill switch is disabled (i.e. set to enable the radio)? Note, I'm not talking about Fn-F5 -- on my t61 and this t400 there are mechanical slide switches on the front edge of the laptop. Your machine may have something similar. I dont know what last kernel was that worked, i updated my computers and after the update wireless was broken. [root@thundera packages]# rpm -qa | grep kernel kerneloops-0.12-1.fc10.i386 kernel-2.6.27.19-170.2.35.fc10.i686 kernel-2.6.27.12-170.2.5.fc10.i686 kernel-2.6.27.15-170.2.24.fc10.i686 kernel-firmware-2.6.27.19-170.2.35.fc10.noarch [root@thundera packages]# uname -r 2.6.27.19-170.2.35.fc10.i686 I have no physical kill switch, im running F10 on two Dell Latitude D830 laptops, so the kill switch message makes no sense. Let me know if i can provide more input for fast resolving since this issue is most troubleing. I see...and what happens when you manipulate the soft rfkill switch that must be somewhere on that box? Also, please ensure that there is no BIOS setting disabling the wireless lan device. Im sorry, i must be really tired....it works fine for me. I had manually disabled the wifi card and was stupid enough to didnt double check this before reporting! Im sorry again! Hey, it happens... :-) Andrew, are you still experiencing a problem? I was, then I read this report this morning and found the mechanical slide switch you mention. I've not seen it before and it looks like due to the dumb positioning of the switch, it's been knocked into a semi-on/off position that disabled RF. Flicking it turned Bluetooth back on. Wifi needed a reboot but it seems to be back now. Thanks for the solution. This bug can now be closed. |