With the above build of mesa, hardware accel seems to be completely unavailable for 4 of 4 tested machines (3 intel gfx, 1 AMD gfx), at least in GNOME Wayland: * Intel GMA 4500MHD * Intel Ivy Bridge (HD 4000) * Intel Haswell (HD 5000) * Radeon 300 series Example symptoms: * totem fails with Clutter error including "Missing Cogl context" * gnome-mpv fails with "Failed to initialize opengl-cb" * glxinfo | grep OpenGL shows "OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)" etc. * Gradual fade-in of GNOME's "night light" colour temperature change (on GDM start and session login) is very slow and jerky on a system with a 4k display (suggests software rendering) All previous versions (F27, and all F28 builds from 18.0.0-0.3.rc4.fc28 to 18.0.0-2.fc28.1) work fine. Presumably this is directly related to "Disable build of wayland packages" from the changelog. mesa-libwayland-egl remains installed, on whatever the previous version was before upgrading all the other mesa packages to 18.0.0-3.
Igor can you take a quick look at this. I dropped the wayland packages from mesa after you added the obsoletes for mesa-libwayland to the wayland spec file. Did I miss something?
Today the most recent build of wayland appeared in the repos (it wasn't there using dl.fedoraproject.org directly yesterday) and that build actually obsoleted mesa-libwayland-egl with libwayland-egl (per the changelog - "Make mesa-libwayland-egl obsoleting actually work"). However, upgrading to wayland-*-1.14.93-2 with that replacement libwayland-egl package (and to mesa-*-18.0.0-3) also/still results in software rendering (only tested on one machine, but I'm presuming it'll be the same on the others).
Can you attach the output from this command: LD_DEBUG=files LIBGL_DEBUG=verbose glxinfo
What version of libdrm do you have installed?
The mesa package is not requiring a new enough version of libdrm. That could be the issue here.
libdrm-2.4.91-1.fc28 Do you still need/want the glxinfo debug info?
(In reply to Stephen from comment #6) > libdrm-2.4.91-1.fc28 > > Do you still need/want the glxinfo debug info? Yes.
Created attachment 1418259 [details] glxinfo stdout
Created attachment 1418260 [details] glxinfo stderr
(In reply to Tom Stellard from comment #7) > > Do you still need/want the glxinfo debug info? > > Yes. Attached. So you're not able to reproduce?
(In reply to Stephen from comment #10) > (In reply to Tom Stellard from comment #7) > > > Do you still need/want the glxinfo debug info? > > > > Yes. > > > Attached. > > So you're not able to reproduce? No, I need to get the right kind of system setup. Can you post your xorg.log and/or any wayland logs?
> No, I need to get the right kind of system setup. That's very surprising, I was able to reproduce this on 3 different generations of Intel graphics as well as amdgpu. I also managed to reproduce it on a fresh vanilla install of F28 Beta from live workstation ISO with all default settings (doesn't result in software rendering fallback initially) then upgraded to latest packages incl. mesa-*-18.0.0-3 (fallback occurs).
> Can you post your xorg.log None since 2015 ;) > and/or any wayland logs? Which logs? I'm using GNOME Wayland. There's nothing relevant in /var/log, and the only thing that might be relevant in journald containing either 'wayland' or 'mutter' is pairs of messages like this for a few applications (Evolution, Epiphany etc.): WaylandCompositor requires eglBindWaylandDisplayWL, eglUnbindWaylandDisplayWL and eglQueryWaylandBuffer. Nested Wayland compositor could not initialize EGL And possibly this (not sure if this was when I was trying the above upgrade to libwayland-egl): gnome-shell[2031]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1468]: reference to undefined property "MetaWindowXwayland"
Created attachment 1418518 [details] glxinfo full
Created attachment 1418519 [details] $ journalctl -u gdm
I fresh installed Fedora 28 Beta yesterday on i7-8550U (Kabylake GT1.5) laptop and see exact same issues as mentioned in the first post. $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) OpenGL version string: 2.1 Mesa 18.0.0 Installed a fresh Fedora 27 Live Image on USB and it boots with proper HW acceleration: $ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Kabylake GT1.5 OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.2
Proposed as a Blocker and Freeze Exception for 28-final by Fedora user mikhail using the blocker tracking app because: Many users with Intel and AMD GPU experience this bug. Consequences of this problem: * totem fails with Clutter error including "Missing Cogl context" * gnome-mpv fails with "Failed to initialize opengl-cb" * glxinfo | grep OpenGL shows "OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)" etc. * Gradual fade-in of GNOME's "night light" colour temperature change (on GDM start and session login) is very slow and jerky on a system with a 4k display (suggests software rendering) * Not working games from steam store
+ cheese also crashed https://bugzilla.redhat.com/show_bug.cgi?id=1564796 $ cheese (cheese:20007): Clutter-CRITICAL **: 21:56:10.401: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. ** (cheese:20007): ERROR **: 21:56:10.401: cheese-application.vala:86: Unable to initialize libcheese-gtk Trace/breakpoint trap (core dumped)
Confirm regression, hardware acceleration seems to be completely unavailable. $ lspci -nnk |grep -iA3 "VGA" 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Redwood PRO [Radeon HD 5550/5570/5630/6510/6610/7570] [1002:68d9] Subsystem: ASUSTeK Computer Inc. Device [1043:036c] Kernel driver in use: radeon Kernel modules: radeon
Could it be that disabling wayland support in mesa regressed this? I suspect the wayland support check does more than just controlling whether libwayland-egl gets built. If that's the case, then instead of completely disabling wayland support, should just rm the libwayland-egl library files in %install.
I tested Kalev's suggestion and it fixed the issue for me.
Should be fixed now in https://src.fedoraproject.org/rpms/mesa/c/9f97135799d23da89c2c802f140e4880873ac2de
*** Bug 1564653 has been marked as a duplicate of this bug. ***
*** Bug 1564356 has been marked as a duplicate of this bug. ***
Kalev: can you please submit an update ASAP? This is breaking things for lots of people. Thanks.
mesa-18.0.0-4.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-10fbc1fcf6
(In reply to Adam Williamson from comment #25) > Kalev: can you please submit an update ASAP? This is breaking things for > lots of people. Thanks. Sure, was just waiting for mesa to finish building. Submitted now.
18.0.0-4 (Koji build 1067643) works for me. I also upgraded libwayland-*, which I was holding back to be able to remain on the working mesa-*-18.0.0-2.fc28.1 build previously. Thanks Kalev!
If the update in koji works fine, please give karma for a fastly update...
Discussed during the 2018-04-09 blocker review meeting: [1] The decision to classify this bug as an AcceptedBlocker was made as it violates the following blocker criteria: "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test" [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2018-04-09/f28-blocker-review.2018-04-09-16.01.txt
mesa-18.0.0-4.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-10fbc1fcf6
*** Bug 1565741 has been marked as a duplicate of this bug. ***
mesa-18.0.0-4.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.