Also just decided to try the onboard bluetooth again.
Fresh install of Raspberry Pi OS Lite on thumb drive
No dongles attached
Fresh install of Raspberry Pi OS Lite on thumb drive
No dongles attached
Code:
alturick@doomsday:~ $ sudo bluetoothctlAgent registered[CHG] Controller DC:A6:32:C5:AE:F2 Pairable: yes[bluetooth]# showController DC:A6:32:C5:AE:F2 (public)Name: doomsdayAlias: doomsdayClass: 0x00000000Powered: yesDiscoverable: noDiscoverableTimeout: 0x000000b4Pairable: yesUUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)Modalias: usb:v1D6Bp0246d0542Discovering: noRoles: centralRoles: peripheralAdvertising Features:ActiveInstances: 0x00 (0)SupportedInstances: 0x05 (5)SupportedIncludes: tx-powerSupportedIncludes: appearanceSupportedIncludes: local-name[bluetooth]# power onChanging power on succeeded[bluetooth]# agent onAgent is already registered[bluetooth]# discoverable onChanging discoverable on succeeded[CHG] Controller DC:A6:32:C5:AE:F2 Discoverable: yes[bluetooth]# scan onDiscovery started[CHG] Controller DC:A6:32:C5:AE:F2 Discovering: yes[NEW] Device 51:C4:7D:7C:B8:81 51-C4-7D-7C-B8-81[NEW] Device 58:A5:62:37:9B:CA 58-A5-62-37-9B-CA[NEW] Device EC:4F:73:A0:DE:A0 N07XD[NEW] Device 60:A4:23:A2:91:6E 60-A4-23-A2-91-6E[NEW] Device 08:EB:ED:E9:25:3F Anker SoundCore[bluetooth]# pair 08:EB:ED:E9:25:3FAttempting to pair with 08:EB:ED:E9:25:3F[CHG] Device 08:EB:ED:E9:25:3F Connected: yesRequest confirmation[agent] Confirm passkey 059295 (yes/no): yes[CHG] Device 08:EB:ED:E9:25:3F Bonded: yes[CHG] Device 08:EB:ED:E9:25:3F UUIDs: 0000110b-0000-1000-8000-00805f9b34fb[CHG] Device 08:EB:ED:E9:25:3F UUIDs: 0000110c-0000-1000-8000-00805f9b34fb[CHG] Device 08:EB:ED:E9:25:3F UUIDs: 0000110e-0000-1000-8000-00805f9b34fb[CHG] Device 08:EB:ED:E9:25:3F UUIDs: 0000111e-0000-1000-8000-00805f9b34fb[CHG] Device 08:EB:ED:E9:25:3F ServicesResolved: yes[CHG] Device 08:EB:ED:E9:25:3F Paired: yesPairing successful[CHG] Device 08:EB:ED:E9:25:3F ServicesResolved: no[CHG] Device 08:EB:ED:E9:25:3F Connected: no[CHG] Device EC:4F:73:A0:DE:A0 ServiceData Key: 0000feaf-0000-1000-8000-00805f9b34fb[CHG] Device EC:4F:73:A0:DE:A0 ServiceData Value: 10 01 00 02 5a 23 09 00 20 95 f1 00 00 30 b4 18 ....Z#.. ....0.. 00 . [bluetooth]# trust 08:EB:ED:E9:25:3F[CHG] Device 08:EB:ED:E9:25:3F Trusted: yesChanging 08:EB:ED:E9:25:3F trust succeeded[bluetooth]# connect 08:EB:ED:E9:25:3FAttempting to connect to 08:EB:ED:E9:25:3FFailed to connect: org.bluez.Error.Failed br-connection-profile-unavailable[DEL] Device 60:A4:23:A2:91:6E 60-A4-23-A2-91-6E[NEW] Device 60:A4:23:A2:91:6E 60-A4-23-A2-91-6E[bluetooth]# quitalturick@doomsday:~ $ lsusbBus 002 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash DriveBus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubBus 001 Device 002: ID 2109:3431 VIA Labs, Inc. HubBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubalturick@doomsday:~ $ sudo hciconfig -ahci0:Type: Primary Bus: UARTBD Address: DC:A6:32:C5:AE:F2 ACL MTU: 1021:8 SCO MTU: 64:1UP RUNNING PSCAN ISCAN RX bytes:6562 acl:10 sco:0 events:475 errors:0TX bytes:66913 acl:10 sco:0 commands:415 errors:0Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: PERIPHERAL ACCEPT Name: 'doomsday'Class: 0x000000Service Classes: UnspecifiedDevice Class: Miscellaneous, HCI Version: 5.0 (0x9) Revision: 0x17eLMP Version: 5.0 (0x9) Subversion: 0x6119Manufacturer: Cypress Semiconductor (305)Statistics: Posted by alturick — Fri Jun 20, 2025 11:56 pm