@theink
Just a tip to better describe you issues:
It would be better if you explicitly say what software you are using. ;-) Because GUI can be confused with RGUI (RetroArch GUI).

When you say GUI in your previous post it seems that you refers to the emulationstation, anyway.

Indeed it was the problem, I restored the original file with # char. That's ok, everything is working. Thanks for your help

Compilation apparently fails with a segfault:

https://github.com/gerstrong/Commander-Genius/issues/258

Reported again here today:

https://www.reddit.com/r/RetroPie/comments/56c9yl/commander_genius/

Reproducing on RetroPie 4.0.2, the problem is a GCC segfault:

[ 93%] Building CXX object src/fileio/CMakeFiles/fileio.dir/CPatcherUtils.cpp.o In file included from /home/pi/RetroPie-Setup/tmp/build/cgenius/src/engine/keen/galaxy/common/ai/platform/CVarPlatform.cpp:8:0: /home/pi/RetroPie-Setup/tmp/build/cgenius/src/engine/keen/galaxy/common/ai/platform/CVarPlatform.h: In member function ‘virtual void galaxy::CVarPlatform::_ZTv0_n112_N6galaxy12CVarPlatform9serializeER19CSaveGameController(CSaveGameController&)’: /home/pi/RetroPie-Setup/tmp/build/cgenius/src/engine/keen/galaxy/common/ai/platform/CVarPlatform.h:37:10: internal compiler error: Segmentation fault void serialize(CSaveGameController &savedGame) ^ Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.

We're a few versions behind on cgenius, but the same occurs with the latest stable (v183):

[ 97%] Building CXX object src/engine/keen/galaxy/CMakeFiles/engine_keen_galaxy.dir/common/ai/platform/CPlatformSit.cpp.o In file included from /home/pi/RetroPie-Setup/tmp/build/cgenius/src/engine/keen/galaxy/common/ai/platform/CVarPlatform.cpp:8:0: /home/pi/RetroPie-Setup/tmp/build/cgenius/src/engine/keen/galaxy/common/ai/platform/CVarPlatform.h: In member function ‘virtual void galaxy::CVarPlatform::_ZTv0_n112_N6galaxy12CVarPlatform9serializeER19CSaveGameController(CSaveGameController&)’: /home/pi/RetroPie-Setup/tmp/build/cgenius/src/engine/keen/galaxy/common/ai/platform/CVarPlatform.h:37:10: internal compiler error: Segmentation fault void serialize(CSaveGameController &savedGame) ^ Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.

Someone else got it to compile by changing build flags, but the result was not good:

https://github.com/gerstrong/Commander-Genius/issues/254#issuecomment-241711960

Seems this is a limitation of Jessie's older GCC and an update limitation is imposed by older glibc:

https://github.com/raspberrypi/tools/issues/61

We could resolve this by cross-compiling with a newer GCC somewhere else and providing binaries which cannot be rebuilt directly on the Pi.

According to OP, upstream v17x compiled okay, we could try downgrade RetroPie's port and forever stay on the old version.

@BuZz any thoughts?

Hey @gomisensei today I bought a Sony Dualshock 4 Wireless USB Adapter.

It does all the wireless pairing in hardware and appears as a plugged-in USB controller, so you don't need to setup Bluetooth or ds4drv or anything special in software at all.

Just plug in, push the adapter for 3 seconds to enter pairing mode, press PS+Select on the controller, and you're good to go.

This worked with both my controllers, the one which works over RetroPie Bluetooth menu, and the one which otherwise needs ds4drv.

If you have multiple controllers, you need one adapter per controller. I'm going to buy another one soon but I expect it'll work fine.

Hope this helps you!

i have pressed F4 and tried to type it out there but now luck.
Very sorry for my lack of understanding of this process, im a complete noob but hope to learn alot here.

In case anyone runs across this in their searches, I have a newer XML maker. Still windows-based: https://retropie.org.uk/forum/topic/4471/updated-gamelist-xml-creator

I recently ran into this issue as well. I'm not sure what the exact cause is, but I can reproduce it consistently. I boot up into emulationstation, and once all booted, I connect my phone to the Pi via Bluetooth. If I launch a ROM at that point, it hangs just prior to launching the ROM. On my TV I can actually see it go really dim, not black, and still see the game selection screen.

I can also reproduce my workaround. So if I get to the point of hanging, if I disconnect the Bluetooth, it launches the ROM.

