hcitool and rfkill list showed nothing, according to them the device isn't there yet. I might be able to get this going with usb_modeswitch but need a product identifier and another item to do that.
On Fri, 17 Dec 2021, deloptes wrote: > Jude DaShiell wrote: > > > Dec 16 17:10:08 taf systemd[1]: Condition check resulted in Bluetooth > > service being skipped. > > Dec 16 17:10:33 taf dbus-daemon[475]: [system] Failed to activate service > > 'org.bluez': timed out (service_start_timeout=25000ms) > > Dec 16 17:20:36 taf kernel: Bluetooth: Core ver 2.22 > > Dec 16 17:20:36 taf kernel: Bluetooth: HCI device and connection manager > > initialized > > Dec 16 17:20:36 taf kernel: Bluetooth: HCI socket layer initialized > > Dec 16 17:20:36 taf kernel: Bluetooth: L2CAP socket layer initialized > > Dec 16 17:20:36 taf kernel: Bluetooth: SCO socket layer initialized > > it says it can not start bluetooth, but HCI device and connection manager > initialized, so what does hcitool said? > and why is pulseaudio involved - perhaps you need > pulseaudio-module-bluetooth and reboot to be sure it all setup properly > > also what said rfkill? > >