Every article tag can be clicked to get a list of all articles in that category. Every article tag also has an RSS feed! You can customize an RSS feed too!
We do often include affiliate links to earn us some pennies. See more here.

Metro Exodus for Linux to run better on AMD GPUs soon with a Mesa fix now merged

By -
Last updated: 20 Apr 2021 at 11:50 am UTC

The new Linux port of Metro Exodus sadly came with a rough launch but for AMD GPU owners it's set to get more playable, with a fix in the Mesa RADV driver now merged. I've been following this quite closely, first posting about it on Twitter yesterday after being told about it.

What's the issue then? Well, this Vulkan port caused a lot of RAM to be eaten from a leak, it got real hungry really fast. A bug report was made with Mesa on April 16, and as of April 19 the fix was merged in - a pretty amazing turn around and shows again the power of open source drivers for solving issues.

Since it's merged it will for sure be in the Mesa 21.2 release, and should also be backported to the next stable update to the current Mesa drivers - hopefully the upcoming Mesa 21.1 release too which would be ideal.

For NVIDIA users, making sure your drivers are up to date is a good idea. My own NVIDIA system seemed more stable with Metro Exodus on the latest 465.24.02 release. There's still crashes in the desert area, but after plenty of research this appears to be very common on even Windows. Adjusting graphical settings down to medium for a bit gets around the areas to cause the crashes.

Article taken from GamingOnLinux.com.
26 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. You can also follow my personal adventures on Bluesky.
See more from me
The comments on this article are closed.
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
48 comments Subscribe
Page: «3/3
  Go to:

Anorelsan 26 Jun 2021
Hello I just bought this game and have an instant crash on startup, not even showing anything. I know that my system is old (ryzen 1800x, r290, 32GB RAM), but do you know if it runs on mesa 20 or i must update to mesa 21 to run it? It works under wayland?

ed: digging into steam forums seems that it can run under mesa 20 (with the memory leak) and wayland, but no luck. Maybe will be my first refund. :(

Did you try from terminal? I was shown a library missing, some libibus or something.

I have libibus instaled, no errors from the terminal. An error logged on dmesg:
 
 1416.623833] MetroExodus[6449]: segfault at 0 ip 0000000000000000 sp 00007ffff2ece758 error 14 in MetroExodus[400000+8000]
[ 1416.623839] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.


On the steam forums someone says that maybe is for an unsuported cpu. It seems strange to me, I have a Ryzen 1800X, a little old but that old? I will dig a little more. I want to play it, enjoyed the first and second, but possibly will be in the future when I change my pc.


Last edited by Anorelsan on 26 Jun 2021 at 9:51 pm UTC
Eike 27 Jun 2021
  • Supporter Plus
On the steam forums someone says that maybe is for an unsuported cpu. It seems strange to me, I have a Ryzen 1800X, a little old but that old? I will dig a little more. I want to play it, enjoyed the first and second, but possibly will be in the future when I change my pc.

I answered over there (as Zyro). I think playing around with kernel (downgrade?) or mesa version (upgrade?) should be able to solve it.
Anorelsan 27 Jun 2021
On the steam forums someone says that maybe is for an unsuported cpu. It seems strange to me, I have a Ryzen 1800X, a little old but that old? I will dig a little more. I want to play it, enjoyed the first and second, but possibly will be in the future when I change my pc.

I answered over there (as Zyro). I think playing around with kernel (downgrade?) or mesa version (upgrade?) should be able to solve it.

Thank you Eike! I use Debian unstable but right now is frozen. I will build mesa from code or wait until frozen is over that it will be soon. When I test it I will report here :)
Lanz 28 Jun 2021
The crashes persist in the desert area for me on a Radeon 6800 XT as of June 28 2021.
CFWhitman 29 Jun 2021
The crashes persist in the desert area for me on a Radeon 6800 XT as of June 28 2021.

What versions of the kernel and Mesa?
Swanny 29 Jun 2021
The Caspian Sea (desert) level is known to be very crashy unless you temporarily reduce detail to medium. This is the same under both Linux and Windows for both AMD and NVidia so less likely to be a Mesa issue but rather an (unfixed) game issue.


Last edited by Swanny on 29 Jun 2021 at 3:13 pm UTC
Lanz 3 Jul 2021
The crashes persist in the desert area for me on a Radeon 6800 XT as of June 28 2021.

What versions of the kernel and Mesa?

Kernel 5.12.14-arch1-1
Mesa 21.1.3-1
CFWhitman 7 Jul 2021
The crashes persist in the desert area for me on a Radeon 6800 XT as of June 28 2021.

What versions of the kernel and Mesa?

Kernel 5.12.14-arch1-1
Mesa 21.1.3-1

Yes, those versions should be good. This seems most likely the issue Swanny mentioned above that is present on both the Linux and Windows versions of the game. You end up having to reduce the detail because the game can't handle it rather than because your hardware/graphics stack can't handle it.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.