No GPUs found on Linux/Lutris

Technical Support
1

Hi,
I’m on linux mint and using lutris/wine for battle.net and it says ‘GPUs not found’ when starting the d4 beta.
Driver version is nvidia-driver-525, version 525.85.05-0ubuntu0.22.04.1
I upgraded from version 510, but the error remains.
Any ideas?

3 Likes
2

Having the same issue with lutris as well No GPU found

3

having the same issue on steam deck, i think its a linux problem we may need new version of Proton?

4

Howdy!

Note: Linux is not a supported Operating System for Diablo IV. That being said, I did forward this upward for review. I would recommend posting these issues on the Bug report forums. I will allow this thread to stay open if you all want to share troubleshooting.

Thank you!

3 Likes
5

Cannot play the game, i get “no gpu detected”, it might be a general Linux issue at the moment.

6

This thing doesn’t let me post the article link so i will copy paste.
(TL:DR use proton 6.3-8 if you know how to do it)
I use now proton 6.3-8 and it launched, i am in the queue.
(you will get an error that the GPU is not updated but launches after)

How to install Battle.net on Steam Deck and SteamOS

  1. On your Steam Deck, go to desktop mode. Click the Steam button, go down to Power, and then Switch to Desktop. Wait for your Deck to reboot.
  2. Next, open up the browser of your choice, go to the Blizzard download page (or just search for it on Google), and download the Windows installer.
  3. Next, we need to add the downloaded .exe file to Steam. Open up desktop Steam, go to Library, and at the bottom left corner, click on the plus sign, then Add a Non-Steam Game.... Navigate to your downloads folder by clicking on Browse, and then go to home/deck/Downloads and add the Battle.net installer file to Steam. Don’t forget to show All Files under File type: if you can’t find the installer.
  4. Now, navigate to the newly added entry in your Steam Library. It should be called something along the lines of Battle.net-Setup.exe. Don’t launch it yet, but instead click on the cog wheel icon, then Properties... and under Compatibility, toggle the Force the use of a specific Steam Play compatibility tool option. Choose Proton 6.3. This is the only version that gets around the “No GPU” error.
  5. Now hit Play to launch the installer, follow the different steps, and wait until it’s done. When the installation process is done, you can remove the Battle.net-Setup.exe from Steam again. Right-click it, go to Manage, then Remove non-Steam game from your library.
  6. Next, we want to add the installed launcher to Steam. In Desktop Steam, go to Library, and at the bottom left corner, click on the plus sign, then Add a Non-Steam Game.... Now we need to look for the file. Click on Browse and navigate to the following folder by going through the folder structure: home/deck/.local/share/Steam/steamapps/compatdata/. Don’t forget to show All Files under File type: if you can’t find the installer.
  7. Here you need to search for the latest added folder under DATE MODIFIED. It should be a 10-character long number. Open it, and go to the following folder: pfx/drive_c/Program Files (x86)/Battle.net. Here select the Battle.net Launcher.exe file. Add this one to Steam. If you can’t see it, be sure you have All Files selected under File type:.
  8. Don’t launch it yet, but instead click on the cog wheel icon, then Properties... and under Compatibility, toggle the Force the use of a specific Steam Play compatibility tool option, like we did in step four.
  9. Phew! We’re finally done. Launch Battle.net now.
3 Likes
7

This didn’t work for me.
Did it work for you? Maybe I did something wrong.

8

I wish i could send links here, check reddit/linuxgaming there is a thread for diablo 4 with ppl that tried other things as well and worked for them

9

I already saw the thread you probably mean, but it still doesn’t work. Same error.
But thanks anyway.

10

I was able to get past the “No GPUs found” error by following the reddit post. I went through a 90 minute queue and watched the opening cinematic. After the cinematic completed I came to a screen that I could create a character. There were other options, however the game crashed before I could select anything. Now I’m in another 60 minute long queue.

1 Like
11

After I downloaded ProtonUp and did all the things in the reddit thread /r/linux_gaming/comments/11tt2zd/for_those_wondering_about_diablo_4_beta_launching/ in lutris it works.
Thanks all.

1 Like
12

when you guys are in queue move the dpad, otherwise like me it won’t load up the controller and you will have to restart again. it will be noticeable that the controller is recognized bellow the “cancel” gonna show the button B

13

Hey, glad that guide helped you out! It seems to be working for a lot of people. As the author it’s ironic that I started figuring out how to get around the No GPU error, posted the guide and had other people playing yet I’m still unable to play. Just a black screen once I load in - much sadness :frowning:

14

