Comment 56 for bug 53310

Wow! I never expected that! Things are looking promising :)

There now looks to be a work-around we could implement in user-space when the system suspends and resumes. A simple shell script reads this value on suspend and writes the same value back on resume.

That would be good since wireless drivers are supposed to be passive and not try to change the state of rfkill, only respond to it's current setting. That's why I suggested in the related acerhk bug report it implement the RFKILL API where driver-handling of this issue should be done.

One thing more: Does this ipw2200 sysfs control mechanism work even when the acerhk autowlan=1 parameter is *not* used?