nvidia-graphics-drivers-384 384.90-0ubuntu6 ADT test failure with linux 4.15.0-1.2

Bug #1737752 reported by Seth Forshee on 2017-12-12
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Seth Forshee
nvidia-graphics-drivers-384 (Ubuntu)
Medium
Seth Forshee
Seth Forshee (sforshee) wrote :
tags: added: kernel-adt-failure
Seth Forshee (sforshee) wrote :

Among other issues this is also failing to link because some of the dma-mapping api has now caused an indirect dependency on a GPL-only export. Adding a linux task for this issue.

Changed in linux (Ubuntu):
assignee: nobody → Seth Forshee (sforshee)
importance: Undecided → Medium
status: New → In Progress
Changed in nvidia-graphics-drivers-384 (Ubuntu):
assignee: nobody → Seth Forshee (sforshee)
importance: Undecided → Medium
status: New → In Progress
Seth Forshee (sforshee) on 2017-12-14
Changed in linux (Ubuntu):
status: In Progress → Fix Committed
Seth Forshee (sforshee) wrote :

Attaching an update to fix issues with 4.15, along with a fix for an issue that was missed when updating for 4.14. Note that the following kernel patch from the Ubuntu unstable tree is also needed in order to build with 4.15:

commit 5c07f2a3183e7fae55a990525fc6f407512fb23d
Author: Seth Forshee <email address hidden>
Date: Thu Dec 14 12:59:29 2017 -0600

    UBUNTU: SAUCE: dma-mapping: Change dma_check_mask to an exported function

tags: added: patch
jchook (jchook) wrote :

I'm also getting this issue.

Just want to clarify the workaround... should I download nvidia 384.90 for 16.04 amd64, patch it with the attached patch, then install that? Or should I just roll-back to an older version still in the package management?

jchook (jchook) wrote :

Never mind, I installed the driver manually via the .run file downloaded from http://www.nvidia.com/Download/index.aspx?lang=en-us

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

Other bug subscribers

Bug attachments