Fungal, I suppose that was once a link to another post?
I'm back with more Bluetooth fun...
I'm currently back at my mexican workstation. My NIC is an
Intel Dual AC wireless 7260 mini-PCIe. These intel combined cards are sort of notorious for having issues over several generations. I've never had the need to use Bluetooth on this machine before so I didn't bother. I bought myself some bluetooth speakers though and would like to use them with my Obarun.
So
what's the exact problem?
The bluetooth portion of the card is simply not recognized in Obarun. Also Plasma shows no available devices in its settings.
What packages are installed, what services running?
bluez, bluez-libs, bluez-utils, bluez-qt, bluedevil (plasma), qt5-connectivity (optional[?])
bluetoothd-66serv is enabled and running in a root user tree but actually bails in the log:
marian@ obarun [111] ~ % sudo 66-inservice bluetoothd
Name : bluetoothd
Version : 0.2.1
In tree : desktop
Status : enabled, down (exitcode 127) 0 seconds, normally up, want up, ready 0 seconds
Type : classic
Description : bluetooth daemon
Source : /usr/lib/66/service/bluetoothd
Live : /run/66/scandir/0/bluetoothd
Dependencies : bluetoothd-log
External dependencies : None
Optional dependencies : None
Start script : execl-cmdline -s { /usr/lib/bluetooth/bluetoothd ${cmd_args} -f ${conf_file} }
Stop script : None
Environment source : /etc/66/conf/bluetoothd
Environment file : cmd_args=!-n
conf_file=!/etc/bluetooth/main.conf
Log name : bluetoothd-log
Log destination : /var/log/66/bluetoothd
Log file :
2020-06-02 14:22:40.518863630 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:41.519596540 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:42.518570036 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:43.522248264 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:44.522330128 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:45.522682920 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:46.523987885 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:47.525272197 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:48.526387686 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:49.528144026 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:50.528217514 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:51.529249478 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:52.529177465 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:53.532769161 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:54.533084767 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:55.536031566 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:56.537250929 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:57.536417413 execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
Ok. That's pretty clear. But
WHY?
I indeed miss this path completely. There's not even any /usr/lib/bluetooth parent directory on my install. Furthermore the only entries in /usr/lib regarding Bluetooth is the libbluetooth.so.3.19.2* socket and it's corresponding symbolic links. I can install the mentioned packages any times I want. It won't get created either.
rfkill recognizes the device:
marian@ obarun ~ % rfkill
ID TYPE DEVICE SOFT HARD
0 wlan phy0 unblocked unblocked
1 bluetooth hci0 unblocked unblocked
so does the kernel apparently:
marian@ obarun [127] ~ % dmesg | grep Bluetooth
[ 6.824423] Bluetooth: Core ver 2.22
[ 6.824531] Bluetooth: HCI device and connection manager initialized
[ 6.824535] Bluetooth: HCI socket layer initialized
[ 6.824536] Bluetooth: L2CAP socket layer initialized
[ 6.824539] Bluetooth: SCO socket layer initialized
[ 6.853569] Bluetooth: hci0: read Intel version: 3707100180012d0d2a
[ 6.853570] Bluetooth: hci0: Intel device is already patched. patch num: 2a
so does bluez-utils:
marian@ obarun ~ % btmgmt
[mgmt]# info
Index list with 1 item
hci0: Primary controller
addr 7C:5C:F8:6E:50:AE version 6 manufacturer 2 class 0x000000
supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr
current settings: br/edr
name Bluemoon Universal Bluetooth Host Controller
short name
hci0: Configuration options
supported options: public-address
missing options:
Necessary kernel modules seem to be loaded:
marian@ obarun ~ % lsmod | grep blue
bluetooth 696320 5 btrtl,btintel,btbcm,btusb
ecdh_generic 16384 1 bluetooth
rfkill 28672 6 bluetooth,cfg80211
crc16 16384 2 bluetooth,ext4
(Although it sort of throws me off that bluetooth says "btintel". Intel states that iwlwifi is the driver responsible for these cards?)
When I issue "bluetoothctl" from bluez-utils the command will indefinitely try to connect to bluetoothd (surprise surprise, no bluetoothd there to begin with...)
I'm currently dual booting with Windows and have read concerns that Windows can sort of kidnap the MAC of a hardware device. But from all the output I seriously doubt that is the case here. The issue seems to be the missing /usr/lib/bluetooth directory. Also many people advice to disable co-existence of Bluetooth and WIFI on these cards with a iwlwifi module option which didn't work either.
On YouTube people mask out(!) between one and three pins on the NIC itself to get it discovered...(although several of those have this issue even on Windows and
my Windows installation detects the card fine and works out of the box.)
Any idea why /usr/lib/bluetooth might be missing? Am I missing packages? I've read that people of similar Intel cards install bluez-utils-compat from AUR instead of bluez-utils from official repos to get it to work, but that has a systemd dependency...