You are not logged in.
Pages: 1
Hello, I don't know which update did this, or when, but retroarch used to work fine on my system and now trying to launch it does absolutely nothing. I know that version 1.7.8.4-1 wasn't working for sure, and this morning I updated retroarch to 1.7.9.2-1 hoping that it would fix it, but no luck.
When launching it from the command line, I get this output:
charlesg-laptop:~
➜ retroarch -v
[INFO] RetroArch 1.7.9 (Git 4dcd7a0247)
[INFO] === Build =======================================
[INFO] CPU Model Name: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
[INFO] Capabilities: MMX MMXEXT SSE SSE2 SSE3 SSSE3 SSE4 SSE4.2 AES AVX
[INFO] Built: Oct 7 2019
[INFO] Version: 1.7.9
[INFO] Git: 4dcd7a0247
[INFO] =================================================
[INFO] [Environ]: SET_PIXEL_FORMAT: RGB565.
[INFO] Version of libretro API: 1
[INFO] Compiled against API: 1
[INFO] [Audio]: Set audio input rate to: 30000.00 Hz.
[INFO] [Video]: Video @ fullscreen
[ERROR] [Wayland]: Failed to connect to Wayland server.
[INFO] Vulkan dynamic library loaded.
[ERROR] [Vulkan]: Could not find instance extensions. Will attempt without them.
[ERROR] Failed to create Vulkan instance (-9).
[WARN] Failed to bind API (#9, version 1.0) on context driver "x-egl".
[WARN] Failed to bind API (#9, version 1.0) on context driver "kms".
[WARN] Failed to bind API (#9, version 1.0) on context driver "sdl_gl".
[INFO] Vulkan dynamic library loaded.
[ERROR] [Vulkan]: Could not find instance extensions. Will attempt without them.
[ERROR] Failed to create Vulkan instance (-9).
[ERROR] [Vulkan]: Failed to create Vulkan context.
[INFO] [Vulkan]: Detecting screen resolution 320x240.
[INFO] [Vulkan]: Using resolution 320x240
[1] 2650 segmentation fault (core dumped) retroarch -v
Anyone knows what's up with that? Thanks!
Last edited by CharlesG (2019-10-08 22:11:44)
Offline
Haswell/Broadwell level CPUs have a known quite breaking mesa bug, is this the only thing you are noticing issues with? See the following thread: https://bbs.archlinux.org/viewtopic.php?id=249639
Online
My thoughts were different that were V1del's I was wondering if you have recently changed to Wayland?
https://github.com/libretro/RetroArch/issues/6763
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Haswell/Broadwell level CPUs have a known quite breaking mesa bug, is this the only thing you are noticing issues with? See the following thread: https://bbs.archlinux.org/viewtopic.php?id=249639
Yes I see no other issues. Also, it's been broken on my system for quite a while (let's say a month, and the issue you mentioned seems quite recent), but I was waiting for the next retroarch version before bringing that up.
My thoughts were different that were V1del's I was wondering if you have recently changed to Wayland?
https://github.com/libretro/RetroArch/issues/6763
No, I'm on Xorg and haven't switched to Wayland (just checked to make sure).
Thanks for the help!
Offline
My thoughts are different from both of the above...
I'm experiencing a bug with a recent vulkan update, as posted here: https://bbs.archlinux.org/viewtopic.php?id=249696
I see you are using vulkan in retroarch. If you change your display driver from "vulkan" to "gl" does it work?
Offline
Post the coredump, and your retroarch.cfg , retroarch doesn't attempt to utilise a xorg backend. Thrown in
glxinfo -B #Needs mesa-demos
while we are at it.
Online
I see you are using vulkan in retroarch. If you change your display driver from "vulkan" to "gl" does it work?
Yes it does work! Never touched that cfg file before though, so I wonder why it previously worked. Also not sure why retroarch doesn't automatically detect available drivers.
Problem solved, Thanks a lot!
Offline
Pages: 1