We do often include affiliate links to earn us some pennies. See more here.

An explanation of what Mesa is and what graphics cards use it

By - | Views: 77,087
You’ve most likely heard the term “Mesa” thrown around a lot, but you might not quite understand what it is. This is an attempt to clear up the question of “What exactly is Mesa and do I need it?”.

Note: This is an attempt to keep things simple for the average user to understand, so I won’t go overly technical with this.

Mesa is a term used to encompass the different open source graphics drivers available on Linux, so it can be what powers your GPU. I say can be, since AMD and NVIDIA also have their own closed-source proprietary drivers (what you would download from their website on Windows, if that makes that clearer).

Originally, Mesa began only to serve as an open source Linux implementation of OpenGL, but it has since grown to be a lot more than that. Mesa was started in 1993 by Brian Paul, but now it has many more developers, some of which are employed by the likes of AMD, Intel, Valve and others. Linux game porters like Feral Interactive have also contributed code to Mesa. Plenty of people also help with Mesa development in their spare time too.

Mesa itself is not a driver, as you will be using a different part of Mesa for each graphics card vendor. Still with me? Okay!

Mesa implements various API’s (Application programming interface) like OpenGL, OpenGL ES, OpenCL, OpenMAX, VDPAU, VA API, XvMC and Vulkan.

Mesa versioning
Something also worth noting, is that Mesa has switched to a year-based release numbering scheme. This is why Mesa jumped from 13 to 17 in release numbers.

Usually, it is recommended to update to a new major version of Mesa once they have done the first round of bug fixing. If you're concerned with stability and reliability stick to point release numbers like 17.0.1.

How to find your current version of Mesa
Do this in terminal:
glxinfo | grep Mesa
Which will give you something like this:
QuoteOpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.1
OpenGL version string: 3.0 Mesa 17.0.1
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.0.1

So you can see your Mesa version, along with what version of OpenGL support you have. This will likely show nothing if you're not using Mesa.

Intel
The story for Intel is mostly pretty simple, if you’re using Intel integrated graphics, you will be using Mesa. Except for the ‘PowerVR’ based chips in the GMA 500, GMA 600, GMA 3600, GMA 3650 series.

Intel usually supports Mesa quite well and even have their own Mesa update tool named ‘Intel® Graphics Update Tool’ to give certain distributions the latest version of Mesa.

Intel also have the ‘anv’ Vulkan driver, which seems to be largely feature complete and should work.

AMD
There are a number of different Mesa drivers available for AMD cards, you can see a little information on that here.

The latest AMD cards use the ‘amdgpu’ kernel driver (the proprietary AMDGPU-PRO also uses a version of this, which has not yet been accepted into the Linux kernel yet), whereas all older cards use the ‘radeon’ kernel driver. Each part of Mesa listed below hooks into one of those kernel drivers, which part depends on your graphics card model.

As mentioned, the kernel driver (either ‘radeon’ or ‘amdgpu’) is paired with one of these:
radeon - R100 series
r200 - R200 series
r300g - R300, R400, and R500 series
r600g - R600, R700, HD 5000 and HD 6000
radeonsi - HD 7000, HD 8000 and RX 200, RX 300 and RX 400

You also have the ‘radv’ driver for Vulkan, which was officially added in Mesa 13. It’s still in development right now, so it’s to be considered in beta.

Right now, most AMD graphics cards have pretty good support in Mesa, with the closed source driver often not being needed. Our own statistics have users telling us that only around 11% of Linux gamers with an AMD GPU use the proprietary AMD driver.

NVIDIA
NVIDIA isn’t quite such a nice story, as NVIDIA doesn't help towards development of Mesa, since they prefer their own closed-source proprietary drivers. For NVIDIA cards Mesa is typically quite far behind the closed drivers in terms of performance and features due to this. Mesa also typically doesn’t work well, if at all with the very latest generation of NVIDIA graphics cards.

With Mesa, you have the nouveau (pronounced like nu-vo) kernel driver, but like AMD, NVIDIA uses nouveau plus another part of Mesa depending on your graphics card model.

Later generations of NVIDIA cards require something called ‘signed firmware’ in order for Mesa to interact with them and NVIDIA has been quite slow to release it.

The ‘Pascal’ generation in particular right now has very little support, as NVIDIA has only recently provided the signed firmware required.

For NVIDIA, it’s usually best to stick with the proprietary driver. Older generations have reasonable support in Mesa now, but you will still see better performance with the proprietary NVIDIA driver.


I hope this all makes sense, but if anything really needs further clarification be sure to reach out in the comments. Article taken from GamingOnLinux.com.
33 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
22 comments
Page: «3/3
  Go to:

Guppy Mar 7, 2017
Quoting: Creak
Quoting: GuppyI'm curious - under what circumstances would you need HDCP with linux ? I mean there is ( AFAIK ) no licensed BD player for linux so we don't really have a source of HDCP content or am I missing something here?
Maybe I'm wrong, but for what I understand HDCP isn't a feature, it's a mandatory API that has to be implemented if you want to connect devices using DVI, HDMI, DP, etc... A BD player needs it, but your display needs it also. So, no HDCP, no image basically...

As I understand it HDCP is only needed for protected content - basically a bluray player asks if HDCP is supported ( properly via crypto challange ) and if that fails it refuses playback.
For instance HDMI recorders like elgato needs a HDCP free signal, and because of that the PS4 has the ability to turn off HDCP which in turn disables bluray playback
Shmerl Mar 7, 2017
Quoting: CreakMaybe I'm wrong, but for what I understand HDCP isn't a feature, it's a mandatory API that has to be implemented if you want to connect devices using DVI, HDMI, DP, etc... A BD player needs it, but your display needs it also. So, no HDCP, no image basically...

I don't think it's mandatory. It's only used when some device requests it. You can use DP without HDCP. So having a DRM-free firmware should be a possibility, as long as you don't plan to use any HDCP dependent garbage.


Last edited by Shmerl on 7 March 2017 at 7:46 pm 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.