retroarch doesn’t launch on antiX 19.3 i386 core

This topic has 11 replies, 2 voices, and was last updated Nov 10-9:40 am by Raudonkepuris.

Viewing 12 posts - 1 through 12 (of 12 total)

Author

Posts

November 9, 2020 at 8:02 am #44645

Member

Raudonkepuris

I’ve recently revived an old laptop with antix, now I’m trying to run retroarch on it. I installed it via this command that I found on their website:

sudo add-apt-repository ppa:libretro/stable && sudo apt-get update && sudo apt-get install retroarch*

but now I’m getting a weird error, this laptop has VN800 chipset, which in my mind shouldn’t be interfering with retroarch.

here’s the error:

[INFO] RetroArch 1.7.3 (Git b2ceb50)
[INFO] === Build =======================================
Capabilities: MMX MMXEXT SSE1 SSE2 SSE3 
Built: Jun  7 2018
[INFO] Version: 1.7.3
[INFO] Git: b2ceb50
[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: 29970.03 Hz.
[INFO] [Video]: Video @ 960x720
[ERROR] [Wayland]: Failed to connect to Wayland server.
[INFO] [GLX]: GLX_OML_sync_control and GLX_MESA_swap_control supported, using better swap control method...
[INFO] [GL]: Found GL context: x
[INFO] [GL]: Detecting screen resolution 1280x800.
[INFO] [GLX]: Window manager is dwm.
[INFO] [GLX]: X = 0, Y = 0, W = 960, H = 720.
[INFO] [GLX]: Found swap function: glXSwapIntervalEXT.
[INFO] [GLX]: glXSwapIntervalEXT(1)
[INFO] [GL]: Vendor: VMware, Inc., Renderer: llvmpipe (LLVM 7.0, 128 bits).
[INFO] [GL]: Version: 3.1 Mesa 18.3.6.
[INFO] [GL]: Using resolution 698x775
[INFO] [GL]: Default shader backend found: glsl.
[INFO] [Shader driver]: Using GLSL shader backend.
[INFO] [GLSL]: Checking GLSL shader support ...
[WARN] [GL]: Stock GLSL shaders will be used.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] Setting up menu pipeline shaders for XMB ... 
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] Resetting shader to defaults ... 
[INFO] [GL]: Using 4 textures.
[INFO] [GL]: Loaded 1 program(s).
[INFO] [GL]: Using GL_RGB565 for texture uploads.
[INFO] [Joypad]: Found joypad driver: "udev".
[INFO] [Font]: Using font rendering backend: freetype.
[INFO] [X11]: Suspending screensaver (X11, xdg-screensaver).
[INFO] [Video]: Found display server: x11
[INFO] [PulseAudio]: Requested 24576 bytes buffer, got 18432.
[INFO] [Menu]: Found menu display driver: "menu_display_gl".
[INFO] [Font]: Using font rendering backend: freetype.
[INFO] [Font]: Using font rendering backend: freetype.
[INFO] [LED]: LED driver = 'null' 0x86ad20
[INFO] SRAM will not be saved.
[INFO] Loading history file: [/home/user/.config/retroarch/content_history.lpl].
[INFO] Loading history file: [/home/user/.config/retroarch/content_favorites.lpl].
[INFO] Loading history file: [/home/user/.config/retroarch/content_music_history.lpl].
[INFO] Loading history file: [/home/user/.config/retroarch/content_video_history.lpl].
[INFO] Loading history file: [/home/user/.config/retroarch/content_image_history.lpl].
[INFO] [GL]: VSync => on
[INFO] [GLX]: glXSwapIntervalEXT(1)
[INFO] [PulseAudio]: Unpausing.
[INFO] [GL]: VSync => on
[INFO] [GLX]: glXSwapIntervalEXT(1)
[INFO] [PulseAudio]: Pausing.

what happens is that when I launch retro arch, it opens a new black window with the name “broken” hangs for a few seconds and closes.

November 9, 2020 at 9:27 am #44651

Member

Xecure

Helpful

PPAs are for Ubuntu, not Debian.

Purge all retroarch packages, remove the ppa, update package list (sudo apt update) and install retroarch normally
sudo apt install retroarch

Now, back to the probable main problem. Your title states:

