mesa+mesa-amber coexistence

kokoko3k · 2022-04-21 14:47:33

Hi there.
I'm using an haswell cpu with the integrated igp and an RX5600XT via prime.
The new "crocus" mesa drivers do not perform very well with the igp (shaders runs very slow), so i have installed mesa-amber and set __GLX_VENDOR_LIBRARY_NAME=amber to use it (https://bbs.archlinux.org/viewtopic.php … 5#p2031815).
Does this mean i'll use older drivers for the RX5600XT too?

Last edited by kokoko3k (2022-04-22 11:36:19)

V1del · 2022-04-21 15:23:31

Yes, mesa-amber is basically a build of the 21.3.8 series release as far as I know, so at the minimum your radeonsi will be from an older state as well. But this shouldn't have an effect on your vulkan support FWIW, as I'm assuming you can still use the latest radv regardless.

Last edited by V1del (2022-04-21 15:26:54)

dogknowsnx · 2022-04-21 15:30:53

This is how the drivers got built,
mesa:

    -D gallium-drivers=r300,r600,radeonsi,nouveau,virgl,svga,swrast,iris,crocus,zink,d3d12 \
    -D vulkan-drivers=amd,intel,swrast \

respectively,
mesa-amber:

    -D dri-drivers=i915,i965,r100,r200,nouveau \
    -D gallium-drivers=swrast \
    -D vulkan-drivers=auto \

Sources:
https://github.com/archlinux/svntogit-p … k/PKGBUILD
https://github.com/archlinux/svntogit-p … k/PKGBUILD

Last edited by dogknowsnx (2022-04-21 15:33:44)

V1del · 2022-04-21 15:34:46

hmm right, do we even get support on the amdgpu that way? sounds like this would be inherently crippled in that case

kokoko3k · 2022-04-21 15:40:32

Ok, i'm even more confused now.
Aren't radv vulkan drivers == extra/vulkan-radeon?

dogknowsnx · 2022-04-21 15:46:51

kokoko3k wrote:

Ok, i'm even more confused now.
Aren't radv vulkan drivers == extra/vulkan-radeon?

Yes, 'mesa' and 'vulkan-radeon' are spilt packages from the same PKGBUILD - not sure which driver(s) your GPU(s) need/use, though...

Last edited by dogknowsnx (2022-04-21 15:56:57)

kokoko3k · 2022-04-21 16:30:26

In the worst case, maybe one could still build mesa with " -D dri-drivers=i915" (?)

dogknowsnx · 2022-04-21 16:39:55

You might as well build

-D gallium-drivers=i915

(tested and working here (old Intel Atom) with the caveat that the cursor is hidden, which can be worked around - this is well beyond my own comfort zone and I'm only mentioning it bc I've tried it myself...)

kokoko3k · 2022-04-22 11:34:07

Ok, i think the less troublesome way to use them both is to have them both, both the packages:

> cat amber.sh

#!/bin/bash 

# Install/upgrade a copy of concurrent mesa-amber via pacman in a user-selected root with another pacman db
# run opengl apps with it.

# Use:
# me.sh upgrade           # upgrade mesa-amber
# me.sh run command<args> # run command with mesa-amber

MESA_AMBER_DIR="$HOME/.local/share/mesa-amber/" #Where to install mesa-amber
OVERRIDE=i965 #for Haswell

if [ "$1" == "upgrade" ] ; then
		mkdir -p "$MESA_AMBER_DIR"
		sudo pacman -v -Sy --nodeps --nodeps --cachedir "$MESA_AMBER_DIR" --root "$MESA_AMBER_DIR" --dbpath "$MESA_AMBER_DIR" mesa-amber 
	elif [ "$1" == "run" ] ; then
			export __GLX_VENDOR_LIBRARY_NAME=amber
				# https://bugs.archlinux.org/task/74364 and 
				# https://bbs.archlinux.org/viewtopic.php?pid=2031815#p2031815
			export LIBGL_DRIVERS_PATH="$MESA_AMBER_DIR/usr/lib/dri/"
			export MESA_LOADER_DRIVER_OVERRIDE=$OVERRIDE
			shift
			"$@"	
	else
		echo -e "\nUse:\n$0 upgrade|run command"
fi

So that if you run:
> amber.sh upgrade
It will download the latest mesa-amber package in a local directory via pacman

>amber.sh run command
Will start the provided command with mesa-amber and with the overridden driver.

...I'm not sure if i'd better use mesa by default or amber by default, but the script could be easilly "switched".

Do you have any suggestion/hint?
I'm not really happy to have to use use sudo to use pacman, even if the target is a local user owned directory, maybe there is another way equally straightforward?
Never used pacman that way before.

Last edited by kokoko3k (2022-04-22 12:16:25)

Lone_Wolf · 2022-04-23 13:56:13

kokoko3k wrote:

In the worst case, maybe one could still build mesa with " -D dri-drivers=i915" (?)

Only possible by building mesa 21.3.x . All code related to mesa classic drivers (including ALL dri drivers) has been removed from mesa 22 .
see https://gitlab.freedesktop.org/mesa/mes … ests/10153

kokoko3k wrote:

...I'm not sure if i'd better use mesa by default or amber by default, but the script could be easilly "switched".

The best option would probably be to build mesa-amber so it can coexist with mesa .

If someone wants to try that, start with a mesa-amber version that only builds opengl .
Once it works for that, other things like egl could be looked at.

Arch Linux

#1 2022-04-21 14:47:33

mesa+mesa-amber coexistence

#2 2022-04-21 15:23:31

Re: mesa+mesa-amber coexistence

#3 2022-04-21 15:30:53

Re: mesa+mesa-amber coexistence

#4 2022-04-21 15:34:46

Re: mesa+mesa-amber coexistence

#5 2022-04-21 15:40:32

Re: mesa+mesa-amber coexistence

#6 2022-04-21 15:46:51

Re: mesa+mesa-amber coexistence

#7 2022-04-21 16:30:26

Re: mesa+mesa-amber coexistence

#8 2022-04-21 16:39:55

Re: mesa+mesa-amber coexistence

#9 2022-04-22 11:34:07

Re: mesa+mesa-amber coexistence

#10 2022-04-23 13:56:13

Re: mesa+mesa-amber coexistence

Board footer