Package Details: amdonly-gaming-vulkan-mesa-layers-git 24.1.0_devel.184875.893780b3625.d41d8cd98f00b204e9800998ecf8427e-1

Git Clone URL: (read-only, click to copy)
Package Base: mesa-amdonly-gaming-git
Description: Mesa's Vulkan layers
Upstream URL:
Licenses: custom
Conflicts: vulkan-mesa-layer, vulkan-mesa-layers
Provides: vulkan-mesa-layers
Replaces: vulkan-mesa-layer, vulkan-mesa-layers
Submitter: NeroReflex
Maintainer: NeroReflex
Last Packager: NeroReflex
Votes: 13
Popularity: 2.36
First Submitted: 2023-02-27 22:38 (UTC)
Last Updated: 2024-02-17 21:10 (UTC)

Latest Comments

1 2 3 4 Next › Last »

TeaHistoria commented on 2024-03-12 16:15 (UTC)

After I updated this package to the latest version. I can't run Apex Legends stuck on blackscreen loading. one week before the update from the current comment date, the game runs very smoothly

jacekk90 commented on 2024-03-08 18:17 (UTC) (edited on 2024-03-08 18:18 (UTC) by jacekk90)

@NeroReflex it was something with redeonsi and today after kernel update works correctly...

When I run Shotcut i was log in terminal (I use AppImage) more than I wrote here and Googled info was - radeonsi Now I have not this terminal output... I wrote this on Shotcut Facebook page but it was removed becouse Shotcut problem it was not too... i don't know how is it in english :/

2 days ago on EndenavourOS not kernel or mesa update...

NeroReflex commented on 2024-03-07 18:43 (UTC) (edited on 2024-03-07 21:56 (UTC) by NeroReflex)

@jacekk90 I don't have this error and my hyprland set-up works just fine so I might need a few more insights on how your system is configured. And beside I don't think it's correct that swrast gets used for rendering so I think there's something strange there.

Edit. now I have it. Well I don't think there's something we can do except waiting for upstream mesa to fix. this is a -git package of in-development software so brakages are quite normal.

jacekk90 commented on 2024-03-07 18:12 (UTC)

MESA-LOADER: failed to open swrast: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri) failed to load driver: swrast

update and so, so huge error that I can't login. OpenShot or Shotcut memory guard

Grimish commented on 2024-02-21 03:38 (UTC)

I have to say - I really appreciate this package. I see alot of flakey comments but when I compare it to other non-standard builds, this one makes all the difference and for sure is the best thus far on an all AMD hardware machine. Hope you can continue to maintain this.

NeroReflex commented on 2024-02-16 01:03 (UTC)

I will surely do. As of now my time is limited, but it's on my schedule. d3d12 is enabled because (idk if this is still the case) disabling it broke a few games a few months ago. Crocus has been removed. I think I will remove vortio too since using that is a very edge-case scenario, but totally doable on AMD hardware. Main source of differencies are brakages on the past for the lib32 version. Sometimes it doesn't compile and when they fix it I don't know they did or don't have the time to revert workaround changes and ends up forgetting. You are right in your feelings, just keep in mind that mesa sometimes break and this is a -git package. I try to solve issues as soon as I can, but that introduces inconsistencies between regular version and lib32 version

DexterHaxxor commented on 2024-02-15 19:32 (UTC)

No idea why -D intel-clc=enabled is in your build params and no idea why d3d12 and crocus are in your Gallium driver list. Could you please pay a bit more attention to your PKGBUILD? I feel like the package name doesn't represent what's actually being built. Can you please take your time and run through all the config options and consolidate the regular and lib32- package options so that they are identical (there are plenty of differences, like the video codecs)?

Lone_Wolf commented on 2024-02-14 15:13 (UTC)

Mesa commit b52e25d3 breaks intel iris & anv build UNLESS OpenCL support is present.

Incase you don't need those drivers, a temporary workaround is to disable them.

NeroReflex commented on 2024-02-07 00:56 (UTC)

@GrabbenD I am sorry but in my archlinux install attempting to install said packages does not try to bring in official mesa: I think what you see is related to your distro. I am sorry but I can't do anything more than this for you: I already flagged mesa to be proveded by my package.

GrabbenD commented on 2024-02-06 12:06 (UTC) (edited on 2024-02-06 12:06 (UTC) by GrabbenD)

@NeroReflex This can also be reproduced with paru --sync aur/wine-git which is maintained by a different guy.

It seems like the culprit comes from listing mesa packages under makedepends in PKGBUILD