bluetooth device not working (Toshiba A200 1GB)

[TQ]

This is a Toshiba Satellite A200 1GB laptop running Kubuntu gutsy. It has a kill switch for wlan+bluetooth which I kept on the "on" position (i.e. communication enabled) since boot.

Bluetooth does not work.

- Running K Menu -> System -> kbluetooth displays "No Bluetooth Adapter found! Unable to start kbluetooth. Plug in a Bluetooth Adapter or restart the bluetooth service".

- No /dev/rfcomm* device, or anything else I'm able to recognize as bluetooth-related.

- Output of `hciconfig` is empty. Output of `hcitool scan` is "Device is not available: No such device".

- The bluetooth kernel module is loaded automatically on boot. `grep hcid /var/log/syslog` says:

Sep 16 14:18:38 lisa hcid[5448]: Bluetooth HCI daemon
Sep 16 14:18:38 lisa hcid[5448]: Starting SDP server
Sep 16 14:18:38 lisa hcid[5448]: Created local server at unix:abstract=/var/run/dbus-7dn3JMoJy5,guid=c1a36bf6a61f65aeb046390046ed2d2e

What else should I do or report? Feel free to ask.

[TQ (tjgq)]

I managed to get bluetooth working by loading the omnibook module (http://omnibook.sourceforge.net/) with ectype=12. Still, I guess it would be nice to have direct kernel support...

[L Costa (attsok)]

Hallo there doshell!

As I could see, as myself, you were also having trouble initializing X
in Toshiba A200-1Gb. However, reading your post about bluetooth I
understood that you are now able to run KDE with Kubuntu 7.10 (gutsy).
This is now my problem: I can not run X - I've tried several
tutorials, and runned several tests with no success. I wonder if you
can help me? How did you run X?

Thanks in advance!
Best regards,
Attsok

[TQ (tjgq)]

Hello Attsok,

Maybe you're having trouble with the graphics driver? (See the X server log and look for errors.)

The A200 1GB has a Radeon HD2600 card which is supported by the vesa driver (which won't give you the native resolution), the proprietary ATI fglrx driver version 8.41.7 (which works fine on my machine apart from a minor "crash on X logoff issue") or the new radeonhd open source driver (haven't tried it, but it's not expected to work flawlessly). I'd suggest you go with the fglrx driver (check http://wiki.cchtml.com for installation guidelines -- the latest version is not in the repositories yet.)

I hope this helps.

Best regards,
doshell

[L Costa (attsok)]

Olá!

Pelo que pude verificar vc é português, ou pelo menos fala português! Certo?
;)

Eu já tenho minha máquina a funcionar com o kubuntu gutsy beta, o único
problema é que após eu tentar configurar a minha gráfica radion hd 2600 pelo
método 1 e 2 (
http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide) falharam,
no 1 nem entra no X e no 2 fica tudo igual, ou seja como antes de instalar a
driver. Qdo, no método 2, faço fglrxinfo dá este erro:

        fglrxinfo: error while loading shared libraries: libGL.so.1: cannot
open shared object file: No such file or directory

Pode ajudar-me? Como vc fez no seu Toshiba A200 1GB?

Desde já obrigado.

On 10/1/07, doshell < <email address hidden>> wrote:
>
> Hello Attsok,
>
> Maybe you're having trouble with the graphics driver? (See the X server
> log and look for errors.)
>
> The A200 1GB has a Radeon HD2600 card which is supported by the vesa
> driver (which won't give you the native resolution), the proprietary ATI
> fglrx driver version 8.41.7 (which works fine on my machine apart from a
> minor "crash on X logoff issue") or the new radeonhd open source driver
> (haven't tried it, but it's not expected to work flawlessly). I'd
> suggest you go with the fglrx driver (check http://wiki.cchtml.com for
> installation guidelines -- the latest version is not in the repositories
> yet.)
>
> I hope this helps.
>
> Best regards,
> doshell
>
> --
> bluetooth device not working (Toshiba A200 1GB)
> https://bugs.launchpad.net/bugs/139934
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[TQ (tjgq)]

On Tuesday 02 October 2007, L Costa wrote:
> Eu já tenho minha máquina a funcionar com o kubuntu gutsy beta, o único
> problema é que após eu tentar configurar a minha gráfica radion hd 2600
> pelo método 1 e 2 (
> http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide)
> falharam, no 1 nem entra no X e no 2 fica tudo igual, ou seja como antes de

Eu segui o método 2, visto que só esse permite instalar a versão mais recente
(8.41.7) do driver (o método 1 requer que ela já esteja nos repositórios, o
que não é o caso).

Não tive que fazer mais nada. Após instalar o driver, reconfigurar o X e
reiniciar, funcionou. Qual é o erro reportado pelo X no seu caso?

> instalar a driver. Qdo, no método 2, faço fglrxinfo dá este erro:
>
> fglrxinfo: error while loading shared libraries: libGL.so.1: cannot
> open shared object file: No such file or directory

Também passei por este problema (se bem que não me impediu de correr o X,
apenas o fglrxinfo e programas similares). Penso que isto já foi reportado no
Launchpad, mas a solução temporária é criar manualmente uma symlink para a
versão correcta da libgl:

    ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

Boa sorte.

Tiago Quelhas

[Jonathan Jesse (jjesse)]

assigning this to kdebluetooh, please reassing if this is the wrong package. thanks

Jonathan

[Paul Weiss (interweiss)]

This worked for my R200:

http://ubuntuforums.org/showthread.php?t=560475

[Michael Dudalev (dudalev)]

Most probably this is a duplicate of #180659.

[KMitnick (abedzaben-89)]

when i run grep hcid /var/log/syslog

i got

abed@abed-laptop:~$ grep hcid /var/log/syslog
Jul 25 20:54:40 abed-laptop hcid[9412]: Bluetooth HCI daemon
Jul 25 20:54:40 abed-laptop hcid[9412]: Could not become the primary owner of org.bluez
Jul 25 20:54:40 abed-laptop hcid[9412]: Unable to get on D-Bus
Jul 25 20:54:50 abed-laptop hcid[9420]: Bluetooth HCI daemon
Jul 25 20:54:50 abed-laptop hcid[9420]: Could not become the primary owner of org.bluez
Jul 25 20:54:50 abed-laptop hcid[9420]: Unable to get on D-Bus

[eletha (eflores-fatronik)]

I am getting the same problems.
 I'm new to this forum but I've read a lot of pages on trying to get bluetooth working on linux. I implemented many of the different suggestions, but I still get this message:

Aug 5 10:13:15 ubuntu1 hcid[24603]: Bluetooth HCI daemon
Aug 5 10:13:15 ubuntu1 hcid[24603]: Could not become the primary owner of org.bluez
Aug 5 10:13:15 ubuntu1 hcid[24603]: Unable to get on D-Bus

 Does you know any commands that can help me debug why the bluetooth hci daemon can't become the primary owner of org.bluez?

I'm using Ubuntu 7.10 gusty, kernal 2.6.22-14-generic,. i have already changed my system.conf and session.conf within the /etc/dbus-1 dir to contain override files (bluetooth.conf in the system.d folder)

This bluetooth.conf file allows user "root" to own org.bluez

<!-- This configuration file specifies the required security policies
     for Bluetooth core service to work. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

  <!-- ../system.conf have denied everything, so we just punch some holes -->

  <policy user="root">
    <allow own="org.bluez"/>
  </policy>

  <policy at_console="true">
    <allow send_destination="org.bluez.Manager"/>
    <allow receive_sender="org.bluez.Manager"/>

    <allow send_path="/org/bluez"/>

    <allow send_destination="org.bluez.Adapter"/>
    <allow receive_sender="org.bluez.Adapter"/>

    <allow send_destination="org.bluez.Service"/>
    <allow receive_sender="org.bluez.Service"/>

    <allow send_destination="org.bluez.Database"/>
    <allow receive_sender="org.bluez.Database"/>

    <allow send_destination="org.bluez.Security"/>
    <allow receive_sender="org.bluez.Security"/>
  </policy>

</busconfig>

Does this mean bluetooth will only work if working from the root user?
Any other suggestions? I've already made sure to change all the bluetooth config settings to enable bt service, pand service as master, and the hcid.conf file to reflect the name and class of my bt adapter on my Dell Latitude D360.

Thanks for the help!
Eletha

[eletha (eflores-fatronik)]

Here is some more information about what's going on with me
 Gutsy on a Dell630 with built in bluetooth. Hciconfig brings up hci0 with my BT address. But hcitool scan brings up nothing

[CODE]@ubuntu1:~$ hciconfig
hci0: Type: USB
        BD Address: 00:1A:6B:E6:A9:4D ACL MTU: 310:10 SCO MTU: 64:8
        UP RUNNING PSCAN
        RX bytes:985 acl:0 sco:0 events:30 errors:0
        TX bytes:617 acl:0 sco:0 commands:28 errors:0[/CODE]

[CODE]@ubuntu1:~$ hcitool scan
Scanning ...
@ubuntu1:~$ [/CODE]

[CODE]@ubuntu1:/var/run/dbus$ sudo rm -f /var/run/dbus/*
[sudo] password for :
@ubuntu1:/var/run/dbus$ dbus-uuidgen --ensure
@ubuntu1:/var/run/dbus$ dbus-daemon --system
Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_socket": Permission denied
@ubuntu1:/var/run/dbus$ sudo dbus-daemon --system
@ubuntu1:/var/run/dbus$ modprobe bluetooth
@ubuntu1:/var/run/dbus$ modprobe l2cap
@ubuntu1:/var/run/dbus$ modprobe rfcomm
@ubuntu1:/var/run/dbus$ modprobe hci-usb
@ubuntu1:/var/run/dbus$ hcid -n
hcid[7798]: Bluetooth HCI daemon
hcid[7798]: HCI dev 0 registered
hcid[7799]: Can't init device hci0: Permission denied (13)
hcid[7798]: HCI dev 0 already up
hcid[7798]: Device hci0 has been added
hcid[7800]: Can't set link mode on hci0: Permission denied (13)
hcid[7800]: Can't set link policy on hci0: Permission denied (13)
hcid[7798]: Starting security manager 0
hcid[7798]: Can't write inquiry mode for hci0: Operation not permitted (1)
hcid[7798]: Created local server at unix:abstract=/var/run/dbus-BVnoISlG8C,guid=8a5aabd33609a28fc1307d0048998408
hcid[7798]: Can't create server address file
input[7801]: Bluetooth Input daemon
input[7801]: Registered input manager path:/org/bluez/input
input[7801]: Failed to listen on control channel
serial[7802]: Bluetooth Serial Port daemon
serial[7802]: Registered manager path:/org/bluez/serial
network[7803]: Bluetooth Network daemon
network[7803]: Can't create bridge
network[7803]: Bind failed. Permission denied(13)
hcid[7798]: Got NameOwnerChanged signal for :1.3 which has no listeners[/CODE]

Can someone help me make sense of these errors and how I can explore them/ fix them? Are all these permission denied warnings coming up because I am not executing the command as root user? I tried the command as root user, but it still wouldn't work.

When I normally type hcid -n, it tells me the following:
[CODE]Jul 28 12:32:11 ubuntu1 hcid[9176]: Bluetooth HCI daemon
Jul 28 12:32:11 ubuntu1 hcid[9176]: Could not become the primary owner of org.bluez
Jul 28 12:32:11 ubuntu1 hcid[9176]: Unable to get on D-Bus[/CODE]

What does is mean to not be able to become the primary owner of an object path? How can I check why this is happening?

I am also suspecting that the hcid and DBUS session bus are not listening in on the same socket.

[CODE]$ dbus-launch
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-KPh3xmCqvf,guid=99a32f2da779f2875fca52004899685b
DBUS_SESSION_BUS_PID=7442[/CODE]

But in (from /etc/dbus-1/session.conf), session dbus listens to [CODE]<listen>unix:tmpdir=/tmp</listen>[/CODE]

While Bluetooth (from /var/run/dbus/bluetoothd_address) listens to
[CODE]unix:abstract=/var/run/dbus-YTFIvIHHn3,guid...

[ais77 (greenais)]

Hello, Eletha!

I've met the same trouble in my Ubuntu 7.10.
Have you got any workarounds finally?
Please, advise.

WBR,
ais77

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 RC or later?

[Jonathan Thomas (echidnaman)]

Probably not, since kdebluetooth is entirely broken in Intrepid.

[xteejx (xteejx)]

Marking Invalid as per previous comment. If this is still an issue in a supported version of (K)ubuntu, you can reopen this bug by changing the status back to "New".