Difficulty running games on AMD SUMO

[Shanalorm]

Good day, everyone.

I run Ubuntu 20.04 Focal Fossa on an AMD A8-3870 apu and AMD SUMO (AMD Radeon HD 6550D IGP) machine, but seem to have little luck with getting games requiring Direct X 11 working through Steam Play.

When pressing play, for a moment, a game seems to be launching, but then shuts down quietly. Notably, I am trying to get SWTOR and Subnautica to work.

The prerequisites as detailed here at (https://github.com/ValveSoftware/Proton/wiki/Requirements) seem to be met, in so far as I can tell. I have pyton3 installed and added to my path. The 'python3 --version' command returns 'Python 3.8.5'. The ppa:kisak/kisak-mesa was added and mesa drivers are installed.

Considering that I am not on Radeon R9 200/300 series, I skipped the elements about blacklisting radeon and adding amdgpu options to amdgpu.conf.

LLVM is behaving properly, for 'llvm-config --version' returns '10.0.0', and the mesa version should be adequate, as 'glxinfo | grep "OpenGL version"' returns '3.1 Mesa 21.1.0-devel'.

In principle, AMD SUMO, using the TeraScale 2 architecture, is not supported by Vulkan 1.0, according to our trusty friend Wikipedia. Yet with the mesa radeon drivers, vulkan seems to be working with LLVM just fine in so far as I can tell.

In the vulkaninfo.txt file, I placed the output of running the 'vulkaninfo' command on my system.
https://drive.google.com/file/d/18njeO4TsWb3XOAxiugWiMNTXJJh1ceI8/view?usp=sharing

In the vulkaninfo.png image, you can see the command line output of vulkaninfo, which throws errors relating to ELFCLASS32.
https://drive.google.com/file/d/1a2JoSUKAjZDvsdrzKelXmBruec1W3PWi/view?usp=sharing

As my game library is on my main disk, right next to steam itself, formatted in ext4, solutions relating to partitioning problems do not apply, and so I do not know where else to look to get these games to work.

Here's the proton logs for attempting to run Subnautica in two cases, the first with just the 'PROTON_LOG=1 %command%' launch option and the second with 'PROTON_USE_WINED3D=1 %command%' launch option.
https://drive.google.com/file/d/1vtFbvO0lDq5h8DxkTSgXk1pUWsfdEJCm/view?usp=sharing
https://drive.google.com/file/d/1jShtRCBBR6s1TfXXI42XxsjxbnVXcel4/view?usp=sharing

Any help, suggestions or advice in my quest for successful starting of games on my rig would be appreciated.

With kind regards,
Shan.

[Marlock]

proton uses DXVK to translate DX9/10/11 into Vulkan, and has the WineD3D fallback

unfortunately your iGPU is indeed too old for having vulkan support on linux, due to being stuck with the legacy driver (RADEON) while vulkan is only available on the modern driver (AMDGPU), so you just have to work with WineD3D

vulkaninfo will fail, no surprise there, but could you confirm if you have the 32-bit arch enabled and OpenGL 32bit mesa lib installed?

sudo dpkg --add-architecture i386
sudo apt update
sudo apt upgrade
sudo apt install libgl1-mesa-dri:i386

[Shanalorm]

Thank you for your assistance!

These commands do not yield new packages to be installed or updated.
So, yes, 32-bit arch is enabled and OpenGL 32bit mesa lib is installed as well.

[Shanalorm]

As per vulkaninfo failing, does it?
Although vulkaninfo throws a couple errors, it follows with regular vulkaninfo output (as shown in vulkaninfo.txt). Am I mistaken in assuming that this means it works?

[Marlock]

i saw the errors and the output... if i'm not mistaken llvmpipe appearing here is a cpu-only implementation of vulkan... it will be crawling slow and unstable and incomplete afaik

[Marlock]

maybe you should try this parameter along WineD3D...
https://github.com/ValveSoftware/Proton/blob/proton_5.0/README.md#runtime-config-options

PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command%

[Shanalorm]

Originally posted by Marlock:

if i'm not mistaken llvmpipe appearing here is a cpu-only implementation of vulkan...

That seems consistent with what I have read about llvmpipe so far myself. Sadness. That does seem to mean vulkan is not going to be helping me.

Originally posted by Marlock:

maybe you should try this parameter along WineD3D...
https://github.com/ValveSoftware/Proton/blob/proton_5.0/README.md#runtime-config-options

PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command%

Will do, and get back to you shortly.

[Shanalorm]

No success yet, sadly.

Using

PROTON_LOG=1 PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command%

as launch options, yields:
https://drive.google.com/file/d/1jZAExomC2-0DbSlH9UPYAtOSBNXM1_TD/view?usp=sharing

PS: any sources on how to interpret these log files would be helpful

[Marlock]

yeah, I'd like some help with those logs myself... I still can't "see the matrix" when they are involved

[Shanalorm]

The one thing I manage to recognize as decisively 'bad mojo' is the following block:
X Error of failed request: GLXBadFBConfig
Major opcode of failed request: 153 (GLX)
Minor opcode of failed request: 0 ()
Serial number of failed request: 383
Current serial number in output stream: 383

[Marlock]

it's a longshot, but i see gameoverlayrenderer.so failing to load over and over again... while failing is expected, this looks excessive... could you disable the overlay in game properties or globally in steam settings?

[Shanalorm]

Even with the steam overlay disabled in global settings (and thus grayed out in game settings, just to check) the log file is riddled with the following error:

ERROR: ld.so: object '/home/penguin/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

Also, the same GLXBadFBConfig error occurs.

[Marlock]

see the "ignored" at the end? it should be ok without that overlay... i'm just puzzled that it keeps trying instead of giving up after a first attempt (and now with the overlay turned off)... in any case, that is probably not the real issue

yeah, did you try to google the GLXBadFBConfig error? looks relevant indeed... FB is probably for Framebuffer but beyond that I'm out of my depth

[Shanalorm]

Originally posted by Marlock:

i'm just puzzled that it keeps trying instead of giving up after a first attempt (and now with the overlay turned off)... in any case, that is probably not the real issue

Considering that it also shows up in the logs for Star Wars Battlefront 2 (Classic,2005) and that game does work, I am inclined to agree.

Originally posted by Marlock:

did you try to google the GLXBadFBConfig error?

I did, but could make heads nor tails from the results.

[x_wing]

You will have a hard time trying to make DX11 games work with your GPU. But for DX9 games, you may want to try this: https://github.com/iXit/wine-nine-standalone

[Shanalorm]

Big news, I got Subnautica to run!

It seems that using the set of drivers in the kisak ppa made it impossible. As soon as I did a 'ppa-purge kisak/kisak-mesa', a whole bunch of packages got downgraded.

Consequently, vulkan is no longer working, not even with llvm.

Subnautica ran, however.
How or why is beyond me, but for now I am just happy.
Suggestions for further diagnosis of the situation are welcome!

Here's the proton log file:
https://drive.google.com/file/d/1JiYe_O9LYO8WskZNdn-4nqPg3m8GMlCB/view?usp=sharing