On Sun, 10 Jul 2016 21:37:18 +0100 Luca Boccassi <luca.bocca...@gmail.com> wrote: > On Sun, 2016-07-10 at 21:54 +0200, Peter Keel wrote: > > Hi > > > > * on the Sun, Jul 10, 2016 at 08:23:23PM +0100, Luca Boccassi wrote: > > > I am running the same driver with 4.6 from Jessie backports, and I'm not > > > seeing that problem. Are you sure it's not due to the custom kernel? > > > > Pretty sure, as it did work maybe two weeks ago with 4.5.7 and the > > same kernel config. And I also tried to recompile it now with the > > old kernel 4.5.7, it also has no versions anymore. > > > > I think it's something that changed in the toolchain within debian/sid. > > Not necessarily the nvidia-kernel-dkms package (because I didn't > > change that one neither) but that's probably where it would need to > > be mitigated, so I reported the bug there. > > > > > Could you please try with the kernel from the repositories so that we > > > can narrow it down a bit more? > > > > I'll look into that. > > Just tried in a sid chroot with 367.27 from SVN and the latest kernel > headers, all seems fine: > > root@luca-desktop:/# modprobe --dump-modversions > /lib/modules/4.6.0-1-amd64/updates/dkms/nvidia-current.ko > 0xa435bbb2 module_layout > 0x6bc3fbc0 __unregister_chrdev > 0x5150c634 acpi_bus_register_driver
Is this still an issue with latest drivers (375.xx or newer) and kernels? Andreas
