So it is impossible to program it to only shutdown, but not boot? Because I have it setup so it boots into on game, then another, and then shuts down and I don't want to accedently turn it off

Great news, will do ASAP!

@yogsodoth interesting that it didn't work, I've never had a problem with Win32DiskImager yet. But it's good to know if I run across a similar issue I can always try out etcher.

@mitu your frequency of helping people never ceases to amaze me. Thank you for all the time you put into helping all of us.

@mitu said in Pi Zero W Issues - Won't Boot Without a Keyboard??:

@WishItWas1984 said in Pi Zero W Issues - Won't Boot Without a Keyboard??:

So while the update didn't cause an endless loop of file system checking, I now have this.

It's because systemd updates break auto-login - see https://retropie.org.uk/docs/FAQ/#why-emulationstation-doesnt-start-automatically-after-an-update for an explanation and solution.

Thanks for testing this, it means the original problem is solved by updating the Raspbian packages.

Thanks! That did the trick.

I came across this exact issue this weekend. My situation is, honestly I was curious about having OctoPi for my 3D printing and RetroPi to test some games.

To keep it short:

I was using a 128gb Samsung EVO SD card while dual booting (using berryboot)with Retropie and Octopi. After trying to get it working by uninstalling and re-installing amongst other things, I decided to try another 32GB SD card also a Samsung Evo. I installed RetroPie (From berryboot) first. Verified that the images booted successfully. I added the octopi image from the berryboot images page and copied that over successfully. I applied updates to RetroPie first then to OctoPi. After configuring OctoPi to the way I needed it (after many hours of researching) after rebooting, both images still booted with no issue. I made a backup of the SD card with my desired setup then restored that backup to the 128gb chip. I plan to test this chip to see if I have the same results.

Sidenote: In further research of this issue, the problem seems to be with permissions. This command seems to have worked for those getting the error. A reboot was required afterwards:

sudo usermod -a -G video yourusername

@mitu i tried etcher and Win32DiskImager

@OwenWilsonsNose
Yay! You're welcome. Have a good day.

@Efriim Doing this step by step only:

https://retropie.org.uk/forum/topic/16145/retropie-upgrading-raspbian-jessie-to-stretch

After finished there are some errors in libraries that made crash emulationstation but they are easy to solve. Once it runs very well including with overclocking. With this fan “Noctua Premium Fan, Brown, NF-A4X10-FLX 5V” I could overclock and no problems.

@pengu1n said in Does Retropie 4.4 Run on the CM3+ Lite?:

I ran into a login prompt at the console on reboot though...which was strange

That happens when systemd is updated - a known Raspbian behavior - https://retropie.org.uk/docs/FAQ/#why-emulationstation-doesnt-start-automatically-after-an-update.

@mitu

ah ok - should be fine now.

@X_Splinter said in Unable to use keyboard/controller after rebuild boot partition:

Could this be an issue not related to the boot partition?

Most likely yes. The procedure you performed is not guaranteed to recover another system.

If so is the main partition of retropie a regular EXT3? So I may browse and copy all of my files?

It's an Ext4 partition - should be accessible also as Ext3, but I advise using a Linux installation to try and mount it.

@toucthebitum please note we don't support 3rd party images. You should use the official image from this site.

@mitu You're right. I checked that, and there is something about that, but it's unclear (at least for me, 'couse I read it before).

Anyway, thank you again :>

On a second thought, even better would be to actually use runcommand, taking advantage of its goodies such as video mode settings and emulator selection:

# Launch FixItFelixJr /opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ megadrive "/home/pi/RetroPie/roms/megadrive/FixItFelixJr.bin"

Runcommand also prepares the console like hiding the cursor and even can display a splash screen art if configured. This is the way EmulationStation launches games and you also get the benefit of error messages being logged to /dev/shm/runcommand.log for debugging.

Hi all! I just wanted to say that I got an answer to my issue! My particular problem was due to my using a VGA to HDMI converter to use with my old VGA monitor. What fixed my problem was to edit the config.txt file and uncomment the line "hdmi_force_unplug=1". Works perfectly now. Again, thank you all for your time.

Thank you Clyde. If I had a second micro sd with this size, I would do more experimentation.

@Clyde said in [solved] Stops booting after small changes on gamelist, even if i revert:

That said, I do not understand you completely. Do you say that eject in Nautilus does work now, but didn't back then?

Yes, but on the other hand, I did not test this with adding files. So the eject works, because there is nothing written (maybe).

My best guess is that something prevented a clean ejection of the card's file system and that Retropie had to do an fsck one or two times and repair the unclean file system of the card.

I don't know whats going on here, but this is my guess too.

Found it, thanks!

@mitu I think it should be a selectable option under the es menu, just like you can select specific emulators to open to.