I went to (links not allowed) winehq .org and the maintainer for Diablo IV suggested using the d3d12.dll from vkd3d-proton-2.8 and also the dxgi.dll from dxvk-2.1.
Both packages are available on github.
The d3d12.dll package can be found by searching for : vkd3d-proton
Scroll down the page till you reach Assets: and get the vkd3d-proton-2.8.tar.zst package. You decompress it with zstd, and then un-tar it like normal.
Next to get the dxgi.dll you search for dxvk and the maintainer is doitsujin. You will find the tar package dxvk-2.1.tar.gz down the page in the Assets: section.
I would suggest you extract both packages into one directory. I have a directory in my home directory just for windows DLL files, you can probably guess the name.
So now you have both packages and you will actually have 4 new dll files. There are both 32 bit and 64 bit versions of both files. So you need to put the
64 bit version of the d3d12.dll and dxgi.dll in WINEPREFIX/drive_c/windows/system32
the 32 bit versions go in
WINEPREFIX/drive_c/windows/syswow64

EDIT: Apparently 32 bit dll’s go in syswow64 and 64 bit dll’s go in system32. This is according to the maintainer of the dxvk package.
I was following other instructions instead of reading the README file like I should have. I have made corrections in my post up above. Hope this didn’t mess anyone else up like it did me.

The dll’s are set to native by default so you must set them to builtin using winecfg.

If you like you can rename the original dll files rather than overwriting them. It is so easy to re-install a wine version that it hardly seem worth the effort to me.

OK so if this helps then tell me why I get this error:
You need at least Windows 10 (version 1909).

Of course I have run regedit and set both the CurrentBuild & CurrentBuildNumber to 18363.
If I run wineconsole it says:
Microsoft Windows 10.0.18363
But after D4 fails the FenrisDebug.txt says:
Fenris Release (No Assertions) running under Windows 10-64 (Version 10.0.18362.0)
So FenrisDebug is getting it’s version info from somewhere other than the registry.

If anyone can help with this I would be grateful.
I am positive the great Linux community will figure these problems out in time.

Also I am using wine-staging" Currently wine-8.4 (Staging)strong text

2 Likes
15

Same here. I run Battle.net app in Lutris. All AAA games play perfectly well on it, including other Blizzard games, like D3, D2, Starcraft, etc.
I just installed D4 beta inside Battle.net app. It throws error right away upon clicking “No GPUs found!”.
I did not attempted any modifications as suggested in this thread.
Blizz team, whatever you did, please please revert GPU detection to normal behaviour like in every other game, including other Blizz games.

16

Ok, I found reliable and quick solution! Done without any external tools.

  1. If you have lutris installed, reinstall it, so it pulls newest DXVK and VKD3D libraries upon next startup. In my system, this is done by:
    sudo apt reinstall lutris
  2. Launch Lutris, it will autoupdate automatically for few seconds. Then, go to Runners/Wine menu and download lutris-GE-Proton7-39-diablo_4 runner.
  3. Right click your D4/Battlenet game profile, select Configure, on Runner Options tab, make sure profile uses that Proton runner and latest DXVK and VKD3D libraries.

That’s it, game launches well, no errors :slight_smile:

1 Like
17

I just saw that lutris-GE-proton7-41 was offered so I tried that instead, and it worked fine too. I tried reinstalling Lutris, but at least on my archlinux system it didn’t pull any new libaries.

That said, the lutris install script was a bit weird as in, after installing battle.net client and me in bnet installing D4 and then exiting the bnet client again, the install script would just hang and not do anything, so I cancelled it manually oO. Seems it’s fine though.

2 Likes
18

Yesterday I’ve played using procedure from my earlier post and it was perfectly stable! Graphics 100% correct, sound, overall performance all good also, no stuttering whatsoever. Probably better experience than thousands of Windows native machines :smile: l just launched it on start and process was running for 10 hours straight, no crashes or memory leaks. Very happy with the results. RAM usage 10GB, even on highest graphical settings. Pulling about from 30 to 80 fps, depending on the scene, in 4K all options maxed out, Radeon 6800XT. Utilizing only 1.5x cores out of 8 physical cores, Ryzen 5800X. I was hoping for more fps. I don’t know why game isn’t saturating more than two cores of CPU, never exceeded about 150% utilization in htop.

19

Just tried lutris-GE-proton7-41, and that works also! No need for special lutris-GE-Proton7-39-diablo_4 runner anymore :slight_smile:
Also performance increased, and I am getting well above 30 fps, average I see 57-80 now on all maxed out 4K.

2 Likes
20

Using Lutris I set the wine version to lutris-GE-Proton7.41-x86_64 and I spun it up no problem. I was previously getting this same error.

2 Likes