@mitu Thanks yes you have right Thanks for the help

FYI - I just came across this same error message when using RetroPie Setup on my Raspberry Pi 4. It turns out, I was running it via sudo, while already in a sudo shell. To reproduce, do the following:

sudo -s cd /home/pi/RetroPie-Setup sudo ./retropie_setup.sh

To fix, either just exit out of the sudo shell, or don't use sudo to run RetroPie while already in a sudo shell.

Hope this helps.

- George

@icebear81
Nice. I want to get a Sinden lightgun sometime. I guess I'm out of ideas since I haven't used one before. I thought I read on his site that you have to install some custom software or driver to make it work with the border around the screen.

Maybe someone else who has one might have some ideas. To me it sounds like there is some configuration specific to the way the lightgun detects whether it is pointed at the screen or not. On the original NES Zapper it would select game modes if pointed away from the screen and start one if it was pointed at the screen.

Problem solved, I don't know if this is a general "issue" but the filename had double spaces in the file name . Deleting one and the rom worked.

@wop99
https://retropie.org.uk/docs/lr-mame2003/#samples
https://retropie.org.uk/docs/lr-fbneo/#samples

as said, please fill out the required details for specific help.

@mrnoholster yes. just launch the other version. note, if you're using a split romset you will need to include the parent rom (typically the one without a revision in the file name) in the same directory for dependencies to be met. if you're using a non-merged romset it won't matter - each rom is standalone and should launch.

any problems please fill out https://retropie.org.uk/forum/topic/3/read-this-first including verbose log

@mitu said in Screen tearing in pi 4:

Try using fbi, it's an image viewer that works on the console also.

Thanks that looks promising. I’ll have to see if there’s a way to control which display it outputs to.

@celestial Glad to help you!

I've had a number of people here help me out and help me figure out a lot of things on RetroPie. If I don't respond on a thread, feel free to tag me or send me a PM and a link to the page. If I can help, I want to.

I'm almost positive I used Keyboard Input mode. The problem is, and I'm going to post about this when I have time, every time power goes off in the barn for some reason, the file system on my SD card on my Pi messes up. I'm not sure why, but something goes wrong and it won't reboot. I've found if I take the card and plug it into another Linux system, just trying to read the data seems to fix whatever is wrong on the card.

That's where I am now. We got hit with that large ice storm and it knocked out power. (Thankfully we have our 1st floor in the house on the generator!)

So I can't check until I get the card working again. (I really need to transfer the whole RP setup to the USB drive - that survives shutdowns without issue.)

If I remember correctly, they say you can't do what I did in Keyboard Input Mode, but I really wanted to stick with it because, overall, that gave me the fewest problems to deal with.

While I can't remember the mode, one thing that makes me sure it's keyboard is because all the buttons and joystick positions do output characters when I'm in the Linux terminal.

Are you literally rebuilding your entire house? Is this a renovation? I've been involved in a few cases of tearing down most of the inside and redoing it with some historical properties.

140 tons of dirt - well, with my tractor, it can take time, since it's a smaller tractor. The big issue is it has to go from our front field to the barn (where the arcade machine goes) as part of the renovation - it needs some landscaping work. That's about a 1/2 mile round trip for each load! When I was new to dealing with all this and a contractor bailed on me for the driveway (driveway is 1/3 mile long, full roadway is 1/2 mile, including going to the barn), I had to teach myself to use a Bobcat skid steer. After about 3-5 hours of operational time to learn the Bobcat, I got to the lot early one day and moved 200 tons of dirt! (I had to make the driveway go over a 30" culvert).

@yserra Things are now progressing well and the games that I have are now all running OK.
Thanks for everyone's help.

Using the official image is relatively quick, easy, and free to do.
https://retropie.org.uk/download/

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

@chishiya said in Upgrade to larger SD-card or SSD:

@dankcushions

Thank you for your in-dept pros and cons, I appreciate it a lot!
Funny you mentioned the USB-Hub because I have been thinking about that as well. How does it work out when you play like 4 people on the Hub, is there some issues with the controllers?

nope! in fact i’ve played with 5 before. it being powered may be important as excessive USB power drain can cause issues with undervolting.

You mentioned about the bottleneck of many games on the emulationstation, which Raspberry pi have you been using when you saw that? I have the 4 B version. This is my first Raspberry pi so I can't compare it unfortunately with anything...... I haven't faced any issues with the loading but yes I don't have like 100 roms hehe.

i have heard of slow boots with pi3 for sure. however this’ll anecdotal stuff from years of support. i’ve not heard of it in a while. my pi4 takes a few minutes to boot - i have several 1000 roms, but i keep it on 24/7

@baconbandage Run the following command - with the gamepad plugged in - and post the output

cat /proc/bus/input/devices

Try testing the gamepad with the jstest utility. Exit EmulationStation and run

jstest /dev/input/js0

You should get a listing with the gamepad's input types (buttons/joysticks/etc.) and you can press the buttons/D-Pad/move joysticks to see if they are registering. You can exit the test by pressing Ctrl+C.

@dboy2 The configuration of the gamepad is stored in a .cfg file, which can be found at \\retropie\configs\all\retroarch-joypads. Open the file with a text editor and post the contents, surrounded by code (```) tags, in the topic.

I fixed it on my own. You got to raspiconfig, select advance tools, select configedit and select "libreto, change settings for libreto retorarch, select retroarc.cfg and change Video_driver to "GL" and then change menu settings to "refui" and then turn off threaded video to "false", set audio to "Alsathread" and that did it or something along those lines, I have only just fixed it.