firmware-realtek has been installed a while ago. I'm probably going to have to run usb-modeswitch against the device.
On Thu, 16 Dec 2021, Jude DaShiell wrote: > > > On Thu, 16 Dec 2021, deloptes wrote: > > > Jude DaShiell wrote: > > > > > No Linux firmware came on the disk only windows files. To that extent I > > > checked. On debian does a way exist to check devices for missing > > > firmware? > > > > > > > in the log file journalctl or /var/log/syslog, after plugging in the usb (I > > am not sure if it is usb stick, because you mentioned card, but anywa) > > When bluetooth initializes you should see if it is looking for firmware and > > in your case not loading it. > > > > It could be that you have to install linux firmware packages free or not > > free (depends on the chip you have on the device) > > > > You could also check output of command rfkill list and see if hci0 device > > exists and is blocked > > > > The other thing use hcitool command (hcitool dev) and see if it shows hci > > device - I have seen some cases that hciattach needs to be run to enable > > the device. > Does any of this make sense? This is journalctl output: > 16:56:28 taf bluetoothd[1157]: Starting SDP server > Dec 16 16:56:28 taf bluetoothd[1157]: Bluetooth management interface 1.18 > initialized > Dec 16 16:56:40 taf bluetoothd[1157]: Terminating > Dec 16 16:56:40 taf dbus-daemon[453]: [system] Rejected send message, 0 > matched rules; type="error", sender=":1.9" (uid=1000 pid=817 > comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") > interface="(unset)" member="(unset)" error > name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" > destination=":1.17" (uid=0 pid=1157 comm="bluetoothd ") > Dec 16 16:56:40 taf bluetoothd[1157]: Stopping SDP server > Dec 16 16:56:40 taf bluetoothd[1157]: Exit > Dec 16 16:56:40 taf dbus-daemon[453]: [system] Rejected send message, 0 > matched rules; type="error", sender=":1.9" (uid=1000 pid=817 > comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") > interface="(unset)" member="(unset)" error > name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" > destination=":1.17" (uid=0 pid=1157 comm="bluetoothd ") > Dec 16 17:07:06 taf NetworkManager[1764]: <info> [1639692426.3763] > Loaded device plugin: NMBluezManager > (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so) > Dec 16 17:09:50 taf NetworkManager[476]: <info> [1639692590.3550] Loaded > device plugin: NMBluezManager > (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so) > Dec 16 17:10:08 taf dbus-daemon[475]: [system] Activating via systemd: > service name='org.bluez' unit='dbus-org.bluez.service' requested by > ':1.15' (uid=1000 pid=868 comm="/usr/bin/pulseaudio --daemonize=no > --log-target=jo") > 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 > > > > > >
