This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2107102 - i915_dri.so is missing from mesa-dri-drivers-21.3.4-2.el9
Summary: i915_dri.so is missing from mesa-dri-drivers-21.3.4-2.el9
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: mesa
Version: 9.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Dave Airlie
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-14 11:04 UTC by th1nhhdk
Modified: 2023-09-11 17:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-11 17:12:49 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-2981 0 None Migrated None 2023-09-11 17:12:32 UTC
Red Hat Issue Tracker RHELPLAN-127687 0 None None None 2022-07-14 11:07:50 UTC

Description th1nhhdk 2022-07-14 11:04:08 UTC 
Description of problem:
i915_dri.so is missing from mesa-dri-drivers-21.3.4-2.el9, causes gnome to use llvmpipe instead of Intel HD Graphics on Intel® Pentium(R) CPU G3260

Version-Release number of selected component (if applicable):
21.3.4-2.el9

How reproducible:
maybe?

Steps to Reproduce:
1. Use a 4th gen Intel CPU without any external graphic cards
2. Install RHEL9 with "Workstation" configuration
3. Open gnome-control-center, go to "About" section, Graphics line should say llvmpipe

Actual results:
It shows llvmpipe and gnome use CPU rendering which cause it to be slow

Expected results:
Should show "Intel® HD Graphics (HSW GT1)"

Additional info:
Workaround: Downgrade mesa-dri-drivers and mesa-filesystem to 21.3.4-1.el8 with sudo dnf install "https://dl.rockylinux.org/pub/rocky/8/AppStream/x86_64/os/Packages/m/mesa-filesystem-21.3.4-1.el8.x86_64.rpm" "https://dl.rockylinux.org/pub/rocky/8/AppStream/x86_64/os/Packages/m/mesa-dri-drivers-21.3.4-1.el8.x86_64.rpm"
Comment 1 Dave Airlie 2022-07-18 20:54:03 UTC 
it's not missing i915_dri.so but I think it's messed up i965/crocus installation.

centos stream 9 should have the fixes already, and should be fixed in 9.1
Comment 2 th1nhhdk 2022-07-19 00:56:18 UTC 
(In reply to Dave Airlie from comment #1)
> it's not missing i915_dri.so but I think it's messed up i965/crocus
> installation.
> 
> centos stream 9 should have the fixes already, and should be fixed in 9.1

As of mesa-dri-drivers-22.1.1-1.el9 from CentOS Stream 9 the problem isn't fixed `rpm -ql mesa-dri-drivers-22.1.1-1.el9.x86_64.rpm | grep i915` returns nothing
Comment 3 Dave Airlie 2022-07-25 21:41:54 UTC 
The driver isn't called i915_dri.so for this hardware. It used to be called i965_dri.so and now it's called crocus_dri.so

If it's fixed isn't on the contents of the package, but whether it actually works on the originally reported hardware.
Comment 4 Christian Dersch 2022-07-28 09:16:02 UTC 
Crocus is missing from EL9 (checked CentOS Stream 9) mesa-dri-drivers, looks like only CentOS Stream 8 contains Crocus now.
Comment 5 Phil Baker 2022-11-03 22:32:16 UTC 
I just installed CentOS Stream 9 from the 1 November 2022 ISO image. It contained the Crocus driver and enabled fully-accelerated Wayland out of the box on my Intel NUC Essentials PC, with Pentium Silver N6005 CPU and Intel UHD Graphics.

I did not have this experience with RHEL 9.0, it appeared to be using llvmpipe, screen tearing with moving windows, software cursor, and no Wayland session available. When I tried installing CentOS Stream 9 using an install ISO from December 2021, I couldn't get Anaconda GUI to start. 

My CPU/GPU: https://www.intel.com/content/www/us/en/products/sku/212327/intel-pentium-silver-n6005-processor-4m-cache-up-to-3-30-ghz/specifications.html

So, much progress to report. With CentOS Stream 9 now fully accelerated on my Intel GPU, I would assume the same will hold true for the forthcoming RHEL 9.1 release.
Comment 6 Iuri Gules 2022-11-29 21:28:08 UTC 
The same is happening with r600_dri.so
Comment 7 RHEL Program Management 2023-09-11 15:01:58 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8 RHEL Program Management 2023-09-11 17:12:49 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.