nvidia-331-uvm 331.113-0ubuntu0.0.4: nvidia-331-uvm kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers-331 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hello,
The nvidia-331 kernel module couldn't build during upgrading from kernel 3.13 to 4.0.4. The error messages pop up during the installation of the dpkg of the .deb files for kernel 4.0.4. Actually there are error messages for all the proprietary packages, i.e. nvidia-331 and bcmwl 6.30.223.141 (the installation is looking for 6.30.223.248 which I do not use - I file a separate bug report for that one).
I have tried to prevent those complications by priorly installing the build-essential package, but it did not help. Would it change something if I was unselecting the two proprietary packages from the Software admin prior to installing the new kernel, and then reinstalling after rebooting under the new kernel ?
Meanwhile, I'll see if I am more lucky with another kernel, like 3.18 for my upgrade.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331-uvm 331.113-
ProcVersionSign
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
DKMSKernelVersion: 4.0.4-040004-
Date: Wed May 27 00:30:11 2015
DuplicateSignature: dkms:nvidia-
InstallationDate: Installed on 2015-05-25 (1 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageVersion: 331.113-
SourcePackage: nvidia-
Title: nvidia-331-uvm 331.113-
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Hello,
Now I would like to report that after first reboot after kernel upgrade, my screen came up without any problem, even with my Fn left/right button for brightness fully functional (my modification made under previous kernel in /etc/default/grub were carried out neatly too without further intervention from me) !
So the warnings concerning the module nvidia-331 during kernel upgrade seem not to be an issue after all. Therefore I suppose this bug is solved.