From: CtrlC-Root <CtrlC-Root@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: bluetooth broken after update
Date: Mon, 28 Aug 2023 22:20:01 +0200 [thread overview]
Message-ID: <20230828202001.iisPB7Cgyr8_6n36nS8RAWNeoIuYw3pE2HAGg9-7B6Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45801@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2846 bytes --]
New comment by CtrlC-Root on void-packages repository
https://github.com/void-linux/void-packages/issues/45801#issuecomment-1696356585
Comment:
FWIW I just updated my system and bluetooth works fine.
`xbps-query -l | grep blue`:
```
ii blueman-2.3.5_1 GTK+ Bluetooth Manager
ii bluez-5.68_1 Bluetooth tools and daemons
ii libbluetooth-5.68_1 Library to use the Bluez Linux Bluetooth Stack
ii libspa-bluetooth-0.3.77_1 Server and user space API to deal with multimedia pipelines - bluetooth plugins
```
`ls /var/service/ | sort`:
```
NetworkManager
agetty-tty1
agetty-tty2
agetty-tty3
agetty-tty4
agetty-tty5
agetty-tty6
avahi-daemon
bluetoothd
chronyd
cupsd
dbus
lightdm
spacenavd
sshd
udevd
```
`dmesg | grep Blue`:
```
[ 10.513535] Bluetooth: Core ver 2.22
[ 10.513553] Bluetooth: HCI device and connection manager initialized
[ 10.513555] Bluetooth: HCI socket layer initialized
[ 10.513557] Bluetooth: L2CAP socket layer initialized
[ 10.513559] Bluetooth: SCO socket layer initialized
[ 10.659551] Bluetooth: hci0: Device revision is 2
[ 10.659555] Bluetooth: hci0: Secure boot is enabled
[ 10.659556] Bluetooth: hci0: OTP lock is enabled
[ 10.659556] Bluetooth: hci0: API lock is enabled
[ 10.659557] Bluetooth: hci0: Debug lock is disabled
[ 10.659557] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 10.659558] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ 10.661479] Bluetooth: hci0: Found device firmware: intel/ibt-0040-4150.sfi
[ 10.661499] Bluetooth: hci0: Boot Address: 0x100800
[ 10.661500] Bluetooth: hci0: Firmware Version: 98-13.23
[ 11.596144] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 11.596148] Bluetooth: BNEP filters: protocol multicast
[ 11.596153] Bluetooth: BNEP socket layer initialized
[ 12.176185] Bluetooth: hci0: Waiting for firmware download to complete
[ 12.176554] Bluetooth: hci0: Firmware loaded in 1479591 usecs
[ 12.176697] Bluetooth: hci0: Waiting for device to boot
[ 12.192662] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 12.192692] Bluetooth: hci0: Device booted in 15683 usecs
[ 12.193052] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-4150.ddc
[ 12.194737] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 12.197789] Bluetooth: hci0: Firmware timestamp 2023.13 buildtype 1 build 62562
[ 12.265676] Bluetooth: MGMT ver 1.22
[ 18.925570] Bluetooth: RFCOMM TTY layer initialized
[ 18.925579] Bluetooth: RFCOMM socket layer initialized
[ 18.925583] Bluetooth: RFCOMM ver 1.11
```
So it may be related to your hardware or system setup.
next prev parent reply other threads:[~2023-08-28 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 19:08 [ISSUE] " ObscureXwing
2023-08-28 20:20 ` CtrlC-Root [this message]
2023-09-01 19:15 ` vxld100
2023-10-26 18:32 ` Luciogi
2023-10-26 18:36 ` Luciogi
2023-12-21 14:10 ` bali-BR
2023-12-21 16:08 ` bali-BR
2023-12-21 17:17 ` classabbyamp
2023-12-21 18:15 ` bali-BR
2023-12-21 22:31 ` bali-BR
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=20230828202001.iisPB7Cgyr8_6n36nS8RAWNeoIuYw3pE2HAGg9-7B6Q@z \
--to=ctrlc-root@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).