Main > Raspberry Pi & Dev Board
How to make a dedicated MAME 0.250 Appliance on a Raspberry Pi 4/Pi 400
ZoOl007:
I managed to get it to work on the OdroidXU4. I did not yet set it up as a dedicated tv appliance as you did but I did get mame 0.219 running smoothly.
I tried several games including the ones in your movie and performance is top. WonderBoy3 isn't running at 100% - does that run 100% on the Pi4?
As for audio I can't say as I'm using hdmi to dvi atm.
The only thing that is a pity is that glsl can't work. If that could work it would be perfect.
bbegin:
--- Quote from: ZoOl007 on June 06, 2020, 11:36:06 am ---I managed to get it to work on the OdroidXU4. I did not yet set it up as a dedicated tv appliance as you did but I did get mame 0.219 running smoothly.
I tried several games including the ones in your movie and performance is top. WonderBoy3 isn't running at 100% - does that run 100% on the Pi4?
As for audio I can't say as I'm using hdmi to dvi atm.
The only thing that is a pity is that glsl can't work. If that could work it would be perfect.
--- End quote ---
Great to know that you've been able to successfully replicate the steps on your Odroid XU4 :)
The objective for me is to integrate the Raspberry 4B in a bartop arcade cabinet.
FYI, I also tried Wonder Boy 3, as you proposed and the speed isn't running at 100 % for me too on the Raspberry Pi 4.
HannibalAnthrope:
I burned your latest chip image to a clean chip and tried to boot it in a Pi4B 2gb. Mame splash appears, boot never completes. On tty3 I see a number of "FAILED" messages (Load/Save RF Kill Switch, dependency failed for local file systems, dependency failed for MAME autostart, etc..etc..) and then finally emergency mode. Except it cannot open access to the console and reports the root account is locked. LOL
Can't even get to a # prompt to try to fix it. Shame too because it looks like you put a lotta work into this. Seems like you may have overcooked the soup! A bit too much automation maybe? No offense intended. I'll take a look around it and see if I can find the main issues.
bbegin:
--- Quote from: HannibalAnthrope on August 25, 2020, 09:34:35 pm ---I burned your latest chip image to a clean chip and tried to boot it in a Pi4B 2gb. Mame splash appears, boot never completes. On tty3 I see a number of "FAILED" messages (Load/Save RF Kill Switch, dependency failed for local file systems, dependency failed for MAME autostart, etc..etc..) and then finally emergency mode. Except it cannot open access to the console and reports the root account is locked. LOL
Can't even get to a # prompt to try to fix it. Shame too because it looks like you put a lotta work into this. Seems like you may have overcooked the soup! A bit too much automation maybe? No offense intended. I'll take a look around it and see if I can find the main issues.
--- End quote ---
I would try first to get back the kernel messages on the console so you can pinpoint the problem.
From another computer, you can edit the file /boot/cmdline.txt on the SD card and remove the following arguments from the kernel command-line:
logo.nologo vt.global_cursor_default=0 quiet
And put back "console=tty1", instead of "console=tty3".
Can you take a picture of the kernel messages (and post it here) once the boot process is stucked?
To make an offline switch to Service mode, delete these 2 files from the SD card:
/etc/systemd/systm/network.target.wants/mame-autostart.service.
/etc/systemd/system/multi-user.target.wants/shutdown.service.
bbegin:
--- Quote from: HannibalAnthrope on August 25, 2020, 09:34:35 pm ---I burned your latest chip image to a clean chip and tried to boot it in a Pi4B 2gb. Mame splash appears, boot never completes. On tty3 I see a number of "FAILED" messages (Load/Save RF Kill Switch, dependency failed for local file systems, dependency failed for MAME autostart, etc..etc..) and then finally emergency mode. Except it cannot open access to the console and reports the root account is locked. LOL
Can't even get to a # prompt to try to fix it. Shame too because it looks like you put a lotta work into this. Seems like you may have overcooked the soup! A bit too much automation maybe? No offense intended. I'll take a look around it and see if I can find the main issues.
--- End quote ---
I would try first to get back the kernel messages on the console so you can pinpoint the problem.
From another computer, you can edit the file /boot/cmdline.txt on the SD card and remove the following arguments from the kernel command-line:
logo.nologo vt.global_cursor_default=0 quiet
And put back "console=tty1", instead of "console=tty3".
Can you take a picture of the kernel messages (and post it here) once the boot process is stucked?
To make an offline switch to Service mode, delete these 2 files from the SD card:
- /etc/systemd/systm/network.target.wants/mame-autostart.service OR (old name) autostart-mame.service
- /etc/systemd/system/multi-user.target.wants/shutdown.service
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version