Public bug reported: We are facing an issue that GDM starts with Wayland instead of Xorg, despite of 61-gdm.rules' gdm-disable-wayland for NVIDIA graphics.
The issue happens because gdm-disable-wayland is executed after GDM has started. The reason why the udev rules takes so long is because the the runtime suspended NVIDIA GFX takes more than 1 second to runtime resume, hence the driver starts the probing routine rather late. The proper solution is to impose a barrier like systemd-udev-settle.service before GDM, but limits to the GFX device only to avoid waiting for all udev rules are finished. Since such mechanism isn't available right now, workaround the issue by enabling runtime PM after driver is bound to avoid the runtime resume delay, and hope GDM always starts after the probing is done. Please backport below patch to supported nvidia-drivers: https://github.com/tseliot/nvidia-graphics-drivers/pull/41/commits/7e9e4d4a827dc9da0e27058871034245ae4b7508 ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: Triaged ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1942281 originate-from-1943787 stella ** Tags added: oem-priority originate-from-1942281 stella ** Tags added: originate-from-1943787 ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1949026 Title: System hangs on purple screen Status in OEM Priority Project: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: We are facing an issue that GDM starts with Wayland instead of Xorg, despite of 61-gdm.rules' gdm-disable-wayland for NVIDIA graphics. The issue happens because gdm-disable-wayland is executed after GDM has started. The reason why the udev rules takes so long is because the the runtime suspended NVIDIA GFX takes more than 1 second to runtime resume, hence the driver starts the probing routine rather late. The proper solution is to impose a barrier like systemd-udev-settle.service before GDM, but limits to the GFX device only to avoid waiting for all udev rules are finished. Since such mechanism isn't available right now, workaround the issue by enabling runtime PM after driver is bound to avoid the runtime resume delay, and hope GDM always starts after the probing is done. Please backport below patch to supported nvidia-drivers: https://github.com/tseliot/nvidia-graphics-drivers/pull/41/commits/7e9e4d4a827dc9da0e27058871034245ae4b7508 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1949026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
