Comment 26 for bug 771758

Mauricio, one other thing I'd like you to test. Please try using the rfkill command to block the acer-threeg device and then check to see if the soft-block state changes appropriately. Follow this with an unblock and check the state again. Also, after doing the test of enabling the soft-block on the acer-wireless device, please capture dmesg and attach it along with the 'rfkill list' output. Please also use the test kernel I provided earlier when doing this test.

My suspicion after looking at the DSDT is that the flag that gets read back for the wifi status isn't getting updated when the wifi status is changed, but it's impossible to tell without some trial-and-error testing. If this is the case we may need to add some kind of quirk to the driver to indicate that the wifi status reported by the bios is unreliable.