RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login

    Old Computer Appreciation Thread

    Scheduled Pinned Locked Moved General Discussion and Gaming
    msxmsx2pc88pc98x68000
    1.4k Posts 19 Posters 4.3m Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • TPRT
      TPR @Folly
      last edited by

      @Folly Same for me. So I wonder what could be causing it not to work?

      Is there another log somewhere I could check?

      F 1 Reply Last reply Reply Quote 0
      • F
        Folly @TPR
        last edited by Folly

        @TPR

        Same for me

        Looked at your first log again.
        I see you already used cass1 and it didn't work.

        Did you use the valerino module-scripts to install ?
        Are you able to run it with mame ?
        What run_mess.sh do you use ? ( what is the sha1sum ? )
        Which version of lr-mess do you use ?

        TPRT 1 Reply Last reply Reply Quote 0
        • TPRT
          TPR @Folly
          last edited by TPR

          @Folly Here's my run_mess script I'm using:

          My version of lr-mess is dated 2/24/2021 with a filesize of 182,836,700

          Is there another log I can check to see why those .ddp files stop and kick me back out to ES?

          duglorD F 2 Replies Last reply Reply Quote 0
          • duglorD
            duglor @TPR
            last edited by

            @TPR What is the last version date of either Mess or MAME that the game & Watch games use? Just curious. and if it is mame, that mame is called plain old "MAME" in the retropie , correct

            1 Reply Last reply Reply Quote 0
            • F
              Folly @TPR
              last edited by Folly

              @TPR said in Old Computer Appreciation Thread:

              Your run_mess.sh script is the original from valerino.
              I use the updated one of RusselB with these changes.
              Though I think it's probably not related to the run_mess.sh script.

              Is there another log I can check to see why those .ddp files stop and kick me back out to ES?

              Yes, for a better log it's best to run it with mame standalone.
              This is an adapted runcommand for mame standalone (for you):

              mame-adam-cass1 = "/opt/retropie/emulators/mame/mame -rompath /home/pi/RetroPie/BIOS\;/home/pi/RetroPie/roms/adam -cfg_directory /opt/retropie/configs/adam/mame -v -c -ui_active adam  -cass1 %ROM%"

              You can just paste it in your emulators.cfg of /opt/retropie/configs/adam (at least I assume it is there )
              Verbose mode (-v) is always on, so no need to change it when booting the .ddp)
              Make sure you have mame standalone installed from the exp packages.

              Let me know what your log gives.

              P.s. You may remove the run_mess.sh from your previous post.

              TPRT 1 Reply Last reply Reply Quote 0
              • TPRT
                TPR @Folly
                last edited by TPR

                @Folly I do have stand-alone MAME installed.

                I used that runcommand...

                It loaded up to "initializing" and then booted me back to ES.

                Where can I find the MAME log file at? I can't seem to find it in any of the more obvious places in my directories.

                Here is what my runcommand log file says:

                Parameters: 
Executing: /opt/retropie/emulators/mame/mame -rompath /home/pi/RetroPie/BIOS\;/home/pi/RetroPie/roms/adam -cfg_directory /opt/retropie/configs/adam/mame -v -c -ui_active adam  -cass1 "/home/pi/RetroPie/roms/adam/Alcazar (1986) (Telegames USA) (ADE-SD DDP Patched).ddp"
Attempting load of mame.ini
Parsing mame.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of horizont.ini
Attempting load of computer.ini
Attempting load of raster.ini
Attempting load of source/adam.ini
Attempting load of adam.ini
Reading translation file English: 1 strings, original table at word offset 7, translated table at word offset 9
Loaded 0 translations from file English
Starting plugin data...
Starting plugin hiscore...
Attempting load of mame.ini
Parsing mame.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of horizont.ini
Attempting load of computer.ini
Attempting load of raster.ini
Attempting load of source/adam.ini
Attempting load of adam.ini
Available videodrivers: x11 KMSDRM RPI dummy 
Current Videodriver: KMSDRM
	Display #0
		Renderdrivers:
			    opengl (0x0)
			 opengles2 (0x0)
			  opengles (0x0)
			  software (0x0)
Available audio drivers: 
	alsa                
	sndio               
	dsp                 
	disk                
	dummy               
