Closed fellipec closed 1 month ago
Update: I was forced to change the USB dongle. The new one, looks like the same chipset but works flawlessly:
[ 2.437174] usb 3-4: Product: Bluetooth Radio
[ 4.057471] Bluetooth: Core ver 2.22
[ 4.057495] NET: Registered PF_BLUETOOTH protocol family
[ 4.057496] Bluetooth: HCI device and connection manager initialized
[ 4.057500] Bluetooth: HCI socket layer initialized
[ 4.057503] Bluetooth: L2CAP socket layer initialized
[ 4.057507] Bluetooth: SCO socket layer initialized
[ 4.118025] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[ 4.120027] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 4.120033] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[ 4.122743] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[ 4.123182] Bluetooth: hci0: RTL: cfg_sz 25, total sz 31189
[ 4.398020] Bluetooth: hci0: RTL: fw version 0x9dc6d922
[ 9.860857] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.860862] Bluetooth: BNEP filters: protocol multicast
[ 9.860868] Bluetooth: BNEP socket layer initialized
[ 9.862237] Bluetooth: MGMT ver 1.22
[ 12.361169] Bluetooth: RFCOMM TTY layer initialized
[ 12.361180] Bluetooth: RFCOMM socket layer initialized
[ 12.361187] Bluetooth: RFCOMM ver 1.11
[ 19.607987] input: Microsoft Bluetooth Mouse as /devices/virtual/misc/uhid/0005:045E:082F.0005/input/input25
[ 19.608312] input: Microsoft Bluetooth Mouse Keyboard as /devices/virtual/misc/uhid/0005:045E:082F.0005/input/input26
[ 19.608520] input: Microsoft Bluetooth Mouse as /devices/virtual/misc/uhid/0005:045E:082F.0005/input/input27
[ 19.608656] hid-generic 0005:045E:082F.0005: input,hidraw4: BLUETOOTH HID v2.12 Mouse [Microsoft Bluetooth Mouse] on 00:e0:4c:b0:db:03
[13021.481367] input: Microsoft Bluetooth Mouse as /devices/virtual/misc/uhid/0005:045E:082F.0006/input/input28
[13021.481570] input: Microsoft Bluetooth Mouse Keyboard as /devices/virtual/misc/uhid/0005:045E:082F.0006/input/input29
[13021.481732] input: Microsoft Bluetooth Mouse as /devices/virtual/misc/uhid/0005:045E:082F.0006/input/input30
[13021.481930] hid-generic 0005:045E:082F.0006: input,hidraw4: BLUETOOTH HID v2.12 Mouse [Microsoft Bluetooth Mouse] on 00:e0:4c:b0:db:03
I'll not rule out the old dongle as defective because it works very well in Windows. But for some reason, this new one, even using the same driver, work well.
I'm still open to any questions to help, if needed.
Thanks @fellipec, I think this should be reported upstream on Launchpad for 24.04 since it's completely upstream from us and can be reproduced with Noble directly.
I've a kind of generic USB Bluetooth adapter, that uses a Realtek 8761 firmware.
In Linux Mint 21.3 there was a bug that made the system load the wrong firmware. Instead of loading the file the file
rtl8761b_fw.bin
it loaded the filertl8761bu_fw.bin
. I found out about a workaround in Linux Mint foruns and it solved the problem.In fact, I found out that there was bug into Ubuntu, which was fixed last year in jammy version, and as far as I understood the noble version should not have it.
Turns out that Mint 22 beta is trying to load the wrong firmware, like 21.3 and Ubuntu Jammy before the fix, as can be seen in this
dmesg
excerpt when I plug the USB adapter:The blueman GUI can't scan for devices and in
dmesg
we can see the messagetx timeout
, like above.Troubleshooting steps
The first thing I did was to try the same workwaround that fixed the problem in the previous version:
Plugged and unplugged the USB dongle and not changed anything:
I rebooted the system, and still not worked. But after removing and reinserting the USB dongle, it worked and I was able to pair my mouse:
Tryed once more to be sure:
Just to be more complete, I downloaded a Ubuntu Noble Nobat live image and booted it. Again my USB dongle didn't work out of the box, but after unplugging and plugging again, it worked without having to mess with driver files. I manged to copy the dmesg output too:
I'm aware that Realtek devices aren't the best ones for use with Linux, but I need a 5.0 adapter (because the XBox controller and a headphone) and I already bought two from different brands and turned out to be the same Realtek chipset.
I hope this bug report can be useful and is complete enough to be of value. I'm open to do more tests and help if needed.