@mazterbaker Neither would be the case actually. The source would be downloaded overwriting ours before recompiling.

@jonnykesh I entered this code:
sudo __platform=rpi3 ~/RetroPie-Setup/retropie_setup.sh

and got the same error message.

@janik1501 said in Black screen on first boot:

@digitalmonkey doesnt work either

This means that you are incorrectly setting up your card, your card is not compatible or your card is corrupt.

I am back, well rested and ready to go on what could be my final attempt before I give up.

9:52pm
-What I did different, formatted RP Micro SD card to FAT32 (32gb card) previously was ntfs, I don't even know if it matters. I'm unplugging my ethernet wire. I'm transferring the rom folders that screwed it up in the first place, first.

Transferring over 3 'problem' folders first, plugging external into pi. works, transferring over every rom folder but about 4 now.

10:26pm
3. mostly all rom folders are transferred, about to test it now.
4. boost file system error as seen above..... i dont know what to do.

@nsuk ok so you made me look like a jackass thanks.

That guide is outdated (I think it was around RetroPie 2), the mk_arcade_joystick module can be installed from the Retropie setup drivers menu.

Exit problem fixed here: https://support.xgaming.com/support/solutions/articles/5000554993

sorry "flag" meaning a indicator of power supply problem, thanks I will check into this as you have advised !

@herb_fargus @pjft thanks for the information guys. looks like the easiest way is to update all from binary than update ES from source, or update each individually.

@hello-its-me we don't support the orange pi, and pretty much nobody here uses it.

The retro orange pi group has a Facebook I think you'll probably have better luck there

@dankcushions No, I am not running any videos.
@pjft I looked at memory usage via htop several times, and nothing was hogging CPU time or memory. However, I do have new information that changes my prior conclusion that ES was the culprit: the hang did reappear even when ES was not running. I did not see that behavior before because it appears to be taking much longer when ES is not running (on the order of a day instead of a few hours).

@spieddy said in autostart.sh not running:

I had the same problem chmod +x autostart.sh did the trick for me

This solved my problem too!

omg! I'm blind...sorry. I see it now. @BuZz @dankcushions thank you thank you!

@kousuke 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

@edmaul69 I am curious to know, how is your zdoom.ini configured? I want to run mutliple wads but no matter what the different configs I set up only play one

Is anyone able to help? Did I miss something obvious?

@olleulv 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