desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #131545
[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
> Teo,
> the Optimus issue is definitely a *separate bug*, requiring its own
> resolution.
I was not talking about the optimus issue.
I was talking about the fact that the update of the NVidia drivers overwrote some system settings that shouldn't have been touched. Before the update, my system was set up to not use nVidia drivers; after the update, it was set to use them. That's a bug in the update that was released.
I'm not quite sure whether or not that should be considered a separate
issue, because it is an issue directly caused by the fix to this issue.
That is, the fix to this issue caused a bug of its own.
--
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:
Invalid
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
Invalid
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:
Invalid
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
Invalid
Status in nvidia-graphics-drivers-340 source package in Trusty:
Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
Fix Released
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