desktop-packages team mailing list archive

[mat <drmtiede@xxxxxxxxx>]

What I don't understand, the proposed drivers are they already implemented
in the routine update (I thought they had to be updated manually)?
Otherwise I might have had a completely different problem with the
bumblebee and nvidia drivers, solved by chance with Your approach.

2015-07-27 18:33 GMT+02:00 KennoVO <ubuntu@xxxxxxxxx>:

> Mat, I am happy you got past your blank-screen problem, even though the
> things mentioned in my previous post may or may not have played a role
> in solving it.
>
> To be perfectly clear toward other people who come across this
> discussion, the points (1)-(4) in my previous post DO NOT represent a
> step-by-step solution for getting a graphical desktop back after running
> a routine kernel upgrade. They are a few things *I* tried for the
> specific case of APPLYING THE DRIVERS FROM TRUSTY-PROPOSED TO AN
> EXISTING BUMBLEBEE SETUP. And it's quite likely some of them are not
> useful or even harmful.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1411919).
> 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
>


-- 
Dr. M. Tiede


Clausola di Riservatezza

Si fa presente che tutte le notizie (nomi, fatti, notizie sanitarie, etc)
contenute in questo messaggio sono sottoposte alla normativa sulla tutela
della riservatezza (D. Lgs 196/2003) e in particolare sulla tutela dei dati
sensibili. E' pertanto richiesta ai destinatari della presente la massima
riservatezza nel trattare la documentazione. Se il ricevente non è il
destinatario diretto del presente messaggio è pregato di contattare
l'originario mittente e di cancellare questo messaggio ed ogni suo allegato
dal sistema di posta, sono vietati l'uso, la riproduzione e la stampa di
questo messaggio e di ogni suo allegato, nonché la diffusione del
loro contenuto a qualsiasi altro soggetto.

This e-mail message and any files transmitted with it may contain
confidential information intended only for the person(s) to whom it is
addressed. If you are not the intended recipient, you are hereby notified
that any use or distribution of this e-mail is strictly prohibited: please
notify the sender and delete the original message.

Thank you.

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