You are not logged in.
Pages: 1
I performed ~sudo pacman -Syu yesterday and when my wireless headphones disconnected the bluetooth is no longer working.
~> sudo dmesg | grep -iE 'hci|blue|bcm|btusb|ibt'
[ 0.810972] ahci 0000:00:17.0: version 3.0
[ 0.811372] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
[ 0.811379] ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part deso sadm sds apst
[ 0.812727] scsi host0: ahci
[ 0.813024] scsi host1: ahci
[ 1.738086] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.738115] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[ 1.739237] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810
[ 1.739610] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.739618] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 1.739624] xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
[ 1.739710] usb usb1: Product: xHCI Host Controller
[ 1.739714] usb usb1: Manufacturer: Linux 6.1.37-1-lts xhci-hcd
[ 1.754049] usb usb2: Product: xHCI Host Controller
[ 1.754051] usb usb2: Manufacturer: Linux 6.1.37-1-lts xhci-hcd
[ 2.002461] usb 1-1: new low-speed USB device number 2 using xhci_hcd
[ 2.269135] usb 1-3: new low-speed USB device number 3 using xhci_hcd
[ 2.535756] usb 1-6: new high-speed USB device number 4 using xhci_hcd
[ 2.822478] usb 1-10: new full-speed USB device number 5 using xhci_hcd
[ 3.405803] usb 1-10: new full-speed USB device number 6 using xhci_hcd
[ 4.269141] usb 1-10: new full-speed USB device number 7 using xhci_hcd
[ 4.805805] usb 1-10: new full-speed USB device number 8 using xhci_hcd
[ 13.788117] Bluetooth: Core ver 2.22
[ 13.788148] NET: Registered PF_BLUETOOTH protocol family
[ 13.788151] Bluetooth: HCI device and connection manager initialized
[ 13.788158] Bluetooth: HCI socket layer initialized
[ 13.788162] Bluetooth: L2CAP socket layer initialized
[ 13.788167] Bluetooth: SCO socket layer initialized
[ 13.806533] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 13.806538] Bluetooth: BNEP filters: protocol multicast
[ 13.806544] Bluetooth: BNEP socket layer initialized
~> sudo dmesg | grep Blue
[ 13.788117] Bluetooth: Core ver 2.22
[ 13.788151] Bluetooth: HCI device and connection manager initialized
[ 13.788158] Bluetooth: HCI socket layer initialized
[ 13.788162] Bluetooth: L2CAP socket layer initialized
[ 13.788167] Bluetooth: SCO socket layer initialized
[ 13.806533] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 13.806538] Bluetooth: BNEP filters: protocol multicast
[ 13.806544] Bluetooth: BNEP socket layer initialized
~> lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0c45:671e Microdia Integrated_Webcam_HD
Bus 001 Device 003: ID 10c4:8108 Silicon Labs USB OPTICAL MOUSE
Bus 001 Device 002: ID c0f4:07d0 Usb KeyBoard Usb KeyBoard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
~lsmod | grep btusb
btusb 69632 0
btrtl 28672 1 btusb
btbcm 24576 1 btusb
btintel 45056 1 btusb
btmtk 16384 1 btusb
bluetooth 937984 14 btrtl,btmtk,btintel,btbcm,bnep,btusb
~> bluetoothctl power on
No default controller available
~ rfkill
ID TYPE DEVICE SOFT HARD
0 wlan phy0 unblocked unblocked
Tried everything in troubleshooting section of wiki and also tried many stack exchange and forums answers. Nothing worked.
Offline
I have this exact same problem on 6.4.1-tkg, but I don't have it on 6.4.1-arch
Offline
Did the kernel get updated? Did you reboot?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Did the kernel get updated? Did you reboot?
Yep, I used linux-zen and it updated yesterday before this error occurred. I downgraded the kernel but still same. Then I switched to linux-lts but the problem still persists.
~> uname -a
Linux archlinux 6.1.37-1-lts #1 SMP PREEMPT_DYNAMIC Sun, 02 Jul 2023 09:31:30 +0000 x86_64 GNU/Linux
Last edited by SudeepSharma100 (2023-07-06 00:55:13)
Offline
I don't know how but now all of a sudden its working again without doing anything.
Offline
It happened again! This time it just randomly crashed. I got this while launching blueberry:
ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
(blueberry.py:1208): com.linuxmint.blueberry-WARNING **: 12:14:36.013: Could not retrieve the BT adapter name with 'bt-adapter -i': Command '['timeout', '2s', 'bt-adapter', '-i']' died with <Signals.SIGABRT: 6>.
**
ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
(blueberry.py:1208): com.linuxmint.blueberry-WARNING **: 12:14:36.036: Could not retrieve the BT adapter name with 'bt-adapter -i': Command '['timeout', '2s', 'bt-adapter', '-i']' died with <Signals.SIGABRT: 6>.
also,
~ bt-adapter -i
**
ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
Bail out! ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
fish: Job 1, 'bt-adapter -i' terminated by signal SIGABRT (Abort)
Offline
Were there any kernel messages recorded in the journal when it happened again? Please use code tags for commands and their outputs.
Offline
Pages: 1