You are not logged in.
My laptop is the Dell Latitude 7280, and setting things up has mostly been smooth sailing so far, except for bluetooth functionality. I've done a full system upgrade with pacman, tried numerous different solutions I've found on here and other sites already, but with no luck. Here are a few of my system details from neofetch:
OS: Arch Linux x86_64
Host: Latitude 7280
Kernel: 6.10.9-arch1-2
DE: Xfce 4.18
WM: Xfwm4I'm just getting "No default controller available" from bluetoothctl when I try to do anything with it:
$ bluetoothctl show
No default controller availableStarting with the bluetooth service, the only error I'm getting is "System does not support ccp plugin." Now, I had more errors showing up here before, but after setting "Experimental" to true in /etc/bluetooth/main.conf they went away. Here's the bluetooth service status output:
$ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Thu 2024-09-12 13:54:59 PDT; 18min ago
Invocation: 041d699d714f4df7829ad99b63037826
Docs: man:bluetoothd(8)
Main PID: 2098 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 18987)
Memory: 1.9M (peak: 2.2M)
CPU: 54ms
CGroup: /system.slice/bluetooth.service
└─2098 /usr/lib/bluetooth/bluetoothd
Sep 12 13:54:59 theadventurer systemd[1]: Starting Bluetooth service...
Sep 12 13:54:59 theadventurer bluetoothd[2098]: Bluetooth daemon 5.78
Sep 12 13:54:59 theadventurer systemd[1]: Started Bluetooth service.
Sep 12 13:54:59 theadventurer bluetoothd[2098]: Starting SDP server
Sep 12 13:54:59 theadventurer bluetoothd[2098]: src/plugin.c:init_plugin() System does not support ccp plugin
Sep 12 13:54:59 theadventurer bluetoothd[2098]: Bluetooth management interface 1.22 initializedConfirming my wireless card is in fact the "Intel Wireless 8265 / 8275":
$ sudo lspci | grep "Wireless"
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)Making sure the correct drivers are on my machine:
$ ls /lib/firmware | grep "8265"
iwlwifi-8265-34.ucode.zst
iwlwifi-8265-36.ucode.zstRunning rkill list doesn't show anything that says "Bluetooth" which I find a bit strange, but it doesn't say anything's blocked either:
$ rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: noSome more potentially useful info:
$ sudo dmesg | grep Bluetooth
[sudo] password for mjt:
[ 43.734145] Bluetooth: Core ver 2.22
[ 43.734172] Bluetooth: HCI device and connection manager initialized
[ 43.734176] Bluetooth: HCI socket layer initialized
[ 43.734178] Bluetooth: L2CAP socket layer initialized
[ 43.734181] Bluetooth: SCO socket layer initialized
[ 157.432170] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 157.432176] Bluetooth: BNEP filters: protocol multicast
[ 157.432182] Bluetooth: BNEP socket layer initialized$ journalctl -b | grep Bluetooth
Sep 12 13:52:59 theadventurer systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Sep 12 13:53:01 theadventurer systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Sep 12 13:53:05 theadventurer kernel: Bluetooth: Core ver 2.22
Sep 12 13:53:05 theadventurer kernel: Bluetooth: HCI device and connection manager initialized
Sep 12 13:53:05 theadventurer kernel: Bluetooth: HCI socket layer initialized
Sep 12 13:53:05 theadventurer kernel: Bluetooth: L2CAP socket layer initialized
Sep 12 13:53:05 theadventurer kernel: Bluetooth: SCO socket layer initialized
Sep 12 13:54:59 theadventurer systemd[1]: Starting Bluetooth service...
Sep 12 13:54:59 theadventurer bluetoothd[2098]: Bluetooth daemon 5.78
Sep 12 13:54:59 theadventurer systemd[1]: Started Bluetooth service.
Sep 12 13:54:59 theadventurer kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 12 13:54:59 theadventurer kernel: Bluetooth: BNEP filters: protocol multicast
Sep 12 13:54:59 theadventurer kernel: Bluetooth: BNEP socket layer initialized
Sep 12 13:54:59 theadventurer bluetoothd[2098]: Bluetooth management interface 1.22 initializedI've tried using this to get bluetooth working as well, but to no avail:
sudo rmmod btusb
sudo modprobe btusbI'd appreciate any help with this. This is a bit frustrating to say the least, since this is my sort of "daily driver" laptop I want to regularly use.
Offline
Check whether there's an UEFI setting or physical switch (one that logically detaches the thing entirely, so it wouldn't show up on rfkill)
Other than that, what do we get from
lsusb -tv #usbutils
sudo journalctl -b #The entire thing, so we don't have to grep for random tokens that might lose contextOffline
Ran across this thread because my bluetooth is not working anymore with Kernel 6.10.
When starting the bluetooth service, blueman showed BT as "Deactivated", activating it crashed blueman.
I reverted to 6.9, now it is working again.
My bluetooth device is the same as yours.
EDIT: I did check bluetooth ctl as well, and just like in your case, it could not find a controller. I did not have time to check it out any further yet, as I needed BT working at that moment...
Last edited by arneko (2024-09-16 04:57:02)
Offline
I reverted to 6.9, now it is working again.
Could you also check if 6.11 has this issue? It's currently in the testing repo, so you can install it i.e. like so:
sudo pacman -U https://archive.archlinux.org/packages/l/linux/linux-6.11.arch1-1-x86_64.pkg.tar.zstOffline
Could you also check if 6.11 has this issue? It's currently in the testing repo, so you can install it i.e. like so:
sudo pacman -U https://archive.archlinux.org/packages/l/linux/linux-6.11.arch1-1-x86_64.pkg.tar.zst
That kernel seems to be working fine. Thanks!
Offline