Same software still loaded from yesterdayPro wrote:check lsmod or dmesg (btusb, bluetooth kernel module launched?)perdido wrote: -------------------------------------------------------
I have never seen the 413c:8187 Dell DW375 bluetooth device listed in lsusb when trying any version of bluez 5.xx
I have seen the 413c:8187 Dell DW375 listed in lsusb when trying some versions of bluez 4.xx
lsusb not guarantee that the device works!
bluetooth.sh - script for autolaunch with xorg starts, run only puppybt for testing.
Check update puppybt from github, i not upload latest module because I need to solve the problem with simple pair device.
------------------------------------------------------------
dmesg shows no bluetooth
lsmod -shows no bluetooth driver (btusb module not loaded)
modprobe btusb - loads module ok
lsmod -now shows btusb module loaded
rfkill list bluetooth - not listed
dmesg now shows
Bluetooth: HCI device and connector manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
usbcore: registered new interface driver btusb
Tried to run puppybt
Still get the error
"Error
Local bluetooth device not found"
I see no updated puppybt from github?Check update puppybt from github, i not upload latest module because I need to solve the problem with simple pair device.
lsusb shows no Dell Wireless bluetooth device
My thought is this device needs to get initialized
Will post back after more checks
----------------------------------------------------------------------------
After more checks
Final report- I am not going to try to initialize my bluetooth with bluez 5.xx
I believe this is a hardware problem between bluez 5.xx and my bluetooth adapter.
Thanks for your help. If I get another bluetooth adapter I will be back!
.