In case anyone else encounters the same issue, here are my config.txt settings:

# For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details # uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan disable_overscan=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output hdmi_force_hotplug=1 hdmi_ignore_edid=0xa5000080 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=2 #hdmi_mode=4 # THE ABOVE ARE WORKING, USE AS FALLBACK hdmi_group=1 hdmi_mode=16 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # Uncomment this to enable infrared communication. #dtoverlay=gpio-ir,gpio_pin=17 #dtoverlay=gpio-ir-tx,gpio_pin=18 # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on [pi4] # Enable DRM VC4 V3D driver on top of the dispmanx display stack dtoverlay=vc4-fkms-v3d max_framebuffers=2 [all] #dtoverlay=vc4-fkms-v3d overscan_scale=1 #hdmi_max_pixel_freq:0=200000000 #hdmi_max_pixel_freq:1=200000000

While waiting I installed Recall box to try if it works. It's same there.

However... I found old Saitek Pad (PS2700) and it works like a charm. I decided to try xBox Controller via USB and it works like a charm.

Trying to connect via Bluetooth does not work at all. Will try to ssh and play with BT then, maybe console will tell me something.
Since I can't pair my headphones also, I think it might not be pad problem, but bluetooth.

About SteamController. There is problem with mapping of d-pad. It recognizes only swipe in one or 2 directions. Like Analog Left and Analog Up. So its more like Analogue for emulator than D-Pad.
But I think i can pass on stemController if XBox and Saitek works. I'm a fan of D-Pad. Touchpad as D-Pad is not good on SteamController.

@johnodon PR created: https://github.com/RetroPie/EmulationStation/pull/767

I'd like to piggyback here just a bit, and hopefully not offtopic just to share my experience for whatever it's worth.

I've tried many times to get mame installed on my custom built PC from 2012 and failed numerous ways. The PC is AMD processor based and uses a Radeon 7770 GPU, and I can install lr-mame20003 and lr-mame2010 with no problems whatsoever. But when I've tried lr-mame2016, lr-mame, or even mame, I always end up with errors similar to the above and a failure to install.

fatal: No names found, cannot describe anything.

I've mostly stuck to Ubuntu 20.04, but once tried 21.04 and ran into the same thing @johnodon mentioned about the qt5 dependency. So today I got hold of a Dell Optiplex 3070 to test. I was able to install lr-mame onUbuntu 20.04.2 on the first attempt. This is Intel CPU based with integrated graphics.

I suspected and am now increasingly convinced that either my AMD CPU or my old Radeon GPU has something to do with being unable to install on my old PC. Unfortunately the logs and error messages don't provide enough clues to fix it in my experience. So when I get around to doing an arcade cabinet build, I will be looking for an Intel based system.

I wonder if there is anyone who can say they have installed newer mame cores on Ubuntu using AMD processors or AMD / Radeon GPUs.

@sleve_mcdichael @Addison Thank you for your help!!

@stevenrice please fill out https://retropie.org.uk/forum/topic/3/read-this-first

but again note that it doesn't support .zip files. the behaviour that you're seeing can be caused by incompatible file types. if you're using .zip, extract the files.

Modify the emulators.cfg file from /opt/retropie/configs/wii and add a new emulator entry for the distro's version of dolphin. You can then choose this version from the runcommand launch menu and make it the default for running Wii games.

@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

@madoc said in Player 2 arcade controller inoperative:

HOWEVER. pacman and R-type still stubbornly refuse to use the P2 controls in two player games. They switch player onscreen but you have to use the P1 controls. Is that expected behaviour ?

Yes, some arcade games support2 alternating player, but not simultaneous. If in doubt, you can always check the game at adb.arcadeitalia.net.
Packman - http://adb.arcadeitalia.net/dettaglio_mame.php?game_name=pacman&arcade_only=0&autosearch=1
R-Type - http://adb.arcadeitalia.net/dettaglio_mame.php?game_name=rtype&arcade_only=0&autosearch=1

This mean the configuration for the controller is not saved.
Please add some info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@mitu
Pi4 4GB
Official PSU
Latest retropie (just updated)
Latest Emulationstation (just updated)

As I already mentioned I had configured the controller (wireless PS3 controller) in Reicast manually.

It still did nothing other than launch the game.

I have since (last night) tried two different controllers (PS4 connected using an 8bitDo adaptor and a generic USB wired controller) and they both worked fine without being manually configured in Reicast all be it I couldn't exit the game (I suspect manual config in reicast will solve that)

So it would appear PS3 controllers are not compatable with Reicast despite being listed in the reicast config (my google of the issue did tend to throw up more ps3 controller issues than any other).

I will look into installing flycast

Thanks,

Please add some info about your setup and issue, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Are you using the RetroPie Pi3 image from retropie.org.uk/download ?

Thanks for the help on this everyone

@dankcushions oh cool, then i will try that out. thanks a lot for your help!

@lilian3004 it does. we need more information - please describe exactly what you see, and provide verbose logs and full info as per https://retropie.org.uk/forum/topic/3/read-this-first

@drdave79 please provide us with all the info requested here including verbose log