Actually looking at the Mausberry, it says it uses pins 23 and 24. Im no genius with schematics, but those pins above look to be dead considering they are X'ed out. Worth looking into, but even still you better be comfortable with soldering because the vga666 doesn't have exposed pins so you'll probably have to solder the mausberry wires to the pin bases on top of the vga hat

@mediamogul

I obtained another ROM. I realized that retroachievements showed "bad rom pile" on their website when I loaded the old file.

@b00stnv8 Thanks for your answer. I'm a bit confused about your ON/OFF LED. On which pins did you solder your LED ? Same for your Shutdown scripted button ? I found some interesting answers too here for the GPIO power state led and here for the safe shutdown switch. Tell me what do you think about it.

Thanks Gerald. This worked for me! I'm assuming I'll have to do this for every additional controller I have connected, but it's not a big deal. I wonder why the main Configure Input on the emulation station doesn't work for the individual roms.

Press start and choose Configure Input - try to map buttons once again You can change exit hotkey button but only for two buttons - one button for activate hotkey and second for exit lr-xxx is a libretro so it's all well connected through RetroArch so you can press hotkey set for RetroArch menu and configure your buttons. If you don't use libretro then you have to set it manually (probably by editing some text file) You can do it from pc via SSH but you have to know basics of linux bash. It would be easier to do just by RetroArch and trying to stick to libretro (lr-xxx) emulators. Just use RetroArch menu during libretro emulator working.

@Melvin.FoX i will. And if i still have issues i will post them.

The same problem sonicsheppard, the topic of the post was back -- the keyboard not working. Context. In any case, I recompiled SDL2 and EmulationStation from source and all is now well for me.

Hello,

I have this same issue and after some research i have determined that it is a problem with how wminput uses the blue-tooth adapter.

Here is an old Ticket for wminput that explains the problem a little better.
http://abstrakraft.org/cwiid/ticket/71

Using -d appears to be what causes the issue.

When I remove the -d flag I can ssh into my raspberry pi however with -d enabled I cannot.

HOWEVER:

By removing -d you cannot add a wiimote after the system has started.

You can connect them when the retropie screen appears by pressing 1 and 2.

Questions like this should be in KODI forum and not here... Well it shouldn't be anywhere because they are very well explained in Kodi wiki...

@krull please post the contents of that file. Use pastebin site, or put in code block (SSH in).

@FlyingTomahawk

The theme used does have a CC license on it.

It's not a fake sd card but I think I have confirmed it is a faulty unit. I decided to look in the vendor's, adafruit support forums and found this. https://forums.adafruit.com/viewtopic.php?f=8&t=109254&p=545910&hilit=freeze+pi#p545910
It seems im not the only one having this issue, I have since contacted them for a replacement or return and now im just waiting on their reply. Thank you everyone.

I figured it out. In the Retropie menu, I had to go into Audio options and change the audio output from 3.5mm Stereo to HDMI because I went from using a PC monitor with the 3.5mm out to full HDMI A/V on my TV. Now FBA and everything else plays smooth and sounds fine.

@jabberwock101 yes i would still try this patch. I would say it is most likely to fix it.