[tendonut]

Pastebin is just a website you can copy/paste large amounts of text to and have it generate you a link (www.pastebin.com). That way, it doesn’t fill up the forums with poorly formatted copypasta.

[tendonut]

Me too. I mean, in the week or two I’ve been playing with RetroPie, I’ve got it figured out, but I wouldn’t want to have to learn all over again. So many puzzle pieces that aren’t apparent. If I wasn’t a linux sysadmin already, I’d be extremely frustrated.

[tendonut]

Run the following commands and use pastebin.com to post the response
cat /var/log/messages | grep EXT4-fs
cat /var/log/messages.1 | grep EXT4-fs

messages.1 may not exist yet, so if it doesn’t, just skip that.

[tendonut]

It doesn’t work out-of-the-box. In the /home/pi/RetroPie-Setup/retropie_setup.sh script, you have to tell it to install the PS3 controller driver. The “Pair PS3 Controller” script though, always seems to fail. Floob made a good video about it.

I also went through this and was able to get it working my own way.

After running the “Install PS3 controller driver” script, do the following:

1.) Make sure the PS3 controller is still plugged in. The lights should all be flashing.

2.) Run the sixpair utility
sudo /opt/retropie/supplementary/ps3controller/sixpair
This should Make sure the controller (second MAC address) is paired to the MAC address of the Bluetooth dongle (first MAC address)

3.) Add the sixad daemon to the startup sequence
sudo sixad --boot-yes

4.) Unplug the controller, then reboot the system. When the system is back online, Turn on the PS3 controller using the PS button and it should pair up.

[tendonut]

Are you copying the ROMs from the USB stick to the internal microSD card? As far as I know, the Pi doesn’t read the ROMs directly from the USB stick.

[tendonut]

Are you having the same weird graphical issues with all 3 systems?

I’ve personally experienced this issue with the N64 emulator. Luckily, RetroPie comes with a few N64 emulator plugins for Mupen64plus.

Assuming you have RetroPie 3.0 Beta installed, once you start the game, immediately hit X or M on a keyboard after you select the game and the screen goes to a command line and it gives you the option to select different entry. Try the to see what one gives you the best performance. You can do this on a per-ROM basis, since some roms get along with certain emulators, but not others.

[tendonut]

Which system are you talking about specifically? And what version of RetroPie did you install? I’ve seen this on N64 games.

[tendonut]

You can probably skip step 2. Shutdown stops the service as well. But yeah, the built in PS3 pairing system doesn’t really seem to work.

It appears as if the service doesn’t get added to the boot process automatically unless the PS3 pairing script finishes successfully (which I’ve never gotten it to do). So once you install the PS3 drivers, then plug in the controller and run..

sudo /opt/retropie/supplementary/ps3controller/sixpair

and get the two MAC addresses to match, confirming the top MAC address (the controller) matches the bottom MAC address (your Bluetooth Dongle), you can then go ahead and add the sixad daemon to the startup sequence.

sudo sixad --boot-yes

Unplug the USB cable, give the Pi a reboot, and it should sync up after it boots up when you hit the PS button.

[tendonut]

What are you trying to do exactly? Get the RPi to control the power to a monitor/TV somehow?

[tendonut]

I have not tried any themes, I’m about to install RetroPie 3.0 Beta 2 this evening on my new memory card, so I’ll give it a shot if I have time.

[tendonut]

The splash screen uses PNG files. Just make sure the resolution is equal to your TV, or you may get a distorted/pixelated image.

Then you can drop the file into /home/pi/RetroPie-Setup/supplementary/splashscreens. All the other splash screens will be in there, typically in their own directory with just the image inside it.

Once it’s in there, run

sudo ~/RetroPie-Setup/retropie_setup.sh

Navigate to option 3 (SETUP), enable splash screens, then select your splash screen.

I can go into more detail if needed.

[tendonut]

Were you saving using snapshots, or the in-game save functions?

Worse case scenario, you can search the system for the save files.

