How to install ED on Linux using Wine [EXPERIMENTAL, NOT OFFICIALLY SUPPORTED]

is outdated.

5- Use Protontricks to make Elite Dangerous working on Linux​


this step is NOT needed. Proton Experimental works out of box. No additional steps:
1. Install Steam
2. Select default compatibility tool into steam's settings as "proton experimental"
3. Click "install" on Elite
4. Click "Play" on Elite.
 
I deleted the game, deleted wine en started to follow the instructions on https://cialu.net/how-to-install-and-play-elite-dangerous-on-linux/
First step was to install Steam. Alas, a few repositories that needed installing were not installed and that gave me some bad feelings.
Still it seemed Steam itself was installed.
I could go through the instructions and got quite far. ED was installed on my system. There was this Play button.
Bu the game still does not play.

Are there alternative instructions to make ED work from scratch with Steam?

Maybe the information on https://cialu.net/how-to-install-and-play-elite-dangerous-on-linux/ is outdated.

I did it the following way:

0. Check protonDB if your game is supported by proton for Linux: https://www.protondb.com/app/359320 (in case of Elite, it is)
1. Install steam via your packet manager (Arch linux for me so I used pacman). This way steam runs natively since Valve highly supports gaming on Linux
2. Go to https://github.com/GloriousEggroll/proton-ge-custom/releases and download and install this custom proton version (it worked wonders for me for Elite and other games)
3. After successfully installing, go to steam and change the proton settings for Elite to enforce using this custom proton version

It goes without saying that you will probably need some additional dependencies, like the post above me mentioned, protontricks will often times be such a dependency (it's a wrapper that runs winetricks command (yet another dependency) which ultimately solves a lot of "missing XYZ" issues).
The main selling point is to use this custom proton version as the team behind it did an awesome job customizing proton for specific games, including Elite Dangerous, which saves a lot of configuration time if it works out of the box and usually doesn't require much more configuration time if it doesn't.

Try these steps. Obviously no guarantee that it will work like this but if you encounter any issues during these steps I will gladly be here to assist you. :)
 

5- Use Protontricks to make Elite Dangerous working on Linux​


this step is NOT needed. Proton Experimental works out of box. No additional steps:
1. Install Steam
2. Select default compatibility tool into steam's settings as "proton experimental"
3. Click "install" on Elite
4. Click "Play" on Elite.
Your instructions are straight forward, but It still does not work.

There only is this PLAY button in the Steam window, which I then press.
I then choose 'Play Elite Dangerous (not the VR mode).
A list of 3 CD keys appears, defaulting on Elite dangerous: Game key, which I choose.
The Steam window then says 'Elite Dangerous is launching'.
Microsoft VC package seems to be installed.
The message changes to 'Elite dangerous is running'.
And then nothing but the reappearance of the green PLAY button.

Of course I then quit Steam and try again.
No succes.
Then I reboot and try gain.
No succes.
 
And then nothing but the reappearance of the green PLAY button.
You need to enable proton log and read it then, maybe launch steam from console window too and read what it prints in console.
I had similar behaviour 2 times last year:
1. That was prefix with manually installed .net/mono, then removed. That didn't go well. So deleting prefix total and let proton create fresh helped.
2. That was case sensitivity names mess and symlinks I made mess.

Helper for windows games to check case sensivity, save and do chmod +x on it:
Bash:
#!/bin/bash
DEF="."
SRC="${1:-$DEF}"

echo "Scanning $SRC for case insensitive dupes"

find $SRC | sort -f | uniq -di

Also if you have AMD card check here:
 
Last edited:
You need to enable proton log and read it then, maybe launch steam from console window too and read what it prints in console.
I had similar behaviour 2 times last year:
1. That was prefix with manually installed .net/mono, then removed. That didn't go well. So deleting prefix total and let proton create fresh helped.
2. That was case sensitivity names mess and symlinks I made mess.

Helper for windows games to check case sensivity, save and do chmod +x on it:
Bash:
#!/bin/bash
DEF="."
SRC="${1:-$DEF}"

echo "Scanning $SRC for case insensitive dupes"

find $SRC | sort -f | uniq -di

