nvidia-352 driver won't load

Bug #1548309 reported by Conrad Knight
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-352 (Ubuntu)
Confirmed
High
Unassigned

Bug Description

After the latest kernel update for wily, to 4.2.0-29, i can no longer load the nvidia-352 driver. After noticing it was not being loaded on boot, i used `modprobe nvidia` to try loading it manually, and got an error:

> modprobe: ERROR: could not insert 'nvidia_352': Invalid argument

I found the following in my kern.log file:

    Feb 21 19:34:44 inanna kernel: [78265.113976] nvidia: disagrees about version of symbol drm_pci_init
    Feb 21 19:34:44 inanna kernel: [78265.114001] nvidia: Unknown symbol drm_pci_init (err -22)
    Feb 21 19:34:44 inanna kernel: [78265.114133] nvidia: disagrees about version of symbol drm_gem_prime_handle_to_fd
    Feb 21 19:34:44 inanna kernel: [78265.114136] nvidia: Unknown symbol drm_gem_prime_handle_to_fd (err -22)
    Feb 21 19:34:44 inanna kernel: [78265.114178] nvidia: disagrees about version of symbol drm_gem_private_object_init
    Feb 21 19:34:44 inanna kernel: [78265.114180] nvidia: Unknown symbol drm_gem_private_object_init (err -22)
    Feb 21 19:34:44 inanna kernel: [78265.114424] nvidia: disagrees about version of symbol drm_gem_handle_create
    Feb 21 19:34:44 inanna kernel: [78265.114426] nvidia: Unknown symbol drm_gem_handle_create (err -22)
    Feb 21 19:34:44 inanna kernel: [78265.114534] nvidia: disagrees about version of symbol drm_pci_set_busid
    Feb 21 19:34:44 inanna kernel: [78265.114536] nvidia: Unknown symbol drm_pci_set_busid (err -22)
    Feb 21 19:34:44 inanna kernel: [78265.114609] nvidia: disagrees about version of symbol drm_pci_exit
    Feb 21 19:34:44 inanna kernel: [78265.114611] nvidia: Unknown symbol drm_pci_exit (err -22)
    Feb 21 19:34:44 inanna kernel: [78265.114667] nvidia: disagrees about version of symbol drm_gem_prime_export
    Feb 21 19:34:44 inanna kernel: [78265.114669] nvidia: Unknown symbol drm_gem_prime_export (err -22)

I have also booted into kernel 4.2.0-28 and the driver was initially not found (i had been running 4.2.0-27 previously, installed -28, but not bothered to reboot until after the -29 update). I used `apt-get install --reinstall nvidia-352` and then the driver loaded with no problem. I tried the same after booting back into the -29 kernel, but still no luck.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-29-generic 4.2.0-29.34
ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3
Uname: Linux 4.2.0-29-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: conrad 3217 F.... pulseaudio
Date: Mon Feb 22 08:01:26 2016
HibernationDevice: RESUME=UUID=eb2b25c8-5489-484c-b3d1-b0db88311114
InstallationDate: Installed on 2013-02-14 (1102 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-29-generic root=UUID=b2f1b8ee-6793-4070-8eb3-a07e52b30d03 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-29-generic N/A
 linux-backports-modules-4.2.0-29-generic N/A
 linux-firmware 1.149.3
SourcePackage: linux
UpgradeStatus: Upgraded to wily on 2015-10-23 (122 days ago)
dmi.bios.date: 05/02/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.0A
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 181D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 52.18
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.0A:bd05/02/2012:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr078F100000205720000620100:rvnHewlett-Packard:rn181D:rvr52.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: 078F100000205720000620100
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Conrad Knight (iestynapmwg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High
affects: linux (Ubuntu) → nvidia-graphics-drivers-352 (Ubuntu)
Changed in nvidia-graphics-drivers-352 (Ubuntu):
status: Confirmed → New
Revision history for this message
Conrad Knight (iestynapmwg) wrote :

Issue is still present with latest kernel: 4.2.0-30-generic #36-Ubuntu

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-352 (Ubuntu):
status: New → Confirmed
Revision history for this message
J. Cano Tomas (k-jaime) wrote :

Same problem is present in 4.2.0-34-generic #39-Ubuntu and nvidia-361 and even same errormessage for nouveau

Revision history for this message
Eirik Gjerløw (egjerlow) wrote :

The same problem here. Completely uninstalling the intel graphics drivers (https://gist.github.com/phdelodder/b28e8df770a6bc020aab) removed the dmesg error messages and lshw -C display now shows the nvidia driver as loaded, though I still have problems with the display, as none of the regular displays shows up in xrandr. This after upgrading the kernel.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.