nvidia proprietary dkms module builds but doesn't load

Bug #1845269 reported by Steve Conklin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-signed-hwe (Ubuntu)
New
Undecided
Unassigned

Bug Description

This is a freshly installed 18.04.3 system.

lspci -vv output for the video card:
02:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 440] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 440]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 30
 Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at e8000000 (64-bit, prefetchable) [size=128M]
 Region 3: Memory at f0000000 (64-bit, prefetchable) [size=32M]
 Region 5: I/O ports at e000 [size=128]
 Expansion ROM at 000c0000 [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: nouveau
 Kernel modules: nvidiafb, nouveau

I'll attach the driver install and build logs

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.0.0-29-generic 5.0.0-29.31~18.04.1
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 24 16:58:42 2019
InstallationDate: Installed on 2019-09-24 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Steve Conklin (sconklin) wrote :
Revision history for this message
Steve Conklin (sconklin) wrote :

purging all nvidia* and libnvidia* packages and rebooting restores operation on Nouveau

Revision history for this message
Alberto Milone (albertomilone) wrote :

Hi Steve, it looks like you are using drivers from a PPA (I can tell because the version is 390.129-0ubuntu0~gpu18.04.1), and that, perhaps, the nouveau driver is still loaded (?).

Can you attach the output of "journalctl -S today" and your /var/log/gpu-manager.log after reproducing the problem, please?

Revision history for this message
Steve Conklin (sconklin) wrote :

Thanks, Alberto

Yes, I'm using this PPA:
$ cat /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-bionic.list
deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic main

Attaching the other requested output.

Revision history for this message
Steve Conklin (sconklin) wrote :

Thanks, Alberto

Yes, I'm using this PPA:
$ cat /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-bionic.list
deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic main

Attaching the other requested output.

Revision history for this message
Steve Conklin (sconklin) wrote :
Revision history for this message
Alberto Milone (albertomilone) wrote :

For some reason, the nouveau kernel module is being loaded, whereas it should be blacklisted (gpu-manager.log says otherwise, though).

Did you collect the output of "journalctl -S today" after reproducing the problem? (if not, please do)

Also, I noticed that you are using Secureboot. It is another potential source of failure.

Revision history for this message
Steve Conklin (sconklin) wrote :

Yes, the output of "journalctl -S today" was attached.

During installation, Secureboot was made a necessity for including non free package repositories.

Revision history for this message
Steve Conklin (sconklin) wrote :

Thanks for mentioning Secureboot, I was able to fix the problem.

During installation of 18.04, I selected the option to enable Secureboot, and it enabled "Windows" as the secureboot OS in the BIOS. After I went back into the BOIS config and changed the Secureboot OS to "Other", I was presented with teh dialog to enter the key at boot, and once I did that everything worked.

Revision history for this message
Steve Conklin (sconklin) wrote :

Feel free to close this or whatever. Thanks!

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.