Also if you have AMD card check here:
Sounds like a good idea.
How can I enable the proton log en view it?
As for steam in a bash terminal: I started steam in a console with 'steam -whatever' and saw that a load of ' too many files open' errors appeared in the end. Still, there was a client window and the setup of shaders en planet generation was done. But then new loads of 'too many files open' and there was a crash.
Could it have been the number of files open? I remember that this once was a problem, years ago.
ulimit -n gave a number of 4096, both soft and hard.
I could however not find a way to increase the maximum allowed number of open files. I edited /etc/security/limits.conf, but it had no effect after reboot.
So I changed the file back to the original contents, rebooted, opened a terminal and was surprised to see the message ' Invalid MIT-MAGIC-COOKIE-1 key' appearring about every second among all other output. Wonder where so suddenly that came from.
Silly the I cannot even recreate the situation of before. No client window appears anymore.
 
Last edited:
Sounds like a good idea.
How can I enable the proton log en view it?
Right click on game in steam library, settings. Find something like launch parameters (command line field txet box there) and type exact:
PROTON_LOG=1 %command%
Basically left side you can define env variables, ending %command% parses as full steam's launch command.
Log will be in $HOME folder.

Then post it to
with questions.
 
Last edited:
I do not see 'settings' appear when I do that, only Properties.
 

Attachments

  • 1638293191023.png
    1638293191023.png
    426.1 KB · Views: 118
I did it the following way:

0. Check protonDB if your game is supported by proton for Linux: https://www.protondb.com/app/359320 (in case of Elite, it is)
1. Install steam via your packet manager (Arch linux for me so I used pacman). This way steam runs natively since Valve highly supports gaming on Linux
2. Go to https://github.com/GloriousEggroll/proton-ge-custom/releases and download and install this custom proton version (it worked wonders for me for Elite and other games)
3. After successfully installing, go to steam and change the proton settings for Elite to enforce using this custom proton version

It goes without saying that you will probably need some additional dependencies, like the post above me mentioned, protontricks will often times be such a dependency (it's a wrapper that runs winetricks command (yet another dependency) which ultimately solves a lot of "missing XYZ" issues).
The main selling point is to use this custom proton version as the team behind it did an awesome job customizing proton for specific games, including Elite Dangerous, which saves a lot of configuration time if it works out of the box and usually doesn't require much more configuration time if it doesn't.

Try these steps. Obviously no guarantee that it will work like this but if you encounter any issues during these steps I will gladly be here to assist you. :)
The Proton 6.21-GE-2 tarball I extracted to:
/home/vaessen/.local/share/Steam/compatibilitytools.d
Now Proton 6.21-GE-2 is detected by steam and occurs on the list of Proton versions, but it will not work with it.
In settings, ' Enable steam play for all other titles' can be checked, but after that steam forces a restart and I find it unchecked again. Not so for 'Proton Experimental' or 'Proton 6.3-8'. It does not make a difference if I work with a Steam Beta Update or not. It also does not matter if in the Library, when right clicking on the game Elite Dangerous and going to properties-> compatibility, I force the use of it.

I do not think the version Proton is what matters in my case.

What I do see many times in the log is that the message ' too many file open' appears about 2048 times.
Since I can have 4096 files open when, this problem has clearly something to do with it.
But I do not think so many files need to be open at all.
 
But I do not think so many files need to be open at all.
That is not really "files". It is handles. Meaning everything - files, pipes, shared memory etc, etc. - i.e. kernel managed resource. And you have limit 4096 for all.
I would rise limit. I recall I was doing something with limits in fact. I think you need to change default RNICE to -1 too, otherwise wine cannot adjust thread's priorities. By default it is 0 on latest linuxes like that:

1638311526606.png


Also here is my GRUB config which I have current to play games:

GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 mitigations=off nvidia-drm.modeset=1 systemd.restore_state=0"
GRUB_CMDLINE_LINUX="mitigations=off nvidia-drm.modeset=1 systemd.restore_state=0"

And:
 
Last edited:
That is not really "files". It is handles. Meaning everything - files, pipes, shared memory etc, etc. - i.e. kernel managed resource. And you have limit 4096 for all.
I would rise limit. I recall I was doing something with limits in fact. I think you need to change default RNICE to -1 too, otherwise wine cannot adjust thread's priorities. By default it is 0 on latest linuxes like that:

View attachment 277775

Also here is my GRUB config which I have current to play games:



And:
I added the following lines to /etc/security/limits.conf:

vaessen soft nofile 8192
vaessen hard nofile 8192
vaessen hard nice -1

This to no avail however, not even after a reboot.

ulimit -Sn still gives 4096, like ulimit -Hn does.

I cannot remember how I managed to increase this limit on OpenSuSE, it being years ago when I did it. Surprisingly little information can be found on the internet about this subject.

Anyway, the error messages of 'Too many file open' are still there in great numbers.
The client window (when it appears at all) remains black, though process EliteDangerous6 takes about 30% CPU and sometimes even over 100%.
 
