There's no separate bsnes-mercury package in RetroPIe, just regular bsnes.

@kylen12 said in Connecting Playstation 2 Controller via GPIO Pins:

Do you think it is feasible to have a Python script that would do so?

Probably yes, but I'm not famiiar with the SPI ecosystem on the PI. There's https://github.com/mholgatem/GPIOnext which is a simpler input simulation library (i.e. 1 GPIO line = 1 input/button) and can provide a starting point for the 'virtual' input device creation, but for the SPI part I'm afraid I have no idea.

@windg This worked great! Thank you so much @windg!!

@mitu That fixed it, thank you.

@boogyman062190 please add some more details about your system as outlined in https://retropie.org.uk/forum/topic/3/read-this-first

Can you post the relevant log file from ~/RetroPie-Setup/logs?

@tavuntu

In my last post I had to get a bit acquainted with DietPI.
I was thinking there wasn't a normal user so I added user "pi" now.
I overlooked that a normal user "dietpi" already exists.
So we user "dietpi" is usable in the future.

Anyway, I did somewhat a new RetroPie-Setup as user "dietpi" again.
Everything seems to work ok now and Emulationstation works too.
The desktop parts at the right and the left when starting a libretro core, that I described in my earlier post, are gone now too.

The experience is just like the normal "Debian 11 Bullseye / 32 bit" with mate desktop installed.

Conclusion :
After making a fresh OS you have to :

login as "dietpi" get RetroPie patch the sdl2.sh, system.sh and emulationstation.sh files install sdl2 install the core, main and other packages enjoy

Edit :
Too bad, I have no sound from hdmi, it seems some audio packages could be missing ;-(
Jack output works though. ;-)

@ciel Please provide details from your set-up and a log of the errors you are getting (See RetroPie-Setup/logs). Please put the logfile on a pastebin site rather than directly in the forum.

https://retropie.org.uk/forum/topic/3/read-this-first

@sleve_mcdichael aahh ok, so it's cause it's not on a Raspberry, ok that makes sense then. Thank you

@quasimaddboy neither. They mean the script itself. From the main menu (not the "manage packages" submenu), choose Update (updates the setup script and all installed packages) or Update RetroPie-Setup script (does what it says on the tin, updates just the setup script but not the underlying packages. The first one takes a lot longer.)

@mitu That worked perfectly - thanks!!

@mitu said in x86 Ubuntu install trouble / dependencies:

You could change your current Ubuntu repository mirror and retry (apt update first). You can use apt-cache policy to check the troublesome packages and see what version are available and from which repository.

I was unable to find held packages, but you got me going in the right direction. For whatever reason, my sources.list file had a comment in it that suggested that because I used a smaller ISO it might not have been the full file. Perhaps a side effect of not allowing online updates during install.

So I got hold of a more 'full' listing of the official sources and ran apt update and it suddenly had way more packages to update and then the install script could find more of what it needed.

Thanks!

@greenhawk84 said in How often do you fresh build?:

Hello, just curious about something I have never done until I have to with a new Pi model or mandatory change, which is start over again with a fresh install. How often do you do this?

Like others here, I also don't do it without good reason, e.g. when I switched from my Pi 3b to my new Pi 4 last spring. I also have customised my installation pretty much, so a new installation would require a good amount of re-configuration, even if most configurations can just be copied over from the old system.

I often wonder if so many updates through a package update eventually cause regressions.

RetroPie is built on Linux which in my long lasting experience doesn't "litter" the system over time as much as Windows does. You usually don't have to clean up or re-install a standard Linux system at all. As far as I can tell as a mere (power) user, RetroPie itself is also pretty neatly designed in the same way, so you shouldn't fear any regressions by just updating it via the RetroPie setup.

All that said, one important thing for any system is to back it up on a regular basis. Apart from failed updates or operating errors, every hardware can break any day for a number of reasons. See the Docs about Making a Backup.

My suggestion would be to use the RetroPie image directly and not through BerryBoot.

@mitu I'm having this same issue.

I've ran sudo ufw disable to disable my linux firewall.

I'm thinking that the issue is with my OPNSENSE router.

Which ports should I forward to my retropie server?

@xtv Just out of curiosity: Did you actually use beetle-psx on a Pi (which one?) and if so, how did it hold up since it's known for being too slow on ARM?

@reborn1840 said in I put retropie on raspbian,but Basic installation error.:

@mitu PING google.com (8.7.198.46) 56(84) bytes of data.

That's not saying much - do you get a reply back ? Is the connection working ? Can you install a simple package via apt get ?

You'll need to enable SSH on your PI and use an utility like CyberDuck or FileZilla to be able to download the log file to your mac, then unpack the log and upload its contents to pastebin.com.