@mitu
I had a pretty bad go of it with this controller. I moved to the ps3controller driver and I did not get that to work per the docs. I tried to sort out which clone I may have, using lsusb, evtest, and dmesg but none gave me any indication other than Sony. So, I tried them all-- Official Sony, shanwan, and gasia. Although I appreciate the info to get additional bluetooth debugging, that project is "crossing the line" with regard to the time I am willing to invest.

Perhaps to make you laugh a bit-- I used retropie for several years with a Logitech F710 controller and an Intellivision Flashback controller. The F710 was getting worn out so I bought another one. It worked terrible! While the new F710 connected no problem, it was very clunky in terms of usability--buttons didn't work quite right, sometimes the control is sticky. Odd! Years ago I had a PS3 and I remember the controller fondly so I thought, I'll try one of those. Needless to say, instead of playing games I'm troubleshooting why this apparently poorly made clone isn't connecting. While the "thrill of the hunt" for the solution to the problem was fun, I'm done.

So, I'm not quite sure which controller I will try next, but the PS3 dualshock clone just found its way to my electronics-recycling box while I sort out my next step.

@phane said in Sixaxis dies after a few minutes, takes BT with it, requires reboot to reconnect:

What rate should I change (there are three in the file based on some if statements I don't understand) and what would be a good setting to reduce it to?

Change the 921600 value and halve it to 460800 (then 230400, 115200 etc.).

@crush I was too. AFAIK if you have ps3controller installed and you install sixaxis, then ps3controllergets automatically uninstalled. But seems like installing ps3controller works perfectly after having installed sixaxis.

This continues to be an issue on x86 builds. I have opened an issue on the RA github but don't have much hope of it getting any traction.

https://github.com/libretro/RetroArch/issues/12312

I updated the original post to say that I am not seeing this issue on older versions of RA (specifically 1.7.3 anyway).

Is there ANYONE else that has 4x genuine PS sixaxis dualshock controllers that can verify what I am seeing? If so, this may give us enough ammo to push the issue with the Libretro team.

John

johnodon created this issue in libretro/RetroArch open RA 1.9.1 - 4th Genuine PS3 Controller Maps to P1 #12312

I have to apologise - I got the same error! Was caused by a recent change: https://github.com/mupen64plus/mupen64plus-ui-console/commit/e147b94f3c82866a42e3f72820e73c441158e7d5#comment

it has been reverted following discussion here: https://github.com/mupen64plus/mupen64plus-ui-console/pull/61

Please try again and it should work.

Jj0YzL5nvJ created this issue in mupen64plus/mupen64plus-ui-console closed Allow non-default compilers without resorting to symbolic links #61 3 richard42 committed to mupen64plus/mupen64plus-ui-console Merge pull request #61 from Jj0YzL5nvJ/alter_cc_cxx Allow non-default compilers without resorting to symbolic links

Hello Guildux,

I got the same issue.

Do you found a solution ?

Thanks'

@psyke83

Love this community. Thanks for a fast response @psyke83 & @mitu.

I ended up hacking your hack in sixaxis-helper.sh.
I basically disabled the whole restart and renaming section by commenting it out.

sixaxis_rename() { local bt_profile="/var/lib/bluetooth/${BLUETOOTH_MAC^^}/${SIXAXIS_MAC^^}/info" if [[ "$(grep -e "^Name=PLAYSTATION(R)3 Controller" -e "^Trusted=true" -c "$bt_profile" 2>/dev/null)" == "2" ]]; then echo "BlueZ <5.48 hack: renaming BT profile to make consistent with kernel module name" # systemctl stop bluetooth # sed 's/.*Name=PLAYSTATION(R)3 Controller.*/Name=Sony PLAYSTATION(R)3 Controller/' -i "$bt_profile" # systemctl start bluetooth exit 0 fi }

The controller paired then.
but like you stated I had to re-config the controller inputs (for BT vs USB).

Digging deeper I compared the two files under var/lib/bluetooth/${BLUETOOTH_MAC^^}/${SIXAXIS_MAC^^}/info for the On-board BT and the Dongle BT addresses.

The file for the on-board BT holds the changes to the renaming "Sony PLAYSTATION(R)3 Controller"
But for the BT dongle - on restart it must overwrite the file again with the old name "PLAYSTATION(R)3 Controller".

Anyway I have a fix that works for me.

@Efriim well thec64 mini doesnt even have a boot folder or 99.9% of linux in it. They made that thing absolutely bare bones as possible. I did discover that the ppsspp emulator on the pi uses a gamecontrollerdb.txt. I added theMayflash adapter to the gamescontrollerdb.txt and then tested in the emulator and the hats work fine. So i am not sure what the c64 mini’s problem is. I do however have a raphnet chip for wii classic controllers that i can solder up the wires to tomorrow to see if that one is working.

https://retropie.org.uk/forum/topic/22312/latest-update-and-ps3-sixaxis-controller/7

Here is the link for others. Will test later.

E: Downgrading worked.

@psyke83 Hi, I was away since a long time.
I'm installing the latest Retropie version on an Rpi 3 and wanted to try the sixaxis driver with a SHANWAN PS3 clone controllor.
I was able to pair the controller but not to connect, the led on number 1 turn on solid red for less than a second and then disconnects.
Sometimes happens that while doing it, Emulationstation crash.
This is the messages on bluetoothctl

Agent registered [<span style="color:blue">CHG</span>] Device 00:26:5C:5D:BD:00 Connected: yes [CHG] Device 00:26:5C:5D:BD:00 Name: PLAYSTATION(R)3 Controller [CHG] Device 00:26:5C:5D:BD:00 Alias: PLAYSTATION(R)3 Controller [CHG] Device 00:26:5C:5D:BD:00 Connected: no [CHG] Controller B8:27:EB:75:21:27 Powered: no [CHG] Controller B8:27:EB:75:21:27 Discovering: no Agent unregistered [DEL] Device 00:26:5C:5D:BD:00 PLAYSTATION(R)3 Controller [DEL] Controller B8:27:EB:75:21:27 retropie [default] Agent registered [CHG] Controller B8:27:EB:75:21:27 Powered: yes [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 Alias: BlueZ 5.50 [CHG] Controller B8:27:EB:75:21:27 Name: retropie [CHG] Controller B8:27:EB:75:21:27 Alias: BlueZ 5.50 [CHG] Controller B8:27:EB:75:21:27 Alias: retropie

There is something I can try to solve the problem ?
Thank you in advance.

Hello! First, thanks @psyke83 for the great work on the ps3/ps4 controllers support in RetroPie.

What is the current status of the driver/procedure for latest RetroPie 4.4 on Debian Stretch to use ps3/ps4 controllers? Are the instructions in https://github.com/RetroPie/RetroPie-Setup/wiki/PS3-Controller still the preferred method at the moment to use these controllers?

Thanks!

@peg As a very experienced windows user and novice Linux user I cant thank you enough for this. Took me about 3 days to get near to achieving it, and you did it in 5 minutes :) Tested on 3 b+ running 4.5.1

I accessed the retropie settings > misc > reicast options about adding a controler, and dimply ran that and told it to add the same PS3 pad, it asked for a few bindings which I set and others didn't (such as 'c' and 'z', no idea what those correspond to the dreamcast controller)

anyway now it works, no idea why it just stopped working. I did do a full retropie update yesterday though.