Anyway, the error messages of 'Too many file open' are still there in great numbers.
Well,
[alex@newsuper ~]$ ulimit -Hn
524288
[alex@newsuper ~]$ ulimit -Sn
1024
[alex@newsuper ~]$
I think I was rising those yes. For something just big.
I think, things like GPU <--> CPU channels consume file handles too. That's why need so many to play games.
 
The Proton 6.21-GE-2 tarball I extracted to:
/home/vaessen/.local/share/Steam/compatibilitytools.d
Now Proton 6.21-GE-2 is detected by steam and occurs on the list of Proton versions, but it will not work with it.
In settings, ' Enable steam play for all other titles' can be checked, but after that steam forces a restart and I find it unchecked again. Not so for 'Proton Experimental' or 'Proton 6.3-8'. It does not make a difference if I work with a Steam Beta Update or not. It also does not matter if in the Library, when right clicking on the game Elite Dangerous and going to properties-> compatibility, I force the use of it.

I do not think the version Proton is what matters in my case.

What I do see many times in the log is that the message ' too many file open' appears about 2048 times.
Since I can have 4096 files open when, this problem has clearly something to do with it.
But I do not think so many files need to be open at all.

I see, so your problem appears to be more complicated than originally assumed. Could you share your system specs and error logs on something like https://pastebin.com/ ? In the meantime, I will do some research based on your error reports and call back once I know more. Deal? :)
 
I see, so your problem appears to be more complicated than originally assumed. Could you share your system specs and error logs on something like https://pastebin.com/ ? In the meantime, I will do some research based on your error reports and call back once I know more. Deal? :)
I send you two log files, both with Steam using Proton-6.21-GE-2.
In one case, Steam does not work with beta updates, in the other it does.
Mind that in neither case I can set steam to use Proton-6.21-GE-2 for other games.
 

Attachments

  • Steam log with Proton-6.21-GE-2.txt with Steam Beta Update.txt
    12.6 KB · Views: 123
  • Steam log with Proton-6.21-GE-2.txt without Steam Beta Update.txt
    10.5 KB · Views: 143
I send you two log files, both with Steam using Proton-6.21-GE-2.
In one case, Steam does not work with beta updates, in the other it does.
Mind that in neither case I can set steam to use Proton-6.21-GE-2 for other games.
Thanks. I will need to perform some tests tomorrow. In the meantime, you can update steamdeps as the error log says
Couldn't import apt, please install python3-apt or update steamdeps for your distribution.
I don't believe this will solve your problem but it is a good gesture to do it anyways.

However, there are errors that caught my attention (and yours probably too).
Some .so files can not be loaded, namely gameoverlayrenderer.so.
Could you show me the output of the following three commands? (You can send me a private message if you wish to keep your data private)

ls /usr/share/vulkan/icd.d/
vulkaninfo --summary
lspci -k
 
CAPIJobRequestUserStats - Server response failed 2

Hmm ... looks like TLS 1.3 problem. And / or outdated root cert.
SWTOR/Elite had that problem an year ago about.
TLS problem solved by downgrading some lib in system responsive for....maybe ok now.
and certs - I just imported outdated.
Here the files I used for SWTOR. Maybe it is ok for Elite, don't have anything else stored here. Maybe I found by google ...that was once long ago.
 

Attachments

  • thawte_Primary_Root_CA.zip
    2.4 KB · Views: 94
Thanks. I will need to perform some tests tomorrow. In the meantime, you can update steamdeps as the error log says
Couldn't import apt, please install python3-apt or update steamdeps for your distribution.
I don't believe this will solve your problem but it is a good gesture to do it anyways.

However, there are errors that caught my attention (and yours probably too).
Some .so files can not be loaded, namely gameoverlayrenderer.so.
Could you show me the output of the following three commands? (You can send me a private message if you wish to keep your data private)

ls /usr/share/vulkan/icd.d/

lspci -k
Hello,

I do not have steamdeps or python3-apt, the latter seeming a bit of an odd requierement on a rpm system that OpenSuSE is.
Here come the results of applying the three commands you suggested.

ls /usr/share/vulkan/icd.d/
drwxr-xr-x 2 root root 4096 nov 27 18:53 .
drwxr-xr-x 4 root root 4096 feb 21 2021 ..
-rw-r--r-- 1 root root 146 feb 21 2021 intel_icd.i686.json
-rw-r--r-- 1 root root 148 feb 21 2021 intel_icd.x86_64.json
-rw-r--r-- 1 root root 147 feb 21 2021 radeon_icd.i686.json
-rw-r--r-- 1 root root 149 feb 21 2021 radeon_icd.x86_64.json

