dilyn-corner@ubuntu:~$ sudo bluez.btmgmt
[mgmt]# info
Index list with 1 item
hci0: Primary controller
addr A0:80:69:60:CB:E6 version 12 manufacturer 2 class 0x000000
supported settings: powered connectable fast-connectable discoverable
bondable link-security ssp br/edr hs le secure-conn debug-keys privacy
configuration static-addr phy-configuration wide-band-speech
current settings: ssp br/edr le secure-conn
name BlueZ 5.64
short name
hci0: Configuration options
supported options: public-address
missing options:
[mgmt]# advinfo
Reading adv features failed with status 0x0c (Not Supported)
[mgmt]# power on
hci0 class of device changed: 0x00010c
hci0 Set Powered complete, settings: powered ssp br/edr le secure-conn
[mgmt]# advinfo
Reading adv features failed with status 0x0c (Not Supported)
[mgmt]# power on
hci0 Set Powered complete, settings: powered ssp br/edr le secure-conn
[mgmt]# advinfo
Reading adv features failed with status 0x0c (Not Supported)
[mgmt]# find
Discovery started
hci0 type 7 discovering on
hci0 dev_found: 4F:80:48:7F:FD:5E type LE Random rssi -82 flags 0x0000
AD flags 0x1a
eir_len 19
*** SNIP ***
[mgmt]# advinfo
Reading adv features failed with status 0x0c (Not Supported)
The system has the following snaps:
dilyn-corner@ubuntu:~$ snap list
Name Version Rev Tracking Publisher Notes
core22 20230304 547 latest/stable canonical✓ base
pc 22-0.3 127 22/stable canonical✓ gadget
pc-kernel 5.15.0-66.73.1 1224 22/stable canonical✓ kernel
snapd 2.59 18745 latest/beta canonical✓ snapd
Some relevant other facts:
dilyn-corner@ubuntu:~$ sudo dmesg | grep Blue
[ 11.155665] Bluetooth: Core ver 2.22
[ 11.155681] Bluetooth: HCI device and connection manager initialized
[ 11.155683] Bluetooth: HCI socket layer initialized
[ 11.155684] Bluetooth: L2CAP socket layer initialized
[ 11.155686] Bluetooth: SCO socket layer initialized
[ 11.280913] Bluetooth: hci0: Device revision is 0
[ 11.280924] Bluetooth: hci0: Secure boot is enabled
[ 11.280925] Bluetooth: hci0: OTP lock is enabled
[ 11.280925] Bluetooth: hci0: API lock is enabled
[ 11.280926] Bluetooth: hci0: Debug lock is disabled
[ 11.280926] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 11.280927] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build
38
[ 12.537783] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[ 13.740678] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 13.740680] Bluetooth: BNEP filters: protocol multicast
[ 13.740683] Bluetooth: BNEP socket layer initialized
[ 14.100880] Bluetooth: hci0: Waiting for firmware download to complete
[ 14.101807] Bluetooth: hci0: Firmware loaded in 1527362 usecs
[ 14.101940] Bluetooth: hci0: Waiting for device to boot
[ 14.119926] Bluetooth: hci0: Device booted in 17676 usecs
[ 14.120575] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-0040-0041.ddc
[ 14.123999] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 14.128005] Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build
38020
dilyn-corner@ubuntu:~$ uname -a
Linux ubuntu 5.15.0-66-generic #73-Ubuntu SMP Fri Feb 3 14:23:37 UTC 2023
x86_64 x86_64 x86_64 GNU/Linux
These commands were run with bluez installed from the 22/stable and 22/beta
channels fully confined with every interface connected.
While running these commands, no relevant information is flagged by
AppArmor in the logs. This indicates that AppArmor is not denying
bluez's ability to execute these commands, but instead bluez is
experiencing some sort of problem when it attempts to query the features
on the device.
Attached is potentially some useful information on the WiFi/BT in this laptop.
The diff:
--- devices-info-core
+++ devices-info-desktop
@@ -1,10 +1,11 @@
lspci -vvv -k
-00:14.3 Network controller: Intel Corporation Device 51f0 (rev 01)
+00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev
01)
Subsystem: Intel Corporation Device 4090
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
+ IOMMU group: 12
Region 0: Memory at 6287194000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
@@ -13,13 +14,18 @@
Address: 0000000000000000 Data: 0000
Capabilities: [40] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
- ExtTag- RBE-
- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
- RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+
+ ExtTag- RBE- FLReset+
+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
+ RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
- DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
- DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR+, OBFF Via WAKE#
- DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis-, LTR+, OBFF
Disabled
+ DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
+ DevCap2: Completion Timeout: Range B, TimeoutDis+ NROPrPrP- LTR+
+ 10BitTagComp- 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
+ EmergencyPowerReduction Not Supported,
EmergencyPowerReductionInit-
+ FRS-
+ AtomicOpsCap: 32bit- 64bit- 128bitCAS-
+ DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis- LTR+ OBFF
Disabled,
+ AtomicOpsCtl: ReqEn-
Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
Vector table: BAR=0 offset=00002000
PBA: BAR=0 offset=00003000
@@ -30,7 +36,6 @@
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
-
lsusb -v
Bus 003 Device 004: ID 8087:0033 Intel Corp.
Device Descriptor:
@@ -51,7 +56,7 @@
Configuration Descriptor:
bLength 9
bDescriptorType 2
- wTotalLength 200
+ wTotalLength 0x00c8
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
@@ -309,3 +314,17 @@
Usage Type Data
wMaxPacketSize 0x003f 1x 63 bytes
bInterval 1
+Binary Object Store Descriptor:
+ bLength 5
+ bDescriptorType 15
+ wTotalLength 0x000c
+ bNumDeviceCaps 1
+ USB 2.0 Extension Device Capability:
+ bLength 7
+ bDescriptorType 16
+ bDevCapabilityType 2
+ bmAttributes 0x0000040e
+ BESL Link Power Management (LPM) Supported
+ BESL value 1024 us
+Device Status: 0x0001
+ Self Powered
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2006517
Title:
Bluetooth works on desktop but not on ubuntu core
Status in bluez package in Ubuntu:
Confirmed
Bug description:
We have built a snap that uses some bluetooth functionality.
The snap runs well when using Ubuntu desktop 22.04 (all updates applied end
of Jan 2022).
We have tried using this same snap on Ubuntu Core 22 running on X86_64.
On some hardware platforms (thinkpad E15 and x86 Mac) everything works as
expected.
We can install the snap on Jammy 22.04 or Core 22 on these platforms and get
expected functionality regardless of OS.
On our targeted platform (a Dell 5570) things are not working. When running
22.04 Jammy, everything works. When running Core 22, some advanced bluetooth
functionality is not available.
Since the Core 22 image installs and runs on other X86_64 hardware we suspect
a device driver issue.
Attached are several files taken from the Dell 5570
1) dmesg from Core 22.
2) dmesg from Jammy 22.04
3) output of lspci from Jammy 22.04
4) Output of lsusb from Jammy 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
