@mitu
Hello,

I don't have a PS3.

What PC program do I use to test the controller?

The controller does not have a switch option but it can be reset, after connecting it to the PC and testing it, I try to reset the controller.

If after doing a reset, it still does not work, I will try the option to reinstall xpad.

Thank you.

Reading the replies from @doug and @b3n, I've managed to implement the fix by giving a change to the report when the controller is connected.

[48361.273580] usb 1-2.4: USB disconnect, device number 25 [48366.681972] usb 1-2.4: new full-speed USB device number 26 using xhci_hcd [48366.883070] usb 1-2.4: New USB device found, idVendor=054c, idProduct=0268, bcdDevice= 0.01 [48366.883092] usb 1-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [48366.883102] usb 1-2.4: Product: PS3 Controller [48366.890323] usbhid 1-2.4:1.0: can't add hid device: -32 [48366.890366] usbhid: probe of 1-2.4:1.0 failed with error -32 [48366.905149] usb 1-2.4: USB disconnect, device number 26 [48367.449946] usb 1-2.4: new full-speed USB device number 27 using xhci_hcd [48367.643118] usb 1-2.4: New USB device found, idVendor=054c, idProduct=0268, bcdDevice= 5.72 [48367.643141] usb 1-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [48367.643150] usb 1-2.4: Product: PS3 Controller [48367.654388] input: PS3 Controller Motion Sensors as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0/0003:054C:0268.0014/input/input47 [48367.706730] input: PS3 Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0/0003:054C:0268.0014/input/input46 [48367.707515] sony 0003:054C:0268.0014: input,hiddev98,hidraw6: USB HID v81.11 Joystick [PS3 Controller] on usb-0000:00:14.0-2.4/input0

Good: The driver works even with the latest driver available. It just change the report of the given controller, so, other controllers will remain functional.

Bad: The controller only works with the cable and the player's count LEDs turn on in a weird way.

TODO: I still want to make this driver actually doable. Any help will be very welcome.

GitHub: https://github.com/KanuX-14/GeneriKit

Edit: The original driver will be kept. It can be enabled again by deleting the line 'blacklist hid-sony' in /etc/modprobe.d/generikit.conf.

Can you add more details about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first ?

@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.

@steeeb I've tried that. I've actually tried all 4 possible drivers and none of them seem to work for any of the three generic controllers. For each driver, I do the same thing:

First, install the driver. I choose the "Pair" option for the respective driver. The dialog pops up to connect the controller through USB. I connect the controller for around 10s, and then disconnect it. I then press the PS button on the controller and.... The lights just flash repeatedly and none of them become solid, meaning that the controller wasn't able to connect.

I've probably tried the Shanwan driver the most but it's always the same result.

I am running a Pi3 64gb card

thanks, but problem persist. When I install the ps3 controller driver, the onboard bluetooth of the pi3 stops working and when I remove it works again.

when doing "sudo service bluetooth status" I get the following:

pi@retropie:~ $ sudo service bluetooth status

● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Active: failed (Result: signal) since Tue 2017-06-13 00:05:01 UTC; 5min ago
Docs: man:bluetoothd(8)
Main PID: 767 (code=killed, signal=KILL)
Status: "Running"

Jun 12 02:17:08 retropie bluetoothd[767]: Bluetooth daemon 5.23
Jun 12 02:17:08 retropie systemd[1]: Started Bluetooth service.
Jun 12 02:17:08 retropie bluetoothd[767]: Starting SDP server
Jun 12 02:17:08 retropie bluetoothd[767]: Bluetooth management interface 1.1...d
Jun 12 02:17:08 retropie bluetoothd[767]: Sap driver initialization failed.
Jun 12 02:17:08 retropie bluetoothd[767]: sap-server: Operation not permitte...)
Jun 13 00:05:01 retropie systemd[1]: bluetooth.service: main process exited...LL
Jun 13 00:05:01 retropie systemd[1]: Unit bluetooth.service entered failed ...e.
Hint: Some lines were ellipsized, use -l to show in full.
pi@retropie:~ $