NetworkManager sets rfkill state to 2, fails to re-enable

[Khashayar Naderehvandi]

This is on an Asus N20A, with the Intel wifi link 5100 chip. This laptop has a hardware switch on that's supposed to disable the radio adaptors. Without Networkmanager running, it does this just fine. Switching to off, writes a 0 to /sys/class/net/wlan1/device/rfkill/rfkill0/state and 0 to /sys/devices/platform/asus-laptop/bluetooth. Turning the switch back on back on, writes 1 to both of those files, and we're back up and rolling again.

However, when NetworkManager is running, the switch off will write 2 to /sys/class/net/wlan1/device/rfkill/rfkill0/state, also disabling the wifi. Turning the switch back on, however, won't change this. Only thing to do to get wifi back is to modprobe -r iwlagn && modprobe -r rfkill && modprobe iwlagn.

Networkmanager is the version from intrepid (with -updates enabled). Hal, on the other hand, is a rebuild from Jaunty, i.e. 0.5.12rc1, since hal from intrepid doesn't seem to recognize the rfkill functionality here.

I'd be glad to give further information as need be.

[Khashayar Naderehvandi (khashayar)]

I'm starting to think this is more of a hal bug.
I've filed a bug against hal upstream, will link.

[Khashayar Naderehvandi (khashayar)]

The freedesktop bugzilla tracking here shouldn't say "networkmanager", but rather "hal". I don't know how to set it correctly...

[Peter Meiser (meiser79)]

Hi, same problem here with a Fujitsu-Siemens Amilo Pi1536 laptop. Have you found a solution? Reloading the iwl3945 module is a workaround, but I'm searching for a better way.

[Peter Meiser (meiser79)]

My issue was solved in bug 193970.