Maybe your psu is faulty, or poor quality/knock off etc. with any sort of issue like this, the first thing is to rule out the psu. I have seen reboots before with usb devices connected when the PSU was not sufficient. Also without the usb devices, to make sure it isn’t related to them.

try with another PSU. Also ry booting without USB device etc.

FIXED!

If anyone is interested, to bypass the welcome, no gampad detected screen even with no controllers connected this is what I did to make it work everytime:

plug in a USB keyboard and setup the buttons with the keyboard ONCE. Unplug keyboard and reboot. Should go straight to the main emulator menu.

Thanks

Which version of retropie are you running?

(Make sure you are running the latest 2.5.x version)

how are you powering your pi ?

(I have seen reboots like this due to power supply issues.)

have you enabled overclocking ?

(Can also cause instability depending on settings)

do you have any usb devices connected?

Well I finally got RetroPie up and running via Buzz Img.

Now I am stuck on trying to configure my Realtek RLN8192CU WLAN adapter. I’ve looked at a TON of things online but nothing is working.

I have one question do I need to be connected via Ethernet BEFORE I can configure it?!

Any suggestions, or threads I should try?

EDIT****

Well I finally got the USB to work.
What I did differently was unplug the adapter change the settings reboot the Pi then plug it in.

Now I’m updating the binaries…and my god this is taking awhile. I wish there was a progress bar somewhere.

This is taken from my own PERSONAL installation guide that i have been creating as I build my retro station. Please excuse any spelling mistakes and such, I spun this off while working on the pi, but the steps are exactly the process I used while doing individual emulator mapping.

ALTERING EMULATOR SPECIFIC CONTROLS

Assuming you have 4 controllers that are the same… (if not scroll down)

From terminal, type”

cd /opt/retropie/emulators/retroarch/configs

dir (or ls -1)

Now select a controller to look at for reference for button mapping

sudo nano “controller cfg file to reference/alter”

find specific buttons to change and write down the current configuration. For example, I want to change the NES a and b button mapping by swapping the function of each. MadCatzXbox360Controller.cfg states:

input_a_btn = “0”
input_b_btn = “1”

So now I exit without changing anything (ctrl X, n, enter)

Now type:

cd /opt/retropie/configs/nes
sudo nano retroarch.cfg

Now in nano, scroll to the bottom and type:

input_player1_a_btn = “1”
input_player2_a_btn = “1”
input_player3_a_btn = “1”
input_player4_a_btn = “1”
input_player1_b_btn = “0”
input_player2_b_btn = “0”
input_player3_b_btn = “0”
input_player4_b_btn = “0”

Now press ctrl x to exit, y to save, and enter.

IF YOU HAVE DIFFERENT CONTROLLERS (not all the same type)

Enter the emulator you want to alter mapping for. Find the USB that controls the 1st, 2nd, 3rd, and 4th player controllers. Write down the type of controller is for each # player. Exit emulation and emulationstation.

Now in terminal follow the above instructions but repeat the first part for finding how the controller is configured (cd /opt/retropie/emulators/retroarch/configs and sudo nano config file for the controllers that need to be changed) for the controller type for each player. Write down the controls that you want to change under each controller type/player.

Continue to the emulator retroach.cfg file (IE: cd /opt/retropie/configs/nes then
sudo nano retroarch.cfg) and alter the buttons by player# and controller type for remapping (using the configurations from the controller config files). for example, if player 1 is an xbox controller, player one should be reconfigured using mapping for xbox controllers, playstation player # to playstation mapping, etc..

NOTE: You may want to mark what ports they are plugged into by painting a number on the port and the controller. As long as the controllers are in the SAME ports when you load the pi, they should be correctly mapped each time you start emulation.

[quote=87244][directory] artwork=/home/pi/RetroPie/roms/mame-artwork rompath=/home/pi/RetroPie/roms/mame samplepath=/home/pi/RetroPie/roms/mame-samples[/quote]

