You are not logged in.

#1 2024-03-20 00:18:01

anyone_yun
Member
Registered: 2024-03-20
Posts: 2

TP-Link UB500 Bluetooth Dongle issues

Hi all, I have just bought a TP-Link UB500 after reading it has been working well for some users and it being supported by default on newer kernels. Now I do have some issues and I'm unable to solve them. First of all, when a device is paired, it works but after a reboot it stops and I have to re-pair it again. Another workaround is to disconnect the dongle and reconnect it.
The other thing is, when suspending my system the bluetooth service seems to hang the computer, requiring a hard reboot.
I already checked some things, rfkill is not blocking bluetooth, dmesg and journalctl don't show any particular error.
The bluetooth.service status also seems normal.
Any idea? Thanks!

Offline

#2 2024-03-20 08:59:31

anyone_yun
Member
Registered: 2024-03-20
Posts: 2

Re: TP-Link UB500 Bluetooth Dongle issues

After some other testing, journalctl returns:

mar 20 09:50:26 archlinuxdesktop systemd[861]: Reached target Bluetooth.
mar 20 09:50:26 archlinuxdesktop kernel: hid-generic 0005:057E:2009.000F: unknown main item tag 0x0
mar 20 09:50:26 archlinuxdesktop kernel: input: Pro Controller as /devices/virtual/misc/uhid/0005:057E:2009.000F/input/input30
mar 20 09:50:26 archlinuxdesktop kernel: hid-generic 0005:057E:2009.000F: input,hidraw14: BLUETOOTH HID v0.01 Gamepad [Pro Controller] on e8:48:b8:c8:20:00
mar 20 09:50:26 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: unknown main item tag 0x0
mar 20 09:50:26 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: hidraw14: BLUETOOTH HID v80.01 Gamepad [Pro Controller] on e8:48:b8:c8:20:00
mar 20 09:50:27 archlinuxdesktop plasmashell[1187]: file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/FullRepresentation.qml:65:13: QML Toolbar: Binding loop detected for property "leftInset"
mar 20 09:50:30 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: failed reading SPI flash; ret=-110
mar 20 09:50:30 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: using factory cal for left stick
mar 20 09:50:32 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: failed reading SPI flash; ret=-110
mar 20 09:50:32 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: using factory cal for right stick
mar 20 09:50:34 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: failed reading SPI flash; ret=-110
mar 20 09:50:34 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: Failed to read left stick cal, using defaults; e=-110
mar 20 09:50:36 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: failed reading SPI flash; ret=-110
mar 20 09:50:36 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: Failed to read right stick cal, using defaults; e=-110
mar 20 09:50:38 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: failed reading SPI flash; ret=-110
mar 20 09:50:38 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: using factory cal for IMU
mar 20 09:50:40 archlinuxdesktop systemd-timesyncd[678]: Timed out waiting for reply from 162.159.200.1:123 (2.arch.pool.ntp.org).
mar 20 09:50:40 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: failed reading SPI flash; ret=-110
mar 20 09:50:40 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: Failed to read IMU cal, using defaults; ret=-110
mar 20 09:50:40 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: Unable to read IMU calibration data
mar 20 09:50:40 archlinuxdesktop systemd-timesyncd[678]: Contacted time server 194.58.207.148:123 (2.arch.pool.ntp.org).
mar 20 09:50:40 archlinuxdesktop systemd-timesyncd[678]: Initial clock synchronization to Wed 2024-03-20 09:50:40.500366 CET.
mar 20 09:50:42 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: Failed to set report mode; ret=-110
mar 20 09:50:42 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: Failed to initialize controller; ret=-110
mar 20 09:50:42 archlinuxdesktop kernel: nintendo 0005:057E:2009.000F: probe - fail = -110
mar 20 09:50:42 archlinuxdesktop kernel: nintendo: probe of 0005:057E:2009.000F failed with error -110

Instead, when the dongle is unplugged and plugged back in, journalctl says:

mar 20 09:57:03 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: unknown main item tag 0x0
mar 20 09:57:03 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: hidraw14: BLUETOOTH HID v80.01 Gamepad [Pro Controller] on e8:48:b8:c8:20:00
mar 20 09:57:07 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: failed reading SPI flash; ret=-110
mar 20 09:57:07 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: using factory cal for left stick
mar 20 09:57:09 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: failed reading SPI flash; ret=-110
mar 20 09:57:09 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: using factory cal for right stick
mar 20 09:57:11 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: failed reading SPI flash; ret=-110
mar 20 09:57:11 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: Failed to read left stick cal, using defaults; e=-110
mar 20 09:57:11 archlinuxdesktop plasmashell[1187]: file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/FullRepresentation.qml:65:13: QML Toolbar: Binding loop detected for property "leftInset"
mar 20 09:57:13 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: failed reading SPI flash; ret=-110
mar 20 09:57:13 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: Failed to read right stick cal, using defaults; e=-110
mar 20 09:57:15 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: failed reading SPI flash; ret=-110
mar 20 09:57:15 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: using factory cal for IMU
mar 20 09:57:15 archlinuxdesktop systemd[861]: Started suyu - Switch Emulator.
mar 20 09:57:17 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: failed reading SPI flash; ret=-110
mar 20 09:57:17 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: Failed to read IMU cal, using defaults; ret=-110
mar 20 09:57:17 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: Unable to read IMU calibration data
mar 20 09:57:18 archlinuxdesktop rtkit-daemon[954]: Successfully made thread 3143 of process 3124 owned by '1000' high priority at nice level -10.
mar 20 09:57:18 archlinuxdesktop rtkit-daemon[954]: Supervising 8 threads of 5 processes of 1 users.
mar 20 09:57:18 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: controller MAC = 98:B6:E9:60:B1:1B
mar 20 09:57:18 archlinuxdesktop kernel: input: Nintendo Switch Pro Controller as /devices/virtual/misc/uhid/0005:057E:2009.0011/input/input31
mar 20 09:57:18 archlinuxdesktop kernel: input: Nintendo Switch Pro Controller IMU as /devices/virtual/misc/uhid/0005:057E:2009.0011/input/input32
mar 20 09:57:23 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: joycon_enforce_subcmd_rate: exceeded max attempts
mar 20 09:57:27 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: joycon_enforce_subcmd_rate: exceeded max attempts
mar 20 09:57:30 archlinuxdesktop kernel: nintendo 0005:057E:2009.0011: joycon_enforce_subcmd_rate: exceeded max attempts
mar 20 09:57:42 archlinuxdesktop plasmashell[1187]: kpipewire_logging: PipeWire remote error:  -2 target not found
mar 20 09:57:42 archlinuxdesktop plasmashell[1187]: kpipewire_logging: PipeWire remote error:  -2 unknown resource 4 op:7
mar 20 09:57:48 archlinuxdesktop plasmashell[1187]: kpipewire_logging: PipeWire remote error:  -2 target not found
mar 20 09:57:48 archlinuxdesktop plasmashell[1187]: kpipewire_logging: PipeWire remote error:  -2 unknown resource 4 op:7

Last edited by anyone_yun (2024-03-20 09:03:41)

Offline

Board footer

Powered by FluxBB