UB500 (rtl8761b chipset) timeout

Questions about hardware, drivers and peripherals
Forum rules
Before you post please read how to get help
Post Reply
schmafu
Level 1
Level 1
Posts: 5
Joined: Fri Sep 30, 2022 4:47 am

UB500 (rtl8761b chipset) timeout

Post by schmafu »

I desperately try to get my new TP-Link UB500 Bluetooth 5.0 USB Adapter to work with Kernel Version 5.18.0, however, failed miserably so far.
Updated /lib/firmware using 'apt install linux-firmware' already as the rtl8761bu_* files were not found initially, however, the stick still does not work.

Detection works fine:

Code: Select all

$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 2357:0604 TP-Link TP-NLjk UB500 Adapter
Bus 001 Device 004: ID 0e0f:0008 VMware, Inc. Virtual Bluetooth Adapter
Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Code: Select all

$ sudo dmesg|tail
[  165.287766] usb 1-2.2: Manufacturer:  
[  165.287766] usb 1-2.2: SerialNumber: E848B8C82000
[  165.352613] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[  165.357584] Bluetooth: hci1: RTL: rom_version status=0 version=1
[  165.357588] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin
[  165.358300] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_fw.bin
[  165.358316] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin
[  165.358457] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_config.bin
[  165.358467] Bluetooth: hci1: RTL: cfg_sz 6, total sz 20522
[  166.581567] Bluetooth: hci1: RTL: fw version 0x0999646b
Trying to enable to device seems to be successful, however, sometimes it times out. What is strange is the device name.

Code: Select all

$ sudo hciconfig hci1 up
$ sudo hciconfig hci1 -a
hci1:	Type: Primary  Bus: USB
	BD Address: E8:48:B8:C8:20:00  ACL MTU: 1021:6  SCO MTU: 255:12
	UP RUNNING 
	RX bytes:1911 acl:0 sco:0 events:160 errors:0
	TX bytes:21654 acl:0 sco:0 commands:160 errors:0
	Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH HOLD SNIFF PARK 
	Link mode: PERIPHERAL ACCEPT 
	Name: 'TP-Link UB500 Adapter�����������'
	Class: 0x000000
	Service Classes: Unspecified
	Device Class: Miscellaneous, 
	HCI Version: 5.1 (0xa)  Revision: 0x999
	LMP Version: 5.1 (0xa)  Subversion: 0x646b
	Manufacturer: Realtek Semiconductor Corporation (93)
Scanning does not work at all, always times out:

Code: Select all

$ sudo hcitool lescan
Enable scan failed: Connection timed out

Code: Select all

$ sudo dmesg|tail
[  165.287766] usb 1-2.2: SerialNumber: E848B8C82000
[  165.352613] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[  165.357584] Bluetooth: hci1: RTL: rom_version status=0 version=1
[  165.357588] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin
[  165.358300] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_fw.bin
[  165.358316] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin
[  165.358457] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_config.bin
[  165.358467] Bluetooth: hci1: RTL: cfg_sz 6, total sz 20522
[  166.581567] Bluetooth: hci1: RTL: fw version 0x0999646b
[  220.922866] Bluetooth: hci1: command 0x200c tx timeout
Hopefully, somebody can help me or point me in the right direction.
User avatar
Joe2Shoe
Level 5
Level 5
Posts: 779
Joined: Wed Oct 18, 2017 8:12 pm
Location: Ozone

Re: UB500 (rtl8761b chipset) timeout

Post by Joe2Shoe »

Some Bluetooth 5.0 adapters which use the rtl8761b firmware are not working correctly on Ubuntu 20.04 and 22.04 (Possibly other Linux distributions too), because of a bug in loading the correct driver for these devices.

In other words, the driver is there on the system and has no issue, but it is not loaded correctly when the Bluetooth device is plugged into the PC.
This happens because the rtl8761bu firmware is being requested, but the system should have loaded the rtl8761b firmware, not the rtl8761bu one.

To fix this issue, just create a symbolic link to link the rtl8761bu driver firmware to the rtl8761b one. In this way, any time the system requests the rtl8761bu files it will load the correct rtl8761b ones.

Simply create a soft link on the rtl_bt/rtl8761bu_fw.bin file like this in the Terminal:
cd /lib/firmware/rtl_bt

sudo ln -s rtl8761b_config.bin rtl8761bu_config.bin

sudo ln -s rtl8761b_fw.bin rtl8761bu_fw.bin

Then just remove the Bluetooth 5.0 adapter from the PC and plug it in again, and it should be working.
"Tolerance is the refuge of men without conviction."
"Common sense is not so common" - Voltaire
User avatar
hglee
Level 6
Level 6
Posts: 1423
Joined: Fri Jun 22, 2018 4:31 pm

Re: UB500 (rtl8761b chipset) timeout

Post by hglee »

schmafu wrote:
Fri Sep 30, 2022 5:02 am
I desperately try to get my new TP-Link UB500 Bluetooth 5.0 USB Adapter to work with Kernel Version 5.18.0, however, failed miserably so far.
Updated /lib/firmware using 'apt install linux-firmware' already as the rtl8761bu_* files were not found initially, however, the stick still does not work.

Earlier this week, someone else here had a connection issue with their TP-Link UB500. See their solution:

