Confused on Steam Play and Proton? Be sure to check out our guide.
We do often include affiliate links to earn us some pennies. See more here.

Reminder: Update your PC info for the next round of statistics updates

By - | Views: 32,822

This is your once a month reminder to make sure your PC information is correct on your user profiles. A fresh batch of statistics is generated on the 1st of each month.

You need to be logged in to see when you last updated your PC info!

You can see the statistics any time on this page.

While we don't currently have a drop-off implemented for old/stale data, it will be implemented next year. If you want to make sure you're included at any time, clicking update without any changes will update the last time you edited them. The drop-off for old data will be done in months, since people aren't likely to change hardware that often.

Article taken from GamingOnLinux.com.
Tags: Site Info, Survey
0 Likes
The comments on this article are closed.
86 comments
Page: «7/9»
  Go to:

slaapliedje Dec 28, 2017
Quoting: Shmerl
Quoting: natis1For starters, Gentoo includes git versions of all packages in its repos so no need to git clone, ./configure, make, make install anything manually. Arch does something similar with its aur.

More importantly though, when you build a package from source using a git repository as the source on Arch that package is tracked by your package manager and can be updated along with the rest of your system (pacaur -Syu --devel). As far as I know, Debian and variants lets you build a package from source, but doesn't automatically keep it up to date. If you install Mesa git but never update it it will quickly fall behind the fixed release version.

I see. But all those methods install Mesa as a replacement for stable one. That's not the goal for me in this case. I like to have experimental / master Mesa alongside stable one, and only use it on demand when needed. So in such case building it and placing it in custom location works best.

Here is an example how to do it: https://www.gamingonlinux.com/wiki/Building_Mesa_from_source

So are you just launching with an LD_PRELOAD? Or do you change the .desktop file? I was going to ask about steam command parameters, but I don't think you use it due to DRM, right?
slaapliedje Dec 28, 2017
Quoting: Shmerl
Quoting: slaapliedjeWell, the open source driver went through many names / iterations. radeon, radeonhd, radeonsi, radv, etc. Nvidia has had nv, nouveau.

I think you are mixing up kernel driver (radeon / amdgpu), and API implementations (radeonsi/r600 for OpenGL, radv/amdvlk for Vulkan and etc.). Having different names is quite reasonable, if they have actually different code for different hardware, or simply different implementations.

Oh, actually I was thinking of xorg drivers. But yeah they split them up into multiple kernel modules/xorg drivers. Instead of just 'radeon'.
Shmerl Dec 28, 2017
Quoting: slaapliedjeSo are you just launching with an LD_PRELOAD? Or do you change the .desktop file? I was going to ask about steam command parameters, but I don't think you use it due to DRM, right?

I'm using LD_LIBRARY_PATH and a bunch of variables needed for OpenGL and Vulkan custom locations. See in the linked wiki page. I'll update it soon and will also put my common scripts somewhere so you can see examples.

I.e. I made a script mesa_run.sh which launches its parameter with custom mesa, and I simply use that when I want to run something using that custom Mesa, rather default system one. You surely can use the same idea in desktop launchers and other scripts.


Last edited by Shmerl on 28 December 2017 at 11:07 pm UTC
Shmerl Dec 28, 2017
Example of how you can do it (assuming you put your mesa in /opt/mesa-${branch})

mesa_run.sh

#!/bin/bash

export mesa_dir=${mesa_dir:-"mesa-master"}

if [[ "$1" == "32" ]]; then
   arch_dir="x86"
   vk_arch="i686"
   shift
else
   arch_dir="x86_64"
   vk_arch="x86_64"
fi

mesa_env="LD_LIBRARY_PATH=/opt/${mesa_dir}/${arch_dir}:$LD_LIBRARY_PATH LIBGL_DRIVERS_PATH=/opt/${mesa_dir}/${arch_dir} EGL_DRIVERS_PATH=/opt/${mesa_dir}/${arch_dir} VK_ICD_FILENAMES=/opt/${mesa_dir}/${arch_dir}/radeon_icd.${vk_arch}.json"

echo "Mesa env:"
echo "${mesa_env}"
echo "==========================================="

export ${mesa_env}
$@



Last edited by Shmerl on 28 December 2017 at 11:10 pm UTC
Shmerl Dec 29, 2017
I updated the wiki, and put the build script here: https://gist.github.com/shmerl/f4e5f76871239158cf083e37c5da56f4
Cyba.Cowboy Dec 29, 2017
You need to add System 76's "Pop!_OS", and the NVIDIA GeForce 920MX; both are it is missing from the computer specifications.


Last edited by Cyba.Cowboy on 30 December 2017 at 9:04 am UTC
Siinamon Dec 29, 2017
Quoting: ShmerlWhat was the last AMD card you used? I was Nvidia user for a long time, but got fed up with poor integration and need to use the blob, so I switched to Polaris a while ago (RX 480). It's been a breeze since.

AMD RX 460 was the last card I used.
Shmerl Dec 29, 2017
Quoting: SinaCutieAMD RX 460 was the last card I used.

That's strange, since Polaris is quite well supported. I didn't have any major issues with RX 480. What exactly was the problem with your card?
musojon74 Dec 29, 2017
I still use 970 with nvidia binary driver. It works. I don't have tearing etc. To those saying about compiling from source, if we want an upturn in the amount of Linux users we need to make this unnecessary. Sure we can all do these tasks but many will balk at this task and go back to windows.
mrdeathjr Dec 29, 2017
Quoting: musojon74I still use 970 with nvidia binary driver. It works. I don't have tearing etc.

To those saying about compiling from source, if we want an upturn in the amount of Linux users we need to make this unnecessary.

Sure we can all do these tasks but many will balk at this task and go back to windows.

Compiling for new users is really annoying when for this users must be only download and install (ppa is acceptable)

^_^
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.