So the way this is *supposed* to work is that bluetooth.target is
activated by udev rules, like those:
99-systemd.rules:SUBSYSTEM=="bluetooth", TAG+="systemd",
ENV{SYSTEMD_ALIAS}+="/sys/subsystem/bluetooth/devices/%k"
99-systemd.rules:SUBSYSTEM=="bluetooth", TAG+="systemd",
ENV{SYSTEMD_WANTS}+="bluetooth.target"
But in my current "udevadm info --export-db" I don't have any device
with SUBSYSTEM=bluetooth, and /sys/class/bluetooth/ is empty. In dmesg I
see
[ 6639.785913] bluetooth hci0: Direct firmware load failed with error -2
[ 6639.785918] bluetooth hci0: Falling back to user helper
[ 6639.787431] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-21e6.hcd not
found
So this seems to be the reason why even after starting bluetooth.service
manually (which was a red herring) there are still no BT devices. Can
you please confirm that your problem is the same? I. e. run "dmesg |
grep bluetooth", and you get something like above? Thanks!
** Summary changed:
- bluetooth.service not started automatically
+ bluetooth does not work due to firmware load failure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387282
Title:
bluetooth does not work due to firmware load failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387282/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