Build version:      0.224 (mame0224)
Build architecure:  
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1 
Build defines 1:    LSB_FIRST=1 MAME_NOASM=1 
SDL/OpenGL defines: SDL_COMPILEDVERSION=2009 USE_OPENGL=1 
Compiler defines A: __GNUC__=8 __GNUC_MINOR__=3 __GNUC_PATCHLEVEL__=0 __VERSION__="8.3.0" 
Compiler defines B: __unix__=1 
Compiler defines C: __USE_FORTIFY_LEVEL=0 
Enter init_monitors
Adding monitor screen0 (1920 x 1080)
Leave init_monitors
Enter sdlwindow_init
Using SDL native texturing driver (SDL 2.0+)
Loaded opengl shared library: <default>

Hints:
	SDL_FRAMEBUFFER_ACCELERATION             (NULL)
	SDL_RENDER_DRIVER                        (NULL)
	SDL_RENDER_OPENGL_SHADERS                (NULL)
	SDL_RENDER_SCALE_QUALITY                 (NULL)
	SDL_RENDER_VSYNC                         (NULL)
	SDL_VIDEO_X11_XVIDMODE                   (NULL)
	SDL_VIDEO_X11_XINERAMA                   (NULL)
	SDL_VIDEO_X11_XRANDR                     (NULL)
	SDL_GRAB_KEYBOARD                        (NULL)
	SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS         (NULL)
	SDL_IOS_IDLE_TIMER_DISABLED              (NULL)
	SDL_IOS_ORIENTATIONS                     (NULL)
	SDL_XINPUT_ENABLED                       (NULL)
	SDL_GAMECONTROLLERCONFIG                 (NULL)
	SDL_JOYSTICK_ALLOW_BACKGROUND_EVENTS     (NULL)
	SDL_ALLOW_TOPMOST                        (NULL)
	SDL_TIMER_RESOLUTION                     (NULL)
	SDL_RENDER_DIRECT3D_THREADSAFE           (NULL)
	SDL_VIDEO_ALLOW_SCREENSAVER              (NULL)
	SDL_ACCELEROMETER_AS_JOYSTICK            (NULL)
	SDL_MAC_CTRL_CLICK_EMULATE_RIGHT_CLICK   (NULL)
	SDL_VIDEO_WIN_D3DCOMPILER                (NULL)
	SDL_VIDEO_WINDOW_SHARE_PIXEL_FORMAT      (NULL)
	SDL_VIDEO_MAC_FULLSCREEN_SPACES          (NULL)
	SDL_MOUSE_RELATIVE_MODE_WARP             (NULL)
	SDL_RENDER_DIRECT3D11_DEBUG              (NULL)
	SDL_VIDEO_HIGHDPI_DISABLED               (NULL)
	SDL_WINRT_PRIVACY_POLICY_URL             (NULL)
	SDL_WINRT_PRIVACY_POLICY_LABEL           (NULL)
	SDL_WINRT_HANDLE_BACK_BUTTON             (NULL)