<SOLVED> Need help getting Bluetooth to work with TP-Link UB500 Bluetooth

Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
schmafu
Level 1
Level 1
Posts: 5
Joined: Fri Sep 30, 2022 4:47 am

Re: UB500 (rtl8761b chipset) timeout

Post by schmafu »

@Joe2Shoe, @hglee:

Thank you! Tried your recommendations, however, the behavior is exactly the same as before.

Links:

Code: Select all

$ ls -la /lib/firmware/rtl_bt/rtl8761bu_*
lrwxrwxrwx 1 root root    19 Oct  1 08:23 /lib/firmware/rtl_bt/rtl8761bu_config.bin -> rtl8761b_config.bin
-rw-r--r-- 1 root root     6 Oct 18  2021 /lib/firmware/rtl_bt/rtl8761bu_config.bin_bkp
lrwxrwxrwx 1 root root    15 Oct  1 08:23 /lib/firmware/rtl_bt/rtl8761bu_fw.bin -> rtl8761b_fw.bin
-rw-r--r-- 1 root root 34796 Oct 18  2021 /lib/firmware/rtl_bt/rtl8761bu_fw.bin_bkp
dmesg:

Code: Select all

[  526.389810] usb 2-2.2: USB disconnect, device number 5
[  543.526659] usb 2-2.2: new full-speed USB device number 6 using uhci_hcd
[  544.052303] usb 2-2.2: New USB device found, idVendor=2357, idProduct=0604, bcdDevice= 2.00
[  544.052309] usb 2-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  544.052311] usb 2-2.2: Product: TP-Link UB500 Adapter
[  544.052312] usb 2-2.2: Manufacturer:  
[  544.052313] usb 2-2.2: SerialNumber: E848B8C82000
[  544.117295] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[  544.123315] Bluetooth: hci1: RTL: rom_version status=0 version=1
[  544.123319] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin
[  544.123349] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_fw.bin
[  544.123364] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin
[  544.123373] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_config.bin
[  544.123383] Bluetooth: hci1: RTL: cfg_sz 25, total sz 21389
[  545.294298] Bluetooth: hci1: RTL: fw version 0x0d99646b
[  559.061995] Bluetooth: hci1: command 0x0c14 tx timeout
[  572.051897] hub 2-2:1.0: hub_ext_port_status failed (err = -110)
The last post also mentioned:
Disable Secure Boot in your BIOS, because it's known to interfere with device drivers & firmware. If you run Windows on the same PC as Linux, it's best to disable Windows Fast Startup, otherwise it can leave your hardware in a zombie state at any time.
Linux is running on a Virtual Machine. Could it be that the hardware state gets corrupted somehow when the device is handed over to the VM once the stick is plugged in?
User avatar
hglee
Level 6
Level 6
Posts: 1423
Joined: Fri Jun 22, 2018 4:31 pm

Re: UB500 (rtl8761b chipset) timeout

Post by hglee »

schmafu wrote:
Fri Sep 30, 2022 5:02 am
I desperately try to get my new TP-Link UB500 Bluetooth 5.0 USB Adapter to work with Kernel Version 5.18.0, however, failed miserably so far.
Hopefully, somebody can help me or point me in the right direction.

To post essential details about your PC setup: Plug in all relevant dongles, accessories, and peripherals. Then

Open a Terminal (ctrl-alt-T), then copy-and-paste the following long line of green text into the Terminal window, then tap Enter...

Code: Select all

C=code];echo "[$C`inxi -Fxxxmprzc0 --slots;mokutil --sb-state;cat /proc/cmdline;dkms status;rfkill;lsusb;lsblk -fir;lspci -nnk;(lsmod;dmesg)|egrep -i "blu|bt|fai|una|unk|err|fir"`[/$C"|xed -
Within a moment, xed text editor pops open, showing technical data useful for others to analyze PC & peripheral issues.

Copy-and-paste everything from xed into a Reply here. < The required [code] tags have been added for you />

Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
schmafu
Level 1
Level 1
Posts: 5
Joined: Fri Sep 30, 2022 4:47 am

Re: UB500 (rtl8761b chipset) timeout

Post by schmafu »

Thank you for your time :wink:

Code: Select all

System:
  Kernel: 5.18.0-kali7-amd64 arch: x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Xfce v: 4.16.1 tk: Gtk v: 3.24.34 info: xfce4-panel wm: xfwm
    v: 4.16.1 dm: LightDM v: 1.26.0 Distro: Kali GNU/Linux 2022.3
    kali-rolling base: Debian testing
Machine:
  Type: Vmware System: VMware product: VMware Virtual Platform v: N/A
    serial: <filter> Chassis: No Enclosure type: 1 serial: N/A
  Mobo: Intel model: 440BX Desktop Reference Platform serial: N/A
    BIOS: Phoenix v: 6.00 date: 07/29/2019
