@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.

You are truely a hero!
Your solution works very well. I have tested the easyrpg player with my homemade RPG and it works, as far as I have played, without any differences compered to the windows pc version.

Thanks a lot!

@fluffypillow thanks again for putting this together. For better or worse it has inspired me to start on a Pi4 build and hopefully learn a bit more about this stuff.

And to the rest of the team keep on doing the amazing stuff that you do.

@avih7531 The Wii emulator (dolphin) is only available for the PC builds, it can't run on a Raspberry Pi.

@mitu said in Removed emulationstation-dev help:

@paffley Just install Emulationstation (the regular package) from the core packages section.

Thanks @mitu

I installed a fresh ES from binary then had to re-add es_systems.cfg content from an old backup I had (modified).

All working now thank you! keep up the super work!

@BillyH If you haven't fiddled with the RA's configuration, the save files would stay alonside your ROM files, in the roms sub-folders. Once you access the file shares (\\retropie\roms), you can easily check the contents of those folder and see your save files (most of them have the .srm extension).

@Jareth247 Glad you got it working; I don't think the power switch script had anything to do with it - although the incorrect file that was causing the problem for apt could have been produced by an improper shutdown in the middle of an install operation.

Thank you @mitu
You're a star :)

Rob

@jareth247 You should open a new topic and provide the latest update log, as described in this topic. And please also add more information about your system - https://retropie.org.uk/forum/topic/3/read-this-first.

This is not implemented, you either update all installed or individually.

@mitu Thank for that info. I did remove the !kms and it build with no errors, but I get this when I try to run dosbox

DOSBox version 0.74
Copyright 2002-2010 DOSBox Team, published under GNU GPL.

Exit to error: Can't init SDL Unable to open mouse

So it's a start...