[SOLVED] Fail to bring up bluetooth device: Protocol not supported (93)

overjoo · 11-29-2020, 09:12 AM

My initial intent was to connect bluetooth device to my laptop. I was not able to start blueman to connect bluetooth device and started debugging the issue.

Investigation lead to me this info and I stuck here:

Code:

$ blueman-adapters 
blueman-adapters version 2.1.4 starting
blueman-adapters 17.10.52 ERROR    Adapter:53 __init__  : No adapter(s) found

Code:

    $ hciconfig
    hci0:	Type: Primary  Bus: USB
    	BD Address: 5C:BA:EF:67:25:4A  ACL MTU: 1021:6  SCO MTU: 255:12
    	DOWN 
    	RX bytes:2738 acl:0 sco:0 events:232 errors:0
    	TX bytes:35990 acl:0 sco:0 commands:232 errors:0

    $ sudo hciconfig hci0 up
    Can't init device hci0: Protocol not supported (93)

btmon logs of this error:

Code:

    LE Set Resolvable Private Address Timeout (0x08|0x002e) ncmd 2
            Status: Unsupported Remote Feature / Unsupported LMP Feature (0x1a)
    = Close Index: 5C:BA:EF:67:25:4A                                                                                                                                                                         [hci0] 796.914402
    @ RAW Close: hciconfig                                                                                                                                                                                 {0x0002} 796.915186

I've updated bluez and realtek bluetooth driver, bluetoothd seems to be running just fine. Additional info below.

Code:

    $ dmesg | grep -i blue
    [    2.894429] usb 3-4: Product: Bluetooth Radio
    [    3.816914] Bluetooth: Core ver 2.22
    [    3.816924] Bluetooth: HCI device and connection manager initialized
    [    3.816928] Bluetooth: HCI socket layer initialized
    [    3.816929] Bluetooth: L2CAP socket layer initialized
    [    3.816931] Bluetooth: SCO socket layer initialized
    [    3.821296] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822
    [    3.822288] Bluetooth: hci0: RTL: rom_version status=0 version=3
    [    3.822289] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
    [    3.823066] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8822cu_fw.bin
    [    3.823078] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
    [    3.823444] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8822cu_config.bin
    [    3.823466] Bluetooth: hci0: RTL: cfg_sz 6, total sz 34338
    [    3.989017] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [    3.989020] Bluetooth: BNEP filters: protocol multicast
    [    3.989028] Bluetooth: BNEP socket layer initialized
    [    4.123315] Bluetooth: hci0: RTL: fw version 0x099a281a
    [   46.215744] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=099a lmp_ver=0a lmp_subver=281a
    [   46.215756] Bluetooth: hci0: RTL: unknown IC info, lmp subver 281a, hci rev 099a, hci ver 000a
    [   46.215758] Bluetooth: hci0: RTL: assuming no firmware upload needed
    [  339.709825] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=099a lmp_ver=0a lmp_subver=281a
    [  339.709833] Bluetooth: hci0: RTL: unknown IC info, lmp subver 281a, hci rev 099a, hci ver 000a
    [  339.709834] Bluetooth: hci0: RTL: assuming no firmware upload needed
    [ 1112.920843] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=099a lmp_ver=0a lmp_subver=281a
    [ 1112.920850] Bluetooth: hci0: RTL: unknown IC info, lmp subver 281a, hci rev 099a, hci ver 000a
    [ 1112.920851] Bluetooth: hci0: RTL: assuming no firmware upload needed


    $ rfkill list
    0: hci0: Bluetooth
    	Soft blocked: no
    	Hard blocked: no
    1: phy0: Wireless LAN
    	Soft blocked: no
    	Hard blocked: no

    $ hcitool dev
    Devices:

I have dual boot system with Windows 10 and Kali Linux on Laptop hp pavilion 15 gaming ec1007ua.

Code:

 $ uname -srvo
    Linux 5.9.0-kali2-amd64 #1 SMP Debian 5.9.6-1kali1 (2020-11-11) GNU/Linux

Bluetooth works in Windows just fine. I've also disabled fastboot in Windows per suggestions on web.
I will appreciate any hints on how to continue (NOT reinstall linux). Google was not helpful in searching for Protocol not supported error. Thanks!

pan64 · 11-30-2020, 11:08 AM

most probably this is related: https://ubuntuforums.org/showthread....194&p=14002797 - looks like a kernel/driver issue.
But kali is not really meant to do this: https://www.linuxquestions.org/quest...ad-4175614092/

rakeshj010 · 01-08-2021, 05:37 AM

what is the solution for the issue??please provide the solution i am facing the exact same issue in kali with hp gaming 15 lap

rakeshj010 · 01-08-2021, 05:39 AM

Quote:

hi any res

whats the solution

rakeshj010 · 01-08-2021, 06:07 AM

I have dual boot system with Windows 10 and Kali Linux on Laptop hp pavilion 15 gaming ec0101AX

after kali installation followed by updates and upgrades(and reboot) I tried opening blueman-manager but it did not open,
tried opening in terminal ,it showed up no default adapter found.

details:

Code:

blueman-manager 
 blueman-manager version 2.1.4 starting
 blueman-manager 17.23.53 ERROR    Manager:118 on_dbus_name_appeared: Default adapter not found, trying first available.
 blueman-manager 17.23.53 ERROR    Manager:122 on_dbus_name_appeared: No adapter(s) found, exiting

Code:

$ blueman-adapters
 blueman-adapters version 2.1.4 starting
 blueman-adapters 17.26.26 ERROR    Adapter:53 __init__  : No adapter(s) found

Code:

$ hciconfig         
hci0:   Type: Primary  Bus: USB
        BD Address: 20:4E:F6:51:E5:90  ACL MTU: 1021:6  SCO MTU: 255:12
        DOWN 
        RX bytes:1482 acl:0 sco:0 events:158 errors:0
        TX bytes:32288 acl:0 sco:0 commands:158 errors:0

$ hciconfig hci0 up
Can't init device hci0: Operation not permitted (1)

$ sudo hciconfig hci0 up
Can't init device hci0: Protocol not supported (93

updated bluez and realtek bluetooth driver, bluetoothd seems to be running just fine.

Code:

$ hcitool  dev                                                                                              1 ⨯
Devices:

Code:

$ sudo service bluetooth status
[sudo] password for rakesh: 
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Fri 2021-01-08 16:03:58 IST; 1h 30min ago
       Docs: man:bluetoothd(8)
   Main PID: 637 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 6905)
     Memory: 3.2M
        CPU: 23ms
     CGroup: /system.slice/bluetooth.service
             └─637 /usr/libexec/bluetooth/bluetoothd

Code:

lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pan64 · 01-08-2021, 06:39 AM

the solution is to use a different distro. For example ubuntu.

sevendogsbsd · 01-08-2021, 06:55 AM

What pan64 said: there is not one single reason to use Bluetooth in a penetration testing distro. If you are learning Kali and maybe taking a class, do yourself a huge favor and run Kali in a VM using their premade VM images. Much easier. My entire team runs Kali this way on a daily basis and we have zero issues.