I just tried this on a T42p with kernel 2.6.31-9.29. Either this changed now or that model behaves different, which makes not much sense. I can see the event going through acpid and causing /etc/acpi/ibm-wireless being called.
So for me it goes through the 4 states. The only problem I see is that bluetooth now seems to be tied to two rfkill switches. One from the thinkpad-acpi driver which is persistent and one other from the hci driver which is created and removed whenever the ThinkPad driver changes state. Unfortunately it is always re-created in off state, so one has to enable it manually all the time.
I just tried this on a T42p with kernel 2.6.31-9.29. Either this changed now or that model behaves different, which makes not much sense. I can see the event going through acpid and causing /etc/acpi/ ibm-wireless being called.
So for me it goes through the 4 states. The only problem I see is that bluetooth now seems to be tied to two rfkill switches. One from the thinkpad-acpi driver which is persistent and one other from the hci driver which is created and removed whenever the ThinkPad driver changes state. Unfortunately it is always re-created in off state, so one has to enable it manually all the time.