Red Hat Bugzilla – Bug 505456
iwl3945 killswitch works only once
Last modified: 2009-07-07 13:52:57 EDT
Description of problem:
The RF killswitch works only once. Activating the killswitch is possible, deactivating it again does not work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot with RF killswitch disabled
2. Enable killswitch
3. Disable it again
##Killswitch enable event here
iwl3945: No space for Tx
iwl3945: Error sending REPLY_CARD_STATE_CMD: iwl3945_enqueue_hcmd failed: -28
iwl3945: Radio Frequency Kill Switch is On:
Kill switch must be turned off for wireless networking to work.
##Killswitch disable event here
Enabling and disabling again should be possible.
Can you do an 'ifconfig wlan0 up' after disabling the killswitch?
# ifconfig wlan0 up
SIOCSIFFLAGS: No such device
That seems odd...maybe the firmware error leads to deregistering the device?
What about if you do a 'modprobe iwlagn' first?
(In reply to comment #0)
> Description of problem:
> The RF killswitch works only once. Activating the killswitch is possible,
> deactivating it again does not work.
Could you please elaborate on "does not work"?
> Version-Release number of selected component (if applicable):
> How reproducible:
> Steps to Reproduce:
> 1. Boot with RF killswitch disabled
> 2. Enable killswitch
> 3. Disable it again
What do you do as step 4 to test if there is a problem?
> Actual results:
> ##Killswitch enable event here
> iwl3945: No space for Tx
> iwl3945: Error sending REPLY_CARD_STATE_CMD: iwl3945_enqueue_hcmd failed: -28
> iwl3945: Radio Frequency Kill Switch is On:
> Kill switch must be turned off for wireless networking to work.
> ##Killswitch disable event here
The rfkill log messages are not very friendly here. We have the rfkill enabling messages as a warning, but the disabling is a debug message. So, if you just go by the log messages (and you do not have debugging enabled) then it will seem as though rfkill is still enabled when it is not. You can get a better idea of what is going on by enabling debugging (make sure driver is compiled with CONFIG_IWL3945_DEBUG) and load module with "modprobe iwl3945 debug=0x20000" or "modprobe iwl3945 debug=0x63fff).
This bug looks _very_ similar as 498622. Christian could you try kernel provided here:
*** This bug has been marked as a duplicate of bug 498622 ***