Bug#826712: [nvidia-legacy-304xx-kernel-dkms] Does not build for kernel 4.6.0-1, -rt (also 4.4.0-1-rt)

David Baron d_baron at 012.net.il
Wed Jun 8 10:13:35 UTC 2016


On Wednesday 08 June 2016 10:46:25 Luca Boccassi wrote:
> Control: tags -1 pending
> 
> On Wed, 2016-06-08 at 11:41 +0300, David Baron wrote:
> > Package: nvidia-legacy-304xx-kernel-dkms
> > Version: 304.131-4
> > Severity: normal
> > 
> > --- Please enter the report below this line. ---
> > Newly installed kernels and  headers 4.6.0-1 and 4.6.0-1-rt, the driver
> > did
> > not build.
> > Including error log:
> > /var/lib/dkms/nvidia-legacy-304xx/304.131/build/make.log
> > 
> > Notes.
> > 1. Had this problem previously, corrected in newer kernel updates for
> > version.
> The updates to fix the build in 4.6 are in the SVN repo pending uploads
> to unstable.
Great!

> > 2. The 4.4.0-1-rt version did not build. May assume log was similar. Do
> > not
> > have the old ones.
> 
> If memory serves, I think we already discussed supporting -rt and
> decided not to, due to the need for massive and very invasive changes
> and patches that would be needed. Unfortunately the time and resources
> we have is limited so we have to pick our battles.
True. I remember editing sources to do so in the "distant" past (simple stuff, 
however).

The only reason I am using the nvidia-legacy is problems in KDE, Iceweasel 
hangups and segfaults. Responders to these bugs said forget Nouveau, which BTW 
I do like, and go to the proprietary NVidia. May or may not still be the case.

At one time, I had boot command lines to choose Nvidia vs Nouveau, but things 
have changed, i.e. systemd, no more Xorg.conf, etc. If someone could tell me 
how to accomplish this now, I would be a happy camper. Apparently, a blacklist 
file is all that controls whether or not the included Nouveau driver is 
activated. Simply a missing nvidia driver dkms update will produce an error.



More information about the pkg-nvidia-devel mailing list