Memory:
  RAM: total: 7.76 GiB used: 871.4 MiB (11.0%)
  Array-1: capacity: N/A slots: 128 note: check EC: N/A
    max-module-size: N/A
  Device-1: NVD #0 type: no module installed
  Device-2: NVD #1 type: no module installed
  Device-3: NVD #2 type: no module installed
  Device-4: NVD #3 type: no module installed
  Device-5: NVD #4 type: no module installed
  Device-6: NVD #5 type: no module installed
  Device-7: NVD #6 type: no module installed
  Device-8: NVD #7 type: no module installed
  Device-9: NVD #8 type: no module installed
  Device-10: NVD #9 type: no module installed
  Device-11: NVD #10 type: no module installed
  Device-12: NVD #11 type: no module installed
  Device-13: NVD #12 type: no module installed
  Device-14: NVD #13 type: no module installed
  Device-15: NVD #14 type: no module installed
  Device-16: NVD #15 type: no module installed
  Device-17: NVD #16 type: no module installed
  Device-18: NVD #17 type: no module installed
  Device-19: NVD #18 type: no module installed
  Device-20: NVD #19 type: no module installed
  Device-21: NVD #20 type: no module installed
  Device-22: NVD #21 type: no module installed
  Device-23: NVD #22 type: no module installed
  Device-24: NVD #23 type: no module installed
  Device-25: NVD #24 type: no module installed
  Device-26: NVD #25 type: no module installed
  Device-27: NVD #26 type: no module installed
  Device-28: NVD #27 type: no module installed
  Device-29: NVD #28 type: no module installed
  Device-30: NVD #29 type: no module installed
  Device-31: NVD #30 type: no module installed
  Device-32: NVD #31 type: no module installed
  Device-33: NVD #32 type: no module installed
  Device-34: NVD #33 type: no module installed
  Device-35: NVD #34 type: no module installed
  Device-36: NVD #35 type: no module installed
  Device-37: NVD #36 type: no module installed
  Device-38: NVD #37 type: no module installed
  Device-39: NVD #38 type: no module installed
  Device-40: NVD #39 type: no module installed
  Device-41: NVD #40 type: no module installed
  Device-42: NVD #41 type: no module installed
  Device-43: NVD #42 type: no module installed
  Device-44: NVD #43 type: no module installed
  Device-45: NVD #44 type: no module installed
  Device-46: NVD #45 type: no module installed
  Device-47: NVD #46 type: no module installed
  Device-48: NVD #47 type: no module installed
  Device-49: NVD #48 type: no module installed
  Device-50: NVD #49 type: no module installed
  Device-51: NVD #50 type: no module installed
  Device-52: NVD #51 type: no module installed
  Device-53: NVD #52 type: no module installed
  Device-54: NVD #53 type: no module installed
  Device-55: NVD #54 type: no module installed
  Device-56: NVD #55 type: no module installed
  Device-57: NVD #56 type: no module installed
  Device-58: NVD #57 type: no module installed
  Device-59: NVD #58 type: no module installed
  Device-60: NVD #59 type: no module installed
  Device-61: NVD #60 type: no module installed
  Device-62: NVD #61 type: no module installed
  Device-63: NVD #62 type: no module installed
  Device-64: NVD #63 type: no module installed
  Array-2: capacity: 9 GiB slots: 64 EC: None max-module-size: 8 GiB
    note: est.
  Device-1: Slot0 info: single-bank type: DRAM detail: edo size: 8 GiB
    speed: N/A volts: N/A width (bits): data: 32 total: 32 manufacturer: N/A
    part-no: N/A serial: N/A
  Device-2: Slot1 type: no module installed
  Device-3: Slot2 type: no module installed
  Device-4: Slot3 type: no module installed
  Device-5: Slot4 type: no module installed
  Device-6: Slot5 type: no module installed
  Device-7: Slot6 type: no module installed
  Device-8: Slot7 type: no module installed
  Device-9: Slot8 type: no module installed
  Device-10: Slot9 type: no module installed
  Device-11: Slot10 type: no module installed
  Device-12: Slot11 type: no module installed
  Device-13: Slot12 type: no module installed
  Device-14: Slot13 type: no module installed
  Device-15: Slot14 type: no module installed
  Device-16: Slot15 type: no module installed
  Device-17: Slot16 type: no module installed
  Device-18: Slot17 type: no module installed
  Device-19: Slot18 type: no module installed
  Device-20: Slot19 type: no module installed
  Device-21: Slot20 type: no module installed
  Device-22: Slot21 type: no module installed
  Device-23: Slot22 type: no module installed
  Device-24: Slot23 type: no module installed
  Device-25: Slot24 type: no module installed
  Device-26: Slot25 type: no module installed
  Device-27: Slot26 type: no module installed
  Device-28: Slot27 type: no module installed
  Device-29: Slot28 type: no module installed
  Device-30: Slot29 type: no module installed
  Device-31: Slot30 type: no module installed
  Device-32: Slot31 type: no module installed
  Device-33: Slot32 type: no module installed
  Device-34: Slot33 type: no module installed
  Device-35: Slot34 type: no module installed
  Device-36: Slot35 type: no module installed
  Device-37: Slot36 type: no module installed
  Device-38: Slot37 type: no module installed
  Device-39: Slot38 type: no module installed
  Device-40: Slot39 type: no module installed
  Device-41: Slot40 type: no module installed
  Device-42: Slot41 type: no module installed
  Device-43: Slot42 type: no module installed
  Device-44: Slot43 type: no module installed
  Device-45: Slot44 type: no module installed
  Device-46: Slot45 type: no module installed
  Device-47: Slot46 type: no module installed
  Device-48: Slot47 type: no module installed
  Device-49: Slot48 type: no module installed
  Device-50: Slot49 type: no module installed
  Device-51: Slot50 type: no module installed
  Device-52: Slot51 type: no module installed
  Device-53: Slot52 type: no module installed
  Device-54: Slot53 type: no module installed
  Device-55: Slot54 type: no module installed
  Device-56: Slot55 type: no module installed
  Device-57: Slot56 type: no module installed
  Device-58: Slot57 type: no module installed
  Device-59: Slot58 type: no module installed
  Device-60: Slot59 type: no module installed
  Device-61: Slot60 type: no module installed
  Device-62: Slot61 type: no module installed
  Device-63: Slot62 type: no module installed
  Device-64: Slot63 type: no module installed
