desktop-packages team mailing list archive

[KennoVO <ubuntu@xxxxxxxxx>]

Fix confirmed on 2 very different machines both running Ubuntu 14.04
"Trusty" with the 3.13 kernel. Detailed notes:

AMD workstation with only a discrete nvidia GPU (nothing else)
====================================================
Synaptic complained about conflicts when selecting updated driver from trusty-proposed (something involving nvidia-libopencl1-* vs nvidia-opencl-icd-* IIRC). Installing through aptitude worked better. No further issues when rebooting, updating the kernel and rebooting again.

Intel laptop running bumblebee
==========================
Blank screen after updating. Solutions tried:
(1) starting the kernel with nogpumanager and removing /etc/X11/xorg.conf generated by gpu-manager
(2) removing the newly created file /etc/prime-discrete
(3) sudo sed -i 's/-current/-346-updates/g' /etc/bumblebee/bumblebee.conf
(4) adding lines for 340 and 346 to /etc/modprobe.d/bumblebee.conf

Applying all of the above fixed the problem, and (1)-(3) without (4)
didn't, so it's very likely that (4) is necessary. What I cannot tell is
which of (1)-(3) are also necessary and which are optional.(*) Bottom
line is that special precautions should be taken to prevent bumblebee
from breaking when rolling this out.

(*) I could of course figure that out by reverting the changes one-by-
one, but this bug already robbed me of an outrageous amount of my time
and all of my goodwill, so you're on your own. Thanks a lot for finally
fixing it, though.

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