On Mon, 30 Nov 2009, Kevin Locke wrote: > Then, the radio is unblocked by rfkill_switch_all which is queued by > rfkill_schedule_evsw_rfkillall as part of input_register_device: That means rfkill thinks the radio should be enabled, and tells thinkpad-acpi to do it, which it does. If you're in single user mode, it is happening because of thinkpad-acpi and rfkill interactions. If you disable bluetooth through rfkill (and not through bluetooth_enable) before you rmmod thinkpad-acpi ; modprobe thinkpad-acpi, what happens? Also, are you sure you don't have a "bluetooth=enable" parameter in an options line for thinkpad-acpi somewhere in the modprobe config (in /etc/modprobe.d/*) ? Note: 2.6.31 has an all-new rfkill core and thinkpad-acpi glue, so it is worth testing it on 2.6.31 too. One known bug: will resume with radios disabled. A fix is ready for that problem already, but it has not made it to the kernel, yet. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