PCI Slots:
  Slot: N/A type: ISA bits: 16 status: unknown info: J8 length: short
    volts: 5.0 bus-ID: 00ff:ff:1f.7
  Slot: N/A type: ISA bits: 16 status: unknown info: J9 length: short
    volts: 5.0 bus-ID: 00ff:ff:1f.7
  Slot: N/A type: ISA bits: 16 status: unknown info: J10 length: short
    volts: 5.0 bus-ID: 00ff:ff:1f.7
  Slot: 1 type: PCI bits: 32 status: in use info: J11 length: long
    volts: 3.3 bus-ID: 00:0f.0
  Slot: 2 type: PCI bits: 32 status: in use info: J12 length: long
    volts: 3.3 bus-ID: 00:10.0
  Slot: 3 type: PCI bits: 32 status: in use info: J13 length: long
    volts: 3.3 bus-ID: 00:11.0
  Slot: 4 type: PCI bits: 32 status: available info: J14 length: long
    volts: 3.3 bus-ID: 00:12.0
CPU:
  Info: 4x 1-core model: AMD Ryzen 7 3700X bits: 64 type: SMP
    smt: <unsupported> arch: Zen 2 level: v3 rev: 0 cache: L1: 4x 64 KiB (256
    KiB) L2: 4x 512 KiB (2 MiB) L3: 4x 32 MiB (128 MiB)
  Speed (MHz): avg: 3600 min/max: N/A volts: 3.3 V cores: 1: 3600 2: 3600
    3: 3600 4: 3600 bogomips: 28800
  Flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports:
    active: Virtual-1 empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5,
    Virtual-6, Virtual-7, Virtual-8 bus-ID: 00:0f.0 chip-ID: 15ad:0405
    class-ID: 0300
  Display: x11 server: X.Org v: 1.20.11 compositor: xfwm v: 4.16.1 driver:
    X: loaded: vmware unloaded: fbdev,modesetting,vesa gpu: vmwgfx
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1718x928 s-dpi: 96 s-size: 454x245mm (17.87x9.65")
    s-diag: 516mm (20.31")
  Monitor-1: Virtual-1 mapped: Virtual1 res: 1718x928 hz: 60 size: N/A
    modes: max: 1718x928 min: 640x480
  OpenGL: renderer: llvmpipe (LLVM 14.0.6 256 bits) v: 4.5 Mesa 22.2.0-rc3
    direct render: Yes
Audio:
  Device-1: Ensoniq ES1371/ES1373 / Creative Labs CT2518 driver: snd_ens1371
    v: kernel bus-ID: 02:02.0 chip-ID: 1274:1371 class-ID: 0401
  Sound Server-1: ALSA v: k5.18.0-kali7-amd64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: yes
Network:
  Device-1: Intel 82371AB/EB/MB PIIX4 ACPI vendor: VMware Virtual Machine
    type: network bridge driver: N/A port: N/A bus-ID: 00:07.3
    chip-ID: 8086:7113 class-ID: 0680
  Device-2: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT
    Single Port driver: e1000 v: kernel port: 2000 bus-ID: 02:01.0
    chip-ID: 8086:100f class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: VMware Virtual Bluetooth Adapter type: USB driver: btusb v: 0.8
    bus-ID: 2-2.1:4 chip-ID: 0e0f:0008 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: <filter>
  Device-2: TP-Link UB500 Adapter type: USB driver: btusb v: 0.8
    bus-ID: 2-2.2:9 chip-ID: 2357:0604 class-ID: e001 serial: <filter>
  Report: ID: hci1 rfk-id: 5 state: down bt-service: disabled rfk-block:
    hardware: no software: no address: <filter>
Drives:
  Local Storage: total: 80 GiB used: 22.49 GiB (28.1%)
  ID-1: /dev/sda vendor: VMware model: Virtual S size: 80 GiB type: N/A
    serial: N/A rev: 1.0 scheme: MBR
Partition:
  ID-1: / size: 76.23 GiB used: 22.49 GiB (29.5%) fs: ext4 dev: /dev/sda1
Swap:
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda5
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Repos:
  Packages: pm: dpkg pkgs: 3283
  Active apt repos in: /etc/apt/sources.list
    1: deb http://http.kali.org/kali kali-rolling main non-free contrib
Info:
  Processes: 204 Uptime: 26m wakeups: 1521 Init: systemd v: 251
  target: graphical (5) default: graphical Compilers: gcc: 12.2.0
  alt: 10/11/12 clang: 8.0.1-4 Shell: Bash (sudo) v: 5.2.0-rc2
  running-in: xfce4-terminal inxi: 3.3.21
BOOT_IMAGE=/boot/vmlinuz-5.18.0-kali7-amd64 root=UUID=d339729e-3161-42a4-83f2-bcdf68c192b2 ro quiet splash
xtrx/0.0.1+git20190320.5ae3a3e-3kali1, 5.18.0-kali7-amd64, x86_64: installed
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 5 bluetooth hci1   unblocked unblocked
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 009: ID 2357:0604 TP-Link TP-Link UB500 Adapter
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Virtual Bluetooth Adapter
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda       
sda1 ext4 1.0  d339729e-3161-42a4-83f2-bcdf68c192b2 49.8G 30% /
sda2       
sda5 swap 1  372746d0-df7d-485a-a21e-1475e9102454   [SWAP]
sr0       
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 01)
	Subsystem: VMware Virtual Machine Chipset [15ad:1976]
	Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge [8086:7191] (rev 01)
00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 08)
	Subsystem: VMware Virtual Machine Chipset [15ad:1976]
