Ubuntu
linux-source-2.6.20 package

Bluetooth not working on ThinkPad Z61m

Bug #90955 reported by Frank
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

As described here: https://launchpad.net/ubuntu/+source/hotkey-setup/+bug/74908 the FN-F5 key did not works for Feisty Fawn Herd 5 on ThinkPad Z61m.
 tail -f /var/log/acpid shows after pressing the appropriate keys

[Fri Mar 9 21:26:42 2007] received event "ibm/hotkey HKEY 00000080 00001005"
[Fri Mar 9 21:26:42 2007] notifying client 4877[107:112]
[Fri Mar 9 21:26:42 2007] notifying client 5036[0:0]
[Fri Mar 9 21:26:42 2007] executing action "/etc/acpi/ibm-wireless.sh"
[Fri Mar 9 21:26:42 2007] BEGIN HANDLER MESSAGES
/etc/acpi/wireless.sh: line 9: echo: write error: Invalid argument
[Fri Mar 9 21:26:42 2007] END HANDLER MESSAGES
[Fri Mar 9 21:26:42 2007] action exited with status 0
[Fri Mar 9 21:26:42 2007] completed event "ibm/hotkey HKEY 00000080 00001005"

The bluetooth module did not work. After booting the status of

cat /proc/acpi/ibm/bluetooth

is "disabled" but the module is marked as loaded at syslog (see attachment)

Trying to add "enable", "disable" manually by:

sudo echo > enable /proc/acpi/ibm/bluetooth

results in:

bash: /proc/acpi/ibm/bluetooth: Permission denied

Accomplishing this through sudo -s works for the instruction itself, but whether the bluetooth LED is on not bluetooth is functioning (see syslog, last entry after enabling manually).
But,

cat /proc/acpi/ibm/bluetooth

shows "enabled"

After rebooting all instructions are lost. This is true for both bluetooth and tp-smapi instructions. (See also https://launchpad.net/bugs/88450 (last reply))

Furthermore it is necessary to become XF86AudioPlay working with Amarok to disable the corresponding key within the Gnome-Keyboard-Shortcuts. Otherwise Amarok is not recognizing the key but rhythmbox does.

At least Suspend to ram and Suspend to disk is working out of the box, but waking of from Suspend to ram results in a blank screen. From there it is impossible to execute any command. A hard reboot is necessary. This is only tested with the fglrx-driver from the repository.

Revision history for this message
Frank (frank-schaeffer) wrote :
Revision history for this message
Ben Collins (ben-collins) wrote :

Please attach (do not paste into comments), the output of "lspci -vv" and "lsusb -vv".

Changed in linux-source-2.6.20:
assignee: nobody → ben-collins
status: Unconfirmed → Needs Info
Revision history for this message
Frank (frank-schaeffer) wrote :

Hello Ben Collins,
here the requested output

Best regards

Frank

Revision history for this message
Frank (frank-schaeffer) wrote :

lspci

Ben Collins (ben-collins)
Changed in linux-source-2.6.20:
importance: Undecided → Medium
status: Needs Info → Confirmed
Ben Collins (ben-collins)
Changed in linux-source-2.6.20:
assignee: ben-collins → ubuntu-kernel-team
assignee: ubuntu-kernel-team → ubuntu-kernel-acpi
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Frank - You are reporting 2 problems; enabling bluetooth and resume from suspend. Enabling bluetooth from the command line requires the correct syntax:

sudo echo enable > /proc/acpi/ibm/bluetooth

In the future please file separate reports for each problem.

Revision history for this message
Frank (frank-schaeffer) wrote : Re: [Bug 90955] Re: Bluetooth not working on ThinkPad Z61m

Am Fri, 23 Mar 2007 17:17:01 -0000
schrieb Tim Gardner <email address hidden>:

> Frank - You are reporting 2 problems; enabling bluetooth and resume
> from suspend. Enabling bluetooth from the command line requires the
> correct syntax:
>
> sudo echo enable > /proc/acpi/ibm/bluetooth
>
> In the future please file separate reports for each problem.
>
Hi Tim,
well but I know the right syntax, this was only a "typing" mistake by
myself. The problem occur also with

sudo echo enable > /proc/acpi/ibm/bluetooth

bash: /proc/acpi/ibm/bluetooth: Permission denied

Frank

Revision history for this message
Frank (frank-schaeffer) wrote :

To all developers, especially to the team invoked here,
You did are very very great job.
Afterwards a fresh boot Bluetooth is now functioning. Furthermore I'am able to disable
Bluetooth and Wlan by pressing "Fn F5". Repeated pressing "Fn F5" results in enabling
Wlan again.
Repeated pressing "Fn F5" now results in disabling Wlan and enabling Bluetooth. And at least,
pressing againg "Fn F5" results in a fully functioning of Wlan and Bluetooth. Very great job!!!

At present only the two other issues remains. As posted before enabling / disabling Bluetooth via
the command line results in the mentioned permission problem.

Suspend2Ram is well functioning with the fglrx driver of the repository, but waking of results at this time
in a black screen. Should I file a new bug report to this issue?? (At next time I will follow your advise and seperate each bug.

Thank you

Frank

Revision history for this message
private_lock (private-lock) wrote :

sudo echo enable > /proc/acpi/ibm/bluetooth

The scope of the sudo is only up to the ">" That is why you cannot write to that file this way. Instead do:

sudo su
echo enable > /proc/acpi/ibm/bluetooth

in two commands.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
Curtis Hovey (sinzui)
Changed in linux-source-2.6.20 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.