Ubuntu 19.04 issues

Neo-Rio

@mitu
That’s interesting because 19.04 has better graphics support for AMD graphics, and my system is running an AMD2400G
I would have thought that graphics capabilities would have improved- if anything.
I never had to tweak anything to get 18.04 working, but it looks like I will have to on 19.04

mitu

@Neo-Rio Are you using Wayland ? Can you get a verbose log from RetroArch running a game and post it on pastebin.com ?

Parabolaralus

@Neo-Rio Off-Topic: Have you tried running PCSX2 on Ubuntu with that 2400g? Ive been seriously considering upgrading my Phenom for this emu and this was on my list...

On-Topic: "/opt/retropie/configs/all/retropie.cfg
Since I didn't see any retropie.cfg file in that directory, I created it and added the own_sdl2="0" flag" Works perfectly in a VM, i might do a clean install later!

Neo-Rio

@mitu
I've been uising Xorg, but trying to flip over to Wayland makes no difference. I even installed the hwe package.
It must be some AMD driver problem. Even emulation station seems to judder a little as system logos move left to right.
It's not just mame2010 either, but a whole slew of the default emulators from the basic install are buffering

If you can tell me how to get the log from a session, I'll upload.

For the record, here's my "inxi -Gx" output.
Remember that this is just a system with an AMD 2400G and using built in graphics.

Graphics:
Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
driver: amdgpu v: kernel bus ID: 08:00.0
Display: x11 server: X.Org 1.20.4 driver: amdgpu resolution: 1024x768~60Hz
OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-13-generic LLVM 8.0.0)
v: 4.5 Mesa 19.0.2 direct render: Yes

Also glxinfo -B:

name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org (0x1002)
Device: AMD RAVEN (DRM 3.27.0, 5.0.0-13-generic, LLVM 8.0.0) (0x15dd)
Version: 19.0.2
Accelerated: yes
Video memory: 2048MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 4.5
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
VBO free memory - total: 1829 MB, largest block: 1829 MB
VBO free aux. memory - total: 3039 MB, largest block: 3039 MB
Texture free memory - total: 1829 MB, largest block: 1829 MB
Texture free aux. memory - total: 3039 MB, largest block: 3039 MB
Renderbuffer free memory - total: 1829 MB, largest block: 1829 MB
Renderbuffer free aux. memory - total: 3039 MB, largest block: 3039 MB
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 2048 MB
Total available memory: 5120 MB
Currently available dedicated video memory: 1829 MB
OpenGL vendor string: X.Org
OpenGL renderer string: AMD RAVEN (DRM 3.27.0, 5.0.0-13-generic, LLVM 8.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.2
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.0.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

glxgears works at above 60FPS as well.

Neo-Rio

Never mind. I am a teapot.

My monitor refresh rate was somehow set to 23Hz in the system settings !
I set it back to 60Hz and everything is back to normal!

dgallina

Just to add a data point: I did an in-place upgrade of my Ubuntu 18.10 RetroPie install to 19.04 without issue using the suggested config file change above.

BuZz

Same here. I can't yet reproduce the issues above and I removed all SDL2 dependencies.

BuZz

I will install a fresh 19.04 in a vm to test though.

BuZz

Did anyone post a log? Didn't see one but it may save time to see what the fail was on 19.04.

mitu

@BuZz I don't think there was anything besides the SDL2 dependency and the other posters confirmed it was working fine once that is fixed.
I don't have the Debian Buster system that exhibited the problems at hand, but for the 19.04 I didn't get any errors during installation. I bumped the SDL2 version in sdl2.sh before starting the basic installation.

BuZz

@mitu I'd like to see the full log from any 2.0.8 SDL install fail as it's working here without bumping the version.

tchuyev

Hi,

1./ Bumped from 2.0.8 to 2.0.9 using Ubuntu 19.04 and it does indeed solves this issue.

However, when doing an 'sudo apt update', I get:

The following packages have unmet dependencies:
libsdl2-2.0-0 : Breaks: libsdl2-2.0-0:i386 (!= 2.0.9+1) but 2.0.9+dfsg1-1ubuntu1 is installed
libsdl2-2.0-0:i386 : Breaks: libsdl2-2.0-0 (!= 2.0.9+dfsg1-1ubuntu1) but 2.0.9+1 is installed
libsdl2-dev : Depends: libsdl2-2.0-0 (= 2.0.9+dfsg1-1ubuntu1) but 2.0.9+1 is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

Running 'sudo apt --fix-broken install' would NOT solve the issue:
dpkg: error processing archive /var/cache/apt/archives/libsdl2-2.0-0_2.0.9+dfsg1-1ubuntu1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libsdl2-2.0-0/copyright', which is different from other instances of package libsdl2-2.0-0:amd64
Errors were encountered while processing:
/var/cache/apt/archives/libsdl2-2.0-0_2.0.9+dfsg1-1ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

2./ Using latest Pop!_OS 19.04, I also get the following error messages at the end of a basic install:

Could not install package(s): libxkbcommon-dev libusb-1.0-0-dev libvulkan-dev libavcodec-dev libavformat-dev libavdevice-dev nvidia-cg-toolkit libfreeimage-dev libfreetype6-dev libcurl4-openssl-dev cmake libvlc-dev libvlccore-dev vlc rapidjson-dev mc feh cmake libsamplerate0-dev libspeexdsp-dev libpng-dev libglew-dev libboost-filesystem-dev nasm flex bison libpng-dev libglew-dev nasm libpng-dev

Any suggestions please?

mitu

@tchuyev said in Ubuntu 19.04 issues:

Any suggestions please?

Have you followed @buzz's advice to modify the /opt/retropie/configs/all/retropie.cfg file ? This should make use of the distro's packages for libSDL, so there shouldn't be any conflict.

tchuyev

Thanks, running this set of commands solved all of my issues:

$ sudo sed --in-place 's/2.0.8/2.0.9/g' $HOME/Git/Retropie-Setup/scriptmodules/supplementary/sdl2.sh
$ echo "own_sdl2=\"0"\" >> /opt/retropie/configs/all/retropie.cfg
$ sudo rm /usr/share/doc/libsdl2-2.0-0/copyright
$ sudo apt remove libsdl2-dev
$ sudo apt --fix-broken install
$ sudo apt autoremove
$ sudo ./retropie_setup.sh (Basic install)

Parabolaralus

I finally got around to installing this directly on my laptop (Kubuntu 19.04) last night and may tonight setup my desktop.

To clarify on @tchuyev post listed above;

If you're doing a clean install, setup your OS first and then run:
echo "own_sdl2="0"" >> /opt/retropie/configs/all/retropie.cfg
And everything should be hunky dory doing a basic install at that point.

If you skip that step and start the basic install (which i lol did) youll need to run because retroarch will fail to compile:
sudo apt remove libsdl2-dev
then if you havnt already:
echo "own_sdl2="0"" >> /opt/retropie/configs/all/retropie.cfg
And your basic install, or retroarch itself should be ok.

I didn't have to use the sed command at any point, nor did i have to --fix broken install. Im assuming that these may be required if you're upgrading?

So far all normal cores work fine and even Dolphin as well as PCSX2 1.5.0 (dev) from the PPA.

BuZz

@tchuyev please send me a full log as it's working on my 19.04. check logs folder under RetroPie-Setup

I can fix this with a full log without having to do a new install but no-one has provided one yet.

BuZz

Ok. Actually I just worked it out from your snippet above and apt-cache.

So now libavdevice58 has a dependency on the SDL version included with Ubuntu. Probably overly strict to require that specific version. May report this upstream.

I will maybe just use 2.0.9 for x11 targets and default to off as mentioned earlier.

Imho this is a packaging error. Makes it impossible even to use a newer SDL2 too.

BuZz

Please can you try this

https://github.com/RetroPie/RetroPie-Setup/pull/2696

I threw it together quickly but solves the issue with retroarch dependencies for me.

Parabolaralus

@BuZz Id love to help, but i have absolutely no idea what to do with that...It would be easy for me to set up a clean VM and test what you did, but im clueless as to what to do with that link.
Edit: Fail