retroarch doesn’t launch on antiX 19.3 i386 core

Are you using a Window Manager or Desktop Environment? Which one? What did you install in your system so that it has a GUI environment?

I tested on antiX 19.3 i386 base and retroarch from the debian repos installs and works properly.
Give us more info on how you set up your system.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

November 9, 2020 at 10:31 am #44654

Member

Raudonkepuris

Helpful

I did everything you said and the only difference in logs was this:

[user@antix ~]$ diff retroarchlog retroarchlognew
68c68
< [INFO] [LED]: LED driver = 'null' 0x86ad20
---
> [INFO] [LED]: LED driver = 'null' 0x89fd20

I’m using window manger. It’s dwm. To get it working I installed xorg package, just like it’s shown in the debian wiki, I also installed xserver-xorg-video-openchrome because it’s the driver for my gpu (VN800) and then I compiled everything (dwm, dwmblocks, dmenu) from my github .

This reply was modified 2 years, 6 months ago by Raudonkepuris.

November 9, 2020 at 10:53 am #44656

Member

Xecure

Helpful

I will try this afternoon to set up from antiX core with a minimal WM (JWM) on a VM, and see if I get the same output.
Here is a VM with antiX 19.3 i386 base running retroarch:

Just to make sure, close retroarch, remove ~/.config/retroarch folder and launch it again.

It is possible that the problem is your hardware, but I will not jump to conclusions yet. Share with us inxi -Fxz

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

November 9, 2020 at 11:05 am #44659

Member

Raudonkepuris

Helpful

Deleted the config – same thing.

here’s the inxi output:

System:    Host: antix Kernel: 4.9.212-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: dwm 6.1 
           Distro: antiX-19.2_386-core Hannie Schaft 27 March 2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: FUJITSU SIEMENS product: AMILO PRO V2055 v: 20 serial: <filter> 
           Mobo: FUJITSU SIEMENS model: AMILO PRO V2055 v: 0.3A serial: <filter> BIOS: FUJITSU SIEMENS v: 1.0C-2A16-8A20 
           date: 07/21/2006 
Battery:   ID-1: BAT0 charge: 27.6 Wh condition: 27.6/48.8 Wh (57%) model: SMP SMP-LMXXSS6 status: Full 
CPU:       Topology: Single Core model: Intel Celeron M 410 bits: 32 type: MCP arch: M Yonah rev: 8 L2 cache: 1024 KiB 
           flags: nx pae sse sse2 sse3 bogomips: 2925 
           Speed: 1463 MHz min/max: N/A Core speed (MHz): 1: 1463 
Graphics:  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] vendor: Fujitsu Solutions driver: N/A 
           bus ID: 01:00.0 
           Display: server: X.Org 1.20.4 driver: openchrome unloaded: fbdev,modesetting,vesa resolution: 1280x800~60Hz 
           Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:     Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Fujitsu Solutions driver: snd_via82xx v: kernel bus ID: 00:11.5 
           Sound Server: ALSA v: k4.9.212-antix.1-486-smp 
Network:   Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN vendor: Gemtek driver: b43-pci-bridge 
           v: N/A bus ID: 00:06.0 
           Device-2: VIA VT6102/VT6103 [Rhine-II] vendor: Fujitsu Solutions driver: via-rhine v: N/A port: 2000 
           bus ID: 00:12.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IF-ID-1: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 55.89 GiB used: 9.61 GiB (17.2%) 
           ID-1: /dev/sda vendor: Fujitsu model: MHV2060BH size: 55.89 GiB 
Partition: ID-1: / size: 52.76 GiB used: 9.61 GiB (18.2%) fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   Missing: Required tool sensors not installed. Check --recommends 
Info:      Processes: 112 Uptime: 56m Memory: 1.41 GiB used: 96.6 MiB (6.7%) Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 
           Shell: zsh v: 5.7.1 inxi: 3.0.36

I just noticed that it’s not 19.3 but 19.2, I’ll go ahead and install 19.3 on my machine and report results after.

November 9, 2020 at 11:11 am #44660

Member

Xecure

Helpful

Raudonkepuris wrote:

I just noticed that it’s not 19.3 but 19.2

Not much difference, as 19.2 updates to 19.3 after normal upgrade (it just doesn’t show in inxi).

