Arch Linux

Mechanicus

Member

Registered: 2025-01-13

Posts: 16

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

You have done a serious partial update, and your system is in a completely unsupported and unsupportable state.

I'll point you to https://bbs.archlinux.org/viewtopic.php … 0#p2219910 for the right way to handle this, downgrading a bunch of things is NOT it.

Isn't it simpler just to switch to mesa-amber for a while? No conflicts, just install mesa-amber and it`ll replace the mesa package.

kclisp

Member

Registered: 2025-01-04

Posts: 26

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

The mesa-git version I used seemed very stable to me, but now I count two freezes during the last few days. That's way better than with other 24.3.x-Versions, but shouldn't happen. Of course, who knows if there is not another problem on my pc teasing me?

The freezes happen out of the blue.  I can hardly move the mouse pointer (very, very slow reaction) but no input is accepted and the keyboard doesn't react at all.

Yes, that's the same behavior that I saw with the original freezes. So trunk probably still has the bug. Can you test with Lone_Wolf's most recent trunk build without patch so that we're consistent with our builds (everyone who wants to help should test this as well)? Because the freezes seem somewhat random, we'll have to test for a lot longer than the expected time for a freeze in order to be confident in the build's stability.

I'll continue testing with the patched version to help isolate the freeze cause if I encounter one.

AzraelNewtype

Member

Registered: 2024-12-16

Posts: 1

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

@Mechanicus There might not be any conflicts, but it took about a minute from starting X for my wallpaper to appear, and the rest of my desktop never actually did, so I'm not sure mesa-amber is a viable solution on this hardware (3200g like a couple others).

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,253

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

You have done a serious partial update, and your system is in a completely unsupported and unsupportable state.

I'll point you to https://bbs.archlinux.org/viewtopic.php … 0#p2219910 for the right way to handle this, downgrading a bunch of things is NOT it.

Isn't it simpler just to switch to mesa-amber for a while? No conflicts, just install mesa-amber and it`ll replace the mesa package.

Do you know where hardware support for the radeon non-gallium driver stopped? I don't. If your card is newer, that would just switch you to software rendering, which isn't a good option.

orbit-oc

Member

Registered: 2024-12-15

Posts: 42

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

After what @bernd_b recently said, I can understand @kclisp's suggestion to test the mesa-test-git 25.0.0 without the patch again, as the situation has now become even more confusing.

Even without @kclisp's suggestion, I had already considered this.
In post #156 I had also decided to use this test-git after testing the overdue release 24.3.4, *also* to make sure whether it works or not.

Maybe I will actually do this beforehand. It also depends on whether 24.3.4 is released in the next few hours or not...

by the way: mesa 24.3.3-2 is running almost the best for me so far. It has only crashed once up to now...

Last edited by orbit-oc (Yesterday 23:09:20)

pacmancrashedagain

Member

Registered: 2024-12-14

Posts: 12

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

by the way: mesa 24.3.3-2 is running almost the best for me so far. It has only crashed once up to now...

Sorry orbit-oc, i've lost track with all the different versions and patches going around, this is the version from the repos without any modifications at all?

orbit-oc

Member

Registered: 2024-12-15

Posts: 42

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

@pacmancrashedagain

Yes, I mean the current version of the official repository...

NuSkool

Member

Registered: 2015-03-23

Posts: 173

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

Unfortunately, I'm lost with troubleshooting at this point. Fortunately seems there are more knowledgeable people here than myself testing and reporting results...

It's also looking like a fix could be quite a while down the road. That in mind I rolled up my sleeves and rebuild the repo version of mesa against the current packages.
I'm running it now and it passed the 'glxinfo -B' and 'vainfo' tests.

In case others may find this useful or would provide feedback if I obviously f##ked up somewhere, I'll provide the build process I used.
It took about 20 min to build on my system.

git clone https://gitlab.archlinux.org/archlinux/packaging/packages/mesa.git

Rename: PKGBUILD-bu and .SRCINFO-bu

Used my git-rollback script to make this selection:

commit 825be1410117ed165a6eee7a11e3a3e3cce2ae4b
Author: Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Date:   Wed Nov 13 18:25:53 2024 +0100

    1:24.2.7-1: Unsplit vdpau/vaapi drivers
    
    They are part of libgallium and only symlinks remain.

