Solved Bluetooth not working on fedora 38

Solved issue
Sunix Unix

Sunix Unix

New Member
Joined
Jun 27, 2023
Messages
7
Reaction score
0
Credits
96
Os:Fedora 38
Desktop:Gnome
pc: hp pavilion 17
Bluetooth does not work for me when I connect the Linux adapter sees it but it says that it is turned off and I cannot turn it on what to do
 


have you checked the output of the command

rfkill

to see if bluetooth is blocked? if it is not blocked and you need to troubleshoot further, it may help to know if the adapter is a usb or is built into the system. either way it should show up in the output of the command

lsusb

if you can post the line that has info about your adapter, that may help.
 
[unix@fedora ~]$ rfkill
ID TYPE DEVICE SOFT HARD
1 wlan phy0 unblocked unblocked
2 bluetooth hci0 unblocked unblocked
[unix@fedora ~]$ lsusb
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 046d:c09d Logitech, Inc. G102 LIGHTSYNC Gaming Mouse
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 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 004: ID 064e:e266 Suyin Corp. HP Truevision HD
Bus 001 Device 003: ID 0c45:760b Microdia USB Keyboard
Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[unix@fedora ~]$
 
you could try checking systemctl status bluetooth to see if the bluetooth service is up and running. you could also try checking bluetoothctl show to see if you have a default controller available.
 
No default controller available

● 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 Tue 2023-06-27 21:08:40 +04; 1h 40min ago
Docs: man:bluetoothd(8)
Main PID: 761 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 6887)
Memory: 2.0M
CPU: 84ms
CGroup: /system.slice/bluetooth.service
└─761 /usr/libexec/bluetooth/bluetoothd

27 21:08:39 fedora bluetoothd[761]: Bluetooth daemon 5.66
27 21:08:40 fedora bluetoothd[761]: Starting SDP server
27 21:08:40 fedora systemd[1]: Started bluetooth.service - Bluetooth service.
27 21:08:40 fedora bluetoothd[761]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
27 21:08:40 fedora bluetoothd[761]: src/plugin.c:plugin_init() Failed to init vcp plugin
27 21:08:40 fedora bluetoothd[761]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
27 21:08:40 fedora bluetoothd[761]: src/plugin.c:plugin_init() Failed to init mcp plugin
27 21:08:40 fedora bluetoothd[761]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
27 21:08:40 fedora bluetoothd[761]: src/plugin.c:plugin_init() Failed to init bap plugin
27 21:08:40 fedora bluetoothd[761]: Bluetooth management interface 1.22 initialized
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-24/24 (END)


I'm new to linux, so I'll send what terinal linux gives out
 
you could try unplugging the adapter, running the command dmesg -w and then plugging the adapter back in. fair warning: dmesg will most likely output a whole lot of info. you only need to look at or share the messages that appear after you plug the adapter back in. on some distributions, you need root authentication to run dmesg. i am not sure if fedora is one of those. if you get any kind of permission error or no output, you could try running sudo dmesg -w

you are looking for any errors or warnings in those messages that may give a hint about why the controller isn't getting set up.
 
Any errors
[ 0.111624] x86/cpu: VMX (outside TXT) disabled by BIOS

