Comment 11 for bug 767192

I have not been able to discern any effect of loading acer-wmi except for the new ACPI Exception and ACPI Error messages in syslog and kern.log

The workaround protocol I have developed for dealing with the wireless:

1) Boot the laptop & log in
2) Look at the Network Manager wireless indicator.
2a) If indicator is "hollow" then the wireless is not going to even attempt to connect (no ESSIDs listed) but that may change spontaneously sometime within the next few hundred seconds.
2b) If indicator has pulsing waves then it is trying to connect, but it may try to establish the auto connection and in a few seconds will ask for the credentials of the access point.
2c) If the indicator has pulsing waves SOMETIMES it will connect after just a few seconds.

If either 2a or 2b failures are detected, it seems to help to un-check "Enable Wireless" in network manager, wait a while (a minute?) and check it again. After maybe 30-60 seconds it will usually switch from the hollow to pulsing waves and successfully connect.

I usually leave the wireless power switch alone. If you press it, the light goes off. Press it again and the light comes back on. HOWEVER after turning wireless back on, if you do not subsequently toggle the "Enable Wireless" setting off then on in Network Manager, the wireless connection will fail anyway and will not successfully establish a connection to the access point.

SO if I flip the wireless power off and on, I need to be sure to do the same with Network Manager.

I hope this description is helpful in describing what I see.