Comment 12 for bug 816145

Hi Seth, thanks for looking at this.
It appears that rfkill may indeed be the problem, but the situation is that rfkill works first time only if the laptop was rebooted from windows.
After that, rfkill unblock {0,1} works, but yes, temporarily, as the local APs are displayed in network-manager, but then rfkill HARD blocks/kills the wireless button (hp-wifi) after about 10-30 seconds.
No amount of messing around with the rfkill options works.