Leave sdlwindow_init
Enter sdl_info::create
Leave renderer_sdl2::create
window: using renderer opengl
renderer: flag SDL_RENDERER_ACCELERATED
renderer: flag SDL_RENDERER_TARGETTEXTURE
Audio: Start initialization
Audio: Driver is alsa
Audio: frequency: 44100, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 22528 bytes
Audio: End initialization
Keyboard: Start initialization
Input: Adding keyboard #0: System keyboard (device id: System keyboard)
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding mouse #0: System mouse (device id: System mouse)
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Input: Adding joystick #0: MicrosoftX-Box360pad (device id: 030000005e0400008e02000020010000)
Joystick: Microsoft X-Box 360 pad [GUID 030000005e0400008e02000020010000]
Joystick:   ...  4 axes, 13 buttons 1 hats 0 balls
Joystick:   ...  Physical id 0 mapped to logical id 1
Joystick:   ...  Has haptic capability
Joystick: End initialization
Searching font Liberation Sans in -. path/s
font Liberation Sans|Regular is not TrueType or BDF, using MAME default
Region ':os7' created
unzip: opened archive file /home/pi/RetroPie/BIOS/adam.zip
unzip: found /home/pi/RetroPie/BIOS/adam.zip ECD
unzip: /home/pi/RetroPie/BIOS/adam.zip has no ZIP64 ECD locator
unzip: read /home/pi/RetroPie/BIOS/adam.zip central directory
unzip: closing archive file /home/pi/RetroPie/BIOS/adam.zip and sending to cache
Region ':boot' created
unzip: found /home/pi/RetroPie/BIOS/adam.zip in cache
unzip: opened archive file /home/pi/RetroPie/BIOS/adam.zip
unzip: closing archive file /home/pi/RetroPie/BIOS/adam.zip and sending to cache
unzip: found /home/pi/RetroPie/BIOS/adam.zip in cache
unzip: opened archive file /home/pi/RetroPie/BIOS/adam.zip
unzip: closing archive file /home/pi/RetroPie/BIOS/adam.zip and sending to cache
unzip: found /home/pi/RetroPie/BIOS/adam.zip in cache
unzip: opened archive file /home/pi/RetroPie/BIOS/adam.zip
unzip: closing archive file /home/pi/RetroPie/BIOS/adam.zip and sending to cache
unzip: found /home/pi/RetroPie/BIOS/adam.zip in cache
unzip: opened archive file /home/pi/RetroPie/BIOS/adam.zip
unzip: closing archive file /home/pi/RetroPie/BIOS/adam.zip and sending to cache
unzip: found /home/pi/RetroPie/BIOS/adam.zip in cache
unzip: opened archive file /home/pi/RetroPie/BIOS/adam.zip
unzip: closing archive file /home/pi/RetroPie/BIOS/adam.zip and sending to cache
Region ':u6' created
unzip: found /home/pi/RetroPie/BIOS/adam.zip in cache
unzip: opened archive file /home/pi/RetroPie/BIOS/adam.zip
unzip: closing archive file /home/pi/RetroPie/BIOS/adam.zip and sending to cache
Region ':net1:kb:u2' created
unzip: opened archive file /home/pi/RetroPie/BIOS/adam_kb.zip
unzip: found /home/pi/RetroPie/BIOS/adam_kb.zip ECD
unzip: /home/pi/RetroPie/BIOS/adam_kb.zip has no ZIP64 ECD locator
unzip: read /home/pi/RetroPie/BIOS/adam_kb.zip central directory
unzip: closing archive file /home/pi/RetroPie/BIOS/adam_kb.zip and sending to cache
Region ':net2:prn:u2' created
unzip: opened archive file /home/pi/RetroPie/BIOS/adam_prn.zip
unzip: found /home/pi/RetroPie/BIOS/adam_prn.zip ECD
unzip: /home/pi/RetroPie/BIOS/adam_prn.zip has no ZIP64 ECD locator
unzip: read /home/pi/RetroPie/BIOS/adam_prn.zip central directory
unzip: closing archive file /home/pi/RetroPie/BIOS/adam_prn.zip and sending to cache
Region ':net3:ddp:m6801' created
unzip: opened archive file /home/pi/RetroPie/BIOS/adam_ddp.zip
unzip: found /home/pi/RetroPie/BIOS/adam_ddp.zip ECD
unzip: /home/pi/RetroPie/BIOS/adam_ddp.zip has no ZIP64 ECD locator
unzip: read /home/pi/RetroPie/BIOS/adam_ddp.zip central directory
unzip: closing archive file /home/pi/RetroPie/BIOS/adam_ddp.zip and sending to cache
Region ':net4:fdc:u6' created
unzip: opened archive file /home/pi/RetroPie/BIOS/adam_fdc.zip
unzip: found /home/pi/RetroPie/BIOS/adam_fdc.zip ECD
unzip: /home/pi/RetroPie/BIOS/adam_fdc.zip has no ZIP64 ECD locator
unzip: read /home/pi/RetroPie/BIOS/adam_fdc.zip central directory
unzip: closing archive file /home/pi/RetroPie/BIOS/adam_fdc.zip and sending to cache
Region ':net5:fdc:u6' created
unzip: found /home/pi/RetroPie/BIOS/adam_fdc.zip in cache
unzip: opened archive file /home/pi/RetroPie/BIOS/adam_fdc.zip
unzip: closing archive file /home/pi/RetroPie/BIOS/adam_fdc.zip and sending to cache
wp_r80.rom ROM NEEDS REDUMP
WARNING: the machine might not run correctly.
Optional memory region ':screen' not found
Optional shared pointer ':slot1:adamlink:rom' not found
Optional shared pointer ':slot3:ram:ram' not found
Optional shared pointer ':slot3:ram:rom' not found
Starting Adam ':'
  (missing dependencies; rescheduling)
