Johannes, Boy is the rfkill subsystem fragile. After all our debugging of the control of the b43 LED with the rfkill switch, it is broken again with 2.6.30-rc1. I put a test print at the start of b43_led_brightness_set(). It gets called lots of times for the TX/RX LED (which I do not have), but only gets called for the radio LED when the driver is loaded or unloaded. Changing the rfkill switch causes the "radio hardware status" messages to be output, but nothing happens with the LED. Now, led_trigger_event() once again is only called indirectly through rfkill_led_trigger() from rfkill_led_trigger_activate(), but rfkill_led_trigger() is never called. I have no idea who is calling b43_led_brightness at start-up/shut-down. It must be some part of the LED system. Some things are working. The contents of /sys/class/rfkill/rfkill3/state change from 0 to 1 when the switch is turned on; however, I have not been able to locate what code is doing the change. Routine rfkill_uevent() is never entered. Larry -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
