Main > Raspberry Pi & Dev Board
How to make a dedicated MAME 0.250 Appliance on a Raspberry Pi 4/Pi 400
HannibalAnthrope:
I had the same ideas, plus I just loaded the overlay to disable wifi because I don't use it.
I got the failed messages pretty much cleared up, and I cleaned up the filesystems on another Pi but I was never able to get past the root account locked problem and a few hours trying to research that on the net was painful and unfruitful. I still don't know what to do to solve it or what causes it because there were as many "answers" as people. I did try more than one Pi even though this one was brand new and is running fine now (and it ran RetroPie just fine too although that was a short test because I hate it and think it's garbage LOL).
If you'd like me to test again I can probably do that, but I would ask that you re-download the image you've posted, burn it to a chip and test it on your Pi4 to verify - and not that I don't appreciate your work, I do - but debugging a bootable chip image is time consuming and frustrating. And I'm pretty sure the final result is going to be confirming for me that MAME still does NOT work right on a Pi4, at least not with the classic games I use (Space Invaders for one). Even back to build .078 and having compiled SDL2 correctly MAME just eats the cpu and is far too slow to even play Space Invaders. I'm not sure how others are reporting it to work ok for them <shrug>. Anyway, let me know if you want try fixing it.
bbegin:
--- Quote from: HannibalAnthrope on August 27, 2020, 09:56:09 am ---I had the same ideas, plus I just loaded the overlay to disable wifi because I don't use it.
I got the failed messages pretty much cleared up, and I cleaned up the filesystems on another Pi but I was never able to get past the root account locked problem and a few hours trying to research that on the net was painful and unfruitful. I still don't know what to do to solve it or what causes it because there were as many "answers" as people. I did try more than one Pi even though this one was brand new and is running fine now (and it ran RetroPie just fine too although that was a short test because I hate it and think it's garbage LOL).
--- End quote ---
I think your problem is caused by the kernel not being able to mount the root filesystem (for some reason). Maybe because of the wrong PARTUUID, depending the tool you used to write the .img file to the SD card. I will update the procedure to switch to LABEL= in /etc/fstab.
Can you try this solution, please:
1. Mount the Raspberry Pi SD card on another computer
2. Edit the file /etc/fstab
3. Make sure you update these 3 lines (notice the LABEL= at leftmost):
LABEL=boot /boot vfat defaults,ro 0 2
LABEL=rootfs / ext4 defaults,noatime,ro 0 1
LABEL=data /data f2fs defaults,noatime,discard 0 2
4. Edit /boot/cmdline.txt and replace the parameter "root=PARTUUID=xxxxxxxx" by:
root=/dev/mmcblk0p2
--- Quote from: HannibalAnthrope on August 27, 2020, 09:56:09 am ---If you'd like me to test again I can probably do that, but I would ask that you re-download the image you've posted, burn it to a chip and test it on your Pi4 to verify - and not that I don't appreciate your work, I do - but debugging a bootable chip image is time consuming and frustrating. And I'm pretty sure the final result is going to be confirming for me that MAME still does NOT work right on a Pi4, at least not with the classic games I use (Space Invaders for one). Even back to build .078 and having compiled SDL2 correctly MAME just eats the cpu and is far too slow to even play Space Invaders. I'm not sure how others are reporting it to work ok for them <shrug>. Anyway, let me know if you want try fixing it.
--- End quote ---
If you are not able to emulate Space Invaders on a Raspberry Pi with MAME, it's because the hardware acceleration is not enabled.
I am able to emulate much more complex games with full speed (DoDonPachi, Truxton II, etc.) on my Raspberry Pi 4 with the provided How-To.
teller:
I got your image running and it's a great project! I would like to know how I can update MAME to the latest version (0.224). As far I followed to your step-by-step tutorial you excluded MESS. I would like to include the whole MAME (with the systems from MESS). What do I need to modify in the update script?
bbegin:
Hi teller,
To get the full MAME (arcade and classic systems), just remove SUBTARGET=arcade from MAKEOPTS variable asingment.
Be advised that I did not tested this build/compilation.
teller:
Thanks for your quick reply.
So I better make a backup before I update.
What are the update commands in servicemode?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version