Starting Zilog Z80 ':u1'
Starting Motorola MC6801 ':u6'
Starting TMS9928A VDP ':tms9928a'
Starting Video Screen ':screen'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting SN76489A ':u20'
Starting ADAMnet bus ':adamnet'
Starting ADAMnet slot ':net1'
Starting Adam keyboard ':net1:kb'
Starting Motorola MC6801 ':net1:kb:u2'
Starting ADAMnet slot ':net2'
Starting Adam printer ':net2:prn'
Starting Motorola MC6801 ':net2:prn:u2'
Starting ADAMnet slot ':net3'
Starting Adam Digital Data Pack ':net3:ddp'
Starting Motorola MC6801 ':net3:ddp:m6801'
Starting Cassette ':net3:ddp:cassette'
Starting Cassette ':net3:ddp:cassette2'
Starting ADAMnet slot ':net4'
Starting Adam FDC ':net4:fdc'
Starting Motorola MC6801 ':net4:fdc:u6'
Starting Western Digital WD2793 FDC ':net4:fdc:u11'
Starting Floppy drive connector abstraction ':net4:fdc:u11:0'
Starting 5.25" single-sided double density floppy drive ':net4:fdc:u11:0:525ssdd'
Starting Speaker ':net4:fdc:u11:0:525ssdd:flopsndout'
  (missing dependencies; rescheduling)
Starting Floppy sound ':net4:fdc:u11:0:525ssdd:floppysound'
Starting ADAMnet slot ':net5'
Starting Adam FDC ':net5:fdc'
Starting Motorola MC6801 ':net5:fdc:u6'
Starting Western Digital WD2793 FDC ':net5:fdc:u11'
Starting Floppy drive connector abstraction ':net5:fdc:u11:0'
Starting 5.25" single-sided double density floppy drive ':net5:fdc:u11:0:525ssdd'
Starting Speaker ':net5:fdc:u11:0:525ssdd:flopsndout'
  (missing dependencies; rescheduling)
Starting Floppy sound ':net5:fdc:u11:0:525ssdd:floppysound'
Starting ADAMnet slot ':net6'
Starting ADAMnet slot ':net7'
Starting ADAMnet slot ':net8'
Starting ADAMnet slot ':net9'
Starting ADAMnet slot ':net10'
Starting ADAMnet slot ':net11'
Starting ADAMnet slot ':net12'
Starting ADAMnet slot ':net13'
Starting ADAMnet slot ':net14'
Starting ADAMnet slot ':net15'
Starting ColecoVision cartridge port ':cartslot'
Starting ADAM expansion slot ':slot1'
Starting AdamLink modem ':slot1:adamlink'
Starting ADAM expansion slot ':slot2'
Starting ADAM expansion slot ':slot3'
Starting Adam 64KB RAM expansion ':slot3:ram'
Starting ColecoVision control port ':joy1'
Starting ColecoVision Hand Controller ':joy1:hand'
Starting ColecoVision control port ':joy2'
Starting RAM ':ram'
Starting Software List ':colec_cart_list'
Starting Software List ':adam_cart_list'
Starting Software List ':cass_list'
Starting Software List ':flop_list'
Starting Adam ':'
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting Speaker ':net4:fdc:u11:0:525ssdd:flopsndout'
Starting Speaker ':net5:fdc:u11:0:525ssdd:flopsndout'
Starting Adam ':'
Attempting to parse: default.cfg
Attempting to parse: adam.cfg
/opt/retropie/supplementary/runcommand/runcommand.sh: line 1313:  6446 Killed                  /opt/retropie/emulators/mame/mame -rompath /home/pi/RetroPie/BIOS\;/home/pi/RetroPie/roms/adam -cfg_directory /opt/retropie/configs/adam/mame -v -c -ui_active adam -cass1 "/home/pi/RetroPie/roms/adam/Alcazar (1986) (Telegames USA) (ADE-SD DDP Patched).ddp"

                This is breaking my brani! lol I cannot figure out why it worked before, doesn't work now, but all my .dsk files still work.

                F 2 Replies Last reply Reply Quote 0
                • F
                  Folly @TPR
                  last edited by Folly

                  @TPR said in Old Computer Appreciation Thread:

                  Where can I find the MAME log file at? I can't seem to find it in any of the more obvious places in my directories.
                  Here is what my runcommand log file says:

                  The runcommand.log is the mame log.

                  Sadly also not working, doesn't seem to be due to the bios files and the emulators.

                  Not sure either on what the problem could be, I will have to think again on what the problem could be.

                  I have just checked my log with yours and yours is missing a line like this :

                  :net3:ddp:cassette: opened image file /home/pi/RetroPie/roms/coleco/adam/ddp-cass/Pitfall! (1987) (Telegames USA) (ADE-SD DDP Patched).ddp with flags=00000003

                  So somehow it looks that the .ddp file isn't loaded.

                  1 Reply Last reply Reply Quote 0
                  • F
                    Folly @TPR
                    last edited by

                    @TPR

                    Can you try to run it directly from the CLI ?
                    (press F4 in emulationstation and you should get in the CLI)
                    And then try to manually load your rom with mame, with this command :

                    /opt/retropie/emulators/mame/mame -rompath /home/pi/RetroPie/BIOS\;/home/pi/RetroPie/roms/adam -cfg_directory /opt/retropie/configs/adam/mame -v -ui_active adam -cass1 "/home/pi/RetroPie/roms/adam/Alcazar (1986) (Telegames USA) (ADE-SD DDP Patched).ddp"
                    mituM 1 Reply Last reply Reply Quote 0
                    • mituM
                      mitu Global Moderator @Folly
                      last edited by

                      @Folly Mame version ?

                      F 1 Reply Last reply Reply Quote 0
                      • F
                        Folly @mitu
                        last edited by Folly

                        @mitu

                        Yes he uses an old version, but that should not matter.

                        @TPR
                        As @mitu suggests you could try to update the mame version and see if that makes a difference.

                        Anyway, if both suggestions don't work it will take too much time to figure out what the problem is.

                        I would then suggest that you make a whole new image with the latest retropie-setup and the latest emulators.
                        I would then recommend to use my project instead of using Valerino's module-scripts :
                        https://retropie.org.uk/forum/topic/29682/development-of-module-script-generator-for-lr-mess-lr-mame-and-mame-standalone

                        TPRT 1 Reply Last reply Reply Quote 1
                        • TPRT
                          TPR @Folly
                          last edited by

                          @Folly I'll try all this tonight. Thank you guys. And I think you might be right about having to scrap all my old MESS stuff and re-build with your newer one. I've just been reluctant to do that only because everything else seems to work, and you know what they say... if it ain't broke! lol

                          But now something broke!

                          I'll see what I can do!

                          F 1 Reply Last reply Reply Quote 0
                          • F
                            Folly @TPR
                            last edited by

                            @TPR

                            Any luck ?

                            TPRT 1 Reply Last reply Reply Quote 0
                            • TPRT
                              TPR @Folly
                              last edited by TPR

                              @Folly @mitu So I have an update on this ADAM thing that I absolutely do not understand, and I'm hoping you guys could make some sense of it...

                              So I was testing out a new Retroflag case... popped a different Pi board into it... was testing some things... and all of a sudden I noticed... my DDP files are working!

                              WTF!?!?!

                              So I took my build out of that case, put it back into my other Pi board...

                              CRASHED! Back to ES again.

                              So now I had to further investigate...

                              Only things I have connected are my controller and hard drive that my ROMs are on.

                              Turns out, the board it keeps crashing on is a 1gb RAM board. I tested with all my other boards:

                              8gb board - Works.
                              4gb board - works
                              2gb board - works
                              1gb board - crashed
                              1gb board #2 - crashed (just to make sure)
                              1gb board #3 - Crashed (just to make REALLY sure!)

                              All the 1gb boards I have are newer... bought within the last year.

                              I have never heard of something not loading up with the 1gb board??? I mean, I'm full on running PSP games at amazing frame rates on the 1gb board but I can't get a Coleco ADAM game to run?

                              And why is it ONLY the .ddp data pack files?

                              Any idea how to fix this other than "don't use a 1gb board?" :P

                              F 1 Reply Last reply Reply Quote 0
                              • F
                                Folly @TPR
                                last edited by

                                @TPR

                                Very strange indeed.
                                Could it be the assigned memory in the /boot/config.txt ?

                                If I get a good idea about it I will post it to you.

                                TPRT 1 Reply Last reply Reply Quote 0
                                • TPRT
                                  TPR @Folly
                                  last edited by

                                  @Folly Here is what is in my current config.txt

                                  # For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=0

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
overscan_left=-50
overscan_right=-50
overscan_top=-35
overscan_bottom=-35

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=1
hdmi_mode=16

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
overscan_scale=1
dtoverlay=RetroFlag_pw_io.dtbo
enable_uart=1
                                  F 1 Reply Last reply Reply Quote 0
                                  • F
                                    Folly @TPR
                                    last edited by

                                    @TPR

                                    Looking at this doc, memory-split isn't used anymore by the pi4.
                                    So that isn't something we can try and test.

                                    If I have some time I will try adam on my pi3 which also has 1gb.
                                    Perhaps that can give us an idea on where to look for the problem.

                                    TPRT 1 Reply Last reply Reply Quote 0
                                    • TPRT
                                      TPR @Folly
                                      last edited by

                                      @Folly Awesome! Thank you!

                                      F 1 Reply Last reply Reply Quote 0
                                      • F
                                        Folly @TPR
                                        last edited by Folly

                                        @TPR

                                        Seems my hunch is correct.

                                        The pi3 suffers with the same problem.
                                        Although the .ddp game will work sometimes probably due to the fact that sometimes it just has enough memory left.

                                        I reduced the gpu memory in the raspi-config from 64mb to 32mb.
                                        Tested the pitfall.ddp again and now it works.

                                        The problem is that the pi4 seems to use a different approach with using the memory although you could give raspi-config a shot but that probably won't solve the problem.

                                        Another solution I can think of is to add some swap memory or use zram.sh.

                                        I still have an old script called zram.sh that I once found, you can try that on you own risk :

                                        #!/bin/bash
cores=$(nproc --all)
modprobe zram num_devices=$cores

swapoff -a

totalmem=`free | grep -e "^Mem:" | awk '{print $2}'`
mem=$(( ($totalmem / $cores)* 1024 ))

core=0
while [ $core -lt $cores ]; do
  echo $mem > /sys/block/zram$core/disksize
  mkswap /dev/zram$core
  swapon -p 5 /dev/zram$core
  let core=core+1
done

                                        Just run it with sudo bash zram.sh

                                        With the command free you can see how much memory and swap-memory you have before and after running the script.

                                        Notice that when you reboot your system zram isn't there anymore.
                                        So if this solution works you have to run it every time after a bootup or you have to make it stick so every time it boots zram.sh is loaded.

                                        I tested pitfall.ddp a couple of times (with zram enabled) and it seems to load every time now.

                                        TPRT 1 Reply Last reply Reply Quote 0
                                        • TPRT
                                          TPR @Folly
                                          last edited by

                                          @Folly Wow! That is very interesting indeed! So is this the first thing on the RetroPie that doesn't run on a 1gb board? I've yet to find any other console that has an issue.

                                          I'll try that script to see what it does, but I'm afraid it might break other things? So maybe I'll only use that when running ADAM .ddp files.

                                          F 1 Reply Last reply Reply Quote 0
                                          • F
                                            Folly @TPR
                                            last edited by

                                            @TPR

                                            Did it work ?

                                            1 Reply Last reply Reply Quote 0
                                            • F Folly referenced this topic on
                                            • AshpoolA Ashpool referenced this topic on
                                            • First post
                                              Last post

                                            Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                                            Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.