I blame PulseAudio, but really it might just be the way emulationstation and Pulse play together, both/neither of them actually being the culprit.

Hopefully that helps!
-Chad

This is a tough question to answer because it can depend on which emulators you installed after a fresh install of RetroPie 4.0.2.

Just for fun I mounted the retropie-4.0.2-rpi2_rpi3.img file and browsed to the /home/pi/RetroPie/BIOS directory and here's the only files I saw:

fast.bin skip.bin system.bin

Make sure you've got everything backed up before proceeding!!!

Maybe you can just move all the other BIOS files into a Temp directory and then just run the RetroPie Setup Script and then Update All Installed Packages. Maybe that'll reinstall all the other stock BIOS files. I don't know if it will work but it's worth a shot.

If all else fails, just reimage and reload the ROM and BIOS files that you actually want.

@DJQuad the most supported is lr-mame 2003 even if it has less games. If you play a game on lr-2010 vs the same game on lr-2003, lr-2003 more than likely will run better on a lower processing board like the pi. Just try both because the games vary and pick which you think works best for the games you want to play. I generally just stick with lr-mame2003

@BuZz
My sincere apologies about the formatting BuZz. I did read that first and had full intentions of following it, but in my haste to post totally forgot about it. Again, my apologies!

I think you're correct with the date and time thing. I noticed this before and tried to fix it, and with that too now, I am having issues.

I've googled and followed a ton of ways to try and get the time to sync, but no dice.
I suppose that should be a separate thread, and if that is what you want, just let me know. I'm totally at a loss as to whats going on with this Pi. I've just installed the image again and no luck changing the date, OR using the scraper.

For the date/time I've tried:

Setting the timezone in raspi-config (didn't stick after reboot)

Tried these to no avail:

https://www.raspberrypi.org/forums/viewtopic.php?f=53&t=144095

https://victorhurdugaci.com/raspberry-pi-sync-date-and-time

And a few others I don't remember the URL's.

Thanks a lot!
I've installed the ua4all emulator (<Retropie Setup / Manage Packages / Manage Optional Packages / ua4all / install from binaries ) and it works!

@leejsmith @Twitch0815

The AMD driver download at http://support.amd.com/en-us/download/embedded?os=Linux x86_64 will not work on Ubuntu 16.04

AMD's proprietary Catalyst driver (called fglrx) is not compatible with the Xorg shipped in Ubuntu 16.04 or later. AMD are no longer updating Catalyst for Linux so this proprietary driver is no longer an option.

The only option available is to use the open source driver (called radeon) which is already included.

There is a newer AMD driver framework upstream (called amdgpu) which has both open source and proprietary options, but it does not support the older HD8000-series in the Gizmo 2 (nor does it support the HD6870 I'm running in my desktop PC).

The free radeon driver used to be fairly terrible, but it's quite good these days. Current performance on the Gizmo 2 (and my PC) is as good as it's going to get on Ubuntu 16.04 onwards.

The only way I can see to maybe get better performance is use Ubuntu 14.04 LTS and the proprietary embedded driver linked above, but I don't know if that's possible with the Gizmo 2, nor if RetroPie will still compile on older Ubuntu releases.

Thank you so much! That fixed it for me :D

Great idea! I've never tried it before but I found this:

redoid - A Node.js package that provides an API to control your IKEA Dioder LED light strip on your Raspberry Pi
https://github.com/ffraenz/redoid

Hi,

If you have overclocked your Raspberry Pi at all, the first thing I'd suggest it removing all overclock settings and seeing how the system runs.

Secondly, I'd check that your power supply is up to the job: Looking after your Raspberry Pi – Part 1: The importance of a quality power supply (PSU)

Whether or not you have overclocking enabled, the following guides will allow you to stress/stability test the cpu, ram, and sd storage.

Part 1: Overclocking the Raspberry Pi
Part 2: Stress testing the CPU with mprime
Part 3: Stress testing the RAM with Memtester
Part 4: Stress testing the SD card storage with the Stability Test Script

Regarding the appearance of the yellow square, overheating is common on the Pi 3, however the single-core nature of the emulators in RetroPie generally means this doesn't become a problem - for more information, please see:
Overclocking the Raspberry Pi 3: Thermal Limits and Optimising for Single vs Multicore Performance

Please note that soak testing is important - I found some stability issues that were uncovered only when running these tests for up to 24 hours (that said, for any serious instability these tests will reveal problems far more quickly)

Thank you @edmaul69