Can you run, from a terminal, the following commands:

aplay -l aplay -L

and post the output ? The error in EmulationStation logs indicated the audio settings for the volume control are not correct. Do you have sound during gameplay, when running the emulators ?

@eborius said in PCSX2 & other emulators Crashing on Retropi (Ubuntu x86):

My snes emulator worked yesterday and have now stopped working...

Run it with verbose logging and post the log file (/dev/shm/runcommand.log) on pastebin.com.

@mitu, also a BIG thanks. I recently installed two systems with Xubuntu 22.04.1 and RetroPie. Same issue as described. First time it took me about an hour to locate this post which solved the problem. The last system I had this posting ready and after the first error message (exactly stating the parameters I needed) I fixed it.

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.

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

@doctordruidphd, how did you compile and install in Ubuntu Server? I am trying the same in Ubuntu Server 22.04 but got lots of compile/install errors. Did you change any defaults in the /boot/firmware/config.txt?

@mitu, do you know if once installed I need gnome or can I run from terminal directly?

Thanks!

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.

@slaan1974 said in Controller setup for GameCube in dolphin:

@YFZdude Hi, So I got this piece of software running,

select Controllers , select GC standard controller, press configure, select XInput2/0/Virtual core pointer, press all the individual buttons, they do react

select Emulate Wii BT, Emulated Wii, Config, select XInput2/0/Virtual core pointer, press all the individual buttons, they do react , i save this as profile sln

the buttons do react, and i saved it, but still i am not able to press buttons in a GC or Wiiware game

It sounds like you are doing the setup properly. You can confirm your controller settings have 'stuck' by re-opening the GUI and looking at the screens.

When you launch a game, does the runcommand box (grey with text) say it is launching with dolphin-gui ? That's how I run it so it may be necessary.

I haven't configured an emulated wii remote before but I did previously use a Logitech F710 as a gamecube controller and as long as the input is selected to match your device it should work. Double check that part. On my system, the Xinput2/0/Virtual core pointer is my keyboard and touchpad combo I think. I can try to verify that later tonight when I am in front of my system again.

EDIT: I just checked my setup at work that I forgot I had access to. Indeed on this system I have Xinput2/0/Virtual core pointer (keyboard and mouse) and evdev/0/Logitech Gamepad F310 (controller).

to add to the story i use a Wii Pro Controller

Is this the same controller you use with other emulators and it works fine?

Another couple of things you can try:

When you launch the Dolphin GUI, you can set (add) a ROMs directory and the games should show in the list on the main GUI page. Try launching a game directly from the emulator itself instead of through RetroPie and verify if the controller works this way. If that still doesn't work, try launching the Dolpin GUI with the sudo command in front of it and trying again. If the controller works this way, then you will need to add a udev rule to allow the emulator to have proper access to the controller.

on all other emulations i notice there is a bar in the bottom when a game starts this tells me the controller is enabled, but with GC/Wii there is no bar

The bar with the controller information is most likely a RetroArch notification. This would be present in any emulator whose name starts with lr-* which indicates the libretro version of the emulator. Correct me if I'm wrong but I think you are running the standard version of dolpin and not lr-dolphin. So those messages wouldn't appear the same way.

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

@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