desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #125338
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Friends, are you kidding? It is enough, please do not pollute this thread
any longer! If you wonder anything, please google it first. If you cannot
find anything, open a new issue in a related place. Be more responsive
please!
Sorry, I have also made dirty the mail thread but these were necessary to
tell.
Scroll to the very bottom and follow the link
Sent from my Sprint Samsung Galaxy S® 6.-------- Original message --------
From: Umut Yazgan <umut.yaz@xxxxxxxxx>
Date: 06/19/2015 6:06 AM (GMT-07:00)
To: zewbie@xxxxxxxxx
Subject: Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer
violation
Hello how can I unsubscribe this?
On Jun 16, 2015 13:41, "Alberto Milone" <alberto.milone@xxxxxxxxxxxxx>
wrote:
> I am already working on it (I've been busy with other work). There's no
> need to make this any more complicated than it needs to be.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1395993).
> 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:
> Confirmed
> Status in nvidia-graphics-drivers-340-updates source package in Trusty:
> Confirmed
> Status in nvidia-graphics-drivers-346 source package in Trusty:
> Confirmed
> Status in nvidia-graphics-drivers-346-updates source package in Trusty:
> Confirmed
>
> 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
>
--
You received this bug notification because you are subscribed to a
duplicate bug report (1382608).
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:
Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
Confirmed
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
--
You received this bug notification because you are subscribed to a
duplicate bug report (1404624).
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:
Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
Confirmed
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
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates 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:
Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
Confirmed
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
References