RetroArch 1.7.0 error?

mitu

@swampy Can you enable verbose logging when launching a RetroArch game with https://retropie.org.uk/docs/Runcommand/#runcommand-launch-menu ? After you get the error, see what's in /dev/shm/runcommand.log.

Swampy

@mitu said in RetroArch 1.7.0 error?:

/dev/shm/runcommand.log

I hope the last lines could help:

[INFO] [Video]: Graphics driver did not initialize an input driver. Attempting to pick a suitable driver.
[ERROR] Currently active window is not an X11 window. Cannot use this driver.
[ERROR] [Video]: Cannot initialize input driver. Exiting ...
[ERROR] Fatal error received in: "video_driver_init_input()"
[ERROR] This core requires a content file.

MileSacul

I too am having that error with a fresh image of Raspbian Jessie 8.

I did run some apt-get update, installed main and core packages, and then did an rpi-update.

Here is some GL related info:

[INFO] [Video]: Starting threaded video driver ...
[INFO] [EGL] Falling back to eglGetDisplay
[INFO] [EGL]: EGL version: 1.4
[INFO] [EGL]: Current context: 0x1.
[INFO] [GL]: Found GL context: videocore
[INFO] [GL]: Detecting screen resolution 1360x768.
[INFO] [EGL]: eglSwapInterval(1)
[INFO] [EGL]: eglSwapInterval(1)
[INFO] [GL]: Vendor: Broadcom, Renderer: VideoCore IV HW.
[INFO] [GL]: Version: OpenGL ES 2.0.
[INFO] Querying EGL extension: KHR_image => exists
[WARN] [GL]: GLES implementation does not have BGRA8888 extension.
32-bit path will require conversion.
[INFO] [GL]: Using resolution 1360x768
[INFO] [GL]: Default shader backend found: glsl.

FYI, I tried to set GL Driver in raspi-config to G3 Legacy and it tells me "The GL driver is disabled" every time.

mitu

@swampy It looks like the RA tries to initialize an X11 environment, but it shouldn't. RA 1.7.0 was recently released (and added to RP), so it could be that something changed between 1.6.9 and 1.7.0 for the Raspberry PI system. Other users might be affected, not just you.
How did you update - binary or source ?

Swampy

I updated binary. I will try to downgrade RetroArch.
Thank you for your info.

MileSacul

@mitu I updated through binary.

Swampy

Is it possible to downgrade RetroArch?
I tried to changed these files with the older ones of RetroArch 1.6.9 :

scriptmodules/emulators/retroarch.sh
scriptmodules/emulators/retroarch/01_hotkey_hack.diff
scriptmodules/emulators/retroarch/02_disable_search.diff

Then I deinstalled RetroArch and installed it again.
The problem is still present.
Is there any reliable solution to downgrade to 1.6.9?

BuZz

I'll roll back sorry. I obviously didn't do enough testing - rebuilding from source should get 1.6.9 again now after updating retopie-setup. bins being rebuilt.

MileSacul

@buzz No worries. Development is tricky. :)
I'm just glad to find out my fresh install of RetroPie Web Console didn't cause this.

Swampy

Thank you for your quick response and your great work.

BuZz

binaries are back to v1.6.9 - Will do some testing / debugging of 1.7.0 on the RPI before updating again :)

MileSacul

@BuZz Issues resolved :). Let me know if you want me to do any testing. Working on setting up another fresh jessie image.

mitu

@buzz At a first glance it seems the configure script enables X11 even if --disable-x11 is passed as an argument.
In 1.6.9, after running the /configure with the args for RPI3, config.mk contains HAVE_X11 = 0, but 1.7.0 produces a config.mkwith HAVE_X11 = 1. The resulting binary (for 1.7.0) also reports when running with --features

  X11: X11 input/video drivers: yes

psyke83

@buzz: https://github.com/libretro/RetroArch/pull/5983

BuZz

@psyke83 Thanks for looking into this and sorting out a fix. Might wait for the next point release, but will see.

psyke83

@buzz np. If you do wait for 1.7.1, you may want to update the xmb assets at the same time - there's been a bit of activity in the assets repo that might impact it.

https://github.com/libretro/retroarch-assets/commits/master/xmb