00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01)
	Subsystem: VMware Virtual Machine Chipset [15ad:1976]
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix, ata_generic
00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08)
	Subsystem: VMware Virtual Machine Chipset [15ad:1976]
	Kernel modules: i2c_piix4
00:07.7 System peripheral [0880]: VMware Virtual Machine Communication Interface [15ad:0740] (rev 10)
	Subsystem: VMware Virtual Machine Communication Interface [15ad:0740]
	Kernel driver in use: vmw_vmci
	Kernel modules: vmw_vmci
00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405]
	Subsystem: VMware SVGA II Adapter [15ad:0405]
	Kernel driver in use: vmwgfx
	Kernel modules: vmwgfx
00:10.0 SCSI storage controller [0100]: Broadcom / LSI 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01)
	Subsystem: VMware LSI Logic Parallel SCSI Controller [15ad:1976]
	Kernel driver in use: mptspi
	Kernel modules: mptspi
00:11.0 PCI bridge [0604]: VMware PCI bridge [15ad:0790] (rev 02)
	Subsystem: VMware PCI bridge [15ad:0790]
00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:15.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:15.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:15.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:15.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:15.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:15.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:15.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:16.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:16.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:16.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:16.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:16.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:16.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:16.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:16.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:17.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:17.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:17.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:17.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:17.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:17.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:17.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:17.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:18.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:18.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:18.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:18.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:18.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:18.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:18.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
00:18.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
	Subsystem: VMware PCI Express Root Port [15ad:07a0]
	Kernel driver in use: pcieport
02:00.0 USB controller [0c03]: VMware USB1.1 UHCI Controller [15ad:0774]
	Subsystem: VMware USB1.1 UHCI Controller [15ad:1976]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd
02:01.0 Ethernet controller [0200]: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) [8086:100f] (rev 01)
	Subsystem: VMware PRO/1000 MT Single Port Adapter [15ad:0750]
	Kernel driver in use: e1000
	Kernel modules: e1000
02:02.0 Multimedia audio controller [0401]: Ensoniq ES1371/ES1373 / Creative Labs CT2518 [1274:1371] (rev 02)
	Subsystem: Ensoniq Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI] [1274:1371]
	Kernel driver in use: snd_ens1371
	Kernel modules: snd_ens1371
