Public bug reported:

[Impact]

nvidia-dkms-470 fails to build with linux 6.2:

error: ‘struct drm_mode_config’ has no member named ‘fb_base’
  244 | dev->mode_config.fb_base = 0;
      | ^

[Fix]

Change the driver to support also the 6.2 kernel ABI.

[Test case]

With linux 6.2 installed, run:

$ sudo apt install nvidia-dkms-470

[Regression potential]

We may experience regressions in newer kernels (>= 6.2) that are using
nvidia-dkms-470 (source code for previous kernels remain unchanged).

** Affects: nvidia-graphics-drivers-470 (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: nvidia-graphics-drivers-470 (Ubuntu Lunar)
     Importance: Undecided
         Status: New

** Also affects: nvidia-graphics-drivers-470 (Ubuntu Lunar)
   Importance: Undecided
       Status: New

-- 
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/2009246

Title:
  nvidia-dkms-390 FTBS with linux 6.2

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Lunar:
  New

Bug description:
  [Impact]

  nvidia-dkms-470 fails to build with linux 6.2:

  error: ‘struct drm_mode_config’ has no member named ‘fb_base’
    244 | dev->mode_config.fb_base = 0;
        | ^

  [Fix]

  Change the driver to support also the 6.2 kernel ABI.

  [Test case]

  With linux 6.2 installed, run:

  $ sudo apt install nvidia-dkms-470

  [Regression potential]

  We may experience regressions in newer kernels (>= 6.2) that are using
  nvidia-dkms-470 (source code for previous kernels remain unchanged).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2009246/+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