.SRCINFO
PKGBUILD

Recreate files needed:

$ git cat-file -p 825be1410117ed165a6eee7a11e3a3e3cce2ae4b:./.SRCINFO > .SRCINFO
$ git cat-file -p 825be1410117ed165a6eee7a11e3a3e3cce2ae4b:./PKGBUILD > PKGBUILD

Verify PKGBUILD version '24.2.7' and edit: 'pkgrel=2' to differentiate it from my cached version mesa 1:24.2.7-1

Use a script to fetch a PGP key:

$ aurt -pgp 8D8E31AFC32428A6

Used devtools script to clean chroot build the package.

$ pkgctl build

And the build output: http://0x0.st/8HrS.txt

Would it be correct to assume a rebuild required whenever libva updates? Anything else I should be aware of?

EDIT:

Any advise or info on the  soname warnings in the output?
Would symlinks be a possible bandaid for whatever programs/packages may need them?

==> Running checkpkg
  -> Checking packages
                                         >    usr/lib/bellagio/
                                         >    usr/lib/bellagio/libomx_mesa.so
usr/lib/gbm/                                     <
usr/lib/gbm/dri_gbm.so                                 <
usr/lib/libgallium-24.3.3-arch1.2.so                         |    usr/lib/libgallium-24.2.7-arch1.2.so
==> WARNING: Sonames differ in mesa!
dri_gbm.so=dri_gbm.so-64                      <
libgallium-24.3.3-arch1.2.so=libgallium-24.3.3-arch1.2.so-64  |    libgallium-24.2.7-arch1.2.so=libgallium-24.2.7-arch1.2.so-64
                                  >    libomx_mesa.so=libomx_mesa.so-64
==> No soname differences for opencl-clover-mesa.
==> No soname differences for opencl-rusticl-mesa.
==> No soname differences for vulkan-intel.
usr/bin/mesa-screenshot-control.py                         <
usr/lib/libVkLayer_MESA_screenshot.so                         <
usr/share/vulkan/explicit_layer.d/VkLayer_MESA_screenshot.json             <
==> WARNING: Sonames differ in vulkan-mesa-layers!
libVkLayer_MESA_screenshot.so=libVkLayer_MESA_screenshot.so-6 <
==> No soname differences for vulkan-nouveau.
==> No soname differences for vulkan-radeon.
==> No soname differences for vulkan-swrast.
==> No soname differences for vulkan-virtio.
usr/share/doc/mesa/relnotes/24.1.5.html                         <
usr/share/doc/mesa/relnotes/24.1.6.html                         <
usr/share/doc/mesa/relnotes/24.1.7.html                         <
usr/share/doc/mesa/relnotes/24.3.0.html                         |    usr/share/doc/mesa/relnotes/24.2.7.html
usr/share/doc/mesa/relnotes/24.3.1.html                         <
usr/share/doc/mesa/relnotes/24.3.2.html                         <
usr/share/doc/mesa/relnotes/24.3.3.html                         <
usr/share/doc/mesa/rust.html                             <
==> No soname differences for mesa-docs.

EDIT:

Any way to search for installed pkgs needing either of the two soname warnings?

Last edited by NuSkool (Today 01:47:58)

SnowF

Member

Registered: Yesterday

Posts: 3

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

[
@Scimmia
No, for a week now everything has been going too well. Previously, when those two mentioned packages were updated, they caused the system to not start, so I returned them to that version that I mentioned.

Really? Tried running rust? clang? postgresql? blender? a whole bunch of other things that are linked to the new lib? You have done a serious partial update, and your system is in a completely unsupported and unsupportable state.

I'll point you to https://bbs.archlinux.org/viewtopic.php … 0#p2219910 for the right way to handle this, downgrading a bunch of things is NOT it.

Yep. I just ran everything you mentioned without problems to check if anything was broken, time will tell, I honestly don't care since I don't use those programs, I just want my PC to work for the basics of editing, games and multimedia. Sorry, I'm new to linux

Last edited by SnowF (Today 01:33:41)