PC setup: PS3 Dualshock connects nothing happens

Hi There,

I followed the instructions to connect PS3 Dualshock controller. I don’t receive a “authorized” controller, yet I’m able paired and trust the controller. I’m currently using a sabrent bluetooth adapter to connect. I searched for a fixed and nothing comes up.

Is there a fix to this?

Thank You.

Hi,

Did you check common issues ?

Is it possible to get the output of lsusb after plugging your BT adapter ? You need to access Lakka command line interface.

Thank you.

Hello,

I receive this log.

Thanks!

Lakka:~ # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

________________________________________________________________________________________________________________________________– Also,

the “dmesg” command

[ 3398.018286] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 3398.018293] Bluetooth: HIDP socket layer initialized [ 3398.019438] input: PLAYSTATION®3 Controller as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/bluetooth/hci0/hci0:2/0005:054C:0268.0002/input/input16 [ 3398.019764] sony 0005:054C:0268.0002: input,hidraw0: BLUETOOTH HID v0.00 Joystick [PLAYSTATION®3 Controller] on 00:15:83:15:a3:10


My current status

Lakka:~ # systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2010-07-30 02:55:53 UTC; 1h 14min ago Main PID: 357 (bluetoothd) Status: “Running” CGroup: /system.slice/bluetooth.service └─357 /usr/lib/bluetooth/bluetoothd

Jul 30 02:55:53 Lakka systemd[1]: Started Bluetooth service. Jul 30 02:55:53 Lakka bluetoothd[357]: Bluetooth daemon 5.37 Jul 30 02:55:53 Lakka bluetoothd[357]: Starting SDP server Jul 30 02:55:53 Lakka bluetoothd[357]: Failed to open RFKILL control device Jul 30 02:55:53 Lakka bluetoothd[357]: Bluetooth management interface 1.12 initialized Jul 30 02:55:53 Lakka bluetoothd[357]: Failed to obtain handles for “Service Changed” characteristic Jul 30 03:45:11 Lakka bluetoothd[357]: sixaxis: compatible device connected: PLAYSTATION®3 Con…268) Jul 30 03:45:11 Lakka bluetoothd[357]: sixaxis: setting up new device Jul 30 03:52:25 Lakka bluetoothd[357]: sixaxis: compatible device connected: PLAYSTATION®3 Con…268) Jul 30 04:02:25 Lakka bluetoothd[357]: input-hid profile connect failed for E0:AE:5E:2D:49:97: D…busy Hint: Some lines were ellipsized, use -l to show in full.

Also,

the “dmesg”

[ 3398.018286] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 3398.018293] Bluetooth: HIDP socket layer initialized [ 3398.019438] input: PLAYSTATION®3 Controller as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/bluetooth/hci0/hci0:2/0005:054C:0268.0002/input/input16 [ 3398.019764] sony 0005:054C:0268.0002: input,hidraw0: BLUETOOTH HID v0.00 Joystick [PLAYSTATION®3 Controller] on 00:15:83:15:a3:10

First, did you try also to reset your controller ?

Can you try this little setup ?

By the way, what is the output of lsusb when you controller is plugged ?

Thank you.

use a nightly build if you aren’t using one yet-happens to my xbox360 controller too

Here’s the lsusb log.

Lakka:~ # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

When your controller is plugged in usb :wink:

Sorry about that.
Lakka:~ # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 054c:0268 Sony Corp. Batoh Device / PlayStation 3 Control ler Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle ( HCI mode) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lakka:~ #

I’ve successfully ran the nightly backup. BTW: this is a pc setup.

Currently this is my status:

Lakka:~ # systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2010-07-31 02:27:25 UTC; 8min ago Main PID: 369 (bluetoothd) Status: “Running” CGroup: /system.slice/bluetooth.service └─369 /usr/lib/bluetooth/bluetoothd

Jul 31 02:34:28 Lakka bluetoothd[369]: input-hid profile connect failed for E0:AE:5E:2D:49:97: Device or resource busy Jul 31 02:34:28 Lakka bluetoothd[369]: input-hid profile connect failed for E0:AE:5E:2D:49:97: Device or resource busy Jul 31 02:34:28 Lakka bluetoothd[369]: input-hid profile connect failed for E0:AE:5E:2D:49:97: Device or resource busy Jul 31 02:34:29 Lakka bluetoothd[369]: input-hid profile connect failed for E0:AE:5E:2D:49:97: Device or resource busy Jul 31 02:34:29 Lakka bluetoothd[369]: input-hid profile connect failed for E0:AE:5E:2D:49:97: Device or resource busy Jul 31 02:34:29 Lakka bluetoothd[369]: input-hid profile connect failed for E0:AE:5E:2D:49:97: Device or resource busy Jul 31 02:34:30 Lakka bluetoothd[369]: input-hid profile connect failed for E0:AE:5E:2D:49:97: Device or resource busy Jul 31 02:34:30 Lakka bluetoothd[369]: input-hid profile connect failed for E0:AE:5E:2D:49:97: Device or resource busy Jul 31 02:34:31 Lakka bluetoothd[369]: input-hid profile connect failed for E0:AE:5E:2D:49:97: Device or resource busy Jul 31 02:34:32 Lakka bluetoothd[369]: input-hid profile connect failed for E0:AE:5E:2D:49:97: Device or resource busy