public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: rbell@alumni.caltech.edu
To: "The excellent bluez mailing list!!" <linux-bluetooth@vger.kernel.org>
Subject: src/plugin.c:init_plugin() System does not support ccp plugin
Date: Sun, 13 Oct 2024 09:40:53 -0600	[thread overview]
Message-ID: <202410131540.49DFer5C020925@randytool.net> (raw)

	bluetooth stopped recognizing any of my controllers Saturday
morning.  (They work on a different computer.)  I get:

	Oct 11 09:59:12 mydomain kernel: Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... 
	Oct 11 09:59:12 mydomain kernel: Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround 
	Oct 11 09:59:12 mydomain kernel: Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. 
	Oct 11 09:59:12 mydomain kernel: Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
       	Oct 11 09:59:12 mydomain kernel: Bluetooth: hci0: HCI Set Event Filter command not supported. 
	Oct 11 09:59:15 mydomain kernel: Bluetooth: hci0: Opcode 0x1004 failed: -110 
	Oct 11 09:59:15 mydomain kernel: Bluetooth: hci0: command 0x1004 tx timeout
	Oct 11 09:59:25 mydomain bluetoothd[30412]: src/plugin.c:init_plugin() System does not support ccp plugin
	Oct 11 09:59:36 mydomain kernel: Bluetooth: hci0: CSR: Local version failed (-110)


	What does the ccp plugin do?  What support could it be missing?

	Thanks for your attention.

russell bell

             reply	other threads:[~2024-10-13 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-13 15:40 rbell [this message]
2024-10-14  1:20 ` src/plugin.c:init_plugin() System does not support ccp plugin Luiz Augusto von Dentz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202410131540.49DFer5C020925@randytool.net \
    --to=rbell@alumni.caltech.edu \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox