Henrique de Moraes Holschuh wrote: > That said, please play with the master_switch_mode parameter of the > rfkill module. I personally cannot tolerate anything but > master_switch_mode=1, and I dare think it might solve your problem :) Sadly not. It looks like it should, and I've instrumented the rfkill module to be sure the parameter is set, which it is. Debug log (WWAN) follows. Bluetooth behaves the same way as WWAN - powers up after killswitch toggle, regardless of its state prior to that. # cat /sys/module/rfkill/parameters/master_switch_mode 1 prior to sleep: # find /sys | grep rfkill..name | xargs cat tpacpi_bluetooth_sw tpacpi_wwan_sw hci0 phy0 # find /sys | grep rfkill..state | xargs cat 1 1 1 1 Turn off WWAN vis /sys: # echo 0 > /sys/devices/platform/thinkpad_acpi/rfkill/rfkill1/state Verify it is off: # find /sys | grep rfkill..state | xargs cat 1 0 1 1 Flip rfkill (hard) switch to off: corwyn:/home/collabora# find /sys | grep rfkill..state | xargs cat 2 2 2 note: hci0 goes missing when the hard switch is used. (presumably usb power loss) Flip rfkill (hard) switch back on again: corwyn:/home/collabora# find /sys | grep rfkill..state | xargs cat 1 1 1 1 > I think I can consider this patch approved and add your tested-by? You can certainly add my tested-by for the sleep/resume path patch. Tested-by: Ian Molton <ian.molton@xxxxxxxxxxxxxxx> > Does thinkpad-acpi tells acpi -V -s does not list any wireless devices at all. dmesg has a few mentions of thinkpad-acpi but only the rfkillswitch as far as wireless devices. Thanks for your quick response too :-) -Ian -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
