I am using dual boot win 11 and fedora 42 on two different hard drives. My computer uses mercusys adapter ma530 with bluetooth function. When using win 11, the bluetooth function still works normally, but when switching to fedora, the function fails and cannot find the device to connect. I have tried many ways such as updating the kernel, ... but all failed. My comupter cpu: i3-10100f main: h410 s2h gpu: rx6500xt batrung@fedora:~$ hciconfig hci0: Type: Primary Bus: USB BD Address: 08:8A:F1:18:80:1E ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:7103 acl:0 sco:0 events:1205 errors:0 TX bytes:17608 acl:0 sco:0 commands:1020 errors:0 batrung@fedora:~$ sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: active (running) since Mon 2025-06-30 02:46:32 +07; 50min ago Invocation: b26f9c9b2d2f44198aaf39bd722d3caf Docs: man:bluetoothd(8) Main PID: 916 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18876) Memory: 2.5M (peak: 3.7M) CPU: 152ms CGroup: /system.slice/bluetooth.service └─916 /usr/libexec/bluetooth/bluetoothd Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEnd> Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEnd> Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEnd> Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEnd> Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEnd> Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEnd> Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEnd> Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEnd> Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEnd> Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEnd> lines 1-25/25 (END)...skipping... ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: active (running) since Mon 2025-06-30 02:46:32 +07; 50min ago Invocation: b26f9c9b2d2f44198aaf39bd722d3caf Docs: man:bluetoothd(8) Main PID: 916 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18876) Memory: 2.5M (peak: 3.7M) CPU: 152ms CGroup: /system.slice/bluetooth.service └─916 /usr/libexec/bluetooth/bluetoothd Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSink/opus_g Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/opus_g Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSink/sbc Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/sbc Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/faststream Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/faststream_duplex Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSink/opus_05 Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/opus_05 Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSink/opus_05_duplex Jun 30 02:47:41 fedora bluetoothd[916]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/opus_05_duplex ~ Reproducible: Always
FEDORA-2025-c10d623d39 (bluez-5.83-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-c10d623d39
FEDORA-2025-e53a11a6d0 (bluez-5.83-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-e53a11a6d0
FEDORA-2025-c10d623d39 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c10d623d39` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c10d623d39 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-e53a11a6d0 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-e53a11a6d0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-e53a11a6d0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-c10d623d39 (bluez-5.83-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-e53a11a6d0 (bluez-5.83-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.