Give me a bit of time and I will build a 32 bits core with JWM on a VM and install retroarch. If I still don’t get the error, it may be related to the hardware, but it is also possible that a missing library is the culprit.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

November 9, 2020 at 12:31 pm #44669

Member

Xecure

Helpful

Just installed antiX 19.3 i386 core in a VM.
Packages added: xorg, jwm, arandr and retroarch.
Result:

Worked for me (the only error is “xdg-screensaver: not found”), but it launched for me.
I will not try to compile dwm and use it as I have no experience using tiling window managers.
Or there is a missing package I am not aware of or you need a openGL renderer for your VIA graphics openchrome driver. Install mesa-utils to see openGL renderer info in inxi -Gxxx

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

November 9, 2020 at 4:48 pm #44695

Member

Raudonkepuris

Helpful

I installed antix-19.2.1-base on that laptop (also fully updated the system) and retroarch didn’t work (packages arandr and mesa-utils were installed), however on lubuntu (I didn’t check the exact version) it worked out of the box. I’ll install 19.3-core and try again, if I fix retroarch, I’ll update this thread.

November 9, 2020 at 4:57 pm #44696

Member

Xecure

Helpful

When using lubuntu on the same laptop, please check the output of
inxi -Gxxx
To compare if lubuntu was using the vesa driver or the openchrome driver. Maybe we can find a clue there.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

November 10, 2020 at 7:58 am #44727

Member

Raudonkepuris

Helpful

sorry for the late reply, lubuntu install kept crashing yesterday. here’s inxi -Gxxx output and retroarch running on that machine

EDIT: also I just remembered, on my core install I edited something in my grub to let that laptop run at it’s native resolution, because xrandr couldn’t detect the normal one.

This reply was modified 2 years, 6 months ago by Raudonkepuris.
This reply was modified 2 years, 6 months ago by Raudonkepuris.
This reply was modified 2 years, 6 months ago by Raudonkepuris.

November 10, 2020 at 8:40 am #44731

Member

Xecure

Helpful

antiX 19 system:

Raudonkepuris wrote:

Graphics:  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] vendor: Fujitsu Solutions driver: N/A 
           bus ID: 01:00.0 
           Display: server: X.Org 1.20.4 driver: openchrome unloaded: fbdev,modesetting,vesa resolution: 1280x800~60Hz

Lubuntu XX system:

Raudonkepuris wrote:

Graphics:  Card: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro]
           bus-ID: 01:00.0 chip-ID: 1106:3344
           Display Server: x11 (X.Org 1.19.6 )
           drivers: fbdev (unloaded: modesetting,vesa)
           Resolution: 640x480@73.00hz

So the main differences are:
– Lubuntu isn’t using the openchrome xorg driver, but fbdev instead. This is the most likely reason to your problems.
– Xorg version (newer in antiX, may be related to the problem).
– kernel version (not displayed in Lubuntu, but it probably is a 4.19 or newer kernel, vs 4.9 antiX kernel, which is usually more compatible with older machines).

This reminds me of the Zoom rendering problem for old nvidia graphic card using nouveau vs vesa.
On the installed system, using the nouveau driver, the Zoom app doesn’t render properly.
When the user boots an antiX live USB using safe mode, using the vesa driver, they can launch Zoom.

Openchrome xorg driver has given trouble to a few other users with the recent xorg updates. marcelocripe had to use a very old xorg driver on antiX 16.3 to be able to use a propperly his system with the same 8or similar to yours) VIA chip.
If possible, try to boot without the openchrome driver to force the use of the vesa xorg driver. If needed, try to re-install again without installing the xserver-xorg-video-openchrome package and see if you can force the vesa driver to be used instead.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

November 10, 2020 at 9:40 am #44736

Member

Raudonkepuris

Helpful

– kernel version (not displayed in Lubuntu, but it probably is a 4.19 or newer kernel, vs 4.9 antiX kernel, which is usually more compatible with older machines

the lubuntu version I installed is on 4.15.0-122-generic.

I’ll try everything you mention and will update the thread.

This reply was modified 2 years, 6 months ago by Raudonkepuris.

Author

Posts

Viewing 12 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.

Cookie	Duration	Description
cookielawinfo-checkbox-analytics	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional	11 months	The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy	11 months	The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.