Summary: | media-libs/mesa-amber-21.3.9 install broken | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | acmondor <bugs.gentoo> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kripton |
Priority: | Normal | Keywords: | PATCH |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch for missing __driDriverGetExtensions_i915c symbol |
Description
acmondor
2022-08-24 22:20:11 UTC
Interesting, thanks for testing. You appear to be the first person to have tried it :) I was bit by this as well. Thanks for investigating and fixing! In the end, I returned to llvmpipe since the i915 only supports OpenGL 1.3 and some software just doesn't work with that :/ I also stumbled over this issue when I tried to use mesa-amber for my older laptop in the kitchen. It has an old Intel 855GM chipset, but still useful for browsing websites, writing emails or listening music on Spotify. Rebuilding mesa-amber with the provided patch applied, and adding there two environment variables has also fixed it for me. Works like a charm now. I'm wondering why these changes didn't made it into the portage already? However, many thanks for tracking this issue down. Regards, Marco Has the patch been sent upstream anywhere? I have not attempted to upstream the patch. Actually, I'm not sure that would be appropriate. If the media-libs/mesa-amber ebuild hadn't renamed the .so file the bulk (all?) of the patch would not be required. I understand from the comment in the ebuild that the renaming was done to avoid a comflict with media-libs/mesa:0, but I never understood was why both packages need to be installed. I never had a chance to dig into that and was hoping the original creator of the media-libs/mesa-amber ebuild might shed some light on that. Exactly, the problem is caused by the renaming done in mesa-amber to avoid conflicts with the i915g driver that is still in upstream mesa (i915c supports gen2-3; i915g supports only gen3, so they're not interchangeable).
> # Move i915_dri.so -> i915c_dri.so to not conflict with media-libs/mesa:0.
> for dridir in "${ED}"/usr/lib*/dri; do
> if [[ -e ${dridir}/i915_dri.so ]]; then
> mv ${dridir}/i915{,c}_dri.so || die
> fi
> done
The patch is probably the right thing to do.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=01cb5b2658d9421ab5a35e6a36c29e305e68c8f4 commit 01cb5b2658d9421ab5a35e6a36c29e305e68c8f4 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2023-05-12 17:37:34 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2023-05-12 17:38:25 +0000 media-libs/mesa-amber: Fix loading i915c driver Thanks to Allan Mondor <bugs.gentoo@acmondor.ca> for the patch. Closes: https://bugs.gentoo.org/866425 Signed-off-by: Matt Turner <mattst88@gentoo.org> media-libs/mesa-amber/files/mesa-amber-i915c.patch | 46 ++++++++++++++++++++++ ...r-21.3.9.ebuild => mesa-amber-21.3.9-r1.ebuild} | 4 ++ 2 files changed, 50 insertions(+) |