02:03.0 USB controller [0c03]: VMware USB2 EHCI Controller [15ad:0770]
	Subsystem: VMware USB2 EHCI Controller [15ad:0770]
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci
btusb                  65536  0
btrtl                  28672  1 btusb
btbcm                  24576  1 btusb
btintel                45056  1 btusb
btmtk                  16384  1 btusb
bluetooth             888832  7 btrtl,btmtk,btintel,btbcm,btusb
ecdh_generic           16384  1 bluetooth
rfkill                 32768  3 bluetooth
crc16                  16384  2 bluetooth,ext4
usbcore               331776  5 ehci_pci,usbhid,ehci_hcd,btusb,uhci_hcd
[    0.004287] On node 0, zone DMA: 1 pages in unavailable ranges
[    0.004393] On node 0, zone DMA: 97 pages in unavailable ranges
[    0.025268] On node 0, zone DMA32: 32 pages in unavailable ranges
[    0.034861] Unknown kernel command line parameters "splash BOOT_IMAGE=/boot/vmlinuz-5.18.0-kali7-amd64", will be passed to user space.
[    0.080773] RETBleed: Mitigation: untrained return thunk
[    0.106657] node 0 deferred pages initialised in 16ms
[    0.109956] thermal_sys: Registered thermal governor 'fair_share'
[    0.109956] pmd_set_huge: Cannot satisfy [mem 0xf0000000-0xf0200000] with a huge-page mapping due to MTRR override.
[    0.118592] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.123174] ACPI: Using IOAPIC for interrupt routing
[    0.212285] pci 0000:00:11.0: PCI bridge to [bus 02] (subtractive decode)
[    0.212352] pci 0000:00:11.0:   bridge window [mem 0x000a0000-0x000bffff window] (subtractive decode)
[    0.212353] pci 0000:00:11.0:   bridge window [mem 0x000cc000-0x000dbfff window] (subtractive decode)
[    0.212354] pci 0000:00:11.0:   bridge window [mem 0xc0000000-0xfebfffff window] (subtractive decode)
[    0.212355] pci 0000:00:11.0:   bridge window [io  0x0000-0x0cf7 window] (subtractive decode)
[    0.212356] pci 0000:00:11.0:   bridge window [io  0x0d00-0xfeff window] (subtractive decode)
[    0.223689] ACPI: PCI: Interrupt link LNKA configured for IRQ 9
[    0.223745] ACPI: PCI: Interrupt link LNKB configured for IRQ 11
[    0.223829] ACPI: PCI: Interrupt link LNKC configured for IRQ 10
[    0.223882] ACPI: PCI: Interrupt link LNKD configured for IRQ 5
[    0.262717] pci 0000:00:15.3: BAR 13: failed to assign [io  size 0x1000]
[    0.262720] pci 0000:00:15.4: BAR 13: failed to assign [io  size 0x1000]
[    0.262722] pci 0000:00:15.5: BAR 13: failed to assign [io  size 0x1000]
[    0.262724] pci 0000:00:15.6: BAR 13: failed to assign [io  size 0x1000]
[    0.262726] pci 0000:00:15.7: BAR 13: failed to assign [io  size 0x1000]
[    0.262728] pci 0000:00:16.3: BAR 13: failed to assign [io  size 0x1000]
[    0.262730] pci 0000:00:16.4: BAR 13: failed to assign [io  size 0x1000]
[    0.262733] pci 0000:00:16.5: BAR 13: failed to assign [io  size 0x1000]
[    0.262735] pci 0000:00:16.6: BAR 13: failed to assign [io  size 0x1000]
[    0.262737] pci 0000:00:16.7: BAR 13: failed to assign [io  size 0x1000]
[    0.262739] pci 0000:00:17.3: BAR 13: failed to assign [io  size 0x1000]
[    0.262741] pci 0000:00:17.4: BAR 13: failed to assign [io  size 0x1000]
[    0.262743] pci 0000:00:17.5: BAR 13: failed to assign [io  size 0x1000]
[    0.262745] pci 0000:00:17.6: BAR 13: failed to assign [io  size 0x1000]
[    0.262747] pci 0000:00:17.7: BAR 13: failed to assign [io  size 0x1000]
[    0.262750] pci 0000:00:18.2: BAR 13: failed to assign [io  size 0x1000]
[    0.262752] pci 0000:00:18.3: BAR 13: failed to assign [io  size 0x1000]
[    0.262754] pci 0000:00:18.4: BAR 13: failed to assign [io  size 0x1000]
[    0.262756] pci 0000:00:18.5: BAR 13: failed to assign [io  size 0x1000]
[    0.262758] pci 0000:00:18.6: BAR 13: failed to assign [io  size 0x1000]
[    0.262760] pci 0000:00:18.7: BAR 13: failed to assign [io  size 0x1000]
[    0.262763] pci 0000:00:18.7: BAR 13: failed to assign [io  size 0x1000]
[    0.262766] pci 0000:00:18.6: BAR 13: failed to assign [io  size 0x1000]
[    0.262768] pci 0000:00:18.5: BAR 13: failed to assign [io  size 0x1000]
[    0.262770] pci 0000:00:18.4: BAR 13: failed to assign [io  size 0x1000]
[    0.262772] pci 0000:00:18.3: BAR 13: failed to assign [io  size 0x1000]
[    0.262774] pci 0000:00:18.2: BAR 13: failed to assign [io  size 0x1000]
[    0.262776] pci 0000:00:17.7: BAR 13: failed to assign [io  size 0x1000]
[    0.262778] pci 0000:00:17.6: BAR 13: failed to assign [io  size 0x1000]
[    0.262780] pci 0000:00:17.5: BAR 13: failed to assign [io  size 0x1000]
[    0.262782] pci 0000:00:17.4: BAR 13: failed to assign [io  size 0x1000]
[    0.262784] pci 0000:00:17.3: BAR 13: failed to assign [io  size 0x1000]
[    0.262786] pci 0000:00:16.7: BAR 13: failed to assign [io  size 0x1000]
[    0.262789] pci 0000:00:16.6: BAR 13: failed to assign [io  size 0x1000]
[    0.262791] pci 0000:00:16.5: BAR 13: failed to assign [io  size 0x1000]
[    0.262793] pci 0000:00:16.4: BAR 13: failed to assign [io  size 0x1000]
[    0.262795] pci 0000:00:16.3: BAR 13: failed to assign [io  size 0x1000]
[    0.262797] pci 0000:00:15.7: BAR 13: failed to assign [io  size 0x1000]
[    0.262799] pci 0000:00:15.6: BAR 13: failed to assign [io  size 0x1000]
[    0.262801] pci 0000:00:15.5: BAR 13: failed to assign [io  size 0x1000]
[    0.262803] pci 0000:00:15.4: BAR 13: failed to assign [io  size 0x1000]
[    0.262805] pci 0000:00:15.3: BAR 13: failed to assign [io  size 0x1000]
[    0.797465] pcieport 0000:00:15.0: pciehp: Slot #160 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.798360] pcieport 0000:00:15.1: pciehp: Slot #161 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.799206] pcieport 0000:00:15.2: pciehp: Slot #162 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.800045] pcieport 0000:00:15.3: pciehp: Slot #163 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.800877] pcieport 0000:00:15.4: pciehp: Slot #164 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.801720] pcieport 0000:00:15.5: pciehp: Slot #165 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.802556] pcieport 0000:00:15.6: pciehp: Slot #166 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.803388] pcieport 0000:00:15.7: pciehp: Slot #167 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.804245] pcieport 0000:00:16.0: pciehp: Slot #192 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.805136] pcieport 0000:00:16.1: pciehp: Slot #193 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.806022] pcieport 0000:00:16.2: pciehp: Slot #194 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.806870] pcieport 0000:00:16.3: pciehp: Slot #195 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.807706] pcieport 0000:00:16.4: pciehp: Slot #196 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.808580] pcieport 0000:00:16.5: pciehp: Slot #197 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.809455] pcieport 0000:00:16.6: pciehp: Slot #198 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.810276] pcieport 0000:00:16.7: pciehp: Slot #199 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.811101] pcieport 0000:00:17.0: pciehp: Slot #224 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.811950] pcieport 0000:00:17.1: pciehp: Slot #225 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.812802] pcieport 0000:00:17.2: pciehp: Slot #226 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.813633] pcieport 0000:00:17.3: pciehp: Slot #227 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.814519] pcieport 0000:00:17.4: pciehp: Slot #228 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.815370] pcieport 0000:00:17.5: pciehp: Slot #229 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.816202] pcieport 0000:00:17.6: pciehp: Slot #230 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.817031] pcieport 0000:00:17.7: pciehp: Slot #231 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.817878] pcieport 0000:00:18.0: pciehp: Slot #256 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.818739] pcieport 0000:00:18.1: pciehp: Slot #257 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.819562] pcieport 0000:00:18.2: pciehp: Slot #258 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.820442] pcieport 0000:00:18.3: pciehp: Slot #259 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.821287] pcieport 0000:00:18.4: pciehp: Slot #260 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.822179] pcieport 0000:00:18.5: pciehp: Slot #261 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.822997] pcieport 0000:00:18.6: pciehp: Slot #262 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.823843] pcieport 0000:00:18.7: pciehp: Slot #263 AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Interlock- NoCompl+ IbPresDis- LLActRep+
[    1.891188] sd 2:0:0:0: [sda] Cache data unavailable
[    2.636865] usb 2-2.1: Product: Virtual Bluetooth Adapter
[    7.152151] systemd[1]: Kernel Module supporting RPCSEC_GSS was skipped because of a failed condition check (ConditionPathExists=/etc/krb5.keytab).
[    7.155758] systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathExists=!/run/initramfs/fsck-root).
[    7.167425] systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
[    7.791496] systemd[1]: Platform Persistent Storage Archival was skipped because of a failed condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore).
[   15.246816] Bluetooth: Core ver 2.22
[   15.246854] NET: Registered PF_BLUETOOTH protocol family
[   15.246855] Bluetooth: HCI device and connection manager initialized
[   15.246858] Bluetooth: HCI socket layer initialized
[   15.246860] Bluetooth: L2CAP socket layer initialized
[   15.246863] Bluetooth: SCO socket layer initialized
[   15.575462] usbcore: registered new interface driver btusb
[   16.205357] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=0d99 lmp_ver=0a lmp_subver=646b
[   16.276976] Bluetooth: hci0: unexpected cc 0x0c12 length: 2 < 3
[   16.276986] Bluetooth: hci0: Opcode 0x c12 failed: -38
[   16.416362] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[   16.419345] Bluetooth: hci1: RTL: rom_version status=0 version=1
[   16.419348] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin
[   16.561627] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_fw.bin
[   16.561646] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin
[   16.561975] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_config.bin
[   16.561988] Bluetooth: hci1: RTL: cfg_sz 25, total sz 21389
[   16.807368] Bluetooth: hci1: RTL: fw version 0x0d99646b
[  197.763310] Bluetooth: hci1: command 0x0c23 tx timeout
[  544.117295] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[  544.123315] Bluetooth: hci1: RTL: rom_version status=0 version=1
[  544.123319] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin
[  544.123349] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_fw.bin
[  544.123364] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin
[  544.123373] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_config.bin
[  544.123383] Bluetooth: hci1: RTL: cfg_sz 25, total sz 21389
[  545.294298] Bluetooth: hci1: RTL: fw version 0x0d99646b
[  559.061995] Bluetooth: hci1: command 0x0c14 tx timeout
[  572.051897] hub 2-2:1.0: hub_ext_port_status failed (err = -110)
[ 1014.638245] hub 2-2:1.0: hub_ext_port_status failed (err = -110)
[ 1101.429271] hub 2-2:1.0: hub_ext_port_status failed (err = -110)
[ 1127.614910] Bluetooth: hci1: command 0x0c23 tx timeout
[ 1168.339753] hub 2-2:1.0: hub_ext_port_status failed (err = -110)
[ 1178.227537] Bluetooth: hci1: command 0x0c23 tx timeout
[ 1363.960302] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[ 1363.973214] Bluetooth: hci1: RTL: rom_version status=0 version=1
[ 1363.973219] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin
[ 1363.973270] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_fw.bin
[ 1363.973308] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin
[ 1363.973323] bluetooth hci1: firmware: direct-loading firmware rtl_bt/rtl8761bu_config.bin
[ 1363.973333] Bluetooth: hci1: RTL: cfg_sz 25, total sz 21389
[ 1365.055363] Bluetooth: hci1: RTL: fw version 0x0d99646b
schmafu
Level 1
Level 1
Posts: 5
Joined: Fri Sep 30, 2022 4:47 am

