You may remove yourself from this thread at anytime, since you have seemed to have resolved this issue thanks and all the best.
Sent from my Sprint Samsung Galaxy S® 6.-------- Original message --------
From: Jonners59 <email address hidden>
Date: 06/19/2015 5:49 AM (GMT-07:00)
To: <email address hidden>
Subject: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer
violation
Please stop this banter, clogging my emails up.
I sorted my PCs and laptops out with the following fix for now. Not had
ANY issues since doing below:
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.
You may remove yourself from this thread at anytime, since you have seemed to have resolved this issue thanks and all the best.
Sent from my Sprint Samsung Galaxy S® 6.-------- Original message --------
From: Jonners59 <email address hidden>
Date: 06/19/2015 5:49 AM (GMT-07:00)
To: <email address hidden>
Subject: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer
violation
Please stop this banter, clogging my emails up.
I sorted my PCs and laptops out with the following fix for now. Not had
ANY issues since doing below:
Card driver www.nvidia. co.uk/Download/ index.aspx? lang=en- uk
http://
nVidia
Boot and after GRUB…
Control+ALT+F1
Sudo su
sudo update-pciids
sudo lspci -v -s 01:00.0
Sudo service lightdm stop (stopping lightdm)
sudo apt-get clean && apt-get autoclean && apt-get autoremove (a little cleaning)
sudo apt-get update && apt-get install –f (update source and fix)
sudo apt-get purge libvdpau-va-gl1 bumblebee* nvidia*
OR
dpkg -l | grep nvidia
lists everything installed for nvidia
then remove everything except
nvidia-cg-toolkit (if it or equivellent exists)
nvidia-common
sudo apt-get purge nvidia-xxxx (where xxxx is anything from the list)
sudo apt-get autoremove xxx-updates- uvm (install nvidia-xxx where xxx is driver version: 304, 331, 340, 349, 352 or current)
sudo dpkg-reconfigure nvidia-common (should return a message does not exist)
sudo apt-get install nvidia-352 nvidia-settings nvidia-prime nvidia-current nvidia-cg-toolkit nvidia-common
OR
Sudo apt-get install --reinstall nvidia-
sudo apt-get install xserver- xorg-video- nouveau generic linux-gnu_ gl_conf
sudo apt-get install linux-headers-
sudo apt-get clean && apt-get autoclean && apt-get autoremove
sudo apt-get apt-get upgrade && update && apt-get install –f
sudo update-alternatives --config x86_64-
sudo ldconfig -n
sudo update-initramfs -u
sudo shutdown –r now
Let the devs get on and do perm fix in the meantime.
-- /bugs.launchpad .net/bugs/ 1431753
You received this bug notification because you are subscribed to a
duplicate bug report (1382608).
https:/
Title:
Nvidia binary driver FTBS due to DKMS layer violation
Status in nvidia- graphics- drivers- 331 package in Ubuntu: graphics- drivers- 331-updates package in Ubuntu: graphics- drivers- 340 package in Ubuntu: graphics- drivers- 340-updates package in Ubuntu: graphics- drivers- 346 package in Ubuntu: graphics- drivers- 346-updates package in Ubuntu: graphics- drivers- 331 source package in Trusty: graphics- drivers- 331-updates source package in Trusty: graphics- drivers- 340 source package in Trusty: graphics- drivers- 340-updates source package in Trusty: graphics- drivers- 346 source package in Trusty: graphics- drivers- 346-updates source package in Trusty:
Confirmed
Status in nvidia-
Confirmed
Status in nvidia-
Fix Released
Status in nvidia-
Fix Released
Status in nvidia-
Fix Released
Status in nvidia-
Fix Released
Status in nvidia-
Triaged
Status in nvidia-
Triaged
Status in nvidia-
Confirmed
Status in nvidia-
Confirmed
Status in nvidia-
Confirmed
Status in nvidia-
Confirmed
Bug description: 340-updates- uvm.
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-
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: /bugs.launchpad .net/ubuntu/ +source/ nvidia- graphics- drivers- 331/+bug/ 1431753/ +subscriptions
https:/