Bluetooth inactive.

madmodder123

@trekdrop
We need more info: https://retropie.org.uk/forum/topic/3/read-this-first
Also check this page to learn about ds4drv and other methods.
https://github.com/RetroPie/RetroPie-Setup/wiki/PS4-Controller

trekdrop

Thanks, sadly it's not about the ps4 controller. It hangs in the search screen. Raspberry 3b new fresh retropie. Multi sd cards, different retropie img and still hangs in the search screen.

trekdrop

$ sudo service bluetooth status
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
Active: inactive (dead)
Condition: start condition failed at Fri 2018-08-10 07:16:43 UTC; 1min 41s ago
└─ ConditionPathIsDirectory=/sys/class/bluetooth was not met
Docs: man:bluetoothd(8)

So its dead>?

trekdrop

Reinstalled all the drivers.. still no luck.

mitu

This post is deleted!

trekdrop

So i would like to post a log file, i really don't know where to get it. It seems my Bluetooth is broken. After flashing 5 times a new Retropie img on different sd cards and using different power sources. I hope someone can still help me.. So frustrating because yesterday there was no problem.

mitu

@trekdrop Run sudo dmesg > /home/pi/dmesg.log and then post the contents of the dmesg.log file to pastebin.com to take a look.
Did you do any configurations before this happened ? Did you disable the BT via a config.txt line or disabled the WiFi inadvertently ?

trekdrop

@mitu said in Bluetooth inactive.:

sudo dmesg > /home/pi/dmesg.log

I will flash a new img now and send the dmseg.log file. No i never touch the wifi or Bluetooth settings.

https://pastebin.com/93bjnADz This one is ad first boot.

https://pastebin.com/xarec375 This one is second boot.

mitu

@trekdrop There's no indication in the dmesg output that you have a Bluetooth enabled device and I see you're using a wired connection (but the WiFi gets detected). I don't think that a new image would help - can you try running sudo modprobe bluetooth from the command line and then run sudo dmesg | tail to see if any error messages show up ?

trekdrop

@mitu

[ 5.693521] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 5.693883] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.328581] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[ 7.330745] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 72.058269] Bluetooth: Core ver 2.22
[ 72.058406] NET: Registered protocol family 31
[ 72.058414] Bluetooth: HCI device and connection manager initialized
[ 72.060043] Bluetooth: HCI socket layer initialized
[ 72.060083] Bluetooth: L2CAP socket layer initialized
[ 72.060131] Bluetooth: SCO socket layer initialized

mitu

@trekdrop There doesn't seem any error messages after inserting the BT module - does scanning work after running sudo modprobe bluetooth ?

trekdrop

@mitu said in Bluetooth inactive.:

sudo modprobe bluetooth

Still the same.

And if do this:

pi@retropie:~ $ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
Active: inactive (dead)
Docs: man:bluetoothd(8)

Still dead.

I some where found i need to cold or warm reboot the pi.. I don't know how to do it.
Just trying everything here :D

mitu

@trekdrop Warm reboot - normal reboot, cold reboot - shutdown then remove the power.

trekdrop

@mitu

Sorry, can you please explain me how i do this>?
warm reboot - normal reboot, cold reboot - shutdown then remove the power