← Back to team overview

desktop-packages team mailing list archive

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 

This fix works for me although I could not properly test any 3D
applications. My Steam client is acting weird and does not see my
installed games anymore, complaining about partition being non-
executable. Also it was hanging at after entering password. I had to
create a new user and start fresh.

Hardware: GTX 770M with 3GB on Asus G751-JX laptop.

Here are simple steps to test without getting too much into "proposed": (for 14.04)
1) Run "Software & Updates" application, 
2) Click on "Updates" tab,
3) Tick on "Pre-release updates (trusty-proposed)" and hit Close button.
4) Authorize the change and close. It will ask for refreshing software information. Hit Reload and allow this.
5) Run the same app again on item 1 above and go to "Additional Drivers" tab. Now you should see 346 and 340 builds. Chose what you need and hit "Apply Changes"
6) After you are done, reboot first to test. You can repeat steps 1-3 again and disable proposed in order to avoid installing proposed packages for other applications.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Committed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions