LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   DOOM Eternal won't launch - amdgpu driver won't run Vulkan (https://www.linuxquestions.org/questions/slackware-14/doom-eternal-wont-launch-amdgpu-driver-wont-run-vulkan-4175671697/)

1337_powerslacker 03-20-2020 10:23 AM

DOOM Eternal won't launch - amdgpu driver won't run Vulkan
 
I downloaded DOOM Eternal last night after it "unlocked" on Steam. However, I have been unable to launch the game. A quick check on Google indicates that OpenGL is not an option as with DOOM 2016; Vulkan is the only game in town.

I Googled this problem and came across this thread. However, after implementing both dive's and bassmadrigal's suggestions, there has been no change. DOOM Eternal still won't launch. I am at my wits' end. I would appreciate any suggestions. Thanks!

orbea 03-20-2020 10:47 AM

Is this current?

What video card do you have?

Does vkcube work?

Are you using the free radv driver in mesa?

1337_powerslacker 03-20-2020 10:50 AM

Quote:

Originally Posted by orbea (Post 6102622)
Is this current?

What video card do you have?

Does vkcube work?

Are you using the free radv driver in mesa?

- Yes, I run -current.
- I have a Radeon RX 580 w/ 8GB of VRAM
- vkcube works
- I am using the amdgpu driver for my video card.

orbea 03-20-2020 11:00 AM

amdgpu refers to the kernel code, what I am asking is what userspace driver for vulkan you are using. By default this should be radv which is included in mesa. The opengl driver would be radeonsi.

If vkcube works then it must be something related to the game or wine. How are you launching the game? Can you share the stdout from trying to run the game?

1337_powerslacker 03-20-2020 11:11 AM

Quote:

Originally Posted by orbea (Post 6102628)
amdgpu refers to the kernel code, what I am asking is what userspace driver for vulkan you are using. By default this should be radv which is included in mesa. The opengl driver would be radeonsi.

If vkcube works then it must be something related to the game or wine. How are you launching the game? Can you share the stdout from trying to run the game?

I'm going to be embarrassed by my ignorance, but how do I figure out the userspace driver for vulkan?

As far as DOOM Eternal goes, I'm launching it through Steam, as it was downloaded via the Steam client.

orbea 03-20-2020 11:37 AM

This should print your vulkan driver info I think.

Code:

vulkaninfo | grep -i devicename
I don't know enough about steam to help, but ideally looking at exactly why its failing might help find a relevant solution.

bassmadrigal 03-20-2020 11:44 AM

Quote:

Originally Posted by 1337_powerslacker (Post 6102633)
As far as DOOM Eternal goes, I'm launching it through Steam, as it was downloaded via the Steam client.

See if launching steam itself through the command line will cause launches of games within steam to output to the console as well. If not, you could try and figure out how to launch Doom manually. Have a look in ~/.steam/steam/steamapps/common/ for a folder that has Doom in the name (hopefully) and then check the contents of that folder for a binary that you might be able to run manually.

1337_powerslacker 03-20-2020 11:44 AM

Googling some more, I came across a GitHub repo for AMDVLK. I'm building it now; what seems to be the issue is that the file amdvlk64.so is missing from /usr/lib64. Without this file, it seems Vulkan apps won't launch.

I came across this thread also, and it indicates that a variable needs to be set for Vulkan apps to run as well.

We shall see if this works. :D

enorbet 03-20-2020 11:51 AM

This question could be embarrassingly fundamental but are you opted in to Stem Proton beta program? It's currently on v 5.0.1 iirc but versions are easily switched.

szo 03-20-2020 11:53 AM

Have you seen this?
https://www.protondb.com/app/782330

Some usefull information can be found in the comments section on this page:
https://www.gamingonlinux.com/articl...ton-50-5.16255

So it seems Doom Eternal isn't working at all under Steam/Wine/Proton unfortunately .... yet :)

1337_powerslacker 03-20-2020 11:53 AM

Quote:

Originally Posted by enorbet (Post 6102647)
This question could be embarrassingly fundamental but are you opted in to Stem Proton beta program? It's currently on v 5.0.1 iirc but versions are easily switched.

I checked the Steam Play settings and the Proton version is 5.0-4. I did opt-in some time ago for DOOM 2016; that's how I got DOOM to run in the first place. :D

enorbet 03-20-2020 12:08 PM

I looked around a bit and it surely seems that Steam is having a lot of issues with that game even on Windows with either native DX or Vulkan and especially with AMD graphics though some nVidia users complain, too. I see lot's of dubious fixes but I am reminded of something a doctor once told me "You know how you can tell there is no cure for a condition?.... when there's lots of them."

Rather than try a bunch of funky fixes like deleting "DOOMconfig.local" as some have (do Windows guys still not just rename?) I'd wait for Steam to release an official statement of a proper fix. They are usually pretty johnny-on-the-spot.

1337_powerslacker 03-20-2020 12:11 PM

Well, there is one good bit of news to come out of all this, but not related to DOOM Eternal, unfortunately. After building the AMDVLK driver package and copying the files to the appropriate locations, DOOM 2016 now uses the Vulkan API mode flawlessly. I'll surely take that as a sign of progress (in the Vulkan space at least!)

1337_powerslacker 03-20-2020 02:43 PM

AMDGPU driver now running Vulkan apps - DOOM Eternal still won't launch
 
I'm going to mark this thread as [SOLVED], even though the main thrust of this thread, DOOM Eternal still won't launch, we now know the reason; it isn't cooperating for a good number of people.

As enorbet said, it will probably be prudent to wait on Steam to issue a fix for the issue.

I'll update this thread once I see a fix has been issued.

dugan 03-20-2020 04:05 PM

The latest news seems to be that DOOM Eternal uses Vulkan extensions that aren't yet supported by Proton. Or at least that's my understanding.

Just keep tracking this issue:

https://github.com/ValveSoftware/Proton/issues/3654


All times are GMT -5. The time now is 07:36 PM.