Disable bluetooth on boot for thinkpad_acpi doesn't work

[Daniel Jour]

Binary package hint: acpi-support

Hi there

On my Lenovo IBM Thinkpad T500 with up to date Lucid there is a minor problem concerning the thinkpad_acpi module. In fact, everything works so far.
The only thing that's not working is disabling the bluetooth switch at boot time.
I tried to do that using a conf file

/etc/modprobe.d/thinkpad_acpi.conf

options thinkpad_acpi bluetooth=disable

This should disable the bluetooth device per default, but the device is powered up at boot time.
I get the following message concerning this issue:

Apr 5 16:26:47 GosigMus kernel: [ 5.275792] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked

[Steve Langasek (vorlon)]

Thank you for taking the time to report this problem and help to improve Ubuntu.

acpi-support has nothing to do with processing of kernel driver options; reassigning to the kernel.

[Daniel Jour (danieloertwig)]

Ok, thank you so far.
I forgot to mention that i am using a 64bit system.

[Jeremy Foshee (jeremyfoshee)]

Hi Dirty,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 556404

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Daniel Jour (danieloertwig)]

Hi :)

I am still on a complete up to date Lucid from the official repositories. Downloading and reinstalling is not possible due to my very low bandwidth and the fact that my laptop is important for work/school use.

Nevertheless i still have the same issue. My configuration of the system is not changed, so to say none of the files in /etc/ was altered by me (except from /etc/modprobe.d/thinkpad_acpi.conf, which i created to disable bluetooth.)

As i am using a minimal installation i don't have apport installed on my machine (and i don't want to, because it shot my machine the last time i had it installed)
Just tell me what exactly you need and i will give you the information. (me being a manually apport ;) )

What i will do is testing whether the problem exists with the current mainline kernel.

[Though the previous message was an automated one, i hope someone will read this^^ ]

[Jeremy Foshee (jeremyfoshee)]

Hi Dirty,
    I look forward to the results of your mainline kernel testing.

~JFo

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Lasse Riis (lasse-riis)]

I am seeing the same problem on a week-old Ubuntu 10 install....

Created file /etc/modprobe.d/thinkpad.conf:

#disables Bluetooth entirely
options thinkpad_acpi bluetooth=disabled

On every boot, BT still lights up. checking dmesg yields the error:

# dmesg | grep blue
[ 9.363108] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked
# echo disable > /proc/acpi/ibm/bluetooth
# dmesg | grep blue
[ 9.363108] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked

But it seems "radio is blocked" is only a problem during boot, or when the module loads or whatever, as the echo/proc command executes fine and kills BT LED.

Not sure how I re-open the bug.

Regards, Lasse Riis

[Stefan (sreich23)]

I have using an up-to-date Maverick Meerkat on a Thinkpad T400s .
I'm still seeing the same problem with the same error message:

> dmesg | grep blue
thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked

[Indie (alanlitster)]

I think this is the same as bug #273535, when the system is started even though you tell it to disable bluetooth via "options thinkpad_acpi bluetooth=disable" it is still enabled. I've tried it from the terminal and it's about 1 sec later that bluetooth comes on so I think the thinkpad_acpi module is working correctly it's something else that's getting an event and enabling it.

[penalvch (penalvch)]

Daniel Oertwig, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Indie (alanlitster)]

This bug still exists in Ubuntu 12.04.2 LTS 3.2.0-40-generic running on a T61 - it works find on a Dell 3550

dmesg shows
[ 2.452389] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked
[10307.431418] thinkpad_acpi: WARNING: sysfs attribute bluetooth_enable is deprecated and will be removed. Please switch to generic rfkill before year 2010
[10318.969974] thinkpad_acpi: WARNING: sysfs attribute bluetooth_enable is deprecated and will be removed. Please switch to generic rfkill before year 2010
[10341.674382] thinkpad_acpi: WARNING: sysfs attribute bluetooth_enable is deprecated and will be removed. Please switch to generic rfkill before year 2010
[10349.528633] thinkpad_acpi: WARNING: sysfs attribute bluetooth_enable is deprecated and will be removed. Please switch to generic rfkill before year 2010
[10354.074403] thinkpad_acpi: WARNING: sysfs attribute bluetooth_enable is deprecated and will be removed. Please switch to generic rfkill before year 2010

[penalvch (penalvch)]

Indie, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.