[ 15.118878] (sd-execu[499]: /usr/lib/systemd/system-generators/ostree-system-generator failed with exit status 1.

[ 23.016506] debugfs: File 'radeon_ring_gfx' in directory '0' already present!
[ 23.016513] debugfs: File 'radeon_ring_cp1' in directory '0' already present!
[ 23.016517] debugfs: File 'radeon_ring_cp2' in directory '0' already present!
[ 23.016521] debugfs: File 'radeon_ring_dma1' in directory '0' already present!
[ 23.016524] debugfs: File 'radeon_ring_dma2' in directory '0' already present!

[ 63.337895] debugfs: File 'radeon_ring_gfx' in directory '0' already present!
[ 63.337904] debugfs: File 'radeon_ring_cp1' in directory '0' already present!
[ 63.337908] debugfs: File 'radeon_ring_cp2' in directory '0' already present!
[ 63.337912] debugfs: File 'radeon_ring_dma1' in directory '0' already present!
[ 63.337915] debugfs: File 'radeon_ring_dma2' in directory '0' already present

Bluetooth errors(When i plug in)

[ 2894.298430] Bluetooth: hci0: Opcode 0x c03 failed: -110

[ 7041.730181] Bluetooth: hci0: unexpected cc 0x0c25 length: 2 < 3
[ 7041.730195] Bluetooth: hci0: Opcode 0x c25 failed: -38



if you need a full response from the terminal i can send
 
i wouldn't need to see the full response. if you could include the messages from after you plugged the adapter in, that might provide some context.

i see the errors you posted and those might be helpful. i haven't seen those specific ones before. what i generally do with something like

[ 7041.730181] Bluetooth: hci0: unexpected cc 0x0c25 length: 2 < 3

is run a web search for the end without the timestamp (so this part: Bluetooth: hci0: unexpected cc 0x0c25 length: 2 < 3) to see if maybe someone else has posted a similar thread with a solution.

feel free to post the rest of the messages about the bluetooth adapter near the timestamp 7041.730181 and i can look at those and help you do some web searching after i finish lunch :)
 
this is not the full response from the terminal, but this is the full response from the terminal when i plugged in the adapter

[ 2869.947182] usb 1-1: USB disconnect, device number 2
[ 2886.674554] usb 1-1: new full-speed USB device number 5 using xhci_hcd
[ 2886.803436] usb 1-1: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=25.20
[ 2886.803474] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 2886.803482] usb 1-1: Product: CSR8510 A10
[ 2886.807676] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=9 rev=3120
[ 2886.807689] Bluetooth: hci0: LMP ver=9 subver=22bb; manufacturer=10
[ 2886.807695] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once...
[ 2892.251191] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround
[ 2892.251304] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported.
[ 2892.251314] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
[ 2892.251320] Bluetooth: hci0: HCI Set Event Filter command not supported.
[ 2894.298430] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 3301.583016] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[ 5472.393739] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[ 6985.079930] usb 1-1: USB disconnect, device number 5
[ 7041.555310] usb 1-1: new full-speed USB device number 6 using xhci_hcd
[ 7041.684098] usb 1-1: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=25.20
[ 7041.684113] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 7041.684117] usb 1-1: Product: CSR8510 A10
[ 7041.688232] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=9 rev=3120
[ 7041.688248] Bluetooth: hci0: LMP ver=9 subver=22bb; manufacturer=10
[ 7041.688252] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once...
[ 7041.688255] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround
[ 7041.688325] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported.
[ 7041.688329] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
[ 7041.688332] Bluetooth: hci0: HCI Set Event Filter command not supported.
[ 7041.730181] Bluetooth: hci0: unexpected cc 0x0c25 length: 2 < 3
[ 7041.730195] Bluetooth: hci0: Opcode 0x c25 failed: -38
[ 7124.374482] perf: interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
 
thank you. i think that might be helpful. have you gotten this adapter to work with any other linux distribution?

the reason i ask is this line from dmesg:
[ 7041.688252] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once...
Click to expand...

comparing that against this one from lsusb:
Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Click to expand...

i have seen similar dmesg lines. they seem to say that the adapter is not legitimately a Cambridge Silicon Radio adapter as shown in the lsusb output. the other time i saw those lines, the adapter also did not work so it will be helpful to know if you have been able to use it with linux at all yet?
 
when I bought it it was written that it works with Windows , Mac os , x os and linux 64

and according to your answer, it seems to me that my adapter is not working very sorry, I will check it
 
you don't need to apologize and i'm not trying to say it won't work at all. i was just trying to figure out if you had been able to use it yet.

can you or would you consider live booting something like ubuntu and/or endeavour os to see if it worked with either one of those? since they are both from a different system than fedora, it may help let you know if the device works at all.
 
Yes, the device works with Windows, but refuses to work with Linux. On the Internet they write the adapter does not support Linux, but on the site where I bought it, it says that it does, thanks for your help.
 
You must log in or register to reply here.

Members online

Total: 590 (members: 4, guests: 586)

Latest posts

Top