Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 716694 - media-libs/mesa-20.0.4 is missing i965 driver
Summary: media-libs/mesa-20.0.4 is missing i965 driver
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-08 13:41 UTC by Risto A. Paju
Modified: 2020-04-08 20:43 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Risto A. Paju 2020-04-08 13:41:05 UTC
After upgrading Mesa to 20.0.4, the driver for my Intel GPU (Sandy Bridge, i3-2310, HD 3000) is gone, and I only get software rendering.

Reproducible: Always

Steps to Reproduce:
1. Start an OpenGL application, such as glxgears

Actual Results:  
Application shows the following error messages 

libGL error: MESA-LOADER: failed to open i965 (search paths /usr/lib64/dri)
libGL error: failed to load driver: i965

and runs slowly with software rendering.

Expected Results:  
Fast, hardware OpenGL rendering

I notice that the file /usr/lib64/dri/i965_dri.so is missing, instead I have /usr/lib64/dri/i915_dri.so.

Mesa has worked mostly as expected up to and including version 20.0.3.

I have also tested both xf86-video-intel and the Xorg modesetting driver, with no change to Mesa behaviour.
Comment 1 Brian Evans (RETIRED) gentoo-dev 2020-04-08 14:10:19 UTC
Please include 'emerge --info media-libs/mesa'
Comment 2 Matt Turner gentoo-dev 2020-04-08 18:06:05 UTC
Did you also update to libdrm-2.4.101 at the same time you updated to mesa-20.0.4?

Can you give a build log of Mesa?

Also the output of `qlist mesa`.
Comment 3 Risto A. Paju 2020-04-08 20:43:31 UTC
Well, this is interesting. I reinstalled mesa-20.0.4 for more debugging and now it works fine, the i965 driver is there.

I suspect that the i915 version came from a different machine. I use a shared /usr/portage for multiple machines and the xpak format for saving binary packages with different USE flags.

Still, Portage should not install binaries with the wrong USE. I share most of my binary packages between machines, but Portage usually compiles them again if I need a different USE set (mostly due to different hardware).

So I apologise for any trouble, this one can be closed. Though I guess another one is in order about Portage...