That was EXACTLY right Roo!!! I change the path to = /media/usb/mame and now it is finding the roms and all the needed file to run the roms!

Anyone who is running ROMs from USB, here is the answer for MAME not finding ROM files!

Thank you again Roo!

[quote=87271]1. With the increase in horsepower will we see Saturn and Gamecube emulation?[/quote]

Probably not, the Pi is still not powerful enough for that IMO. It’s always possible that some intrepid developer figures out a few hacks to get GameCube running smoothly on Pi, but I wouldn’t hold my breath.

[quote=87271]2. Is it better to run games from the SD Card (IE get a big enough SD card) or just run the Retropie from SD and store the games on USB? Either way is fine for me but I’d rather just use the SD card, but I’ve heard something about the Pi corrupting them?[/quote]

Keep it simple in my opinion. No matter what, you’re going to have an SD card, Pi can’t boot from USB. So why add complexity? Yes, if you don’t shut down the Pi correctly before pulling power you will most certainly corrupt some files on the SD card. If that is a huge concern, make a backup image of your SD card, which only takes a few minutes.

[quote=87271]3. Is the Xbox one controller supported? I know this isn’t a ‘standard’ driver so I imagine someone would need to modify a driver for it?[/quote]

No. I went down this road at first. I ended up buying a wireless xbox 360 for windows controller. Much easier and just works.

If you are starting fresh, I would download the latest retropie image and then run these commands as pi user:

cd RetroPie-Setup
sudo bash retropie_setup.sh

That should open up the retropie screen then select:
SETUP
Install PS3 controller driver

follow the on screen directions and you should be setup for the first controller. (It might complain that it cannot find the controller)

REBOOT

then run these commands as root:

cd /opt/retropie/supplementary/ps3controller

now plug in your first controller via usb and run:

sudo ./sixpair

this should set the MASTER for your controller to your Raspi BT dongle.

now unplug the first controller and plug in the second controller and re-run:

sudo ./sixpair

same thing should happen.

Modify the /usr/bin/emulationstation as described above and reboot

should be golden

I did basically the same thing using parts from X-Arcade and two wired USB controllers. I actually made it to use with my Xbox 360 a few years ago, but it happens to be perfect for the Pi.

Hello all,

As I’m waiting for my Raspberry Pi 2 Model B (First Raspberry Pi, YAY!) to be delivered. I was wondering, what about using two DS4’s with RetroPie/ES? Do I need a second config file, or a second set in the config file.

Can anyone tell me? I think it will be great if I can play together with my girlfriend (Yes, I’m that kind of guy ;)).

Also do I use the DS4 wireless or via a USB cable? May be a dumb question, but I’m not afraid to ask.

And the last thing, can I play N64 games with a DS4 controller? And if I can, can someone explain me how?

Thanks!

[quote=87107]So I tested with a different PSU and USB cable, (i use 220v to USB and then a cable) But the problem remains.[/quote]

Not sure what you mean here. Have you actually tried a different wall wart completely? The part that actually converts AC wall voltage to 5VDC? If so, then I would try a different Pi next in the list of troubleshooting steps. If that’s not feasible, try a different display, but that is a long shot

Thanks, this way works like a charm!

From what I experience, related to the questions a couple of replies above…

1. I’ve changed nothing and everything seems to work fine.
2. Sorry can’t help. I Use dd on Mac here.
3. Works perfectly when the steps are followed. Nice small class 10 card, don’t need much space this way ->cheap:-)
4. Sounds stupid, but when tweaking your system, I was looking for sudden files multiple times, since partially they’re on the sd, partially on the USB, ofcourse…

Again, above is just my personal experience after using this setup for about 3 weeks now.

Like Floob said,
When you configure your gamepad when starting Emulation Station it’ll be setup. just be sure it’s connected when you boot and ES automatically recognises it. You have to press some buttons and the configuration is saved to control ES.

I’ve got some aftermarket snes USB controllers, and here the menu you’re looking for appears by pressing start button also by default.

