Dear hivemind, forgive the fact that I’ve been spoiled by 10+ years of graphics “just working” automatically on Fedora… but how do I actually tell a Fedora machine to “use the i915g driver” instead of the classic i915 driver?
The reason is that I’m trying to check if this Mesa bug (that causes any GTK4 application to instant-crash on systems from the Core2 era, with GMA 3100 graphics for example) is solved by using a different driver, if Fedora is not already using i915g by default. I’ve looked everywhere on the interwebs and could not find any trace of someone asking this question, or documentation on how to do that. If it does make it work, then I would suggest Fedora uses it by default, but I’m not sure where to formally request that.
Really not sure. Is the other driver packaged and available? Usually loading drivers with modprobe does the job? I guess you could blacklist the one you don’t want to use similar to how folks blacklist nouveau when they use the nvidia proprietary driver?
In mesa 22.0 the classic i915 driver has been removed, so newer releases are using i915g. For now you can test it at your own risk by using some copr repo with fresh mesa. In koji there’s only one build for fc37.
Ah, so if I’m interpreting the situation correctly, it seems the upcoming Fedora 36 has mesa 21.3.8 like F35, and it likely still uses i915 instead of i915g? Oh boy, that doesn’t bode well for people using such chipsets as they will encounter those increasingly-numerous insta-crashing GTK4 apps in F36
I’ve no idea what COPR to be looking for though, xxmitsu/mesa-git Copr seems to be the first result that turns up in search engines and the warnings on that page are a bit scary; it seems to have mesa 22.1 in there however, so I presume this would pretty much guarantee that it’s using i915g
Mesa 22.0 will hit F36 soon, probably after it’s release. F35 might not be that lucky.
This repo contains an in-development packages (mesa-git), it’s safer to use released stable versions.
Looking at build from calcastor/mesa Copr, this should be your best bet for now, it’s built from official fedora source:
Keep in mind that it’s the first major release with new features and there’ll be minor releases with bugfixes later.
To be sure, you’d have to check build log (available in copr) for configuration summary (like the one I posted before), if there’s i915 listed in Gallium drivers, you’re guaranteed it’s built. If it’s not built, system will fall-back to software rendering, slower but fully-featured and less buggy than i915.
In case this helps anyone reading this, I tested the F36 beta liveUSB today and it is indeed affected by this bug. I will have to wait some time during the summer, after the F36 release and its post-release updates, to try installing it to a spare test drive to test the machine again; my assumption is that until Mesa 22 is proven to solve the problem, all GTK4 apps will be broken for anyone running i915-based GPUs.
I unfortunately hadn’t gotten around to filing it on Fedora’s Bugzilla yet; I originally filed it in gnome-shell/gnome-shell-extensions-prefs, then was bounced to report the issue in GTK, then was bounced to freedesktop/mesa to file a ticket there that ended up a dead-end (for now), then eventually made it here in a last-ditch attempt at investigating/testing this, to maybe get back to the mesa ticket if the i915g driver happens to be similarly affected… and only recently with the beta live image was I able to check if the issue was still occurring (and I was not able to do much except check there, except run lsmod where it seems the “i915” module is loaded, so I’ll presume it’s not using i915g even with mesa 21). I’m unsure if the final release will be affected. What component should this be filed on in Bugzilla, “mesa” I presume?
I see that there is https://bodhi.fedoraproject.org/updates/FEDORA-2022-4120f31977 in the pipeline now though, so maybe this could solve it (fingers crossed). However, I am unable to test it because that would require a fully upgraded install of F36 beta + test updates, and… you’re going to either laugh or cry at this @mattdm, but Anaconda refuses to start on that machine with the F36 beta liveUSB It launches but then shows up only as a black screen and sits there. Same thing if launched with sudo anaconda from a terminal, and the terminal gives no errors (only atk-bridge warnings). If launched as root (after su in a terminal), then it crashes on startup. And yet, as far as I know, that application is not even GTK4, so maybe I found a wholly different issue now. I guess I’ll try grabbing the resulting 800 MB core dump file that was created in /tmp when run as root, and attach the resulting 15 MB compressed version to a Bugzilla ticket on Anaconda.
So, to recap, GTK4 apps crash on startup in the F36 beta liveUSB, it seems Mesa updates are coming that might (or might not) solve the issue, but I can’t test them in the current state of things… and I may have found an issue that makes the installer unusable on those machines, unless it’s somehow related.
I believe my post right here should give some evidence of Mesa 22 working just fine for i915 on Fedora 36. Are you able to upgrade to Fedora 36 and try it out on your hardware? I have some older hardware here I can possibly bring out, but this looks like a viable test AFAICT for the original post and the mesa issue link.
I think my GPU here is likely close enough to be a useful test for this, but I almost certainly have access to this specific GPU at work. If it’s urgent for Fedora 36, I can try to locate some hardware to test it out early next week.
i915 in your screenshot is the kernel module, not mesa driver (Gen 3 Core CPU has Gen 7 Intel GPU - currently supported by crocus driver that replaced i965 classic driver).
i915 mesa driver supports Gen 2 and Gen 3 Intel GPUs (in early Core CPUs, Pentium 4 and some earlier): intel - Gentoo Wiki
From what I see, with mesa 22 i915 classic has been dropped and i915g isn’t built by default, so building it might fix the anaconda issue.