No Bluetooth Device Detected in hcitool dev

Bug #180659 reported by Sassan
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Linux
New
Undecided
Unassigned
bluez-utils (Ubuntu)
Undecided
Unassigned
linux (Ubuntu)
Undecided
Unassigned

Bug Description

My TOSHIBA Satellite A100 has a built-in Bluetooth device (so I suppose this must be a PCI hw), and the wireless adapter has an external switch for turning on/off. The problem is that no device is found in "hcitool dev". I dont find anything related to Bluetooth in lspci. It sometimes works fine when I restart the system for ten times, but other times I can't get it to work, no matter how many times I restart the Bluetooth daemon or turn it off and on again. It works absolutely fine in Win XP. I also get no results from hciconfig, however the following lines are present in dmesg when the system starts up

[ 21.100000] Failure registering capabilities with primary security module.
[ 21.280000] Bluetooth: Core ver 2.11
[ 21.280000] NET: Registered protocol family 31
[ 21.280000] Bluetooth: HCI device and connection manager initialized
[ 21.280000] Bluetooth: HCI socket layer initialized
[ 21.292000] Bluetooth: L2CAP ver 2.8
[ 21.292000] Bluetooth: L2CAP socket layer initialized
[ 21.340000] Bluetooth: RFCOMM socket layer initialized
[ 21.340000] Bluetooth: RFCOMM TTY layer initialized
[ 21.340000] Bluetooth: RFCOMM ver 1.8

Revision history for this message
Sassan (sasan1365) wrote :

I finally got my bluetooth working. This model of TOSHIBA has a BIOS from Phoenix, so "toshset" cannot be used. The wireless bluetooth adapters are turned off at each power-on self test (POST). In windows turning on the bluetooth adapter is done using hotkeys Fn + F8, as long as hotkeys are not supported in Linux (for models featuring Phoenix BIOS) there is no way to turn it on. So you end up using "omnibook", a package which provides Linux kernel support for TOSHIBA and HP laptops. The package and related documents can be found at http://omnibook.sourceforge.net/doku.php.There is also a supported models list available. A step-by-step installation guide is available at http://ubuntuforums.org/showthread.php?t=316358. The interesting point is that if you are lucky enough you might even have other features enabled such as hotkeys, lcd brightness adjustment, cpu temprature, etc.

Revision history for this message
Michael Dudalev (dudalev) wrote :

On my Toshiba M-100 Bluetooths works only after "hot" reboot from Windows. It's strange that Ubuntu still doesn't include omnibook modules at least in Universe repo.

Changed in bluez-utils:
status: New → Confirmed
Revision history for this message
Angel Guzman Maeso (shakaran) wrote :

It would be nice to try to accelerate development and get this bug fix for 8.10. It is very important for all users of Toshiba

Revision history for this message
future30 (future30) wrote :

and not for users of toshiba but everybody who have computer with phoenix bios
so where can i add this idea to next ubuntu ??

Revision history for this message
David Nicholas (rowerdave) wrote :

Bug still consistent in 10.04 LTS (and in my case a Toshiba A210).

Please confirm if additional details / logs / info are required?

Sassan (sasan1365)
description: updated
Revision history for this message
David Nicholas (rowerdave) wrote :

BlueZ-utils was a transitional package to assist with moving to the BlueZ 4.x stack; fault pathway also raised into Bluez (10.04 on 4.6 stack)

Revision history for this message
David Nicholas (rowerdave) wrote :

Fault appears to be a kernel issue, or certainly one part is related to kernel.

Please test if the bug is still present on the current mainline kernel [1]. Installation instructions are here [2].

[1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
[2]: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds

Initial testing with Kernel 2.6.35-999.201006151505 on Toshiba A210 with 10.04 yields expected bluetooth connectivity without needed to drop into Windows first.

Please confirm if kernel fix corrects fault.

Revision history for this message
David Nicholas (rowerdave) wrote :

Have pointed (or rather, attempted to point) fault towards ubuntu-kernel-team. (please change if I have made an error with the allocation, comes up with linux...)

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Setting to Incomplete, see comment #7! Thank you!

Changed in bluez-utils (Ubuntu):
status: Confirmed → Incomplete
Changed in bluez (Ubuntu):
status: New → Incomplete
Changed in bluez-utils (Ubuntu):
status: Incomplete → Invalid
affects: bluez (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

Sassan, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

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

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: needs-kernel-logs needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers