[PI3B+ & Retropie 4.4.4] Limit on Roms stored?

mitu

@magicfly As I said in my first post - do you have enough memory available ?
There might be an error be in the /dev/shm/runcommand.log file, check that file also. ES launches Runcommand, but Runcommand is unable to start the game

lvl2: /opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS fba /home/pi/RetroPie/roms/fba/1942a.zip
lvl1: ...launch terminated with nonzero exit code -1!

magicfly

@mitu Hi, there's no runcommand. log in that folder so i think that file hasn't been written because the rom hasn't launched at all. any other thing i can check?

mitu

@magicfly You can check the system log, via dmesg, if there are any OOM errors or other process starting warnings.

Clyde

@mitu said in [PI3B+ & Retropie 4.4.4] Limit on Roms stored?:

@magicfly You can check the system log, via dmesg, if there are any OOM errors or other process starting warnings.

@magicfly In addition to that, you can use grep to show only those lines of dmesg that contain a specific term. Examples from my Pi's Retropie:

$ dmesg | grep warning
[    4.826054] random: 7 urandom warning(s) missed due to ratelimiting
$ dmesg | grep memory
[    0.000000] Virtual kernel memory layout:
[    0.001599] Disabling memory control group subsystem
[    0.176509] BCM2708FB: allocated DMA memory ef910000
[    0.263815] vc-sm: Videocore shared memory driver
[    1.217152] Freeing unused kernel memory: 1024K

Just type dmesg | grep and the word(s) you want grep to search for in dmesg's output.

The vertical bar is the Unix Pipeline, also called "pipe", that passes the output of one command (here: dmesg) to another (here: grep).

mitu

What @Clyde said :). What I usually do is clear the log buffer with sudo dmesg -c, try to reproduce the error condition, then run dmesg again just to see the new added messages.

Clyde

@mitu Nice tip! I will try to remember it in the future.

magicfly

something has changed..now i can't enter into emulationstation.
the HDD seems to load a lot and after some minutes from ES splash, the pi quits to the retropie bash with "KILLED" message.
what does it mean? it's a timeout? is there a way to modify this timeout?
Thanks

mitu

@magicfly Looks like the OOM killer kicked in.

magicfly

@mitu said in [PI3B+ & Retropie 4.4.4] Limit on Roms stored?:

@magicfly Looks like the OOM killer kicked in.

i get this log via dmesg:

https://pastebin.com/aGbZfiDb

mitu

@magicfly Yes, the dmesg shows ES being killed for using too much memory - which I've kept repeating since you've brought up this topic in the first place.

magicfly

@mitu than you so much. so all these roms are to heavy for the pie...time to free resources..
thanks again!