I did a little bit of more triaging:
Staying on my
Linux acer07 4.8.0-21-generic #23-Ubuntu SMP Tue Oct 4 18:27:25 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
and only upgrading from "nvidia-304 304.131-0ubuntu5" to "nvidia-304
304.132-0ubuntu1"
brings up this problem.
On the other hand, staying on "nvidia-304 304.131-0ubuntu5" and doing a
complete "apt-get dist-upgrade" otherwise, results in a completely
functioning system.
So looks like this problem is more connected with nvidia-304 versions
than kernel versions.
My workaround is (thanks to BTRFS allowing me to boot into various
snapshots and having the earlier driver version available):
$ cat /etc/apt/preferences.d/nvidia-304_mtrr-prob.pref
Package: nvidia-304
Pin: version 304.132-0ubuntu1
Pin-Priority: -1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1634802
Title:
Could not insert module
Status in nvidia-graphics-drivers-304 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-304 source package in Yakkety:
Triaged
Bug description:
Ubuntu release: 16.10 Yakkety Yak
Kernel version: 4.8.0-22-generic x86_64
Package version: 304.132-0ubuntu1
The nvidia module cannot be loaded. The following errors are reported:
Could not insert module Unknown symbol in module
and:
nvidia: Unknown symbol mtrr_del (err 0)
nvidia: Unknown symbol mtrr_add (err 0)
It looks like the buildfix_kernel_4.3.patch, which is supposed to be
dealing with those calls, is not applied in this release of the
package.
The package was working fine with the previous fully updated Ubuntu
version 16.04 prior to the upgrade to 16.10.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
