group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1717151@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package nvidia-graphics-drivers-384 -
384.111-0ubuntu0.17.10.1

---------------
nvidia-graphics-drivers-384 (384.111-0ubuntu0.17.10.1) artful; urgency=medium

  * SECURITY UPDATE:
    - CVE-2017-5753 (LP: #1741807).
  * New upstream release:
    - Added support for the following GPUs:
      o GeForce MX130
      o GeForce MX110
      o GeForce GTX 1050 Ti with Max-Q Design
      o Quadro P500
    - Fixed a regression that prevented displays connected via some
      types of passive adapters (e.g. DMS-59 to VGA or DVI) from
      working correctly. The regression was introduced with driver
      version 384.98.
    - Fixed a bug that caused Quadro M2200 GPUs to enter the lowest
      available PowerMizer performance level when under load.
  * debian/templates/control.in:
    - Add Replaces/Conflicts/Provide for libcuda-9.0-1.
      Thanks to Graham Inggs for his contribution.
  * debian/templates/dkms_nvidia.conf.in:
    - Drop buildfix_kernel_4.14.patch.

 -- Alberto Milone <alberto.milone@xxxxxxxxxxxxx>  Mon, 08 Jan 2018
15:46:54 +0100

** Changed in: nvidia-graphics-drivers-384 (Ubuntu Artful)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1717151

Title:
  driver installation might not build initramfs then cause dark screen
  after switching to nvidia

Status in OEM Priority Project:
  Fix Released
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Zesty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  When power saving mode is enabled, the initramfs will not be update, thus leading to a potential API mismatch between kernelspace and userspace.

  [Test Case]

  1) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  2) Enable the -proposed repository, and install the new "nvidia-384"

  3) Check that the initramfs is updated.

  4) Restart your computer and see if the driver works correctly (you
  should be able to access the desktop session)

  [Regression Potential]
  Low, as updating the initramfs is always the (intended) default behaviour.
  _______________________________

  Note: without fix be landed , nvidia driver online update could be
  failed.

  nvidia-375.postinst not always build initramfs by default:
  "
          ALTERNATIVE=$(readlink /etc/alternatives/x86_64-linux-gnu_gl_conf)
          if [ "$ALTERNATIVE" = "/usr/lib/nvidia-375/ld.so.conf" ]; then
              # Update initramfs so that the blacklist ends up in the initramfs
              if [ -x /usr/sbin/update-initramfs ]; then
                  /usr/sbin/update-initramfs -u
  "

  it the case of user who are using intel then update driver from
  nvidia-375.20 to nvidia-375.82 will get screen dark after prime-select
  nvidia later.

  syslog:
  "
  NVRM: loading NVIDIA UNIX x86_64 Kernel Module 375.20 Tue Nov 15 16:49:10 PST 2016 (using threaded interrupts)
  ......
  NVRM: API mismatch: the client has the version 375.82, but
  NVRM: this kernel module has the version 375.20. Please
  NVRM: make sure that this kernel module and all NVIDIA driver
  NVRM: components have the same version.
  "

  The root cause is the nvidia kernel module in initramfs not be updated
  in this case.

  impacted issues:
  LP: #1653592

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1717151/+subscriptions