Summary: | [i915] media-libs/mesa[classic gallium] causes kde-frameworks/plasma crashes when setted to gallium (opengl >1.4) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrey Aleksandrovich <andrey.aleksandrovich> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Xorg.0.log
Screenshot 1 - normal Screenshot 2 - artifact |
Description
Andrey Aleksandrovich
2018-09-01 12:00:59 UTC
Created attachment 545710 [details]
Xorg.0.log
Created attachment 545712 [details]
Screenshot 1 - normal
Created attachment 545714 [details]
Screenshot 2 - artifact
I can not see which package is the root of the trouble. please try with <= media-libs/mesa-18.2.0_rc4 There were several diffuse bug reports about mesa recently. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product and name the related package in the summary. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/ It's definitely media-libs/mesa. Earlier I had =media-libs/mesa-17.3.9, and there was mesa module at eselect list and I could switch between classic(no problems)/gallium(all described problems). At =media-libs/mesa-18.1.6 I couldn't switch, Opengl-2.1 is hard-selected. Now, I upgrade to =media-libs/mesa-18.2.0_rc5, Opengl 1.4 is hard-selected. Use flags "classic" and "gallium" are enabled in all cases. Accordind to https://wiki.gentoo.org/wiki/Intel#Feature_support Opengl 2.1 is possible with my GPU. In the following commit I changed the default i915 driver to classic if both classic and gallium are enabled: commit c38db89c56279684dce2769dad09d23a4ed2cc8f Author: Matt Turner <mattst88@gentoo.org> Date: Tue Aug 14 13:29:55 2018 -0700 media-libs/mesa: Default to classic i915 The new meson build system does not like it if you ask it to build both the classic and gallium versions of i915 and fails to configure. If both classic and gallium are enabled build only the classic i915 driver since it is better supported and supports more hardware. Closes: https://bugs.gentoo.org/663400 media-libs/mesa/mesa-18.2.0_rc2.ebuild | 12 ++++++++---- media-libs/mesa/mesa-9999.ebuild | 12 ++++++++---- 2 files changed, 16 insertions(+), 8 deletions(-) i915 hardware is really terrible. Both classic and gallium i915 drivers are really terrible. The hardware does GL 2.1 only in the crappiest possible way -- by saying "yeah, we support XYZ feature but with 0 bits of precision". In upstream commit commit a1891da7c865c80d95c450abfc0d2bc49db5f678 Author: Matt Turner <mattst88@gmail.com> Date: Sun Jan 29 18:20:10 2017 -0800 Revert "i915: Always enable GL 2.0 support." This partially reverts commit 97217a40f97cdeae0304798b607f704deb0c3558. It leaves ES 2.0 support in place per Ian's suggestion, because ES 2.0 is designed to work on hardware like i915. Chrome only uses the GPU if you have GL >= 2.0, and using i915 (and prog_execute) actually hurt performance compared with the software paths. I reverted the patch that enabled GL 2.0 "support" on i915 because it actually made the user experience worse. That commit has been in Mesa since 17.1.0. I don't know how GL 2.1 would have been exposed in 18.1.6. That doesn't seem possible with the classic driver, and it sounds like the gallium driver was pretty broken for you. I'm not really sure what I can do to improve the situation. Both the hardware and drivers really suck. Also, I fixed the wiki page to say Gen3 only supports GL 1.4. Please reopen if/when you respond. (In reply to Matt Turner from comment #6) > I'm not really sure what I can do to improve the situation. Both the > hardware and drivers really suck. Maybe will be better to bring back the ability to switch gallium/classic via eselect? I have a similar issue. I have an old pc with i915 and works perfectly until i upgraded. Now i am hitting a issue with gallium that doesnt happened in classic. I want mesa eselect back if possible. If that is not possible... I will fill an issue to mesa to fix gallium Driver. Anyways... To bring back 2.0 in i915... You need yo config dri https://cgit.freedesktop.org/mesa/mesa/commit/?id=a1891da7c865c80d95c450abfc0d2bc49db5f678 You need to activate fragment shader and occlusion query. (In reply to mercuriete from comment #10) > I will fill an issue to mesa to fix gallium Driver. This makes sense anyway. (In reply to Andrey Aleksandrovich from comment #9) > (In reply to Matt Turner from comment #6) > > > I'm not really sure what I can do to improve the situation. Both the > > hardware and drivers really suck. > > Maybe will be better to bring back the ability to switch gallium/classic via > eselect? No, sorry. I'm not going to readd that complexity for i915. Again, I don't know what I can do here. i915 hardware sucks. i915 drivers suck. You have two options. If your build configuration is now defaulting the other driver, then just switch. I don't know what I can do. Well, mercuriete, all the hope for you. CANTFIX, and I still don't know how GL 2.1 would have been exposed in 18.1.6. |