Hello jeremyszu, or anyone else affected, Accepted ubuntu-drivers-common into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.2.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Description changed: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. + * install nvidia-450 on nvidia-450 supported system. + * prime-select on-demand + * <CHECK THAT ON-DEMAND HAS STUCK> + [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. - --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * <CHECK THAT ON-DEMAND HAS STUCK> [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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