Hi Jeremy,

It's not your fault. This is something your sponsor is supposed to have
checked.

@Alberto

Please could you properly review this, make sure it meets SRU policy,
try to anticipate and answer any questions the SRU team might have in
advance, and then work with Jeremy to resubmit to the queue? It's not
good enough just to sponsor and leave - for example in this case it'd
just get lost because Jeremy isn't aware that the upload needs to be
resubmitted. You need to stick with your sponsorees all the way through
until SRUs land in -updates and no regressions have been found please.

-- 
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:
  Triaged
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.

  [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.

  ---

  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

Reply via email to