Hi Floob,

I’m having a weird problem with my PS3 controller set up. I run the script as in the video, followed all the instructions. It recognises my bluetooth adapter, but when it asks to insert my PS3 controller via USB, it can’t find it.

I’ve used lsusb and it detects it fine. It also see’s my USB dongle fine.

Grabbing the log shows that I’m missing a file:

<snip>

= = = = = = = = = = = = = = = = = = = = =
Building 'ps3controller' : Install/Pair PS3 controller
= = = = = = = = = = = = = = = = = = = = =

In file included from /usr/include/c++/4.7/arm-linux-gnueabihf/./bits/os_defines.h:40:0,
                 from /usr/include/c++/4.7/arm-linux-gnueabihf/./bits/c++config.h:414,
                 from /usr/include/c++/4.7/iostream:39,
                 from main.cpp:1:
/usr/include/features.h:356:25: fatal error: sys/cdefs.h: No such file or directory
compilation terminated.
rm -f *~ bins/*
mkdir -p bins
g++ -O2 -mcpu=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -pipe -Wl,-Bsymbolic-functions sixad-bin.cpp bluetooth.cpp shared.cpp textfile.cpp -o bins/sixad-bin <code>pkg-config --cflags --libs bluez</code> -lpthread -fpermissive
In file included from /usr/include/stdio.h:28:0,
                 from /usr/include/bluetooth/bluetooth.h:33,
                 from bluetooth.h:21,
                 from sixad-bin.cpp:18:
/usr/include/features.h:356:25: fatal error: sys/cdefs.h: No such file or directory
compilation terminated.
In file included from /usr/include/stdio.h:28:0,
                 from /usr/include/bluetooth/bluetooth.h:33,
                 from bluetooth.h:21,
                 from bluetooth.cpp:18:
/usr/include/features.h:356:25: fatal error: sys/cdefs.h: No such file or directory
compilation terminated.
In file included from /usr/include/unistd.h:26:0,
                 from shared.h:21,
                 from shared.cpp:18:
/usr/include/features.h:356:25: fatal error: sys/cdefs.h: No such file or directory
compilation terminated.
In file included from /usr/include/c++/4.7/arm-linux-gnueabihf/./bits/os_defines.h:40:0,
                 from /usr/include/c++/4.7/arm-linux-gnueabihf/./bits/c++config.h:414,
                 from /usr/include/c++/4.7/cstdlib:43,
                 from textfile.h:21,
                 from textfile.cpp:18:
/usr/include/features.h:356:25: fatal error: sys/cdefs.h: No such file or directory
compilation terminated.

I’ve tried searching how I can get this file, but I can’t seem to make head or tail of it.

I’m using Rasp v2, Retropie v3.0 (Using NOOBS and OpenElec) with only the dongle and USB cable connected, along with ethernet for updates, and an HDMI TV (Not that I’m using it, as I’m doing everything via SSH)

Anybody seen this before, and got any ideas what package I need to download to get the cdefs.h file?

Cheers

Hi!

You need to change the Linux kernel to use 2 joysticks using XinMo USB controller.

Try it!

Custom Kernel for Xinmo
https://www.dropbox.com/s/f610y6q91mfv9zb/custom_kernel_1.20150317-1.tar.gz?dl=0

For ease of configuration, go with Microsoft OEM parts. Mine work without fuss, but the reviews on the non-OEM USB receivers are… well, they’re not great. They either work or they don’t, with the same reciever getting both kinds of reviews.

Oh, and they’re like $10 cheaper (at most) than the OEM receiver, so I’d just go OEM if you wanted the 360 controller (I personally find the 360 controller more comfortable than the dual shock ones, and I see far more “help me!” threads for getting bluetooth and the ps3/4 controllers to play nicely. YMMV).

Hey guys,
These videos have been brilliant. I wouldn’t have been able to get up and running without them.

Unfortunately I’ve hit a bit of a snag here. I can use my PS3 controller (same serial as floob’s) via usb cable quite happily and the buttons are configured. I followed this video to the letter to try and get wireless to work but to no avail. I’m using the same BT adapter as floob too so I should’ve been in the best possible place to follow along with it.
I can get as far as the end of the setup and the controller’s lights flash as described and then it settles on being controller one – so it will pair. Then if you restart (and even with the pause) it never pairs with the bluetooth adapter again after the setup screen.
I’m using retropie 3 and grabbed the latest setup script too.

Any thoughts?

1) the icon means there is not enough power being supplied, so it looks like your hub doesn’t output enough power for the pi. strangely, that hub model appears in the ‘working’ list of RPI hubs (http://elinux.org/RPi_Powered_USB_Hubs#Working_USB_Hubs) with a comment that it powers the pi fine, but perhaps they’ve not tested with the pi2, or using applications that push the system as much as emulation.

not sure about 2!

If we’ve already patched the kernel, should we somehow re-patch to the original kernel? Or would an apt-get update take care of that?

I will try it on the THT-THT 2 player USB version of the controller that is being sold as the XIN-Mo and see if this fixes its problems as well.

First off i would like to thank NinjaJoey’s post over at http://forum.8bitdo.com/thread-328-1-1.html

@kingchili for the use of his es_input.cfg

I have beat my head against a wall on this for about 2 days and these are the step I took with Retropie v3.0 final. I have uploaded my es_input.cfg,8BitdoNES30Gamepad.cfg, retroarch.cfg (controllers.rar)
I would make backups of your current es_input and retroarch configs and over write them with the ones i uploaded to save yourself from doing a lot of editing.The biggest thing is getting the bluetooth mac addresses and registering them. I have tested the controllers in Super Dodge Ball and both worked great. Make sure you back up the files you edit incase something goes wrong, or risk reloading your image.

Make sure you have updated your controllers firmware( at the time of posting 2.62)

Raspberry Pi2
RetroPi 3.0
Kinivo BTD400 bluetooth adapter
All commands were done through putty to ensure only the BT dongle was plugged into the Pi
File transfers were done using WinSCP

es_input.cfg goes here: /home/pi/.emulationstation/
retroarch.cfg goes here: /opt/retropie/configs/all/
8BitdoNES30Gamepad.cfg goes here: /opt/retropie/configs/all/retroarch-joypads

1. sudo apt-get update

2. sudo nano /usr/bin/bluez-simple-agent
Once in you need to look for ‘KeyboardDisplay’ (search for it by crtl+w) and change it to ‘DisplayYesNo’
Now hit Ctrl + x, y, enter to save it

3. sudo reboot

4. Make sure your dongle is plugged in and see if it is working
lsusb

5. To check your device number (mine was hci0)
hcitool dev

6. HOLD START on your NES30 controller for 3 secs until it comes on ( YES, just START )

7. hcitool scan (get the MAC address of the controller)
*You will see xx:xx:xx:xx:xx:xx “8Bitodo NES30 GamePad”

8. sudo bluez-simple-agent hci0 xx:xx:xx:xx:xx:xx

9. sudo bluez-test-device trusted xx:xx:xx:xx:xx:xx yes(dont forget the yes)

10. Verify it was added (should return only a “1”, if “0” start over at step 6)
sudo bluez-test-device trusted xx:xx:xx:xx:xx:xx

11. sudo bluez-test-input connect xx:xx:xx:xx:xx:xx
**Now you should have a solid blue light**

12. I changed the retroarch.cfg (if you used the one i uploaded you can skip this)

sudo nano /opt/retropie/configs/all/retroarch.cfg

Now Look for

input_player1_left = left
input_player1_right = right
input_player1_up = up
input_player1_down = down

These should be under keyboard.

Now change them to:

input_player1_left = nul
input_player1_right = nul
input_player1_up = nul
input_player1_down = nul

and at the end of the file add this: ( all the way to the bottom )

# Player 1
input_player1_a_btn = “11”
input_player1_b_btn = “12”
input_player1_y_btn = “15”
input_player1_x_btn = “14”
input_player1_start_btn = “22”
input_player1_select_btn = “21”
input_player1_l_btn = “17”
input_player1_r_btn = “18”
input_player1_left_btn = “2”
input_player1_right_btn = “3”
input_player1_up_btn = “0”
input_player1_down_btn = “5”

# Player 2
input_player2_a_btn = “11”
input_player2_b_btn = “12”
input_player2_y_btn = “15”
input_player2_x_btn = “14”
input_player2_start_btn = “22”
input_player2_select_btn = “21”
input_player2_l_btn = “17”
input_player2_r_btn = “18”
input_player2_left_btn = “2”
input_player2_right_btn = “3”
input_player2_up_btn = “0”
input_player2_down_btn = “5”

input_enable_hotkey_btn = “21”
input_exit_emulator_btn = “22”

13. In Retropie 3.0 controller configs are located:
/opt/retropie/configs/all/retroarch-joypads

I made my own .cfg file named 8BitdoNES30GamePad.cfg and pasted the below into it it, then uplaoded to the controller directory.
####
input_device = “8Bitdo NES30 GamePad”
input_driver = “udev”
input_b_btn = “12”
input_y_btn = “15”
input_select_btn = “21”
input_start_btn = “22”
input_up_btn = “0”
input_down_btn = “5”
input_left_btn = “2”
input_right_btn = “3”
input_a_btn = “11”
input_x_btn = “14”
input_l_btn = “17”
input_r_btn = “18”

input_enable_hotkey_btn = “21”
input_exit_emulator_btn = “22”
####

14. Register the 2nd controller
Hold start on the controller
hcitool scan
sudo bluez-simple-agent hci0 xx:xx:xx:xx:xx:xx
sudo bluez-test-device trusted xx:xx:xx:xx:xx:xx yes

This will add the controllers mac to the trusted devices and will let it connect when using the shell script

I made a shell file on my pc and uploaded it to the ports rom folder to connect player 2 controller
sudo bluez-test-input connect XX:XX:XX:XX:XX:XX (controller2.sh) with your MAC
Do the following so you can execute the script from ES
cd RetroPie/roms/ports
cdmod +x controller2.sh

sudo reboot

Now the shell should show up in the ports folder and can be ran. I just pressed start to start my 2 controller and came up fine.

To be able to control emulationstation with the controller i used config modified by kingchili
make a backup of your current es_input.cfg and over write it with the one post above.

[quote=104460]That lovely little square is telling you you have an insufficient power supply. You need 2A 5V. Sometimes cables can be bad even if your power supply is good. Get a new adapter. I use one from amazon from kootek that seems to work fine for me.
[/quote]

I had this issue and all i had to do was use a shorter usb cable. In some cases it is the power supply but if you have a smaller wire i would try that before changing power supply.

p.s it’s not a stupid question lol.

I’ve finally had some time to test the Xin-mo dual controller with a fresh installation of RetroPie 3.0 and the autofire on the axis issue no longer exists, so applying the previous patch is not needed anymore. Great news!

With regards to it not being recognised as 2 controllers, I’ve tested the addition to /boot/cmdline.txt method that @feederchain describes above and it also works with the Xin-mo dual controller. The code to add to the end of the line (after a white space) is:

usbhid.quirks=0x16c0:0x05e1:0x040

Reboot required after saving the file.

Having reached this solution, I’m not going to bother trying to patch the kernel as this fix is simple enough for those of us with the Xin-mo.

Thanks very much to @feeder for all the help and effort!

Hi guys,

can you help me to set up my PS3 controller.
I’m following the guide step by step but when I pull out the USB cable and press PS button on PS3 controller all 4 LEDs start lighting quickly and stacked just for a half seconds and then continuous lighting an-till goes off and controller not detected.
I have tried 2 Bluetooth dongles with bluetooth version 2 and 4 but nothing append.
My retropie system:
Raspberry Pi2
Retropie 3 final
USB Bluetooth v2 and v4 dongles
PS3 controller

thank you!

[quote=104258]I still need to find a way to control Kodi using a joystick/gamepad. apparently the support is there for it, but it’s been disabled due to openelec.
Using a teensy 2.0 as my usb gamepad controls. trying to find a way to control everything without needing a 2nd device such as a smart phone.

Edit:

Djinny wrote:

from the kodi forums.
AFAIK for joystick support Kodi needs to be compiled with –enable-joystick –enable-sdl.
From what I can see from OSMC git Kodi is explicitly compiled with –disable-sdl –disable-joystick. Frown
Edit: ask in @Milhouse’s openelec thread, openelec has sdl/joystick support, not sure if it’s enabled in @Milhouse’s builds.

Maybe we can enable the sdl here.. has anyone tried?

[/quote]

If you have an Xbox 360 controller I can show you how I have mine set up, it works perfectly in the emulators in ES and in Kodi, I can switch back and forth

To be honest I regret buying the thing, should have just gotten a cheaper wired USB SNES controller instead.

@monchote Exactly! This hack DID fix my 2 player issue (in 3.0 beta). I never actually had the original auto fire issue in the first place. 3.0 (proper) seems to have undone that fix. Whether it was an accident or not, it worked.

@feederchain I have the Xin-Mo 2 player (or at least that’s what I paid for) but it shows up in Retroarch as a “THT THT 2 Player USB.” From what I understand, they’re essentially the same hardware.

Please let me know if I can be of help testing anything.

Hi everyone! I tried the guide to set up my Dual Shock 4 with my RetroPie and once I get to the step where it asks you to connect your controller via USB, my controller is simply not detected. Now, I realise the guide is for PS3 controllers, but is there anything I can do to make a Dual Shock 4 work wirelessly, or is it simply not supported currently?

To be clear, the controller works great when connected via USB in both EmulationStation and in the emulators I’ve tried (NES, SNES, Genesis), so I’m not sure why the script doesn’t find it, though I guess it’s probably looking specifically for a PS3 controller??

Any help or nudges in the right direction appreciated, as I am a complete newbie at this. :)

Thanks!

@ Floob, I can change the corresponding buttons in fba2x.cfg, but none of the changes seem to have impact at all, even the USB keyboard doesn’t respond.

Clean installation of RetroPie 3, enable SSH, Expand File System, Copy NEOGEO ROMS (4 of them), Copy SNES ROM (SMW), Pair PS3 Controller. Nothing more nothing less, so any further advice would be appreciated.

I still need to find a way to control Kodi using a joystick/gamepad. apparently the support is there for it, but it’s been disabled due to openelec.
Using a teensy 2.0 as my usb gamepad controls. trying to find a way to control everything without needing a 2nd device such as a smart phone.

Edit:
[quote=asavah] from the kodi forums.
AFAIK for joystick support Kodi needs to be compiled with –enable-joystick –enable-sdl.
From what I can see from OSMC git Kodi is explicitly compiled with –disable-sdl –disable-joystick. Frown
Edit: ask in @Milhouse’s openelec thread, openelec has sdl/joystick support, not sure if it’s enabled in @Milhouse’s builds. [/quote]

Maybe we can enable the sdl here.. has anyone tried?

I am having the same issue with absolutely no luck. My back up plan, will be to try map player 2 toa usb controller and keep player 1 a keyboard.

reason why I need keyboard input is because I am using an x arcade which encodes keyboard strokes