The result off vulkaninfo --summary are given in the attached file OutputVulkanSummary.txt.
Same for lspci -k, which you find in Output_lspci.txt

Thanks for your support.

Ed
 

Attachments

  • OutputVulkanSummary.txt
    99.8 KB · Views: 104
  • Output_lspci.txt
    2.9 KB · Views: 127
Last edited:
Hello,

I do not have steamdeps or python3-apt, the latter seeming a bit of an odd requierement on a rpm system that OpenSuSE is.
Here come the results of applying the three commands you suggested.

ls /usr/share/vulkan/icd.d/
drwxr-xr-x 2 root root 4096 nov 27 18:53 .
drwxr-xr-x 4 root root 4096 feb 21 2021 ..
-rw-r--r-- 1 root root 146 feb 21 2021 intel_icd.i686.json
-rw-r--r-- 1 root root 148 feb 21 2021 intel_icd.x86_64.json
-rw-r--r-- 1 root root 147 feb 21 2021 radeon_icd.i686.json
-rw-r--r-- 1 root root 149 feb 21 2021 radeon_icd.x86_64.json

The result off vulkaninfo --summary are given in the attached file OutputVulkanSummary.txt.
Same for lspci -k, which you find in Output_lspci.txt

Thanks for your support.

Ed
Hey, I have looked into the files.
First, I need to mention that I am currently short on time due to real life events that require my attention.
However, the time I did spend reading your files I have developed a suspicion that I did not investigate any further due to the above.
The suspicion being that apparently you are having more than one Vulkan implementation (namely intel and radeon).

Also, according to your vulkan summary, your vulkan API version is 1.0.65, but the latest one is 1.2.200. (or something like that).
With this in mind I would suggest to do the following:

0. Backup your system as any changes related to hardware drivers may cause your system to fail during boot
1. Update your GPU drivers in case you didn't already (You are running a Geforce 1060, check available packages for your distribution)
2. Remove all current implementations of vulkan
3. Install the latest vulkan implementations. I am unfamiliar with OpenSUSE but I found a guide that might help you here: https://en.opensuse.org/SDB:NVIDIA_drivers
4. Make sure that there are no uneeded vulkan implementations installed by checking if ls /usr/share/vulkan/icd.d/ only lists .json files for your current hardware (for me it only shows two files, you are currently having 4)
5. Run vulkaninfo --summary again and check if you are having the latest version installed#

If I had more time I could probably give you more detailed instructions but I hope this will help you in the mean time.
I will definately look into your issue again once I have the opportunity.

Best regards
 
Hey, I have looked into the files.
First, I need to mention that I am currently short on time due to real life events that require my attention.
However, the time I did spend reading your files I have developed a suspicion that I did not investigate any further due to the above.
The suspicion being that apparently you are having more than one Vulkan implementation (namely intel and radeon).

Also, according to your vulkan summary, your vulkan API version is 1.0.65, but the latest one is 1.2.200. (or something like that).
With this in mind I would suggest to do the following:

0. Backup your system as any changes related to hardware drivers may cause your system to fail during boot
1. Update your GPU drivers in case you didn't already (You are running a Geforce 1060, check available packages for your distribution)
2. Remove all current implementations of vulkan
3. Install the latest vulkan implementations. I am unfamiliar with OpenSUSE but I found a guide that might help you here: https://en.opensuse.org/SDB:NVIDIA_drivers
4. Make sure that there are no uneeded vulkan implementations installed by checking if ls /usr/share/vulkan/icd.d/ only lists .json files for your current hardware (for me it only shows two files, you are currently having 4)
5. Run vulkaninfo --summary again and check if you are having the latest version installed#

If I had more time I could probably give you more detailed instructions but I hope this will help you in the mean time.
I will definately look into your issue again once I have the opportunity.

Best regards
I deleted all vulkan and nvidia stuff and started anew.
To no avail alas.
What regularly is coming back is this error message that too many files are open.
What I am going to do is reinstalling OpenSuse from scratch and see what happens then.
Thanks very much for your support.
 
too many files open? what does that have to do with vulkan or nvidia ? open file limits are a shell/system limit controlled by an environment variable or sysfs config.

try running ulimit under the user that you're executing steam with.

if it doesn't say unlimited, then set it to unlimited and re-run steam in that specific shell. if it no longer gives you the error, then that's your fix and you just need to set that to be configured at the system level for users on boot
 
Back
Top Bottom