Comment 5 for bug 835408

I've now come across something new: I read a thread regarding ar2413 chips and how they need nohwcrypt as a parameter when loading ath5k, so I gave that a shot. So far my endeavor hasn't worked, because I've now discovered that after TRYING to put the wlan0 interface up with ifconfig wlan0 up, the wireless card gets hard blocked. Let me summarise:

logan@linuxbox:~$ sudo modprobe ath5k
logan@linuxbox:~$ rfkill list all
3: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
logan@linuxbox:~$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: Unknown error 132
logan@linuxbox:~$ rfkill list all
3: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: yes
logan@linuxbox:~$

Why on earth would simply putting the interface up cause a HARD block? The only "hard" block I have on this laptop is a wireless button that I'm fairly sure does nothing on any distro of linux, except toggle bluetooth. Pressing it does nothing to get rid of the hard block, nor does it create a hard block before trying to put the interface up. Anybody got any ideas? Should I take this to the compat-wireless bugzilla?