Use it at your own risk!
This repo is a modified version of che-mesa.
Triggered to be rebuilt every few hours if code update is detected. Is set to follow the official mesa gitlab repo https://gitlab.freedesktop.org/mesa/mesa Built with distro llvm and LTO enabled. In addition to that libdrm updates are provided aswell.
Is this built with VA-API support as before the recent changes?
Yes, VA-API is still included.
You might want to remove “mesa-va-drivers” and “mesa-vdpau-drivers”. Apparently the same legal rules that apply to Fedora apply also to Copr: https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-build-in-copr
It means that the mesa-git Copr could be removed, if I understood it correctly.
You can swap out both with “mesa-va-drivers-freeworld” and “mesa-vdpau-drivers-freeworld”.
( both are included in the RPM Fusion repo “rpmfusion-free-updates-testing” )
Hi, can you add rusticl like rawhide ?
Hey, why does mesa-dri-drivers have a dependency on lm_sensors-libs?
Because GALLIUM_HUD can graph sensors data.
See:
GALLIUM_HUD=help glxgears
for available options.
I use this mesa-git but in last time is problem becouse…
I buy second game - Hogwarts Legacy and on start game is second shaders “working or somethink” CPU usage is high but it is with black screen and never stopt.
so now I need use standard mesa.
YT: mesa 23 2 0 0 3 20230425 10 - YouTube
Cyberpunk 2077 is working well, I do text file for installation and I’m waiting for Hogwarts Legacy support 
My hardware
cpu-x CPU RAM.png - Google Drive
ASUSTeK COMPUTER INC. A88XM-A
16,0 GiB RAM
AMD Athlon™ X4 840 Quad Core × 4
AMD Radeon™ RX 6500 XT (but on highest overclock clocks GPU 2975@1200 VRAM
23.2.0-0.3.20230425.15.e501b31 < NOPE
Does this package provide HW acceleration? Or will I still need to install the freeworld drivers from RPM Fusion?
Have builds stopped working?
Hey OP. Any chance to set up a 23.2.0-git repo?
Emulated RT for RADV has been disabled in 23.3.0-git unexpectedly. 23.2.0-git has functional RADV_PERFTEST=emulate_rt option.
Howdy, it looks like some packages for this repo cannot be installed on Fedora 38:
[SKIPPED] vulkan-loader-devel-1.3.243.0-1.fc38.x86_64.rpm: Already downloaded
[SKIPPED] vulkan-headers-1.3.243.0-2.fc38.noarch.rpm: Already downloaded
error: Verifying a signature using certificate 108E08A840EB2548E6B43856702E7C6094CBA2BC (xxmitsu_mesa-git (None) <xxmitsu#mesa-git@copr.fedorahosted.org>):
1. Certificate 702E7C6094CBA2BC invalid: policy violation
because: No binding signature at time 2023-06-19T11:39:26Z
2. Certificate has no valid binding signature as of the signature's creation time, but is valid now. The certificate has probably been stripped or minimized.
error: Verifying a signature using certificate 108E08A840EB2548E6B43856702E7C6094CBA2BC (xxmitsu_mesa-git (None) <xxmitsu#mesa-git@copr.fedorahosted.org>):
1. Certificate 702E7C6094CBA2BC invalid: policy violation
because: No binding signature at time 2023-06-19T11:39:26Z
2. Certificate has no valid binding signature as of the signature's creation time, but is valid now. The certificate has probably been stripped or minimized.
EDIT: Investigating this further brought me to the conclusion that you should trigger a rebuild for those packages.
Would it be possible for you to fix the issues with this repository’s signing keys?
Hello again, just started running into this issue: https://bugzilla.redhat.com/show_bug.cgi?id=2193335 with these Mesa builds.
For the sake of other users it might be a good idea to highlight this fix for Chromium-based applications: Chromium-based browsers display garbled web pages after Mesa is updated
Cheers.
Is there no mesa-libGLU provided by this copr?
The version of these libs still appears to be the stable version 9.0.3-1.
# rpm -qa | grep mesa |sort
mesa-demos-8.5.0-1.fc38.x86_64
mesa-dri-drivers-24.0.0-0.3.20231101.10.da7e6f3.fc38.i686
mesa-dri-drivers-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-filesystem-24.0.0-0.3.20231101.10.da7e6f3.fc38.i686
mesa-filesystem-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-libEGL-24.0.0-0.3.20231101.10.da7e6f3.fc38.i686
mesa-libEGL-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-libEGL-devel-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-libgbm-24.0.0-0.3.20231101.10.da7e6f3.fc38.i686
mesa-libgbm-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-libGL-24.0.0-0.3.20231101.10.da7e6f3.fc38.i686
mesa-libGL-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-libglapi-24.0.0-0.3.20231101.10.da7e6f3.fc38.i686
mesa-libglapi-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-libGL-devel-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-libGLU-9.0.3-1.fc38.i686
mesa-libGLU-9.0.3-1.fc38.x86_64
mesa-libGLU-devel-9.0.3-1.fc38.x86_64
mesa-libOSMesa-24.0.0-0.3.20231101.10.da7e6f3.fc38.i686
mesa-libOSMesa-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-libxatracker-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-va-drivers-24.0.0-0.3.20231101.10.da7e6f3.fc38.i686
mesa-va-drivers-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-vdpau-drivers-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
mesa-vulkan-drivers-24.0.0-0.3.20231101.10.da7e6f3.fc38.i686
mesa-vulkan-drivers-24.0.0-0.3.20231101.10.da7e6f3.fc38.x86_64
Hi Raman,
mesa-libGLU is a different project. Its source repo is not the same as mesa.
You can check the spec file here. Fedora seems to be already providing the latest available version.
I’m being asked to run crashing code with mesa assertions enabled (-Dbuildtype=debug). Do I need to build mesa myself by modifying the spec file or is there a way I can enable that with this or another copr?
There are few options:
dnf debuginfo-install <package> satisfies your use-case.rpmbuild locally to generate RPMs and install them afterwards with dnf.Thank you. For future note, the linked instructions worked to compile a debug version for testing.
Hi, can you enable d3d12 driver in builds too ?
For some reason, the new NVK driver is not enabled with this build? I thought NVK is enabled by default in mesa by now?