Hi, Andreas has (AFAIK an X61?) Lenovo ThinkPad. When pressing the bluetooth button he gets: acpi_listen ibm/hotkey HKEY 00000080 00001005 but bluetooth is not enabled. echo 1 > /sys/devices/platform/thinkpad_acpi/bluetooth_enable works. Kernel: 2.6.25 Shouldn't the thinkpad driver do this automatically? If this should get routed through userspace, then probably a more general interface than /sys/.../thinkpad_acpi/bluetooth_enable should get used or this ends up in a vendor specific nightmare? Is it correct that only kill switch events are directly passed to the corresponding driver inside the kernel? WLAN/Bluetooth buttons are intended to be routed through userspace? But Hal only passes them as dbus events which in turn need to be picked up by e.g. network manager to switch off the wlan interface? The button (not the kill switch) approach sound rather broken. There should be keys existing with both, bluetooth and wlan switching (I've heard that even on Windows user can decide on key press what to enable/disable). But doing this in Linux (pass it from the kernel to hal to another userspace/X-app) sounds rather error prone. IMO this should also just be done in kernel (if possible)? Thanks, Thomas Thomas ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
