Comment 22 for bug 771758

Thanks Mauricio.

Something is apparently going wrong in the interaction with the bios. acer-wmi calls into the bios to set the rfkill state, but it's always reading back that wifi is disabled. acer-wmi also has a periodic event to read back the state from the bios and set its own rfkill state based on that (I'm not sure why, but I'm guessing there must be some hardware for which this is necessary to determine if wifi has been disabled by either a hotkey or switch). So what happens is that your wifi is unblocked briefly (less than one second) until the next time acer-wmi updates its soft-block state from the bios, which matches the behavior described in comment #5. I'm not sure if it's the setting or the reading of the wifi state, or both, that's going wrong. I need to do some more investigation.

Out of curiosity, what happens if you run 'rfkill block 3' (assuming that 3 is always the index assigned to acer-wireless in 'rfkill list', which is probably worth checking first)?

Your wifi hotkey issue should be an easy fix, but it won't matter until the soft-block problem gets fixed.