Re: UB500 (rtl8761b chipset) timeout

Post by schmafu »

@hglee: I am still struggling with this problem :( Have you had time to have a brief look?
User avatar
hglee
Level 6
Level 6
Posts: 1423
Joined: Fri Jun 22, 2018 4:31 pm

Re: UB500 (rtl8761b chipset) timeout

Post by hglee »

schmafu wrote:
Sat Oct 01, 2022 11:44 am

Code: Select all

System:
  Kernel: 5.18.0-kali7-amd64 arch: x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Xfce v: 4.16.1 tk: Gtk v: 3.24.34 info: xfce4-panel wm: xfwm
    v: 4.16.1 dm: LightDM v: 1.26.0 Distro: Kali GNU/Linux 2022.3
    kali-rolling base: Debian testing

That's Kali Linux, not Mint.

Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
sleeper12
Level 20
Level 20
Posts: 11225
Joined: Thu May 25, 2017 3:22 pm

Re: UB500 (rtl8761b chipset) timeout

Post by sleeper12 »

I don't know if it will work since you are not even on Mint, but JeremyB gave a solution here:
viewtopic.php?p=2140102#p2140102
schmafu
Level 1
Level 1
Posts: 5
Joined: Fri Sep 30, 2022 4:47 am

Re: UB500 (rtl8761b chipset) timeout

Post by schmafu »

hglee wrote:
Thu Oct 06, 2022 2:26 am

That's Kali Linux, not Mint.
Both are Debian based :wink: And you would really help me out here :D
sleeper12 wrote:
Thu Oct 06, 2022 10:49 am
I don't know if it will work since you are not even on Mint, but JeremyB gave a solution here:
viewtopic.php?p=2140102#p2140102
Thank you for the tip. I tried to compile it, however, if fails already when trying to compile btusb.c. I am on kernel 5.18.16 which does not have the prevent_wake definition of the hci_dev struct in the hci_core header any more :? I also tried to boot into the next best old kernel that I had 5.9, however, the compilation failed there as well...

Any ideas?

Code: Select all

kali@kali:~/sandbox/bluetooth-5.13$ make
make -C /lib/modules/5.18.0-kali7-amd64/build M=/home/kali/sandbox/bluetooth-5.13 modules
make[1]: Entering directory '/usr/src/linux-headers-5.18.0-kali7-amd64'
  CC [M]  /home/kali/sandbox/bluetooth-5.13/btusb.o
/home/kali/sandbox/bluetooth-5.13/btusb.c: In function ‘btusb_setup_intel_new’:
/home/kali/sandbox/bluetooth-5.13/btusb.c:2966:23: warning: assignment discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
 2966 |                 match = usb_match_id(data->intf, msft_rej_table);
      |                       ^
/home/kali/sandbox/bluetooth-5.13/btusb.c: In function ‘btusb_probe’:
/home/kali/sandbox/bluetooth-5.13/btusb.c:4660:13: error: ‘struct hci_dev’ has no member named ‘prevent_wake’
 4660 |         hdev->prevent_wake = btusb_prevent_wake;
      |             ^~
make[2]: *** [/usr/src/linux-headers-5.18.0-kali7-common/scripts/Makefile.build:294: /home/kali/sandbox/bluetooth-5.13/btusb.o] Error 1
make[1]: *** [/usr/src/linux-headers-5.18.0-kali7-common/Makefile:1862: /home/kali/sandbox/bluetooth-5.13] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.18.0-kali7-amd64'
sleeper12
Level 20
Level 20
Posts: 11225
Joined: Thu May 25, 2017 3:22 pm

Re: UB500 (rtl8761b chipset) timeout

Post by sleeper12 »

schmafu wrote:
Fri Oct 07, 2022 1:57 am
Any ideas?
None, maybe ask on Kali Linux Forums:
https://forums.kali.org/
User avatar
hglee
Level 6
Level 6
Posts: 1423
Joined: Fri Jun 22, 2018 4:31 pm

Re: UB500 (rtl8761b chipset) timeout

Post by hglee »

sleeper12 wrote:
Fri Oct 07, 2022 11:35 am
schmafu wrote:
Fri Oct 07, 2022 1:57 am
Any ideas?
None, maybe ask on Kali Linux Forums:
https://forums.kali.org/

Unless you use a VPN, then a click on that link results in ...

https://forums.kali.org/ wrote:
Not Found

The requested URL was not found on this server.

Apache/2.4.25 (Debian) Server at forums.kali.org Port 443

The Kali hacker reputation must breed some control-freak paranoia.

Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
sleeper12
Level 20
Level 20
Posts: 11225
Joined: Thu May 25, 2017 3:22 pm

Re: UB500 (rtl8761b chipset) timeout

Post by sleeper12 »

I dunno, that url works fine for me with no VPN.
User avatar
hglee
Level 6
Level 6
Posts: 1423
Joined: Fri Jun 22, 2018 4:31 pm

Re: UB500 (rtl8761b chipset) timeout

Post by hglee »

sleeper12 wrote:
Fri Oct 07, 2022 1:16 pm
I dunno, that url works fine for me with no VPN.

That's its raison d'être: The gate is closed to VPNs.

I run Waterfox through a VPN, and Firefox without it. Waterfox is blocked, Firefox sails on through.

Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
Post Reply

Return to “Hardware Support”