@dankcushions said in Running out of MEM and SWAP when compiling lr-mame:

@johnodon yes, i pointed you towards the script earlier. however the script provides an informed guess rather than a cast-iron guarantee. normally it's enough.

lr-mame is in the experimental packages for a reason...

Gotcha. Thanks for all your help.

@keeks said in pi4 and memory:

@busywait I should have searched for RAM rather than Memory :)

:)

I run a Pi4 4GB behind my TV set. Sometimes I start the Pi Desktop and more RAM might help in that situation. (Browser with too many tabs, ... ?) But if you're sticking to just game emulation, sounds like you can save a little money \o/

Spending the saved cash on a good heatsink case (or case heatsink) would be sensible to stop the Pi getting too hot, and allowing more aggressive overclocking.

@martinfr said in RPi 1 Model B only reports 256MB RAM under RetroPie:

To my surprise, the OS only reports 256MB of memory (checked through ssh).
Is that expected? If not, how can I tell it to use the full 512MB?

I think so - the rest of the memory may be reserved for the GPU, since it's used by both the front-end (EmulationStation) and the emulators.

@dankcushions Perfect! I'll invest in a bigger Micro SD Card and then give it a go. Thank you so much!

I was instructed in one of the threads on here to make an alias to the folder on the usb drive containing the roms and just replace the folder in the retropie roms folder with the same named alias. That also works. One thing that I like about that is I could at any time just delete the alias and replace with a folder to return it to reading off the sd card, or you could have part of a folder on the usb and part on the sd (if you don’t mind having two subfolders in ES).

@greenhawk84
Did u try what i wrote ?
(Have to say I just played with it a bit,quit and play some games of psp .after it was on kodi for weeks... Runs Great so far ;) )
i did try to play with the omx .. read the comments ...
Good luck
With love to hear if u got it FIX :)

it worked! thx guys!

I know this topic is pretty old but I just had this happen to me. It happened because of a conflict in RetroPie auto start. I had manually entered a command line to auto start and then later chose the auto start option in RetroPie setup. Seems the two didn’t work well together. I resolved it by getting back to RetroPie setup in command line and deleted the auto start line. I’m definitely a noob so I apologize if my terminology is wrong. But I’m learning. Hope this helps someone else.

@garradam not safely shutting down can potentially cause corruption of your sd card. If your pi freezes you should remotely access your pi through ssh and safely shutdown that way. Often times it's only emulation station that isnt responding. There are a number of easy to use ssh apps for smartphones that are very convenient to use.

Thank you very much, your suggestion was right. Without the nespi case everything works fine. Thank you so much. Now I have to solve another problem that I don't have in my cabinet. Don't know why the controllers swap themselves after some reboot. I don't touch anything, simply turn off, turn on and magically pad 1 becomes 2 and 2 becomes 1..... howhever, don't wanna go out of post, I'll post it in another one. Thank you again.

@collcroc123 That's normal. Once you start the system, the 2nd partition will be expanded to fill up the free space (that shows up as Unallocated). The 1st partition is the boot partition, only holding the necessary files to start the system and then the actual OS and its files will be on the 2nd partition.

Ok I did that command and I got used 5.4GB(10%) with 51GB available. So I guess I just misread the File Manager.

What prompted me to misread the File Manager I suppose would be when I was scraping games and got a disk full or something else(forget what now) error message. However, I SSH'd into the Pi during the Scrape operation and perhaps that caused that error message and made me paranoid.

Thanks so much EctoOne, that was some sharp eyes :D

I tried to simplify the structure previously by using variables to populate filenames but this ended up causing issues. Changing back to the file structure and hardcoding the names of each graphic seem to fix that. I thought I was done with messing in them sub-theme files and didn't think to check in there.

I was hoping to find that these problems where linked with the memory issues but alas, these problem with random missing images still prevails. Not to worry.

Thanks for helping me solve this problem.

Github updated

Cheers
Dal1980

@dal1980 While you're developing your theme, it's good to start ES with the --debug flag and look in the log file to spot any errors coming from the .xml files parsing. The log file is in /home/pi/.emulationstation/es_log.txt.

Check here for more details on N64 emulators:
https://retropie.org.uk/docs/Nintendo-64

@devin_205 Do you have an USB stick you can use for the transfer? Then use the USB method described in the link @isrnick gave you. It should be the easiest way if you have problems transferring roms over the network.

it says cant upload a psx rom

Please describe exactly what you did and give us the exact error message(s).

@kaz69 No, only one OS boots at a time. Nothing additional is running in the background from the other installations. Not sure if PINN asks or allows you to set the partition sizes but obviously it would be handy to have larger partitions for those OSes that need it.

@paulo75 I think we're talking past each other :)

The file will not be inside the zip. It will be in ~/RetroPie/megadrive (or Genesis).

@TMNTturtlguy I've replied on the ticket. Exit es if building from source. Swap shouldn't fail if being used heavily. Sounds like sd card problems, but could be os. I don't want to add more swap as it would mean large swap file being created when not needed in many cases (with the current calculated swap size code).