Skip to content
Shane Docs

Intel and AMD (Mesa) Graphics on Ubuntu

Intel and AMD GPUs generally use the open-source Mesa stack. This article explains how to check current renderer, install utilities, and cautiously update Mesa when necessary.

1 Check renderer and driver

Section titled “1 Check renderer and driver”
Terminal window
sudo apt install -y mesa-utils
glxinfo | grep "OpenGL renderer"
lspci -k | grep -A3 -i "VGA\|3D"

If output shows llvmpipe or software rasterizer, hardware acceleration is not active and further investigation is needed.

2 Common packages

Section titled “2 Common packages”

Install Mesa and utilities:

Terminal window
sudo apt update
sudo apt install -y mesa-utils libgl1-mesa-dri libglx-mesa0

3 When to update Mesa

Section titled “3 When to update Mesa”

Only update Mesa from trusted sources if you need features or fixes not present in the Ubuntu release. Popular PPAs include oibaf and kisak, but they are third-party and may introduce instability.

Example (use at your own risk):

Terminal window
sudo add-apt-repository ppa:oibaf/graphics-drivers -y
sudo apt update
sudo apt upgrade -y

To revert, remove the PPA and sudo apt update && sudo apt install ppa-purge && sudo ppa-purge ppa:oibaf/graphics-drivers.

4 Troubleshooting

Section titled “4 Troubleshooting”
  1. If you see llvmpipe, check kernel DRM driver and DRI modules (lsmod | grep drm and dmesg | grep -i drm).
  2. Ensure xserver-xorg-video-* packages are not conflicting; modern stacks prefer DRI via Mesa.
  3. For Wayland compositors, check compositor logs (e.g., journalctl -b for GNOME/Wayland messages).

Why this matters

Section titled “Why this matters”

This topic is an important part of building a reliable Linux development workflow. Understanding it clearly will make later tasks easier, because it reduces guesswork and helps you recognize when a step is missing or misapplied.

Practical next steps

Section titled “Practical next steps”
  • Try the commands or configuration shown here in a safe test environment.
  • Compare how the concepts apply across different distributions or tools.
  • Keep a short note of what worked and what failed so you can diagnose future problems faster.
  • Revisit the related article in the series to deepen the connections between topics.

Common pitfalls

Section titled “Common pitfalls”
  • Skipping verification steps and assuming the system is configured correctly.
  • Copying commands without adapting paths, package names, or tool versions for your environment.
  • Treating this topic as an isolated tip rather than part of a larger workflow.