Bluetooth dongle / issue ?

misuok

Hello, i bought this dongle https://www.tp-link.com/ro/home-networking/high-gain-adapter/ub500/ and plugged to usb hub.
Disabled the internal bluetooth.

The new dongle seems to be installed ? but when scanning , no devices are detected

pi@retropie:~ $ sudo dmesg | grep Bluetooth
[ 4.777486] usb 1-1.3: Product: TP-Link Bluetooth USB Adapter
[ 7.218930] Bluetooth: Core ver 2.22
[ 7.219093] Bluetooth: HCI device and connection manager initialized
[ 7.219130] Bluetooth: HCI socket layer initialized
[ 7.219155] Bluetooth: L2CAP socket layer initialized
[ 7.219194] Bluetooth: SCO socket layer initialized
[ 11.674225] Bluetooth: hci0: command 0x1005 tx timeout
[ 12.087446] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 12.087463] Bluetooth: BNEP filters: protocol multicast
[ 12.087489] Bluetooth: BNEP socket layer initialized
[ 305.669430] usb 1-1.2: Product: TP- @l+ Bluetooth USB Adapter

pi@retropie:~ $ lsusb
Bus 001 Device 023: ID 2357:0604 TP-Link
Bus 001 Device 022: ID 03f0:3f4a HP, Inc
Bus 001 Device 021: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

when plugging the dongle

pi@retropie:~ $ bluetoothctl
Agent registered
[CHG] Controller 8C:90:2D:F9:69:9F Powered: no
[CHG] Controller 8C:90:2D:F9:69:9F Discovering: no
[DEL] Controller 8C:90:2D:F9:69:9F retropie [default]
[NEW] Controller 8C:90:2D:F9:69:9F retropie [default]
[CHG] Controller 8C:90:2D:F9:69:9F Powered: yes
[CHG] Controller 8C:90:2D:F9:69:9F Alias: retropie
[CHG] Controller 8C:90:2D:F9:69:9F UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller 8C:90:2D:F9:69:9F UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller 8C:90:2D:F9:69:9F UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller 8C:90:2D:F9:69:9F Pairable: yes
[CHG] Controller 8C:90:2D:F9:69:9F Discovering: no
[CHG] Controller 8C:90:2D:F9:69:9F Discovering: yes

[bluetooth]# show
Controller 8C:90:2D:F9:69:9F (public)
Name: retropie
Alias: retropie
Class: 0x00000000
Powered: yes
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: yes

no devices are detected

[bluetooth]# scan on
Discovery started
[bluetooth]#

misuok

Pi Model or other hardware: pi w 2
Power Supply used: USB-C Power Supply, 5.V 2.5A,
RetroPie Version Used: 4.8.9
Built From: retropie-buster-4.8-rpi2_3_zero2w (1).img.gz

mitu

@misuok said in Bluetooth dongle / issue ?:

The new dongle seems to be installed ? but when scanning , no devices are detected

Which devices do you expect to be detected ? If it's a gamepad/controller - is it set to 'pairing' mode before you set the 'discoverable' mode on the bluetooth adapter ? Is the USB self-powered or it relies on the Pi to provider the power ?

If you're trying to pair a gamepad, try using the RetroPie configuration menu for pairing a Bluetooth controller - https://retropie.org.uk/docs/Bluetooth-Controller/

If your model is the Pi Zero 2W (don't know what a pi w 2 could be but a zero2w), then the power supply is not USB-C, it's micro-USB.

misuok

@mitu it should detect all bluetooth devices. Even my phone too. The controller was set to pair mode before and during scan.

The usb hub is powered by pi (microusb)

also tested with no hub, scanned and no result

pi@retropie:~ $ lsusb
Bus 001 Device 002: ID 2357:0604 TP-Link
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@retropie:~ $ dmesg | grep Bluetooth
[ 3.515582] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[ 7.216133] Bluetooth: Core ver 2.22
[ 7.216282] Bluetooth: HCI device and connection manager initialized
[ 7.216318] Bluetooth: HCI socket layer initialized
[ 7.216340] Bluetooth: L2CAP socket layer initialized
[ 7.216377] Bluetooth: SCO socket layer initialized
[ 10.925565] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.925582] Bluetooth: BNEP filters: protocol multicast
[ 10.925604] Bluetooth: BNEP socket layer initialized

mitu

@misuok said in Bluetooth dongle / issue ?:

also tested with no hub, scanned and no result

How did you test that ? The Pi Zero doesn't have an USB A port.

I've looked online and it may be a firmware issue - see https://forums.linuxmint.com/viewtopic.php?t=368114. Try to download the firmware for it and see if (after a reboot) the scanning gives a result.

misuok

@mitu with a cable mini usb to usb A
I think the link from the supposed fix is not available https://github.com/jeremyb31/bluetooth-5.13.git

also tried this , with no success

cd /lib/firmware/rtl_bt
sudo wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/rtl_bt/rtl8761bu_config.bin
sudo wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/rtl_bt/rtl8761bu_fw.bin

I.m so unlucky :))

mitu

@misuok said in Bluetooth dongle / issue ?:

also tried this , with no success

Did you reboot after installing the new firmware ? If not, reboot first. If it's still not working, can you run

dmesg | grep -i firm

and post the output ? The driver may be looking into a different location to load the firmware files.

misuok

@mitu hi yes , always reboot after changes.

what i did this morning

I still used this fix from https://forums.linuxmint.com/viewtopic.php?t=368114
but I used this url https://github.com/Thundzz/bluetooth-5.13 in the git clone commands because the original url is not available https://github.com/jeremyb31/bluetooth-5.13.git

Now the bluetooth works. I am surprised

I am not a linux expert. Can you check and see what the hell the script did ? installed driver or modified kernel ?

pi@retropie:~ $ lsusb
Bus 001 Device 002: ID 2357:0604 TP-Link
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@retropie:~ $ bluetoothctl
Agent registered
[CHG] Device 08:28:02:0D:40:5C LegacyPairing: no
[CHG] Device 08:28:02:0D:40:5C Name: TESLA SMART TV by JUZ
[CHG] Device 08:28:02:0D:40:5C Alias: TESLA SMART TV by JUZ
[NEW] Device 79:57:1D:9F:30:3F 79-57-1D-9F-30-3F
[NEW] Device 7A:94:83:80:0E:CF 7A-94-83-80-0E-CF
[CHG] Device 7A:94:83:80:0E:CF ManufacturerData Key: 0x0075
[CHG] Device 7A:94:83:80:0E:CF ManufacturerData Value:
5b 7e 7b f1 e8 [~{..
[CHG] Device 08:28:02:0D:40:5C LegacyPairing: yes
[NEW] Device 1B:74:1C:1A:C6:DD Wireless Controller
[CHG] Device 1B:74:1C:1A:C6:DD Connected: yes
[CHG] Device 1B:74:1C:1A:C6:DD UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 1B:74:1C:1A:C6:DD UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 1B:74:1C:1A:C6:DD ServicesResolved: yes
[CHG] Device 1B:74:1C:1A:C6:DD Paired: yes
[CHG] Device 1B:74:1C:1A:C6:DD Trusted: yes

mitu

@misuok said in Bluetooth dongle / issue ?:

I am not a linux expert. Can you check and see what the hell the script did ? installed driver or modified kernel ?

It just modified the btusb driver to include some information to recognize your device.

https://github.com/Thundzz/bluetooth-5.13/commit/07625a74a0d3d0ef859e75b5d3fe883bdfd579aa

misuok

@mitu thanks for suggestions and help