Although strange, I have only declared one controller in ES.
By this way, I have no more strange behaviour on some buttons. So it's better now.
Still have the controller 1 or 2 swapping in some emulators...
Try to manage with joystick-selection, but not sure it could handle this 100%, as name and reference are always the same.

@doctordruidphd said in [solved] Emulators won't start ubuntu 20.04 RPi4b:

Some things don't seem to be working -- the sega cd emulator just goes to a black screen

More likely you're missing the SegaCD BIOS - look it up in the docs.

I have an i5 NUC 8. I don't run Retropie but instead built up a Retropie inspired setup that runs from the Desktop.

@mitu

Thank you! That was exactly what I was missing. It is funny, because in my first Retropie copy I've got exactly that command but forgot about it now.

Sorry for little bit stupid question. Thanks again.

@retrofdi

So, you get the same results on fresh install...And just spit balling per say, how many video ports do you have? Additionally, have you tried any other displays? My thoughts would be the next thing to look at the communications via HDMI (Assuming you are using HDMI based on the hardware). I would use a known/good HDMI cable, attempted another port, and another display is possible.

@stoltzy Something related to your WM maybe or a bug in SDL which doesn't correctly set up fullscreen. What WM/DE are you using ?

Combined with --resolution WxH, you can use --windowed to start ES as 'full screen', just to avoid this issue.

Have you tried https://retropie.org.uk/docs/Wii/#controls ?

Here is a potential solution

From emulationstation, enter RetroPie configuration Then RetroArch In the Main Menu of RetroArch, select Settings -> Input

From there, go down to Port 1 Controls and update the following

Set Device Type to RetroPad with Analog Set Device index to 8BitDo SN30 Pro+

I was able to get two controller working with this work around.

Versions

Program Version / Hash emulationstation 2.9.6RP retroarch-setup.sh b3acb001fcf6276a2ef5c5b4caca135b399797f8 retroarch 8373ac6

In hindsight having a keyboard plugged in may have been problematic in regards to it defaulting to the primary controller.

@mcjones9631 said in Ubuntu PC having issues running ROMs:

Controller always gives "✔️ USB Gamepad (121/17) not configured" when in games and games can only be exited from the keyboard

This usually happens when your controller doesn't have a configuration file/profile in RetroArch. If you configured your controller in EmulationStation, a RetroArch configuration file for the controller should be created automatically, unless you turned of the auto-configuration of controllers in ES.

Is you controller working in EmulationStation, after you have completed the input configuration ? Did you disable the auto-configuration in EmulationStation, by any chance ?

@dirtbagxon Fantastic! Thanks for your support!

John

Commit https://github.com/RetroPie/RetroPie-Setup/commit/ee74dbdf223f8dd99d5457c4563bd7f92e156ed8 has fixed the issue.

Thanks you @mitu

0 joolswills committed to RetroPie/RetroPie-Setup Merge pull request #3369 from cmitu/joy2key-fix1 joy2key: simplify debug message; fix python warning

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

@yfzdude said in Trouble creating desktop launcher file [SOLVED]:

I'm still curious if any GNU/Linux wizards know why the original method was not working. Either way it is working now.

Because runcommand needs a terminal to show the launch menu, launching ES directly would break this. On Debian and friends, you can use x-terminal-emulator as the terminal starting command, which would be expanded to one of the installed terminal emulators.

Either way, check you connection to github.com - that's the reason the installation is not working.
If you run manually one of the git commands, what error do you get ?

git clone --recursive --depth 1 --branch master https://github.com/mupen64plus/mupen64plus-core

@mitu Quick update: lr-pcsx-rearmed and lr-parallel-n64 worked.

@mitu I was just messing around with all of this. I don't have a RP4 yet, but plan to get one. I just wanted to get familiar with the different gaming-centric OSes before I got mine. I'm running this on a laptop that's running Windows 10. I need the ability to have Windows 10 running while I play around with this RP and emu stuff for the time-being. Using VirtualBox gives me that ability. I checked the '3D Acceleration' checkbox and now RetroPie runs. However it's really slow and beyond the configuration menu, I don't see anything else. I've got a VM that only loads an SD card (no 'host' VM OS) of another gaming front-end and the speed of it is great. I'm guessing the slowness has to do with running a system in a system in a VM (or something like that). That's cool. I just wanted to see it.

lrbarrios

@kmancali , on top of what @mitu said, if you want to have some systems directories in different mount points (or partitions) symlink just those directories:

/mnt/roms/amiga to $HOME/RetroPie/roms/amiga

while $HOME/RetroPie/roms remains in the main partition

Are you sure your USB drive is mounted as /mnt/Retro Drive ? Is the user that's running EmulationStation (RetroPie installation user) able to access the driver and its contents ?