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.
Some you may have missed, popular articles from the last month:
Do you think people will be convinced when addressed like this?
Last edited by Eike on 27 December 2017 at 3:38 pm UTC
What 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.
Last edited by Shmerl on 27 December 2017 at 6:11 pm UTC
I don't remember when was the last time nvidia drivers didnt support latest Xorg or Kernel, its been getting new drivers out for the newly released kernel for within 1 week and Xorg hasn't been a problem long long time.
Standard APIs or not, the end user doesn't care. If it doesn't work it doesn't work. I know all the "political" stuff behind all this. Nvidia sucks, yeah. Gsync? F this, their own standards F this... but it works. Until then i have no plan to switch to AMD if i have to fiddle with things. If i buy a 500€ hardware i want it to work and get the most performance out of it, not wait for driver improvements or apply loads of workarounds by searching forums and google.
It doesn't, a least not at all seamlessly. Constant screen tearing (especially in Unity games), constant breaking of the system and need to reinstall the driver on each kernel or xorg update, no framebuffer support, Optimus horror story, opaque bug reporting process and etc. and etc. Wayland support? Forget it. If you really don't care about proper system integration, then Nvidia is OK. But I really appreciate how much better AMD works after switching to it. So talking about "just works" - AMD is way ahead, and that's to be expected, AMD are putting an effort into upstreaming their driver, while Nvidia don't care in the least.
And not really accidentally, all those benefits in AMD are from the fact that their drivers are open. My personal favorite feature though is GALLIUM_HUD.
Last edited by Shmerl on 27 December 2017 at 7:07 pm UTC
I surely must be doing something wrong that I haven't met any of this in many years...
Constant screen tearing? how about ForceCompositionPipline? or 4 years ago when that wasn't a thing there were compositors like compton that fixed it (though there was small perf cost)
Constant breaking of system? what? in 2007, yes. last 5 years, no
framebuffer support, yeah could be handy, but for a user who doesn't need to use TTYs, not a problem.
Optimus support? No idea about this one, who games on laptops anyway, i was talking about Desktop PC's
Wayland support? Wayland is still ways off, many games are not for wayland and perf is much worse with xwayland or whatever translation.
Now lets ask about AMD? Freesync? HDMI/DP audio? (ok those 2 are coming soonish, but what took so much time?) No Simple GUI to change your GPU settings, OC etc? have to use some third-party ones i guess? no OpenGL4.6 support? No Hardware encoder like nvenc. Or how about hard system lockups with RADV or some other scenarios?
Ok i stop arguing now. Do whatever you want. I will pick my next GPU from the side that delivers performance and feature-set with smallest amount of issues.
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. They started supporting DRM/KMS kernel interfaces only recently, and even that isn't done properly yet (so PRIME kind of is there, but doesn't really work from what I've heard). And they never implemented framebuffer, so no idea how you could think it was fixed.
The bottom line - they are moving very slowly, simply because Linux integration was never a priority for them.
Last edited by Shmerl on 27 December 2017 at 7:45 pm UTC
I had it until I switched, so surely it was an issue even recently.
It was off for years, and now all DEs are finally ready to switch to it. Nvidia is nowhere ready.
AMD have their GUI, but they didn't open source it, so I've never used it. Not that I care much - I rarely tweak hardware parameters, defaults work OK. But I don't see why AMD can't open source that as well, once they completely replace their PRO with Mesa (they are gradually working on it, even adding compat profile to Mesa itself). I don't think it makes any sense for them to open it before, since they'll need to rework it.
Mesa supports OpenGL 4.6 except for a couple of extensions needed for Vulkan / OpenGL interop, which are being worked on. Those aren't trivial, since they require reimplementing some parts like IR translation. But it's well on the way. And I don't think you'll notice that. Which application even relies on such interop at present?
See https://mesamatrix.net
Last edited by Shmerl on 27 December 2017 at 7:53 pm UTC
Nothing more to say in this phrase
Wayland dont care for now, as your said too most apps run over x and xwayland have many problems
Sadly amd market quote difficult change* because amd needs improve so much for offer same features than nvidia, as various cited by yourself: random lockups - freezing, driver GUI - lastest opengl support and many others
*In hardware side is worst scenary for amd because them lack of good performance / tdp gpu
^_^
https://bugs.freedesktop.org/show_bug.cgi?id=104193
https://bugs.winehq.org/show_bug.cgi?id=43872
radeonsi now has a problem of hanging the whole system when some wrong stuff goes on with OpenGL. It's surely not the best experience, but I think they improved GPU reset with Vega.
The difference is, I don't mind participating in Mesa bug reporting, but with Nvidia it's completely opaque. I have no idea if anyone is working on that bug, or if they even care.
Exactly my point. And as I said, Mesa already supports 4.6, except for 2 SPIR-V related extensions.
Last edited by Shmerl on 27 December 2017 at 9:36 pm UTC