I have KDE, and I can't enter "Display and Monitor", "Startup and Shutdown" sections (KDE menu) - plasma crashes. Also I had window KDE menu artifact - right margin appears on the left side of screen (see attachments, first screenshot - normal window, second - window resized to the right). The last problem I have solved by enabling "uxa" flag and disabling "sna" flag at x11-drivers/xf86-video-intel. I have: [ebuild R ] x11-drivers/xf86-video-intel-2.99.917_p20180214-r1::gentoo USE="dri dri3 udev uxa xvmc -debug -sna -tools" [ebuild R ] media-libs/mesa-18.1.6::gentoo USE="classic dri3 egl gallium gbm gles1 gles2 llvm nptl vaapi vdpau wayland xa xvmc -bindist -d3d9 -debug -opencl -openmax -osmesa -pax_kernel -pic (-selinux) -unwind -valgrind -vulkan" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="i915 intel (-freedreno) -i965 (-imx) -nouveau -r100 -r200 -r300 -r600 -radeon -radeonsi (-vc4) -virgl (-vivante) -vmware" # lspci | grep Graphics 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) Earlier I switched mesa by eselect to "classic" instead of "gallium". And there was no artifact or any crashes. But it sets OpenGL to 1.4 which bad for playing video in media-video/mpv and some other applications. After @world upgrade I don't see mesa module at eselect. Reproducible: Always emerge --info Portage 2.3.40 (python 3.6.5-final-0, default/linux/amd64/17.0/desktop/plasma, gcc-7.3.0, glibc-2.26-r7, 4.14.65-gentoo-gnu x86_64) ================================================================= System uname: Linux-4.14.65-gentoo-gnu-x86_64-Intel-R-_Core-TM-2_CPU_U7600_@_1.20GHz-with-gentoo-2.4.1 KiB Mem: 2031276 total, 314784 free KiB Swap: 4194300 total, 4194300 free Timestamp of repository gentoo: Wed, 29 Aug 2018 17:00:01 +0000 Head commit of repository gentoo: 952d646a054017bc467408e3e0697cc34f50dff9 sh bash 4.4_p12 ld GNU ld (Gentoo 2.30 p2) 2.30.0 app-shells/bash: 4.4_p12::gentoo dev-java/java-config: 2.2.0-r4::gentoo dev-lang/perl: 5.24.3-r1::gentoo dev-lang/python: 2.7.14-r1::gentoo, 3.6.5::gentoo dev-util/cmake: 3.9.6::gentoo dev-util/pkgconfig: 0.29.2::gentoo sys-apps/baselayout: 2.4.1-r2::gentoo sys-apps/openrc: 0.34.11::gentoo sys-apps/sandbox: 2.13::gentoo sys-devel/autoconf: 2.13::gentoo, 2.69-r4::gentoo sys-devel/automake: 1.11.6-r3::gentoo, 1.15.1-r2::gentoo sys-devel/binutils: 2.30-r2::gentoo sys-devel/gcc: 7.3.0-r3::gentoo sys-devel/gcc-config: 1.8-r1::gentoo sys-devel/libtool: 2.4.6-r3::gentoo sys-devel/make: 4.2.1-r3::gentoo sys-kernel/linux-headers: 4.13::gentoo (virtual/os-headers) sys-libs/glibc: 2.26-r7::gentoo Repositories: gentoo location: /usr/portage sync-type: rsync sync-uri: rsync://192.168.0.1/gentoo-portage priority: -1000 sync-rsync-extra-opts: sync-rsync-verify-metamanifest: yes sync-rsync-verify-jobs: 1 sync-rsync-verify-max-age: 24 ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="@FREE" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -pipe -march=native" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-O2 -pipe -march=native" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--quiet-build=y --keep-going=y" ENV_UNSET="DBUS_SESSION_BUS_ADDRESS DISPLAY PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs buildsyspkg config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync multilib-strict news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="ftp://172.16.1.1/gentoo-distfiles/ ftp://ftp.vectranet.pl/gentoo/" LANG="en_US.utf8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" LINGUAS="en_US" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git" PORTAGE_TMPDIR="/var/tmp" USE="X a52 aac acl acpi activities alsa amd64 berkdb bluetooth branding bzip2 cairo cdda cdr cli consolekit crypt cups cxx dbus deblob declarative dri dts dvd dvdr emboss encode exif fam flac fortran gdbm gif glamor gpm gtk iconv ipv6 jpeg kde kipi kwallet lcms ldap libnotify libtirpc mad mng modules mp3 mp4 mpeg multilib ncurses nls nptl ogg opengl openmp pam pango pcre pdf phonon plasma png policykit ppds pulseaudio qml qt5 readline sdl seccomp semantic-desktop smp spell ssl startup-notification svg symlink tcpd threads tiff truetype udev udisks unicode upower usb vaapi vdpau vorbis widgets wxwidgets x264 xa xattr xcb xcomposite xml xv xvid xvmc zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon plan sheets stage words" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" GRUB_PLATFORMS="pc" INPUT_DEVICES="evdev" KERNEL="linux" L10N="en-US" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-6 php7-0" POSTGRES_TARGETS="postgres9_5 postgres10" PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python2_7 python3_6" RUBY_TARGETS="ruby23" USERLAND="GNU" VIDEO_CARDS="i915 intel" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CC, CPPFLAGS, CTARGET, CXX, INSTALL_MASK, LC_ALL, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
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.
