Retropie Installation on Ubuntu Server x64 18.04.1

johnodon

I tried playing around with various video options (something I normally wouldn't need to do), but lr-dolphin is running games in a small window in the bottom left corner of the screen.
Mario Golf - Toadstool Tour (USA)-201015-074636.png

etheling

@johnodon Great to hear your test results! :) I had not tried lr-dolphin - that's a bummer. Did you try if there is any differenve if you change video drivers? E.g, video_driver=vulkan or video_driver=gl.

I'll try to do some additional testing during the weekend myself with a PC with geforce card.

@MisterB - looks like there is a way around patching retroarch. sh - turns out there is a 'flag' to support kms on x86 in RetroPie-Setup. I'll test that over the weekend too. Looks like I'll do an additional round of updates after all.

etheling

@johnodon Couldn't resist trying. I got same result with lr-dolphin as you did, but switching to video_driver=glcore worked for me (whereas vulkan segfaulted it).

johnodon

@etheling said in Retropie Installation on Ubuntu Server x64 18.04.1:

@johnodon Couldn't resist trying. I got same result with lr-dolphin as you did, but switching to video_driver=glcore worked for me (whereas vulkan segfaulted it).

That did the trick. It's good to have Gamecube back again! :)

johnodon

@etheling I have now moved on to trying to get Firefox to launch. Any hints?

etheling

@johnodon I didn't try this, but startx should launch openbox, and you could add a autostart file that launches Firefox. And you can call startx from a shell script through ports and then in that script add/remove the custom autostart file if you want (but don't use exec or I think otherwise you wont be able to return to ES after closing X). Edit: you should also modify /etc/X11/xorg.conf that the script installed to set resolution appropriate for your display (from 1080p).

johnodon

@etheling said in Retropie Installation on Ubuntu Server x64 18.04.1:

@johnodon I didn't try this, but startx should launch openbox, and you could add a autostart file that launches Firefox. And you can call startx from a shell script through ports and then in that script add/remove the custom autostart file if you want (but don't use exec or I think otherwise you wont be able to return to ES after closing X).

I'm just about there.

If I create a .config/openbox/autostart file with...

gnome-terminal --full-screen --hide-menubar -- firefox

And create a Firefox.sh in ports that has...

startx

It works fine.

However, if delete the autostart file and edit the Firefox.sh file to be...

startx
gnome-terminal --full-screen --hide-menubar -- firefox

I get a black screen.

I know i'm doing something completely stupid! :)

etheling

@MisterB I changed my mind about the 'recipes'. I think. I had some time during the weekend to refactor my KMS/DRM modifications (new gist here) and it's now almost completely split into it's own script that can be run via existing optional script mechanism. Unfortunately I couldn't avoid patching RetroPie setup, so there are three changes that remain in your script (both scripts in gist):

