@kingfrankbob Your last post doesn't seem to fit to this topic. Wrong thread?

@Carnov If you have no interest in any "3D gaming" then your best bet is the Pi 3B+. It's extremely reliable and the support is outstanding. I can get nearly all systems to run quite well, up to and including, Playstation 1 emulation which was considerably more powerful than any 16-bit console up to that point, barring a couple. If you're planning on emulating systems like the NES, SNES, Genesis, Master System, etc from the late 1980's to the mid to late 1990's then the 3B+ will do everything you'll ever need it to. Like I said, the support for this model is outstanding here. I have nearly zero knowledge of the intricacies of any version of Linux and I was able to get the OS installed and my system running with very little trouble. Just make sure you follow the instructions. All systems after installation will require a period of time for you to acclimate yourself to the OS, RetroArch, Emulation Station and the many settings and options you'll have to browse and fiddle with to get everything right where you want it. Each game can have custom options through RetroArch and the amount of control given to the end-user is fantastic. I truly commend the RetroPie team for all their hard work.

@GoodBoy said in [PiShrink] Creating new /etc/rc.local does not end - takes forever.: @mitu My apologies. I would say I waited about an hour and it was still trying to create the etc/rc.local It is a 64GB card, with about 32GB used space. I have just put the image on a 128GB card and I am going to camp this one out for a few hours. If that doesn't work, I am thinking about removing the etc/rc.local and retrying it. Not too sure what that will achieve but it's worth a go. @GoodBoy Why are you trying to shrink the image if you are going to place it on a 128 GB card ? Do a backup of the image..transfer it to the 128GB card and .you will have to expand the filesystem to access the full space on the card

I just remembered that Retropie is doesn't support Buster yet so it would'nt work on Retropie just yet.

Okay cool it might be a while I am doing a portapie homemade so I have to get that fixed and finished before I do that

It looks like your USB gamepad is detected as Player2 - the Sony Vaio keyboard is somehow detected as the 1st joypad connected: [INFO] [udev]: Pad #0 (/dev/input/event5) supports 0 force feedback effects. [INFO] [Autoconf]: 1 profiles found. [INFO] [Autoconf]: no profiles found for Sony Vaio Keys (4173/0). [INFO] [udev]: Plugged pad: usb gamepad (2064:58625) on port #1. [INFO] [Autoconf]: 1 profiles found. [INFO] [autoconf]: selected configuration: /home/esteban/.config/retroarch/autoconfig/usb gamepad .cfg [INFO] [udev]: Pad #1 (/dev/input/event3) supports 0 force feedback effects. You can use the advanced configuration editor and re-order the gamepads by setting the gamepad order for all Libretro based emulators.

@eddygenotype You're welcome! I have been sort of obsessively documenting things in RetroPie lately, and your question was well-timed. :)

@Dyelon hey pal, did you ever get it fixed? Having exact same issue as yourself. Bought USB encoders from amazon same thing.

Mystic Mine is a Python game included in RetroPie. You can find it in the Experimental packages. I strongly recommend you to study how this game is programmed as it runs very well on the Raspberry Pi. The scriptmodule that installs and configures this game in RetroPie is here: https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/ports/mysticmine.sh

@Clyde, this is a co-workers unit and he couldn't remember all of the details about it but I think that you are correct about it being a non official retropie image. It had a very out-dated version and when I updated everything is where the issue happened. I will talk with him at work Monday, explain what happened and let him know that I will set him up with an official copy. Thanks to all that offered help with this issue.

Thanks. I'll keep that in mind.

