@oleguer please provide all the info requested in my link. that includes a specific example game, the image you used, the verbose log, and so forth.

that said, i don't use advmame on pi4 - i believe it is unoptimized. in the first instance you should use one of the recommended MAME/FBN emulators: https://retropie.org.uk/docs/Arcade/#step-1-choose-your-arcade-emulators

lr-fbneo is probably the best all-round performer.

@wtstreetglow1 any update?

The issue seems to be the mirror chosen supports IPv6 and the PI tries to connect via IPv6 to it, then fails. Changing the mirror may work, but you can also configure apt to use IPv4 only - see here.

@sleve_mcdichael ah - I doubt it very much! Thanks for pointing the way, feeling a bit silly now.

@sirhenrythe5th Yes, that's what I have. Just won't play under lr-flycast
@sleve_mcdichael Redream plays it with no problems! Thanks.

@finopoulos90 Hello, I installed coin acceptor in my arcade cabinet with an Ipac2. Please don't connect 12 volt to the Usb Encoder. without a Zener Diode. Because of the same principle you have to use this schematic link from Ultimarc's website below with a Zener Diode (Coin Mech Setup tab)
https://www.ultimarc.com/cabinet-parts/cabinet-parts/coin-mech.-single-coin/

Kind Regards
Niyazi

Looking at the dependency chain startup, mounting of the media is taking the most, delaying the console-setup start.
You can try to disable the auto-mounting of the external disc and manually add the mount command in /opt/retropie/configs/all/autostart.sh, before ES starts. This way the splashscreen service will start sooner.

Looking at the dpkg output, looks like you have the latest versions for the Bluetooth related packages - so no issue here.

@lolonois Thanks, will check it out.

@mitu Thanks...this just might work. I'll give it a go and let you know.

I appreciate the support.

The games is available as a Debian package - https://packages.debian.org/buster/lbreakout2. Just install the desktop and the package, then launch it from the menu.

hi sorry, i'm an idiot, I noticed that I have retropie sd-card in my sd reader

RetroPie doesn't use the desktop env (which I think you'd need for VNC) and it doesn't have it installed by default if you use the provided image. While some Pi4 users run EmulationStation from the desktop, it's not a supported or tested configuration and you may bump into problems at some point.

@lister-of-smeg said in Red Light Power Flickering:

I would start by checking the rest of the peripherals (you mentioned having another pi - use that with the exact existing setup) That should let you know if the original board is faulty or not

If the board is randomly shutting down I suspect it will need replacing

Alright, I'll try that later today. Yeah I also figured it needed replacing.

Just thinking of how to prevent a repeat, could a split-second power outage have caused the Pi to die? While I was playing on it weeks ago, there was a quick power outage a week ago during a thunderstorm, not long enough for the PI to lose power or immediately cause this problem, but maybe that could have fried the electronics? Maybe I need to use a UPS or regulator

This issue has been fixed with an RPI OS update for the Bluetooth packages, so the workaround is no longer necessary - an update of the packages/OS is enough.

You can update the packages as part of RetroPie's update menu or manually with

sudo apt update sudo apt upgrade

The bluez package version that fixes the issue - 5.50-1.2~deb10u2+rpt1.

@stoo said in "Dosbox" mount c /home/pi/RetroPie/roms/pc doesn't exist:

sudo mount -t cifs -o uid=pi,guest,nounix,noserverino //192.168.0.250/storage/RetroPie /home/pi/RetroPie

I am not sure why (maybe the vers=1.0) but using your recommended mount worked perfectly. I appreciate all the assistance to get this sorted. I was definitely stumped on this one. Mark this as solved.

In 1.9.4 you can selectively disable the notifications shown on screen, so you could remove the messages shown on startup by adding

notification_show_remap_load = "false" notification_show_config_override_load = "false" notification_show_autoconfig = "false" notification_show_set_initial_disk = "false"

to /opt/retropie/configs/all/retroarch.cfg.

@mitu Yes, it is!

So I thought I had better post to say that I solved my own problem. I had to get sync from SCART pin 19 on the Pi2SCART's female connector, not pin 20. I did not know about male SCART leads swapping pins 19 and 20. I hope this post might help somebody else out one day.