Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal. You can also buy games using our partner links for GOG and Humble Store.
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,832

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: «5/9»
  Go to:

Eike Dec 27, 2017
View PC info
  • Supporter Plus
Quoting: Shmerl
Quoting: EikeI surely must be doing something wrong that I haven't met any of this in many years...

Nvidia addresses some of those with a crawling pace. They supposedly fixed tearing by making a special double / triple buffering option, but it's off by default. They are working now on new API to propose for Wayland compositors (years late). If it will work out - great, but I don't expect it any time soon.

I can only repeat myself: I'm not experiencing what you're talking about. And I'm not talking about some obscure future, but present and past years. I don't have tearing in Unity games (and I didn't change driver buffering optiond), neither met the other things you mentioned. What am I doing wrong...?
Shmerl Dec 27, 2017
Quoting: EikeI can only repeat myself: I'm not experiencing what you're talking about. And I'm not talking about some obscure future, but present and past years. I don't have tearing in Unity games (and I didn't change driver buffering optiond), neither met the other things you mentioned. What am I doing wrong...?

Good for you. I had constant tearing, and the worst in Unity games (my previous card was GTX 680). That's completely gone since I switched to AMD / Mesa.


Last edited by Shmerl on 27 December 2017 at 9:38 pm UTC
slaapliedje Dec 27, 2017
Quoting: Phlebiac
Quoting: slaapliedjeThough to be fair, the Opteron system that I had worked great for many years.

Ironically, Nvidia made some of the best AMD motherboard chipsets (nForce).

Yeah, that was before AMD bought ATI.
mrdeathjr Dec 27, 2017
Quoting: GuestI have no application that uses GL4.6

Yeah exist cemu in lastest versions

View video on youtube.com

Sadly amd dont have opengl 4.6 for now

^_^
Shmerl Dec 27, 2017
Quoting: mrdeathjrSadly amd dont have opengl 4.6 for now

That's incorrect. It has these:

GL_ARB_indirect_parameters
GL_ARB_pipeline_statistics_query
GL_ARB_polygon_offset_clamp
GL_ARB_shader_atomic_counter_ops
GL_ARB_shader_draw_parameters
GL_ARB_shader_group_vote
GL_ARB_texture_filter_anisotropic
GL_ARB_transform_feedback_overflow_query
GL_KHR_no_error


What's missing are these:

GL_ARB_gl_spirv
GL_ARB_spirv_extensions


Is Cemu using these two? I really doubt it does.


Last edited by Shmerl on 27 December 2017 at 10:22 pm UTC
slaapliedje Dec 27, 2017
Sorry if this was already covered but;

How to get nVidia to 'just work'
1) use a good distribution that actually knows how to package things and include them in the distribution (pretty much any Debian based one)
2) install the nvidia-driver package, which pretty much installs all the needed bits, including nvidia-kernel-dkms.
3) enjoy not having to ever recompile the driver. When you upgrade it, DKMS recompiles it for you, reboot into new kernel and you're good to go.

I haven't had any crashing/freezing due to the nvidia driver that wasn't caused by a particular game in YEARS. In fact I think the last time I had my Linux box lock up was due to playing around with a beta of SteamVR that decided to go a bit funky.

Reason I stopped using AMD is because they'd deprecate support in their closed source driver way quicker on older cards than nVidia does, and the open source driver was never up to the same performance. That and there are what, like 5 different drivers now?

Plus there was a time (I haven't checked lately) when their catalyst driver wouldn't work with the newer xorg or kernels for 8 months. Maybe the open source drivers are much better performance wise now, but they have been historically pretty crap.

Edit: Also, even with the open source stuff, you have to try and get latest Mesa on your system, and that's generally a pretty major thing to do on many of the binary distributions (not so bad on something like Arch.)


Last edited by slaapliedje on 27 December 2017 at 10:25 pm UTC
Shmerl Dec 27, 2017
Quoting: slaapliedjeAlso, even with the open source stuff, you have to try and get latest Mesa on your system, and that's generally a pretty major thing to do on many of the binary distributions (not so bad on something like Arch.)

It's only as major as you are not yet familiar with building Mesa from source. Once you learn that, it's noting major, just compilation time. One thing many are missing that there is no need to replace system Mesa to use the latest one for running some games. You can use system packaged one for everything else, and use your custom built one for launching games that need the newest features. That's exactly what I do, so I don't need any package repositories for that and can build Mesa any time I feel like doing it.

Sure, building stuff from source might sound intimidating, but it's just some learning curve, nothing insurmountable.


Last edited by Shmerl on 27 December 2017 at 10:30 pm UTC
natis1 Dec 28, 2017
View PC info
  • Supporter
Quoting: Shmerl
Quoting: slaapliedjeAlso, even with the open source stuff, you have to try and get latest Mesa on your system, and that's generally a pretty major thing to do on many of the binary distributions (not so bad on something like Arch.)

It's only as major as you are not yet familiar with building Mesa from source. Once you learn that, it's noting major, just compilation time.

I personally disagree. It's much harder to build Mesa from source on a distro like Ubuntu or openSUSE than Arch or Gentoo. Thankfully, you can get around this by using PPAs/ "1 click installers" which can provide binary versions of mesa git.
slaapliedje Dec 28, 2017
Quoting: natis1
Quoting: Shmerl
Quoting: slaapliedjeAlso, even with the open source stuff, you have to try and get latest Mesa on your system, and that's generally a pretty major thing to do on many of the binary distributions (not so bad on something like Arch.)

It's only as major as you are not yet familiar with building Mesa from source. Once you learn that, it's noting major, just compilation time.

I personally disagree. It's much harder to build Mesa from source on a distro like Ubuntu or openSUSE than Arch or Gentoo. Thankfully, you can get around this by using PPAs/ "1 click installers" which can provide binary versions of mesa git.

Yeah, I personally have no problems with compiling things and passing parameters to use the non-system installed stuff, but the typical Ubuntu users are used to the PPAs, which in my experience is fine if you use one or two, but once you start using a bunch of different ones you end up with an unstable mess. The same reason why pre-rpmfusion, Fedora and CentOS/RHEL became broken messes if you tried to use the various repos for decent desktop support.

Anyhow, there are definite advantages to either nvidia or AMD. AMD is on the right track though, and nVidia seems to want to be friendly toward the FOSS people, but they also have the bottom line of their Quadro vs Geforce cards. Does AMD even have the firegl drivers anymore?
Shmerl Dec 28, 2017
Quoting: natis1I personally disagree. It's much harder to build Mesa from source on a distro like Ubuntu or openSUSE than Arch or Gentoo.

How exactly is it harder? Check how official distro packages configure and build Mesa, and use that as a starting point.

And in this case, I don't need PPAs and binary click installers, because I don't want to replace system Mesa with a manually built one, especially if it's a master branch. I need to use them in parallel.


Last edited by Shmerl on 28 December 2017 at 4:31 am UTC
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.