@luckyluca said in Some roms not working with lr-fbneo:

The only reason why I haven't updated the core yet, is that I don't know if doing so might affect other systems I already built, and would necessitate updating their roms too (neogeocd for instance, and anything else I might not think of right now).

Your version is over 6 months old, so no doubt there will be romset updates/additions (we probably added over a dozen of new systems since then), neogeo cd won't be a problem though.

Nvm i figured it out

@2play do you have a Pi3 or Pi4? As far as I have been told, the XINIT option doesn't work in the Pi3 build.

@therealtitleist said in USB Ports not working Retropie 4.7.1 / Raspberry Pi4B:

Does that point to a hardware failure?

Most likely yes.

@jamrom2 Thanks for confirming this.

@richard-baker Before doing @jamrom2's last point ("Go back to your PC …"), you'll have to enable SSH in RetroPie. See the Docs for instructions, I recommend "(Option 2) From the RetroPie menu".

@mitu Thank you, That fixed it.

I changed it because I found emulation station running first was affecting the performance of the pi when doing normal desktop processes and it would quickly get annoying to have to exit emulation station and type startx to get to the desktop(for me let alone my son).

will go back to searching and see if i can figure something else out.

@sleve_mcdichael Thank you. That worked for me. I'll make sure not to change my login in the future -_-

Are you sure you downloaded the right image for your system ? The 'illegal instruction' error at the top makes me think you downloaded the image for a Rpi2/3 or Rpi4 board.

What exactly 'not working' means ? EmulationStation doesn't start ? Games aren't working ? Installation is not completing ?
Please add more details about your setup, including the Ubuntu version and hardware details.

@mitu Thank you it fixed all my problems I was having. You have been most helpful.

@xxalphawolf420xx From the 2nd screenshot, I see that the WLAN Country hasn't been set. It shows as DFS-UNSET, while on a working system it should show:

root@pie4:/home/pi# iw reg get global country UK: DFS-ETSI (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS (57000 - 66000 @ 2160), (N/A, 40), (N/A)

The other command screenshot looks like the command's been miss-typed (wlan instead of wlan0).
Check again your wpa_supplicant.conf and make sure it's correct - no extraneous characters, proper newlines, no funny quotes, un-balanced parantheses {/}. Post it here to take a look.

@G30FF I did not realize the wired version had that limitation, that's good to know

@luzer
I like the idea of a Raspberry Pi 4/Retropie gaming set up but almost 3 months on and I've done very little gaming and many, many hours of troubleshooting.

Similar to your issue - I have RP4, retropie, Xbox One S controllers, updated firmware for XB1S controllers, updated everything possible on the Pi4, installed xpadneo and finally got it paired and connected.

Got 2 current issues:
1st: When configuring the controller it wont let me choose the 'Xbox Home' button. Every other button works except XB home button. Watching ETA Prime (YouTube channel) setup, when he selects the XB Home button as his Hotkey button it registers as button 16. Mine just wont work, even though the button works on other devices (PC and Xbox)

2nd: After you choose a game in Retropie it goes to the blue screen where you get a list of options. D-Pad wont let me navigate so I have to use the left stick. When moving down I have to move it kind of down and to the left. I also have to push A button about 20 times to select something.

The last bit of info is a bit hard to explain but here goes: On the blue screen menu where you have all your options the cursor is flashing underneath the 'OK' , it's flashing super fast.
If I disconnect the XB1 controller the flashing slow down and I can use a usb wired controller to navigate & select everything as normal.
So while the XB1S controller is connected it just wont work properly. It only works in Retropie and the games, but not in the blue screen menu.

You should add a proper title for your topic - just saying Help in a Help and Support category is meaningless.
Take a look at https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=58151#p1485558 to diagnose boot problems. Look at the LED flashing patterns on your Pi and compare it to the diagnose info posted in that forum post to see where the boot stops.

May I suggest you unplug any wireless (game) controllers particularly using bluetooth. I had the same issue but the problem was resolved when I'd disconnect my XBOX One controller via bluetooth and used a wired keyboard,wired mouse and a wired controller/

@MBRetrocade said in HELP! Can’t alter MAME2016 controls:

@MBRetrocade said in HELP! Can’t alter MAME2016 controls:

Hello everyone, so all of the sudden I am getting —- in the control input slots in MAME2016 and MAME2003. These are also uneditable. I would really like to get some game controls configured, so any help would be extremely appreciated! Thank you

This is on Retroarch 1.8.5, and I did not see any error messages. I am just unable to change any of my controls suddenly. I also tried re-installing (assuming that I did something) from binary and it did not help. I did not update the system during this.

Here are my
Details:
Raspberry Pi 4B w/4GB ram, 64bit processor
Power Supply used: MODEL DCAR-RSP-3A5C, INPUT 100-240V AC, OUTPUT: 5.1V 3.5A
RetroPie version: Raspbian GNU/Linux 10 (buster) - Linux retropie 4.19.97-v7l+
Built From: RetroPie-Setup version: 4.6.1 (4464b474)
USB Devices connected: SNES controller, USB keyboard
Controller used: SNES controller, USB keyboard

Please note: I did switch to a PS2 USB controller during the process of going through my arcade games & configuring the emulators. It did let me change the controls at first and I did not update anything so I cannot understand why I am suddenly getting three dashes in the input slots - - -

Also note: Mame2003 works up I cannot go up down left or right.

SOLVED, a MAME 2016.rmp file was generated in
configs/arcade/mame2016 and over wrote my controls. I deleted the .rmp file and now I have my controls working again.

@neurocrash
I have the same problem with segmentation fault while running atari emulator.
I wrote two scripts:
1 - /home/pi/joyoffon.sh - turn off, wait 30 seconds, turn on controller
1-1.5 - this is my controller listed by lsusb -t

sudo echo '1-1.5' | sudo tee /sys/bus/usb/drivers/usb/unbind sleep 30 sudo echo '1-1.5' | sudo tee /sys/bus/usb/drivers/usb/bind

2 - /opt/retropie/configs/all/runcommand-onstart.sh
run joyoffon.sh only for atari emulator

echo "runcommand-onstart.sh" >&2 echo $1 >&2 if [[ $1 == *"atari"* ]]; then echo "This is atari - run script" >&2 /home/pi/joyoffon.sh & fi

After running atari game I have to wait until controller message appears.