Description:
My wireless connection works perfectly when the rfkill switch is off, flawlessly.
Then I switch the rfkill on, in order to save battery, for example, but whenever I try to switch it off again (so that I can start using the internet again) it seems that it goes unnoticed since the wireless no longer works.
Not sure if it's a HAL problem (not catching the event of the rfkill being turned off) or the kernel.

Workaround:
* Reload the driver by issuing the following commands: "modprobe -r iwl3945" and then "modprobe iwl3945"

Additional info:
* kernel26 = 2.6.29.3-1
* hal = 0.5.12git20090421.4fc367-2

Steps to reproduce:
* Boot the system with rfkil switch off.
* Turn the rfkill switch on.
* Try to turn it off again, wireless not longer works.

dmesg right after turning rfkill on:
- iwl3945: Radio Frequency Kill Switch is On:
- Kill switch must be turned off for wireless networking to work.
- iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -5
- wlan0: disassociating by local choice (reason=3)
- wlan0: deauthenticating by local choice (reason=3)
- iwl3945: MAC is in deep sleep!
- iwl3945: MAC is in deep sleep!
- iwl3945: MAC is in deep sleep!

lsmod right after turning rfkill on:
- $ lsmod | grep iwl
- iwl3945 89164 0
- mac80211 158652 1 iwl3945
- lib80211 5208 1 iwl3945
- cfg80211 36524 2 iwl3945,mac80211
- rfkill 9456 4 iwl3945,dell_laptop
- led_class 3416 2 iwl3945,sdhci

After turning it off again, I get no change neither in dmesg nor lsmod.