@Emmuss
From the command prompt

List all USB devices
lsusb

cat /proc/asound/modules

Set "card #1" as the default audio device
sudo nano /etc/asound.conf

pcm.!default { type hw card 1 } ctl.!default { type hw card 1 }

Disable HDMI audio
sudo nano /boot/config.txt

#hdmi_drive = 2

RetroArch audio fix
/opt/retropie/configs/all/retroarch.cfg

audio_device = "<name of USB audio device>"

Test audio
aplay -l

More info here:
https://learn.adafruit.com/usb-audio-cards-with-a-raspberry-pi/updating-alsa-config

@NinjaX567
Please post the contents of your emu.cfg file. You can post it at pastebin.com and put the link to it in your reply.

Sorry, this was not working....

pi@retropie:~ $ bluez-test-device remove E8:06:88:4D:25:43
-bash: bluez-test-device: command not found

I finally decided to address this on my Genesis Pi and tweaking the es_systems.cfg file also fixed it for me. Thanks again to everyone for your support.

@MrMasterGenius It's always easy once you know how!

@kkostis said in Gamepad and Light bolt problem (Rpi3):

May some updates caused that problem?

Sometimes it can happen that a system update will tip you over the edge of what a power supply can handle. If that is in fact the case here, then you were probably at the borderline all along.

I removed the whole opt/ folder from root and replaced it with one from a fresh install and changed the permissions. Then removed the gamecon USB driver for the 2 SNESpads and removed SFC30 from bluetooth. Paired it and set it up in Emulation Station.

Now the SFC30 is working like it should again, I'm pretty sure as soon as I'm going to install the gamecon USB driver again the SFC30 is going to stop working. Any Idea on how to prevent this?

I have the same issue. I am sending this gamepad back and going back to my first gen Amazon Fire TV game controller which surprisingly works great with retropie.

they're both bootable. get the right one for whatever pi you're using: https://retropie.org.uk/download/#Pre-made_images_for_the_Raspberry_Pi

@Seriuskiller Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Which image ? Did you unpack it as detailed in the installation instructions ? 2.5a is recommended for a RPI3, 2a may not be enough, but the boot issue may be due to incorrectly written image or bad download, or something else.

You can also use https://etcher.io/ to write it without unpacking.

@Spiky well that would be a definite sign of a bootleg.

Scratch that- it IS working. Turns out when I changed the default emulator it wasn't saving in the config menu. Thanks @BuZz !

@erenner said in RetroPie 3.7 + Child friendly EmulationStation wont start:

Zigurana...

I installed the child friendly version of ES last night. It has been working fine until now. I just restarted ES, after adding some MAME roms (zip files), and now it won't boot back into it. It keeps taking me back to the command line and at the top it says something about "out of range". Can you help? I didn't do anything else.

Thanks!

Okay...so I did the following through Putty from the command line...

sudo apt-get update
sudo apt-get upgrade
Now it seems to be working again. Hmmm...

Thanks @BuZz. If it does it again next time I start a topic I'll let them know.

leaving the session for a while and coming back

/me Scratches head... Leaving the site? I don't understand... (hehe)

@mahcneto list what files you are having an issue with. I havent found one i have had an issue with yet. Also read the last posts i replied to you on

@Jofo well, being that I now have several versions of the PSX bus reader, I can talk about my results with all versions.

The original version of the driver, even with the Select button filtered, definitely had sporadic issues with input glitches. My updated version was nearly perfect after filtering the Select button. I'm pretty sure the Acknowledgement line implementation is what did it. I'm pretty confident in that one.

However, the Arduino reader is 100% perfect. So far I've needed no filtering, it all just works. I need to work on the CPU usage of the driver though, still, but for what it's worth, it should work on the Pi. Just plug the Arduino in with USB.