find /home/pi/RetroPie -name "*ario*orld*.srm"

I use the wonky “*ario*orld*” search string because I don’t know exactly what the ROM file will be named, nor if “Mario” or “World” is uppercase, and wildcards will remedy that.

[tendonut]

I have you restarted or manually started the sixad service after installing the PS3 drivers from the setup script?

[tendonut]

What version of RetroPie are you running?

[tendonut]

Ah! Thanks. I guess I wasn’t holding it long enough.

I am surprised that wasn’t even mentioned on any of the PS3 controller posts.

[tendonut]

I just set the system up two days ago, but I was able to gather this:

1. when i am at the game station selecting page, when i press Start, there’s a “Configure Input”;

This is the controller configuration for the EmulationStation frontend (The GUI that displays all your available emulators/roms)

2. when i select RetroPie, there’s a “Configure RetreArch Kyeboard/Joystick”

This is the gamepad/keyboard configuration for the emulators that use the RetroArch/Libretro libraries. A good chunk of the emulators use it and would share controller configs.

3. same page, “Controller Configuration”

I believe this is where you’d configure a controller that does NOT use the Retroarch libraries.

Anyone else can correct my if I am wrong with these assumptions.

[tendonut]

AH! There we go. Just as you said.

pi@retropie ~ $ sudo lsusb -v

Bus 001 Device 005: ID 0583:2060 Padix Co., Ltd (Rockfire)
......
  iManufacturer           0
  iProduct                2 USB,2-axis 8-button gamepad
  iSerial                 0
  bNumConfigurations      1

That’s my SNES controller. It happens to match up with…

pi@retropie /opt/retropie/emulators/retroarch/configs $ vim USB_2-axis_8-button_gamepad.cfg
input_device = "USB,2-axis 8-button gamepad  "
input_driver = "udev"
input_b_btn = "1"

And for the PS3 Controller, which is a Bluetooth device, I ran

pi@retropie ~ $ hcitool con
Connections:
        > ACL 00:1E:3D:DF:C9:73 handle 11 state 1 lm MASTER

This give me the MAC address of the controller, so then I investigate the name

pi@retropie ~ $ hcitool name 00:1E:3D:DF:C9:73
PLAYSTATION(R)3 Controller

And that happens to match up to the device name in..

pi@retropie ~ $ cat /opt/retropie/emulators/retroarch/configs/PS3Controller.cfg
input_device = "PLAYSTATION(R)3 Controller"
input_driver = "udev"
input_b_btn = "14"
input_y_btn = "15"
input_select_btn = "0"

That answers my question. I totally didn’t think the Buffalo controller would get reported with such a name, so I never drew that connection. Now to get the PS3 controller to work for my PSX games…

(I’m home now, so I can physically play with stuff)

Floob, in your video I watched earlier today, you mentioned that it may not make a difference if you change the file name of the controller cfg file (USB_2-axis_8-button_gamepad.cfg). It seems, if the only connection between the controller and a profile is the iProduct name, wouldn’t that break the connection?

Also, I’m sorry for missing this bit from the first response:

Retroarch creates a configuration file based off of the lsusb identification.

You did actually answer me with that.

EDIT: I threw a summary into the top so future forum browsers can see it easier.

[tendonut]

“I’m sure there is a setting somewhere related to autoenable that remembers your gamepad.cfg”,

That part right there is what I am curious about.

Unfortunately, I don’t have physical access to the Pi (just SSH since I’m at work). I set the system up yesterday and just copy/pasted some generic button mappings into all/retroarch.cfg, but now that I know more about how it works, I’d rather NOT do it this way and allow each unique controller to use its own cfg file. I’ve since commented out the button mappings I added but I am not physically in front of the system to run through the retroarch-joypad CLI. I would assume the device ID from lsusb would be listed in this config file, OR elsewhere in the system, referencing the cfg file. I’m too lazy to grep the whole file system looking for a specific string.

[Author]

Posts