Connection errors

This post is for people getting connection errors.

Some people reported connection issues that were fixed by upgrading the linux bluetooth stack (default one in Ubuntu 10.10 is version 4.69).

Instructions if you want to do upgrade to the latest version (4.91):

System > Administration > Synaptic Package Manager
Settings > Repositories > Other Software

Add
Apt Line: ppa:blueman/ppa
Close

Reload
Mark all upgrades
Apply

I just upgraded to this version and it seems not to cause any issue on my setup. Do it at your own risk!

Note: bluez version 4.91 is now in Ubuntu 11.04.

5 Replies to “Connection errors”

  1. I wish I could confirm upgrading fixed it, however it did not in my case… 🙁

    Thanks for posting the easy details on how to upgrade though, as I found myself into a dependency hell going about it manually.

    I think I'll try if I can get another bluetooth dongle somewhere to test with that. Hopefully that can rule out any other problems on my end. Will report back when I find anything useful. 🙂

  2. I just tried with another dongle, still no go. Note however that both dongles are from Sweex: Dongle #1 is Sweex BT211, Dongle #2 is Sweex BT202.

    Here are the logs, for completeness' sake:

    ======================================================================
    Dongle 1:
    ======================================================================

    Current Bluetooth master: XX:XX:XX:XX:XX:45
    Current Bluetooth Device Address: XX:XX:XX:XX:XX:a1

    hci0: Type: BR/EDR Bus: USB
    BD Address: XX:XX:XX:XX:XX:A1 ACL MTU: 310:10 SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:1471 acl:0 sco:0 events:46 errors:0
    TX bytes:533 acl:0 sco:0 commands:42 errors:0
    Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH HOLD SNIFF PARK
    Link mode: SLAVE ACCEPT
    Name: 'ubuntu-0'
    Class: 0x000508
    Service Classes: Unspecified
    Device Class: Peripheral, Gamepad
    HCI Version: 2.0 (0x3) Revision: 0xc5c
    LMP Version: 2.0 (0x3) Subversion: 0xc5c
    Manufacturer: Cambridge Silicon Radio (10)

    hci0: Type: BR/EDR Bus: USB
    BD Address: XX:XX:XX:XX:XX:A1 ACL MTU: 310:10 SCO MTU: 64:8
    Unified 21e
    Chip version: BlueCore4-ROM
    Max key size: 128 bit
    SCO mapping: HCI

    Can't get device info: No such device

    run as root user to set device class
    connecting with hci0 = XX:XX:XX:XX:XX:A1 to XX:XX:XX:XX:XX:45 psm 17

    emu: can't connect to control psm: Host is down
    can't connect to control psm

    emu_thread: end

    ======================================================================
    Dongle 2:
    ======================================================================

    Current Bluetooth master: XX:XX:XX:XX:XX:45
    Current Bluetooth Device Address: XX:XX:XX:XX:XX:a1

    hci0: Type: BR/EDR Bus: USB
    BD Address: XX:XX:XX:XX:XX:A1 ACL MTU: 1021:8 SCO MTU: 48:10
    UP RUNNING
    RX bytes:2886 acl:0 sco:0 events:70 errors:0
    TX bytes:522 acl:0 sco:0 commands:69 errors:0
    Features: 0xff 0xfe 0x8d 0x3e 0x88 0x19 0x00 0x00
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH HOLD SNIFF
    Link mode: SLAVE ACCEPT
    Name: 'ISSCEDRBTA'
    Class: 0x000508
    Service Classes: Unspecified
    Device Class: Peripheral, Gamepad
    HCI Version: 2.0 (0x3) Revision: 0x2c6
    LMP Version: 2.0 (0x3) Subversion: 0x2c6
    Manufacturer: Integrated System Solution Corp. (57)

    hci0: Type: BR/EDR Bus: USB
    BD Address: XX:XX:XX:XX:XX:A1 ACL MTU: 1021:8 SCO MTU: 48:10
    Unsupported manufacturer

    Can't get device info: No such device

    run as root user to set device class
    connecting with hci0 = XX:XX:XX:XX:XX:A1 to XX:XX:XX:XX:XX:45 psm 17

    emu: can't connect to control psm: Host is down
    can't connect to control psm

    emu_thread: end

  3. Oh, I just found that dongle #2 doesn't retain the changed address after I reconnect it. If I restart sixemugui it reports the changed address, but the moment I disconnect the dongle & reconnect it, the original address is restored.

    Dongle #1 does retain the changed address after an unplug.

  4. The second one has an "Integrated System Solution Corp" chip. Very few of these are reported to work.

    It seems you are very unlucky 🙁

    Please open an issue. I will ask you a few traces for the first dongle.

    Also, if you can borrow other dongles, please test them.

Leave a Reply

Your email address will not be published. Required fields are marked *