Image Map Image Map
Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: Getting cheap BT dongle to work--Ubuntu64

  1. #1
    Join Date
    Jan 2007
    Location
    Pacific Northwest, USA
    Posts
    30,951
    Blog Entries
    20

    Default Getting cheap BT dongle to work--Ubuntu64

    I picked up a few of the cheap USB Bluetooth dongles, but can't get them to work under either Ubutntu x64 nor Win7. They're registered by the driver software, but refuse to activate.

    Here's the info for the dongle via lsusb:

    Code:
    Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    And what hciconfig says:

    Code:
    hci0:	Type: Primary  Bus: USB
    	BD Address: 33:03:30:0A:C4:A3  ACL MTU: 360:4  SCO MTU: 0:0
    	DOWN 
    	RX bytes:553 acl:0 sco:0 events:28 errors:0
    	TX bytes:368 acl:0 sco:0 commands:30 errors:0
    	Features: 0xff 0xff 0xcd 0xfa 0xdb 0xbf 0x7b 0x87
    	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
    	Link policy: RSWITCH HOLD SNIFF PARK 
    	Link mode: SLAVE ACCEPT
    I can't get the dongle to UP status, no matter what I try.

    If I try "sudo hciconfig hci0 up" I get the following message:

    Code:
    Can't init device hci0: Operation not supported (95)
    Any ideas?
    Oh yeah - lsb_release says:

    Code:
    Distributor ID:	Ubuntu
    Description:	Ubuntu 18.04.2 LTS
    Release:	18.04
    Codename:	bionic
    TIA
    Last edited by Chuck(G); March 15th, 2019 at 06:43 PM.

  2. #2
    Join Date
    Mar 2013
    Location
    Chaffee, MO
    Posts
    1,102

    Default

    Chuck,
    In a terminal type
    Code:
    dmesg | tail
    to see if you have any error messages for the Firmware not being installed. Some of the older BT Dongles
    need specific firmware loaded to support the BT Dongle.

    I have blueman, bluez, and bluetooth installed on Debian (32 Bit) 8.x

    You may have to install one of the firmware packages such as firmware-misc-nonfree.

    I finally found that on a HP computer installed Linux on.

    Larry

  3. #3
    Join Date
    Jan 2007
    Location
    Pacific Northwest, USA
    Posts
    30,951
    Blog Entries
    20

    Default

    Hmmm, actually, to get past the cruft, it's better to dmesg | grep "Bluetooth"

    I do see this message:

    Code:
    [   22.044068] Bluetooth: hci0: command 0x2007 tx timeout
    [   24.925440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [   24.925442] Bluetooth: BNEP filters: protocol multicast
    [   24.925539] Bluetooth: BNEP socket layer initialized
    As far as "service bluetooth status" goes, I get:

    Code:
    ● bluetooth.service - Bluetooth service
       Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
       Active: active (running) since Fri 2019-03-15 22:11:14 PDT; 12min ago
         Docs: man:bluetoothd(8)
     Main PID: 703 (bluetoothd)
       Status: "Running"
        Tasks: 1 (limit: 4915)
       CGroup: /system.slice/bluetooth.service
               └─703 /usr/lib/bluetooth/bluetoothd
    
    Mar 15 22:11:14 Columbia bluetoothd[703]: Bluetooth daemon 5.50
    Mar 15 22:11:14 Columbia bluetoothd[703]: Starting SDP server
    Mar 15 22:11:14 Columbia bluetoothd[703]: Bluetooth management interface 1.14 in
    Mar 15 22:11:14 Columbia systemd[1]: Starting Bluetooth service...
    Mar 15 22:11:14 Columbia systemd[1]: Started Bluetooth service.
    From this, I gather that the Bluetooth daemon is running just fine, but that the device itself isn't responding as expected to a command.

  4. #4
    Join Date
    Jan 2007
    Location
    Pacific Northwest, USA
    Posts
    30,951
    Blog Entries
    20

    Default

    I have this one

    I note that my lsusb says that my type is "Primary" and not "BR/EDR". I wonder if there's something there.

  5. #5
    Join Date
    Mar 2013
    Location
    Chaffee, MO
    Posts
    1,102

    Default

    Chuck,
    Try these commands:
    https://forums.linuxmint.com/viewtop...441402#p441402

    sudo /etc/init.d/bluetooth restart

    https://askubuntu.com/questions/7794...ongle-hci-mode

    bluetoothctl
    list

    CNTL Z

    mycomputer example:
    larry@debian:~$ sudo /etc/init.d/bluetooth restart
    larry@debian:~$ bluetoothctl
    [NEW] Controller 00:1B:DC:06:AF:21 debian [default]
    [NEW] Device 30:4B:07:EF:46:4D XT1710-02
    [NEW] Device 5C:70:A3:D4:87:3D VS985 4G LTE
    [NEW] Device 60:1D:91:9B:30:74 Moto E (4) Plus
    [bluetooth]# list
    Controller 00:1B:DC:06:AF:21 debian [default]
    [bluetooth]#
    [2]+ Stopped bluetoothctl
    larry@debian:~$

    Your Dongle should be detected.

    Larry

  6. #6
    Join Date
    Jan 2007
    Location
    Pacific Northwest, USA
    Posts
    30,951
    Blog Entries
    20

    Default

    Larry, I've done that before. This is what I get:

    Code:
    chuck@Columbia:~/Desktop$ sudo service bluetooth restart
    [sudo] password for chuck: 
    chuck@Columbia:~/Desktop$ sudo bluetoothctl
    Agent registered
    [bluetooth]# list
    [bluetooth]# quit
    chuck@Columbia:~/Desktop$
    I suspect that there's a regression in the BT code. If I have time this weekend, I'll try the same on a copy of Ubuntu 14.04 LTS.

  7. #7
    Join Date
    Jan 2007
    Location
    Pacific Northwest, USA
    Posts
    30,951
    Blog Entries
    20

    Default

    Tried the dongle on14.04LTS x32. Identical behavior.

    Something tells me I'm missing a driver, but I don't know what it is.

    sigh.

  8. #8
    Join Date
    Jan 2007
    Location
    Pacific Northwest, USA
    Posts
    30,951
    Blog Entries
    20

    Default

    On a whim, I plugged the dongle on my Orange Pi PC and got this for hciconfig -a:
    Code:
    hci0:	Type: BR/EDR  Bus: USB
    	BD Address: 33:03:30:0A:CC:7D  ACL MTU: 360:4  SCO MTU: 0:0
    	UP RUNNING PSCAN ISCAN 
    	RX bytes:587 acl:0 sco:0 events:38 errors:0
    	TX bytes:3777 acl:0 sco:0 commands:38 errors:0
    	Features: 0xff 0xff 0xcd 0xfa 0xdb 0xbf 0x7b 0x87
    	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
    	Link policy: RSWITCH HOLD SNIFF PARK 
    	Link mode: SLAVE ACCEPT 
    	Name: 'orangepipc'
    	Class: 0x1c0000
    	Service Classes: Rendering, Capturing, Object Transfer
    	Device Class: Miscellaneous, 
    	HCI Version: 4.0 (0x6)  Revision: 0x709
    	LMP Version: 4.0 (0x6)  Subversion: 0x709
    	Manufacturer: Cambridge Silicon Radio (10)
    And it works fine--Ubuntu 16.04 for ARM. Usually, it's the ARM releases that have issues. I'll have to try 16.04 on an x64 system.

  9. #9
    Join Date
    Jan 2007
    Location
    Pacific Northwest, USA
    Posts
    30,951
    Blog Entries
    20

    Default

    Tried 16.04 LTS on a x64 system--same as 14.04 and 18.04 LTS: squat.

  10. #10
    Join Date
    Mar 2013
    Location
    Chaffee, MO
    Posts
    1,102

    Default

    Chuck,
    These instructions may help.

    REF: https://askubuntu.com/questions/6323...2-isnt-working

    Enter the following command to discover which driver name is the kernel looking for when loading the drives while booting:

    Code:
    dmesg | grep -i 'firmware load'
    Try this one if it does not find anything:

    Code:
    dmesg | grep -i 'bluetooth'
    The result should be something like this:

    bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed with error -2
    Explanation: in my case the kernel is looking for the file BCM.hcd under the directory /lib/firmware/brcm where the Broadcom drivers are expected to be.
    If the Kernel is looking for another driver name, you must rename the driver file (BCM43142A0-0a5c-216c.hcd in my case for the BCM43142 (0a5c:216d))
    to the required name by the kernel.

    Move the renamed driver (BCM.hcd) to your home directory (/home/YourUsername/) and run the following command in order to move it to the folder the kernel is looking on while booting:

    Code:
    sudo mv ~/BCM.hcd /lib/firmware/brcm
    You must use the corresponding driver depending on your device and rename it if requested for the kernel.

    The Broadcom drivers can be found at:
    https://github.com/winterheart/broad...ee/master/brcm

    Reboot your computer and it should work!* (you can enter dmesg | grep -i 'bluetooth' once again to see if the driver has been loaded)


    Larry

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •