1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Intel Mesa Gives Problems With KDE's KWin, Again

Mesa

Published on 18 April 2011 10:26 AM EDT
Written by Michael Larabel in Mesa
94 Comments

Martin Gräßlin, the lead KDE developer of the KWin compositing window manager, usually has fairly insightful and technical blog posts. Last week he was talking about possibly moving the KDE screensaver into the KWin compositor for KDE SC 4.8 after writing the KDE view on GNOME's new compositing manager. Today he has written a new post, but this time it's about the open-source Intel Mesa driver breaking (again) for KWin.

Martin's post is more of a rant this time, but it's over Intel changing their OpenGL renderer string in a Mesa point release. Within the Mesa 7.10.x branch, Intel removed the "GEM" (Graphics Execution Manager) reference from their renderer string and in master (for Mesa 7.11) they have done further reformatting to this information for not only Intel but the other Mesa drivers too.

KWin was using the GEM reference in the OpenGL renderer string to determine whether direct rendering was available. With "GEM" no longer being in the string, KWin's blur effect is now disabled using Mesa 7.10 or Mesa 7.11-devel Git. Martin's main frustration is that Intel changed this in their stable branch and that KDE won't be able to detect Intel's GEM-capable driver by other means until their next major release, but not a KDE monthly point release. This is a problem hitting Ubuntu 11.04 "Natty" users right now where the problem was first discovered with KWin suddenly breaking on Intel hardware.

From Martin's blog post, "I'm now doing this kind of stuff for more than three years and changing the driver strings seems to be a hobby of the free drivers. The only driver which has in that time not change the pattern is NVIDIA. Apparently they recognize that customers may parse this information and rely on it. But of course as we all are open source evangelists it would be completely unacceptable to recommend the use of the NVIDIA driver or to recommend people to buy NVIDIA cards because their driver is bad, bad, bad just by the fact that it is closed!"

This is not the first time open-source drivers have broke with KWin. "Now we all remember the time of the 4.5 release and how the drivers announced support for what they don’t support. At that time the driver developers justified themselves with we should have known better, asked or at least assume that if the drivers say they support version X, that they in fact only support version X-2. Now my question: how should we handle such custom adjustments for broken drivers if the drivers change how they can be recognized?"

The workaround right now for KDE users with the latest Intel Mesa code is to set the KWIN_DIRECT_GL environmental variable to bypass the renderer string checks.

What's nice though about the OpenGL renderer string changes on Mesa master for the 7.11 release is the reporting of the short Git commit hash. This way it's much easier -- in useful cases such as benchmarking -- to immediately keep track of what Git revision the Mesa build currently is on. The driver date has been removed from the renderer string since these driver dates were rarely ever maintained by the developers. This is just not a change for the Intel driver but all of the Mesa drivers. Fortunately, the Phoronix Test Suite isn't solely dependent upon the OpenGL renderer string but has additional GEM checks (such as by some of the GEM sysfs entries) as additional fall-backs for detecting the in-kernel video memory management mechanism.

Latest Linux Hardware Reviews
  1. ASUS AM1I-A: A Mini-ITX Board For Socketed Kabini APUs
  2. Mini-Box M350: A Simple, Affordable Mini-ITX Case
  3. Overclocking The AMD AM1 Athlon & Sempron APUs
  4. AMD Athlon 5350 / 5150 & Sempron 3850 / 2650
Latest Linux Articles
  1. Ubuntu 12.04.4 vs. 13.10 vs. 14.04 LTS Desktop Benchmarks
  2. AMD OpenCL Performance With AM1 Kabini APUs
  3. A Quick Look At GCC 4.9 vs. LLVM Clang 3.5
  4. Are AMD Athlon/Sempron APUs Fast Enough For Steam On Linux?
Latest Linux News
  1. FreeBSD Advances For ARM, Bhyve, Clang
  2. Ubuntu 14.04 LTS "Trusty Tahr" Officially Released
  3. Ubuntu 12.04 LTS vs. 14.04 LTS Server Benchmarks
  4. QEMU 2.0 Released With ARM, x86 Enhancements
  5. Running The Unity 8 Preview Session On Ubuntu 14.04 LTS
  6. R600 Gallium3D Disables LLVM Back-End By Default
  7. Fedora 21 Gets GNOME 3.12, PHP 5.6, Mono 3.4
  8. Fedora Workstation Is Making Me Quite Excited
  9. Maynard: A Lightweight Wayland Desktop
  10. Chromium Browser Going Through Growing Pains In Ubuntu 14.04
  11. KDE 4.13 Is Being Released Today With New Features
  12. Trying Out Radeon R9 290 Graphics On Open-Source
Latest Forum Discussions
  1. Radeon 8000M problematic on Linux?
  2. Updated and Optimized Ubuntu Free Graphics Drivers
  3. Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd
  4. The GNOME Foundation Is Running Short On Money
  5. After Jack Keane, RuseSoft will briing Ankh 3 to Linux through Desura
  6. Suspected PHP Proxy Issue
  7. Change installation destination from home directory
  8. Bye bye BSD, Hello Linux: A Sys Admin's Story