Add libdrm-dev dependency that RetroArch needs to compile when KMS/DRM flags are enabled (this really should go to ~/RetoPie-Setup/..../retroarch.sh , but on the other hand I really want to avoid patching it).
Patch ~/RetroPie-Setup/scriptmodules/system.sh to include x11 flag when compiling kms target (this is needed to get e.g. vulkan support, and be able to run under both KMS and X (or Wayland).
set __has_kms flag to let RetroPie-Setup know we want to do kms 'target'. My script checks that it's been set before executing as well.

I briefly consider (but didn't test) doing all of the above from my script, and then re-running RetroPie setup basic_install, but install takes long enough already, and dealing with all kinds of unexpectedness resulting from running it twice didn't really thrill me.

But other than that, it looks like it works really nicely as an optional script. And especially now that I ended up adding some complexity to it, I think it's much cleaner this way. I do rollback some of the changes made by your script, but it was much less work than I thought it would be.

Changes to KMS/DRM setup script functionality-wise (see previous posts for others):

Detect if we're using Intel/i915 based setup and add i915.modeset= kernel boot option
Probe maximum resolution of framebuffer device and if less than 1080p, (try to) find suitable resolution
Construct video= kernel boot option to include connector (e.g. HDMI-A-3, DP-1, Virtual-1...)
Added some error checking that we're getting 'official' version of libsdl2 from libsdl.org (e.g. I am not big fan of downloading 'random' tarballs from a website and then executing what gets compiled)

And lastly, while not completely unexpected, still somewhat disappointing: it looks like nVidia or Radeon based systems don't trivially support this approach. They might still, but... I got KMS/DRM working under Nouveau nVidia driver (used 'nouveau.modeset=1 i915.modeset=0' boot options), but performance was subjectively substandard to running emulators under X with nVidia binary drivers, so unless one is open source purist, I don't know why would you want to do that.

Although there are some cleanups to do for my script, I hope I won't have any changes that would need to go to your script anytime soon. I think I said that few days a go too! ;-) As for my script, I guess I should create a github repo for it and move it there.

Edit: I updated the Gist. I had a last minute omission there that broke it.

johnodon

FYI...

Unless it is installed via the Retropie setup script (or somewhere else early in the process), software-properties-common needs to be added to the dependencies otherwise apt-add-repository won't be there. The Ubuntu mini source ISOs don't have this included.

etheling

@johnodon said in Retropie Installation on Ubuntu Server x64 18.04.1:

However, if delete the autostart file and edit the Firefox.sh file to be...

I'm pretty sure startx blocks. And I don't think adding & to background it would work either.

johnodon

@etheling said in Retropie Installation on Ubuntu Server x64 18.04.1:

@johnodon said in Retropie Installation on Ubuntu Server x64 18.04.1:

However, if delete the autostart file and edit the Firefox.sh file to be...

I'm pretty sure startx blocks. And I don't think adding & to background it would work either.

So, Chromium appears to work just fine when calling it directly using startx (startx chromium-browser). If I try to do the same with Firefox, the window isn't maximized and the mouse goes whacko.

etheling

@MisterB Ubuntu 20.10 is now out. I quickly tested the script and looks like Python2 dependency python-xdg is no longer available and thus it doesn't install any of the other dependencies either and produces broken install (after reboot you'll get the infamous black screen). Changing to python3-xdg appears to fix it and produce mostly working install (see next message; not all libretro cores get installed). (edit)

20.04 appear to have python3-xdg as well.

I'm not familiar for what it is used for, so don't know if this is the right way to fix this though.

Maybe the script should abort/exit if RETROPIE_DEPENDS fails to install in any case? Something like this:

# Install RetroPie dependencies                                                                                                           
function install_retropie_dependencies() {
    echo "--------------------------------------------------------------------------------"
    echo "| Updating OS packages and installing RetroPie dependencies"
    echo "--------------------------------------------------------------------------------"
    apt-get update && apt-get -y upgrade && \
        apt-get install -y $APT_RECOMMENDS ${RETROPIE_DEPENDS[@]}
    if [ ! $? -eq 0 ]; then
        echo "ERROR: Problem with apt-get. Cowardly refusing to continue."
        exit 1
    fi
    echo -e "FINISHED install_retropie_dependencies \n\n"
    sleep 2
}

etheling

Also noticed that RetroPie setup basic_install doesn't pass on Ubuntu 20.10 x64. ~~I suspect this might be related to recent RetroPie/Retroarch updates more so than testing it on 20.10 though.~~ But just wanted to drop it here as I have the logs in front of me now (will test on 20.04 soon).

Edit #1: tested on a clean 20.04.1 and 20.10 VMs. Looks like this only happens on 20.10. GCC on 20.04 is 9.3.0 and on 20.10 it is 10.2.0.

Edit #2: Looks like this is caused by Ubuntu 20.10 upgrading to GCC 10.x. Created new thread with a workaround here.

...
Getting sources for 'lr-mupen64plus' : N64 emu - Mupen64Plus + GLideN64 for libretro
= = = = = = = = = = = = = = = = = = = = =

git clone --recursive --depth 1 --branch master "https://github.com/libretro/mupen64plus-libretro.git" "/home/pi/RetroPie-Setup/tmp/build/lr-mupen64plus"
....
/home/pi/RetroPie-Setup/tmp/build/lr-mupen64plus /home/pi

= = = = = = = = = = = = = = = = = = = = =
Building 'lr-mupen64plus' : N64 emu - Mupen64Plus + GLideN64 for libretro
...
...
g++   -march=native -O2 -fvisibility-inlines-hidden -std=c++11 -O2 -DNDEBUG -fsigned-char -ffast-math -fno-strict-aliasing -fomit-frame-pointer -fvisibility=hidden -DGIT_VERSION=\"" ab8
134a"\" -DOS_LINUX -DARCH_MIN_SSE2 -msse -msse2 -D__LIBRETRO__ -DUSE_FILE32API -DM64P_PLUGIN_API -DM64P_CORE_PROTOTYPES -D_ENDUSER_RELEASE -DSINC_LOWER_QUALITY -DTXFILTER_LIB -D__VEC4_O
PT -DMUPENPLUSAPI -I./custom -I./custom/mupen64plus-core -I./custom/android/include -I./custom/GLideN64 -I./GLideN64/src -I./GLideN64/src/osal -I./mupen64plus-core/src -I./mupen64plus-c
ore/src/api -I./custom/mupen64plus-core/plugin/audio_libretro -I./libretro-common/include -I./libretro -I./GLideN64/src/inc -I./xxHash -I./libretro-deps/libpng  -fPIC  -DCORE -DHAVE_OPE
NGL -DDYNAREC -c GLideN64/src/ShaderUtils.cpp -o GLideN64/src/ShaderUtils.o
In file included from GLideN64/src/ShaderUtils.cpp:3:
GLideN64/src/ShaderUtils.h:10:52: error: ‘string’ in namespace ‘std’ does not name a type
   10 | void logErrorShader(GLenum _shaderType, const std::string & _strShader);
      |                                                    ^~~~~~
GLideN64/src/ShaderUtils.h:6:1: note: ‘std::string’ is defined in header ‘<string>’; did you forget to ‘#include <string>’?
    5 | #include "Combiner.h"
  +++ |+#include <string>
    6 | 
GLideN64/src/ShaderUtils.h:11:93: error: ‘std::string’ has not been declared
   11 | int compileCombiner(const gDPCombine & _combine, Combiner & _color, Combiner & _alpha, std::string & _strShader);
      |                                                                                             ^~~~~~
make: *** [Makefile:433: GLideN64/src/ShaderUtils.o] Error 1
make: *** Waiting for unfinished jobs....
Removing additional swap
/home/pi
Could not successfully build lr-mupen64plus - N64 emu - Mupen64Plus + GLideN64 for libretro (/home/pi/RetroPie-Setup/tmp/build/lr-mupen64plus/mupen64plus_libretro.so not found).
Errors:
Could not successfully build lr-mupen64plus - N64 emu - Mupen64Plus + GLideN64 for libretro (/home/pi/RetroPie-Setup/tmp/build/lr-mupen64plus/mupen64plus_libretro.so not found).
No module 'splashscreen' found for platform x86

sthope

@noise said in Retropie Installation on Ubuntu Server x64 18.04.1:

My main problem is now pcsx2 i can't install from

Did you managed to install it?!
I recently got into RetroPie and had PCSX2 installed on my normal Ubuntu 20.04 Desktop version, yesterday when I found this script online I switched to Ubuntu server 20.04 and now can't install PCSX2 either.

etheling

I never really had used/liked shaders much for a variety of reasons such as speed, gimmicky look, etc. Over the weekend I came a cross some posts with examples of scalefx and xBRZ shaders and started reading more about Pixel-art scaling algorithms. And it looks like I can run many systems (SNES, NeoGeo, ...) with full framerate with ScaleFX or xBRZ enabled (on 8th gen NUC). And while results and performance vary, subjectively these filters really perform miracles on some games - see below:

alt text

Looks like RetroArch is moving away from [old?] GLSL/Cg shaders to new(er) Slang shaders (Github) which are also only supported shaders with Vulkan and glcore video drivers.

Setup script didn't install slang shaders. I modified install_retroarch_shaders() to install them to /opt/retropie/configs/all/retroarch/shaders-slang. See below. Also sent pull request to @MisterB with these updates.

# Install RetroArch shaders from official repository                                                                
function install_retroarch_shaders() {
    echo "--------------------------------------------------------------------------------"
    echo "| Remove the RPi shaders installed by RetroPie-Setup and replace with"
    echo "| RetroArch (merge of common & GLSL, and new Slang) shaders from Libretro"
    echo "--------------------------------------------------------------------------------"
    # Cleanup pi shaders installed by RetroPie-Setup                                                                
    rm -rf /opt/retropie/configs/all/retroarch/shaders
    mkdir -p /opt/retropie/configs/all/retroarch/shaders
    mkdir -p /opt/retropie/configs/all/retroarch/shaders-slang
    # Install common shaders from Libretro repository                                                               
    git clone --depth=1 https://github.com/libretro/common-shaders.git /tmp/common-shaders
    cp -r /tmp/common-shaders/* /opt/retropie/configs/all/retroarch/shaders/
    rm -rf /tmp/common-shaders
    # Install GLSL shaders from Libretro repository                                                                 
    git clone --depth=1 https://github.com/libretro/glsl-shaders.git /tmp/glsl-shaders
    cp -r /tmp/glsl-shaders/* /opt/retropie/configs/all/retroarch/shaders/
    rm -rf /tmp/glsl-shaders
    # Install Slang shaders from Libretro repository (for use with Vulkan, glcore, ..)                              
    # https://www.libretro.com/index.php/category/slang/                                                            
    git clone --depth=1 https://github.com/libretro/slang-shaders.git /tmp/slang-shaders
    cp -r /tmp/slang-shaders/* /opt/retropie/configs/all/retroarch/shaders-slang
    rm -rf /tmp/slang-shaders

    # Remove git repository from shader dir                                                                         
    rm -rf /opt/retropie/configs/all/retroarch/shaders/.git
    rm -rf /opt/retropie/configs/all/retroarch/slang-shaders/.git
    chown -R $USER:$USER /opt/retropie/configs
    echo -e "FINISHED install_retroarch_shaders \n\n"
    sleep 2
}

elliot123

Installed this mod years ago and it worked straight away. But after installing this script, after the initial RetroPie animation loading bar, it just goes to the black screen.

Tried another fresh Ubuntu image but got to the same point again.

Any ideas?

I am using the ubuntu-20.04.1-live-server-amd64 version of Ubuntu.

etheling

@elliot123 It sounds like you maybe hitting this problem (discussed earlier in this thread).

psybertech

@johnodon said in Retropie Installation on Ubuntu Server x64 18.04.1:

You learn something new everyday.

I run RetroPie on top of Ubuntu on an Asus CN65 Chromebox (Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz). I also have an Asus CN60 Chromebox (Celeron) that runs stock ChromeOS. I use this second box to stream web content (mainly sports from some nefarious sources).

And then it dawned on me...

Why not just install genuine Google Chrome (no need for Chromium) on the RetroPie box and create a launcher for it in Ports. It works BEAUTIFULLY!!! I can stream 4K content from Youtube without a single hiccup and I can now retire a piece of equipment.

If anyone wants to do this, all I did was download the current stable release and install it using apt:
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo apt install ./google-chrome-stable_current_amd64.deb
If not already done, add 'Ports' to your /opt/retropie/configs/all/emulationstation/es_systems.cfg:
  <system>
    <name>ports</name>
    <fullname>Ports</fullname>
    <path>~/RetroPie/roms/ports</path>
    <extension>.sh .SH</extension>
    <command>bash %ROM%</command>
    <platform>ports</platform>
    <theme>ports</theme>
  </system>
Create a ~/Retropie/roms/ports/Google Chrome.sh script with the following in it:
google-chrome &>/dev/null
Create a ~/Retropie/roms/ports/gamelist.xml:
<?xml version="1.0"?>
<gameList>
	<game>
		<path>./Chrome.sh</path>
		<name>Chrome</name>
		<playcount>2</playcount>
		<lastplayed>20200906T151625</lastplayed>
	</game>
	<game>
		<path>./Google Chrome.sh</path>
		<name>Google Chrome</name>
		<desc>Google Chrome is a cross-platform web browser developed by Google. It was first released in 2008 for Microsoft Windows, and was later ported to Linux, macOS, iOS, and Android where it is the default browser built into the OS. </desc>
		<image>./images/Google Chrome-image.png</image>
		<video>./images/Google Chrome-video.mp4</video>
		<marquee>./images/Google Chrome-marquee.png</marquee>
		<rating>0.85</rating>
		<releasedate>20080902T000000</releasedate>
		<developer>Google</developer>
		<publisher>Google</publisher>
		<genre>Web Browser</genre>
		<playcount>1</playcount>
		<lastplayed>20200906T153421</lastplayed>
	</game>
</gameList>
And of course add some images and video if you like.

John

PERFECT!

This is the first and only thing I tried and BAM! Works perfectly!
I only wanted to add it to load a hi-score web page/tracker I whipped up and this was super simple to setup in like 30 seconds.
Thank you, John!

Jay
cheers

Nobodyfamous

I just had to register so I could say, YOU GUYS ROCK! This will be about my 10th Ubuntu/retoropie install trying to get a good working setup on an old laptop. I have a really good feeling about this one!

Nobodyfamous

@elliot123 as per the "error above" (earlier in the thread) What Kernal version are people running? I get

pi@retropie:~$ uname -r
5.4.0-58-generic

I am also getting the black screen. I first tried installing via Ubuntu 20.04 live server, then with the link for mini.iso provided by MizterB on GitHub.

if I hit alt +F2, login and run emulationstation on the laptop, it says

lvl0: Error initializing SDL!
No available video device
lvl0: Renderer failed to initialize!
Window failed to initalize!

And somewere I read to look in a log file, but I don't remeber where or what log file, but do recal it said something about "screens found, but none configured correctly"