From: quentin-z80 <quentin-z80@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Bluetooth not working in kernel 5.16.7
Date: Wed, 09 Feb 2022 03:13:33 +0100 [thread overview]
Message-ID: <20220209021333.byFxljjUwZFyrHvND-fTxqgfdhQWw5fnkXK_nwfKLvU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35464@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]
New comment by quentin-z80 on void-packages repository
https://github.com/void-linux/void-packages/issues/35464#issuecomment-1033046617
Comment:
~~Same issue here on my Thinkpad P15s Gen2.~~
PEBKAC, bluetooth was off. The error messages I see in dmesg seem to be mostly harmless
```
[ 3.876228] Bluetooth: Core ver 2.22
[ 3.876236] NET: Registered PF_BLUETOOTH protocol family
[ 3.876237] Bluetooth: HCI device and connection manager initialized
[ 3.876239] Bluetooth: HCI socket layer initialized
[ 3.876240] Bluetooth: L2CAP socket layer initialized
[ 3.876242] Bluetooth: SCO socket layer initialized
[ 4.138745] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[ 5.403489] Bluetooth: hci0: Device revision is 0
[ 5.403491] Bluetooth: hci0: Secure boot is enabled
[ 5.403492] Bluetooth: hci0: OTP lock is enabled
[ 5.403492] Bluetooth: hci0: API lock is enabled
[ 5.403492] Bluetooth: hci0: Debug lock is disabled
[ 5.403493] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 5.403494] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ 5.404926] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ 5.404958] Bluetooth: hci0: Boot Address: 0x100800
[ 5.404959] Bluetooth: hci0: Firmware Version: 134-39.21
[ 6.686324] Bluetooth: hci0: Waiting for firmware download to complete
[ 6.686474] Bluetooth: hci0: Firmware loaded in 1251509 usecs
[ 6.686547] Bluetooth: hci0: Waiting for device to boot
[ 6.713724] Bluetooth: hci0: Device booted in 26566 usecs
[ 6.714176] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0041-0041.ddc
[ 6.716583] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 6.719597] Bluetooth: hci0: Firmware timestamp 2021.39 buildtype 1 build 31878
[ 6.790500] Bluetooth: hci0: Failed to read codec capabilities (-56)
[ 6.791502] Bluetooth: hci0: Failed to read codec capabilities (-56)
[ 6.792499] Bluetooth: hci0: Failed to read codec capabilities (-56)
[ 6.793499] Bluetooth: hci0: Failed to read codec capabilities (-56)
[ 6.794500] Bluetooth: hci0: Failed to read codec capabilities (-56)
[ 6.795489] Bluetooth: hci0: Failed to read codec capabilities (-56)
[ 38.054019] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 38.054022] Bluetooth: BNEP filters: protocol multicast
[ 38.054105] Bluetooth: BNEP socket layer initialized
```
next prev parent reply other threads:[~2022-02-09 2:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 20:49 [ISSUE] " RicArch97
2022-02-08 20:47 ` quentin-z80
2022-02-08 20:47 ` quentin-z80
2022-02-08 20:56 ` Vistaus
2022-02-09 2:13 ` quentin-z80 [this message]
2022-02-09 2:18 ` quentin-z80
2022-02-09 8:59 ` oynqr
2022-02-09 16:36 ` RicArch97
2022-02-10 7:05 ` oynqr
2022-02-10 10:41 ` Vistaus
2022-02-10 10:41 ` Vistaus
2022-02-26 17:16 ` [ISSUE] [CLOSED] " RicArch97
2022-02-26 17:16 ` RicArch97
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=20220209021333.byFxljjUwZFyrHvND-fTxqgfdhQWw5fnkXK_nwfKLvU@z \
--to=quentin-z80@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).