Hi! I am Ahmer. I had issue with my bluetooth dongle that was working fine with kernel 5.11, but then it broke again. But thanks to the effort of the linux community people it worked again. But, it doesn't work now with kernel 6.0.0 and newer. This is the output of "sudo dmesg | grep Blue" ,hope this helps:

[21358.775509] Bluetooth: Core ver 2.22
[21358.775565] Bluetooth: HCI device and connection manager initialized
[21358.775571] Bluetooth: HCI socket layer initialized
[21358.775574] Bluetooth: L2CAP socket layer initialized
[21358.775581] Bluetooth: SCO socket layer initialized
[21358.853107] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=9 rev=3120
[21358.853115] Bluetooth: hci0: LMP ver=9 subver=22bb; manufacturer=10
[21358.853118] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once...
[21364.100605] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround
[21364.100667] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported.
[21364.100671] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
[21364.100673] Bluetooth: hci0: HCI Set Event Filter command not supported.
[21366.112406] Bluetooth: hci0: Opcode 0x c03 failed: -110

Please, help me fix this issue.

We can try to help, but you've not given us much to work with. You don't tell us the brand/model of the bluetooth dongle, what kind of hardware it's plugged in to, using what version/distro of Linux, and what you've done/tried/are-doing to make this work and pair something. All we've got is "it doesn't work", and some dmesg lines; can't do much with that.

Looking at the little you've given us, this thread has some ideas:
https://bbs.archlinux.org/viewtopic.php?id=274953

...but don't know if they apply or not.

Tbone means something like this

Not even all that; something as simple as "I bought a BrandX model 444 bluetooth dongle and plugged it into my Dell model YYY laptop, running Ubuntu 22.x with Gnome. I went into the Bluetooth applet on the desktop and tried to enable it, but it won't come on." is all that's really needed.

Hi! I am sorry for posting like this actually it is my first time on the linux forums. I have a Dell Optiplex 3010 pc, I run Kali-linux-Rolling release when I plugged the Cambridge Silicon Usb Dongle it shows up in the settings but doesn't turn on, It has no brand but shows as cambridge silicon chip in the terminal. It actually worked on Ubuntu-20.04 as it had old kernel with the patches from this link:
https://bugzilla.kernel.org/show_bug.cgi?id=60824#c155
But, this patch is in kernel 6.0.0 and later but doesn't work. I have tried to manually patch the kernel as some extra files had been added to newer kernels and then compiled. But it didn't work, I have already been to the post you told me. But none of them work with the newer kernels. Please help me. Here is more information about the usb dongle:
"inxi -Eaz" output:
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 2-1.4:4
chip-ID: 0a12:0001 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: disabled
rfk-block: hardware: no software: no address: <filter>
Info: acl-mtu: 0:0 sco-mtu: 0:0 link-mode: peripheral accept

"hciconfig -a" output:
hci0: Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:14 acl:0 sco:0 events:1 errors:0
TX bytes:3 acl:0 sco:0 commands:2 errors:1
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: PERIPHERAL ACCEPT
"lsusb -vv -d 0a12:0001" output:
Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0a12 Cambridge Silicon Radio, Ltd
idProduct 0x0001 Bluetooth Dongle (HCI mode)
bcdDevice 25.20
iManufacturer 0
iProduct 2 CSR8510 A10
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x00b1
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1

Please, tell me if you need any more info.

Bolded and underlined part of what you posted for emphasis...Kali is *NOT* meant for new users, and it's not even meant to be installed on hard drive for 'daily' use. It's for experienced users and even then just for security/pentesting. Read the Kali links in my posting signature and even their own website tells you these things. Wifi and bluetooth are turned off/disabled by default, and you have to go through a good bit to get things working. The fact that you say it worked on Ubuntu should give you a clue.

Don't use Kali; load the latest Ubuntu or Mint and it'll work just fine. Other than that, I doubt many folks are going down the rabbit-hole of custom compiling a Kali kernel to get such a 'consumer' device working on a distro that's not meant for such things. There are a LOT of hits on a search engine for bluetooth on Kali..none of them particularly easy. Use a distro meant for such things.

Hi! Actually the issue is not with kali or any distribution at all. I had confirmed that while going through this bug report : "https://bugzilla.kernel.org/show_bug.cgi?id=60824#c155"; that solved the issue for Linux Kernel 5.0.0 and 5.19 versions. But, it now a problem with the newer 6.0.0 Kernels. Please, I don't know how the new files are organized and the underlying working of linux, So could you tell me which part of the code needs to be changed and what changes to make if you are able to analyze the patch make it work. Here is the code that was added to the mainline 5.8.0 kernel(which was my Ubuntu-20.04) and it worked: "https://github.com/torvalds/linux/commit/cde1a8a992875a7479c4321b2a4a190c2e92ec2a#diff-82175cb30d8f0e6fd9fb8b83571c33aac5db6db4d5f79dd97d4255116a79c79eR1813". But, it stopped working as soon as Kernel-6.0.0 came out. Please, help me and if you need any info tell me.

You, yourself, confirmed that this works under Ubuntu...the issue *IS KALI*, period. Again, Kali is *NOT MEANT* to be used as a daily-use OS, and is for advanced/experienced users doing security and pentesting. You are referencing something that's old, and has been FIXED already in later kernels...but that doesn't mean Kali uses it for the MANY reasons explained on their own website. Again, you need to read their website about what Kali is/does and how such devices are disabled for good reason.

AGAIN: use something other than Kali

Brother, listen carefully as you said don't use Kali Linux, So I switched to Ubuntu 23.04 now it is not working on that. What should I do. Tell me it is giving the same output as earlier. Don't think I am being rude it is just that I am not able to convey my problem to you clearly.

If you have found a problem with Ubuntu, then report it to Canonical.

But Ubuntu 23.04 uses Linux 6.2, not Linux 6.0.0, and also Ubuntu 23.04 stopped being supported on 25th January, and should have been upgraded to 23.10 (on Linux 6.5), which has been out since October.

(Ubuntu users not wanting to upgrade every six months should stick to the LTS releases (i.e. 20.04 LTS and 22.04 LTS), which are released every two years, and supported for five.)

I am not your brother, and I doubt VERY seriously that Ubuntu 23 is giving you the same messages as Kali.

Have you checked to see if bluetooth is enabled?? Again, what desktop environment are you using and how are you trying to get this to work??? Have you checked the status of things with "rfkill list"?? Have you installed the bluetooth/bluez firmware packages??