Then you can quit ES ( to command line ) , reboot your system, or, shutdown ES. In the last case your Pi will shutdown like it should.

Hope this somewhat helps or clarify things…

I’m using buzz’s new RPI2 optimised image, working great so far, having so much fun with all the EMUs.

However, when i run startx from the command line i encounter a whitebox (seems to be a mini command line, but i cannot type anything) in the top left hand corner. I cannot do anything else! Any Ideas???

I needed to enter the GUI so that i can configure my wifi usb adapter. I’m new to all of this and i was able to run startx on my older RPI b+ using the older retropie image.

Any feedback would be appreciated.

Thanks!

[quote=87161]what does the section for mame4all in you es_systems.cfg file look like?[/quote]

Stock, except path is altered to
<path>/media/usb/mame

rather than
<path>~/RetroPie/roms/mame

mame4all is the only emulator that “seems” to hiccup on the path.

I used the DAT file from MAME4ALL (from the pi) to compile through clrmamepro. Though it could be incorrect ROM files, it was matched 100% to the DAT file of MAME4ALL, directly from the pi, and complied using the information directly from the pi.

Also, FBA seems to (mostly) work using the same ROM set and USB settings. As 1941 is on both systems, I tried playing on FBA (works perfect) then tried on MAME4 (does not work). That tells me the directory is not the issue (per say), nor the ROM. For some reason, MAME4 is seeing the ROM, directing to it, then ignoring the files inside the ZIP folder or looking elsewhere… or so it seems.

Well, I have one ROM that works for MAME. Thank you to the anonymous source for the CORRECT version of the ROM to match my cabinet.

So I went to the local arcade shop and picked up a few old cabinets that were “beyond repair” and old as sin. I gutted a couple of them and found that the internals are working well (IE: software), but the hardware (and cabinets) are toast. Rather than “repairing” them, I am pulling the ROMs from the 37.b set and building them into on cabinet whilst storing the original internals in a box.

That said, I first used clrmamepro to ensue that I have the correct ROM set and files. According to CMP, I have every file needed and everything should work fine. I have the ROMs on USB in the pi, set the config file at /etc/emulationstation/es_systems.cfg to search for my ROMs under /media/usb/*system I am using* and it works great for everything except the MAME.

Is there another area in the configuration that would tell MAME4ALL where to look for ROMs that would cause it to see the ROMs, start the ROMs, then look elsewhere to run the ROMs? As there are multiple files within a single ZIP file (unlike SNES or genesis, etc), I am concerned that it is seeing the parent directory to list the ROM in MAME, but then trying to execute from a different location. Can that happen? If not, why is MAE4ALL not able to see the files where it was directed to look?

PS.
Short version when I go to media/usb/mame, it shows the games and required files, but in ES, I click on a game, and then it tells me the files that are in folder (verified) are missing. The one game that works is on a different pi on the SD and only works from terminal (not conducive to portability when I have to drag around a keyboard). Ultimately, I want to run the ROMs from the USB as I have the ability to alter game sets and add/delete with ease.

PPS. FBA (mostly) works on the same configuration of /media/usb/fba. I was just playing 1941, but some other ROMs (compiled by clrmamepro) state they are unsupported (?).

Thoughts? Questions? Emotional outbursts?

I plan to do more checking later on PSX/N64. I should be getting a new (and bigger) SD card today as I’ve been testing on a tiny substitute one using a mounted usb drive. Which image should I use? I did use Buzz’ from p2 but is the 2.5 beta on downloads better or Buzz’ latest version?

Hi Guys,
I have done as suggested but all i get is

-- [ ERROR ] ------------------------------------------------------
USBController::USBController(): libusb_open() failed: LIBUSB_ERROR_ACCESS

when the scripts run
/usr/bin/xboxdrv --config /home/pi/kodi/kodi.ini --silent --autofire RT=25 --autofire LT=25 --autofire du=200 --autofire dd=200 --autofire dl=500 --autofire dr=500

Any ideas?