Hi, this also happens to me. No problems with Pi 3B+, but I just got a new Pi Zero W, and freezes all the time with RetroPie. I've tried this versions: Retropie 4.5.1 -> when it freezes I stil can do F5 in Web Manager and see the temperature, or sometines reboot with Putty if I already had one session opened. And one of those times, Putty threw this when it froze: pi@retropie:~ $ Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.163849] Internal error: Oops: 837 [#1] ARM Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167201] Process emulationstatio (pid: 681, stack limit = 0xcebb6188) Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167355] Stack: (0xcebb7fa8 to 0xcebb8000) Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167463] 7fa0: be82d520 00000001 be82d520 00000001 00000000 00000003 Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167653] 7fc0: be82d520 00000001 00000004 000000a8 00000000 00000000 00000005 00000000 Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.167844] 7fe0: 00000000 be82d518 00000000 b66ea124 80000010 be82d520 00000000 00000000 Message from syslogd@retropie at Aug 23 16:22:05 ... kernel:[ 1835.168038] Code: f10c0080 e5992008 e35204bf 1b000de1 (e5991000) RetroPie 4.5 -> Also freezes randomly. RetroPie 4.4 -> Also freezes, but exits EmulationStation and shows "Segmentation Fault". I have and screenshot if you need it. And Putty threw this: pi@retropie:~ $ Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.770533] Internal error: Oops: 805 [#1] ARM Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773455] Process emulationstatio (pid: 444, stack limit = 0xc0e68188) Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773619] Stack: (0xc0e69e48 to 0xc0e6a000) Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773741] 9e40: 00000010 00000000 00000020 00000030 00000030 00000020 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.773942] 9e60: 00000200 c0e69e8c c0e69edc c0e69e78 bf078ba0 c015a1e4 cd592b60 c0e69ea0 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774148] 9e80: c1eaec00 0000b00a 00000001 be9481d8 c0e69ea8 00000000 00000000 00000ff0 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774353] 9ea0: 020a4371 00000ff0 c13b8de0 cd5dc660 c0e69eec c0e69ec0 c004c3a0 c0623aec Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774556] 9ec0: c004c99c c0040a14 00000000 c13b8de0 00000001 cea06f00 c0e69f1c c0e69ee8 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774755] 9ee0: c0046b2c be9481b4 cf2edd88 c9627320 00000004 00000004 c0e68000 00000000 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.774956] 9f00: c0e69f7c c0e69f10 c016c824 c05025c4 c0e69f74 c0e69f20 c063068c c0046adc Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775156] 9f20: c0e69f44 c006fae0 c0e69f6c c0e69f38 3cbc4f68 c01773f8 cb6ef900 b5feb564 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775358] 9f40: be9481b4 be9481d8 400cc404 00000004 c0e69f6c c9627321 be9481b4 c9627320 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775562] 9f60: 400cc404 00000004 c0e68000 00000000 c0e69fa4 c0e69f80 c016cf20 c016c794 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775762] 9f80: 0000b00a b5feb564 be9481b4 be9481d8 00000036 c000ffa4 00000000 c0e69fa8 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.775963] 9fa0: c000fe00 c016cee8 b5feb564 be9481b4 00000004 400cc404 be9481b4 0000b00a Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.776164] 9fc0: b5feb564 be9481b4 be9481d8 00000036 00000000 be948374 003be5cc 02164608 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.776365] 9fe0: b5feb240 be9481a4 b5fd8c08 b66ef80c 80000010 00000004 00000000 00000000 Message from syslogd@retropie at Aug 24 00:24:08 ... kernel:[ 812.777184] Code: e51f1528 e24b207c ebffea8d e1a09000 (eafffc25) RetroPie 4.3 -> Also freezes NOOBS_v2_8_2 -> Raspbian Ok, update everything..., until I install RetroPie manually, then it freezes right away! I have to try Recalbox...

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

Resolved it by configuring retropie to boot to the command line and then i'll edit .bashrc to house the if logic to launch X or ES depending on TOD and of course if [ "`tty`" = "/dev/tty1" ] Was much easier than I was trying to make it... ##### # Set the hours between which PiClock will Launch #### minHour=6 maxHour=9 #Get Current Hour cHour=$(date +%H) # Get current time and time of boot. # calculate minutes since boot cSec=$(date +%s) sSec=$(date +%s -d "$(uptime -s)") uMin=$(( ($cSec - $sSec)/60 )) # Ensure that we are within 2 minutes of boot. This ensures that user can exit ES to the command line # without this script re-launching ES in an endless loop if [[ $uMin -le 2 ]]; then # Ensure this is tty1 if [[ "`tty`" = "/dev/tty1" ]]; then # If between min and max hour then startx and PiClock else execute autorun if [[ $cHour -ge $minHour && $cHour -lt $maxHour ]]; then startx else bash "/opt/retropie/configs/all/autorun.sh" fi fi fi The issue I see is trying to drop to the command line from ES in which case I believe it will just launch back into ES... i'm ok with this. Maybe some other unintended consequences but I'll find out soon enough. Edit: Added an additional If statement to check for minutes since boot so that one can successfully drop from ES to the CL without

Hi. Tried both MAME emu and Cannonball. Will get the lowdown on all the details for you and let you know..

I recommend to use the artwork for Battle Zone as far as it is running now. There are only two games where i use those, and Battle Zone is one of them, makes this great game look even better (the other one is asteroids btw),