I've just tried with google kickstarts and it work !

@indyviduum It does a CRC check and a name check to see if it matches one of its known configurations. Otherwise it just uses its default profile.

Please add some more info about your setup - as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@grant2258 appreciate it. my setup is pretty much good to go. I have all my neo geo on FBA, and depending on the arcade game a mix between FBA and Mame3000. Thanks again. Have a great day!

@griff How does it plug 'directly' ? GPIO/HDMI ? Check the screen vendor instructions on how to get it to work with Raspbian and apply those instructions to your RetroPie system.

I managed to get it working. I uninstalled amiberry, cleared the /opt/retropie/configs/amiga/amiberry folder. Reinstalled from sources, recopied various bios roms and ended up with this rom working:

kick40068.A1200 -> /opt/retropie/emulators/amiberry/kickstarts/Kickstart - 391773-01 (USA, Europe) (v3.1 Rev 40.068) (A1200).rom

I also ensured 755 permissions on the kickstart roms - they were 744 before. Not sure which of these steps actually fixed the issue though.

@paulnmiller1 Yes, changing video driver to sdl2 in RetroPie Setup as suggested by @mitu worked immediately.

i think i see the problem and it might just be the refreshrates, when in emulationstation after boot,
Putty Display
but hitting a button before kodi loads,
Waveshare LCD Display

Sorry for the larger second image, took it w/ my phone. so the problem might be its setting an invalid 30hz refreshrate that this display cannot handle.

ok, somethinsg dodgy... on loading Kodi, i'm whitescreen as per usual, But putty shows still
alt text
and it recovers after awhile, but the moment i press a button. pfft! Whitescreen.

Edit:
ok lastnight which i forgot to post before passin out.. Reicast had teh same problem but it was setting an independent Render resolution, which was fixed by editing the emu.cfg this has me thinking either Kodi's setting a bad pixelclock/setting an independent resolution which the force options in config.txt dont do didly Squat.

@quicksilver said in White screen after selecting OpenGL:

@nevsan said in White screen after selecting OpenGL:
"Now for me to look at the easiest way to back up what I've done on my SD card in future so I can revert."

If you are using windows just use win32disk imager. Its basically just the inverse of putting the image on the card. I have learned to always make an image back up before making any major changes to my setup.

This is really strange, I haven't used samba for a long time. Maybe it has to do with some RP update? It completely ruined my sanity last night :P

or, even better:

topic tools > ask as question
then
topic tools > mark as solved.

i've done this for you :)

Updated the OP to indicate this problem is solved, and the solution.

@Spectreman I agree that the white screen bug is not fixed, however it has been improved immensely. The performance after the upgrade was significant, so I would consider it a major performance upgrade, but not necessarily a fix. More work still needs to be done for sure, but there are a lot of cool projects going on right now as well. You should be able to run trokyfran on a Pi3 with standard configs with 14 systems without an issue. I would again try to adjust your VRAM up or down in small amounts. Maybe 120 or 80 would work. You never shared what pi model you are running, power supply, do you have any modifications to your settings? Have you changed your gpu settings? Overclocked?