Gallium installation basics

[nottux]

Feature Request

I confirm:

• that I haven't found another request for this feature.
• that I have checked whether there are updates for my system available that
  contain this feature already.

Description

A small guide to install gallium nine in readme

Justification [optional]

Risks [optional]

References [optional]

https://askubuntu.com/questions/1115300/how-to-install-gallium-nine-standalone

Also i use RX 540 gpu with ubuntu-x-swat ppa on xubuntu 18.04.2, i installed libd3dadapter9-mesa libd3dadapter9-mesa-dev libd3dadapter9-mesa:i386 but cs:go and some other games crash or freeze (will test borderlands 2)

[phush0]

I am with Vega M with Padoka PPA on ubuntu 18.04.2 and have installed all libs amd64 and i386, Darksiders2 crash inside libd3dadapter9. I don't thing it is problem to Proton, but in mesa. With Wined3d9 it is working ok, because it will go trough RadeonSI.

[popsUlfr]

Have a look around the wiki, for instance : https://github.com/popsUlfr/Proton/wiki/Requirements
Also make sure PROTON_GALLIUM_NINE_MODULEPATH is correctly set as described here : https://github.com/popsUlfr/Proton/wiki/Installation-and-usage

I haven't have enough time to get out a new version yet, apologies for that. But the plan was to integrate the standalone gallium nine https://github.com/iXit/wine-nine-standalone which most likely fixes many issues.

In the mean time you could drop the files from there into your proton and enable gallium nine with the ninewinecfg.exe tool and see if that works for you.

EDIT: actually just replacing d3d9-nine.dll in my proton which the one from the standalone repo should be enough to test.

[phush0]

Have a look around the wiki, for instance : https://github.com/popsUlfr/Proton/wiki/Requirements
Also make sure PROTON_GALLIUM_NINE_MODULEPATH is correctly set as described here : https://github.com/popsUlfr/Proton/wiki/Installation-and-usage

I haven't have enough time to get out a new version yet, apologies for that. But the plan was to integrate the standalone gallium nine https://github.com/iXit/wine-nine-standalone which most likely fixes many issues.

In the mean time you could drop the files from there into your proton and enable gallium nine with the ninewinecfg.exe tool and see if that works for you.

EDIT: actually just replacing d3d9-nine.dll in my proton which the one from the standalone repo should be enough to test.

I am already done this and I have same crash, so I am sure that problem is in mesa

[rea987]

@phush0 It is most likely a Mesa related crash. Oibaf's Mesa PPA for Ubuntu 18.04 broke its Gallium Nine compatibility for 64 bit in December or January while I was testing this fork of Proton. As I expected the problem to be solved in time, I didn't report it, instead migrated to Ubuntu 18.10 which offers Gallium Nine in its own repos. I am quite certain if you try it on Ubuntu 18.10, you won't have this issue. That said, still having the same issue in Mesa PPA at the end of February is concerning.

[nottux]

i did launched bit blaster xl with these launch options: PROTON_USE_GALLIUM_NINE=1 PROTON_GALLIUM_NINE_MODULEPATH="/usr/lib/i386-linux-gnu/d3d/d3dadapter9.so.1:/usr/lib/x86_64-linux-gnu/d3d/d3dadapter9.so.1" PROTON_LOG=1 %command%
i am on oibaf ppa

Bit blaster xl launches but i don't know if gallium is in use
steam-433950.log

[nottux]

Borderlands with launch options: PROTON_USE_GALLIUM_NINE=1 PROTON_GALLIUM_NINE_MODULEPATH="/usr/lib/i386-linux-gnu/d3d/d3dadapter9.so.1:/usr/lib/x86_64-linux-gnu/d3d/d3dadapter9.so.1" PROTON_LOG=1 %command% crashes.
no window is created but game runs for a couple seconds then crashes
steam-49520.log

[nottux]

@rea987 what mesa version are you on?

[rea987]

@tuxutku I am currently not using Mesa; I returned the laptop I borrowed to conduct tests for this Proton fork. But the issue that @phush0 experienced is the same that I had with Oibaf's Mesa PPA on Ubuntu Mate 18.04 on December/January. It was a 64 bit Mesa/Gallium Nine issue that appeared in December/January. Upgrading to Ubuntu Mate 18.10 to use its own Mesa/Gallium Nine solved my issues at the time. Your issue on the other hand seems to happen with 32 bit games which might be caused by something different.