@mitu said in Install Sixaxis on an old Raspi 3b+:

@pscotto1234 You can either look in $HOME/RetroPie-Setup/logs and unpack the latest log file or just post the error you're seeing on screen.

I tried to launch Retropie Setup script and I am not able to launch it anymore. This is the log I had:

pi@retropie:~/RetroPie-Setup $ sudo ./retropie_setup.sh Did not find needed dependencies: subversion python3-pyudev dirmngr. Trying to install them now. E: Command line option --allow-releaseinfo-change is not understood in combination with the other options Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libbluray1 libgles1-mesa libiso9660-8 libmodplug1 libvcdinfo0 libvlccore8 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libapr1 libaprutil1 libserf-1-1 libsvn1 python3-six Suggested packages: dbus-user-session pinentry-gnome3 tor python-six-doc db5.3-util subversion-tools The following NEW packages will be installed: dirmngr libapr1 libaprutil1 libserf-1-1 libsvn1 python3-pyudev python3-six subversion 0 upgraded, 8 newly installed, 0 to remove and 11 not upgraded. Need to get 2,850 kB/2,903 kB of archives. After this operation, 10.2 MB of additional disk space will be used. Err:1 http://raspbian.raspberrypi.org/raspbian stretch/main armhf dirmngr armhf 2.1.18-8~deb9u4 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] Err:2 http://raspbian.raspberrypi.org/raspbian stretch/main armhf libapr1 armhf 1.5.2-5 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] Err:3 http://raspbian.raspberrypi.org/raspbian stretch/main armhf libaprutil1 armhf 1.5.4-3 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] Err:4 http://raspbian.raspberrypi.org/raspbian stretch/main armhf libserf-1-1 armhf 1.3.9-3+deb9u1 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] Err:5 http://raspbian.raspberrypi.org/raspbian stretch/main armhf libsvn1 armhf 1.9.5-1+deb9u5 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] Err:6 http://raspbian.raspberrypi.org/raspbian stretch/main armhf subversion armhf 1.9.5-1+deb9u5 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/g/gnupg2/dirmngr_2.1.18-8~deb9u4_armhf.deb 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/a/apr/libapr1_1.5.2-5_armhf.deb 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/a/apr-util/libaprutil1_1.5.4-3_armhf.deb 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/s/serf/libserf-1-1_1.3.9-3+deb9u1_armhf.deb 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/s/subversion/libsvn1_1.9.5-1+deb9u5_armhf.deb 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/s/subversion/subversion_1.9.5-1+deb9u5_armhf.deb 404 Not Found [IP: 2a00:1098:0:80:1000:75:0:3 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Unable to install packages required by /home/pi/RetroPie-Setup/retropie_packages.sh - Could not install package(s): subversion python3-pyudev dirmngr.

Resolved changing repository link with:

deb http://legacy.raspbian.org/raspbian/ stretch main contrib non-free rpi

I hope this could help someone else with the same issue!

I've taken a look at this and it seems the issue is the Bluez updates due to CVE-2023-45866 (as I said initially).
This will likely affect any (old) gamepad which doesn't encrypt the comunication with the host. The workaround is suggested in the linked Ubuntu bug report:

Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
Run sudo systemctl restart bluetooth or reboot

Possibly other gamepads affected - the Wii U Pro Controller (haven't tested it yet).

NB: this issue is not restricted to Raspberry Pi, it affects any platform where Bluez was patched for CVE-2023-45866.

@dawc21 said in PS3 Clone Controller is recognized however 2 buttons are not recognized:

@windg

Thank-you for sharing this information. What is the path so that it changes globally? I can find these configurations in a few different places...

The path I think it is :

/opt/retropie/configs/all/retroarch/autoconfig

Yes this the path for the file, this is what i change too.

@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

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.

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 Many thanks for all this work too. Just to let you know I had to tweak this guide slightly as when running 'make modules_prepare' I got errors on Retropie 4.8 running on a pi zero 2W. It seems that I had to install 'libssl-dev' first before this command. Can confirm that after this all other steps worked, rebooted and rumble working on both pads as expected on the Trixes adaptor.

For those getting the same errors, here's a full update to @peg guide (I take no credit and thank @peg for this easy tutorial and just helping anyone with the same issue)

# Install required tools (bc is required for modules_prepare, see Compile) sudo apt-get update sudo apt-get install build-essential bc # Setup required variables FIRMWARE_HASH=$(zgrep "* firmware as of" /usr/share/doc/raspberrypi-bootloader/changelog.Debian.gz | head -1 | awk '{ print $5 }') KERNEL_HASH=$(wget https://raw.github.com/raspberrypi/firmware/${FIRMWARE_HASH}/extra/git_hash -O -) KERNEL_VERSION=$(uname -a | awk '{ print $3 }') HID_DRIVERS_DIR=/lib/modules/${KERNEL_VERSION}/kernel/drivers/hid BUILD_DIR=~/psff_build # Setup build dir mkdir $BUILD_DIR cd $BUILD_DIR # Get kernel source wget https://github.com/raspberrypi/linux/archive/${KERNEL_HASH}.tar.gz -O ${KERNEL_HASH}.tar.gz tar xfz ${KERNEL_HASH}.tar.gz cd linux-${KERNEL_HASH} # Get Module.symvers and Module7.symvers (not sure Module.symvers is really needed) wget https://raw.github.com/raspberrypi/firmware/${FIRMWARE_HASH}/extra/Module.symvers wget https://raw.github.com/raspberrypi/firmware/${FIRMWARE_HASH}/extra/Module7.symvers # Get current kernel config sudo modprobe configs gunzip -c /proc/config.gz > .config # Enable force feedback / rumble support sed -i 's/# CONFIG_PANTHERLORD_FF is not set/CONFIG_PANTHERLORD_FF=y/' .config sed -i 's/# CONFIG_GREENASIA_FF is not set/CONFIG_GREENASIA_FF=y/' .config # install libssl-dev otherwise following driver compile will fail on 4.8 / pi zero 2w sudo apt-get install libssl-dev # Compile driver make modules_prepare make drivers/hid/hid-pl.ko # Update existing hid-pl.ko with FF support (w/ backup of old version) sudo cp -b drivers/hid/hid-pl.ko ${HID_DRIVERS_DIR} # Enable ff-memless module (not sure why "sudo echo ..." isn't enough) sudo su echo ff-memless >> /etc/modules exit # Reboot sudo reboot