PS3 dual shocks suddenly stopped working

RetroArch
#1

I am using the newest Lakka on a 64 bit old machine. It works great!

A few days ago my bluetooth dongle arrived, and I quickly followed the details online for setting up the bluetooth. My two PS3 dual shock controllers paired fine and worked wonderfully.

Today when I turn on my machine, my controllers won’t pair. I’m completely lost. Here is what I have below, but I didn’t change anything! Same hardware, same stuff, it just stopped working. Does anyone have any thoughts? What can I try? please help1

Lakka:~ # bluetoothctl 
[NEW] Controller 00:1A:7D:DA:71:11 BlueZ 5.43 [default]
[NEW] Device A4:D1:8C:78:33:7E A4-D1-8C-78-33-7E
[NEW] Device 00:1E:3D:D8:E6:8E PLAYSTATION(R)3 Controller
[NEW] Device 00:21:4F:14:8F:15 PLAYSTATION(R)3 Controller
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller 00:1A:7D:DA:71:11 Discoverable: yes
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1A:7D:DA:71:11 Discovering: yes
[CHG] Device A4:D1:8C:78:33:7E RSSI: -45
[CHG] Device A4:D1:8C:78:33:7E ManufacturerData Key: 0x004c
[CHG] Device A4:D1:8C:78:33:7E ManufacturerData Value: 0x09
[CHG] Device A4:D1:8C:78:33:7E ManufacturerData Value: 0x06
[CHG] Device A4:D1:8C:78:33:7E ManufacturerData Value: 0x03
[CHG] Device A4:D1:8C:78:33:7E ManufacturerData Value: 0x03
[CHG] Device A4:D1:8C:78:33:7E ManufacturerData Value: 0xc0
[CHG] Device A4:D1:8C:78:33:7E ManufacturerData Value: 0xa8
[CHG] Device A4:D1:8C:78:33:7E ManufacturerData Value: 0x00
[CHG] Device A4:D1:8C:78:33:7E ManufacturerData Value: 0x47
[bluetooth]# connect 00:1E:3D:D8:E6:8E 
Attempting to connect to 00:1E:3D:D8:E6:8E
Failed to connect: org.bluez.Error.Failed

Then journalctl gives me

Aug 10 20:59:45 Lakka kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Aug 10 20:59:45 Lakka kernel: Bluetooth: HIDP socket layer initialized
Aug 10 20:59:50 Lakka bluetoothd[516]: connect error: Host is down (112)
Aug 10 21:00:14 Lakka bluetoothd[516]: Can't get HIDP connection info

systemctl status blutooth gives me

● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor pr eset: disabled) Active: active (running) since Fri 2018-08-10 20:57:48 CDT; 11min ago Main PID: 516 (bluetoothd) Status: “Running” CGroup: /system.slice/bluetooth.service └─516 /usr/lib/bluetooth/bluetoothd

Aug 10 21:03:38 Lakka bluetoothd[516]: Can’t get HIDP connection info Aug 10 21:03:43 Lakka bluetoothd[516]: connect error: Host is down (112) Aug 10 21:04:05 Lakka bluetoothd[516]: Can’t get HIDP connection info Aug 10 21:04:10 Lakka bluetoothd[516]: connect error: Host is down (112) Aug 10 21:06:03 Lakka bluetoothd[516]: Can’t get HIDP connection info Aug 10 21:06:08 Lakka bluetoothd[516]: connect error: Host is down (112) Aug 10 21:07:10 Lakka bluetoothd[516]: Can’t get HIDP connection info Aug 10 21:07:15 Lakka bluetoothd[516]: connect error: Host is down (112) Aug 10 21:07:17 Lakka bluetoothd[516]: Can’t get HIDP connection info Aug 10 21:07:22 Lakka bluetoothd[516]: connect error: Host is down (112)

#2

update: I pulled some wii motes out of storage.

I also removed all the devices from bluetoothctl.

now when I scan, it doesn’t seem to detect /any/ devices at all, let alone try to connect to them. So perhaps it’s a device issue. sigh! not sure how to debug this

#3

Update: I moved the bluetooth dongle to a new port on my usb hub, and everything started working :frowning: This isn’t encouraging, I hope it’s not a recurring bug.

1 Like