Bug 1657660

Summary:	remove udev rule for nvidia binary driver
Product:	Red Hat Enterprise Linux 8	Reporter:	Tomas Pelka <tpelka>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	hdegoede, jadahl, jkoten, kem, mclasen, mmcgrath, rstrode, tpopela, wchadwic, zhguo
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-01 07:31:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1639782, 1656905, 1656926, 1656932, 1662087, 1663440, 1676573, 1676585, 1681782
Bug Blocks:	1701002, 1739559

Description Tomas Pelka 2018-12-10 08:58:12 UTC

Description of problem:
Just do not forget to remove gdm udev rule for nvidia binary driver before GA.

Version-Release number of selected component (if applicable):
gdm-3.28.3-11.el8

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 18 Guo, Zhiyi 2019-01-24 06:40:14 UTC

So anyone is looking at Bug 1662112 - Enable wayland desktop session cause gnome-shell crash in dual nvidia gpu system ? I see halfline is working on Bug 1662087 - Desktop on secondary vga is broken already.
Multiple nvidia GPUs inside rhel guest should be an important user case to our virt team,see https://www.redhat.com/en/blog/red-hat-virtualization-supporting-multiple-nvidia-virtual-gpu-workflows-virtualized-environment, Redhat is the first one that support multiple nvidia gpus inside guest.

Comment 31 RHEL Program Management 2021-02-01 07:31:05 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.