Stuck with nvidia graphics only when using the latest NVIDIA 384/387 drivers

Bug #1722039 reported by Dylan Borg
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nvidia-prime (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

On a brand new laptop with GTX 1050 TI and Kaby Lake graphics I cannot switch back to intel's GPU after installing the nvidia drivers + nvidia-prime. prime-select lists the nvidia driver as well as a prime variant as the only available alternatives. When switching to intel and logging out I get failed logins. If I reboot my screen freezes on login. It is possible to do a hard reboot, switch back to nvidia mode in a TTY, reboot and login after this happens.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nvidia-prime 0.8.4
Uname: Linux 4.13.5-041305-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Oct 8 09:42:05 2017
InstallationDate: Installed on 2017-10-02 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
SourcePackage: nvidia-prime
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Dylan Borg (borgdylan) wrote :
Revision history for this message
dino99 (9d9) wrote :
Changed in nvidia-prime (Ubuntu):
status: New → Incomplete
Revision history for this message
dino99 (9d9) wrote :

Until nvidia pushed a new driver version supporting that feature, the workaround is to login on a xorg session instaed of the default wayland one.

Revision history for this message
Dylan Borg (borgdylan) wrote :

I am using X11 throughout. Wayland has not been used anywhere.

Revision history for this message
Dylan Borg (borgdylan) wrote :

Output when running prime-select:

dylan@zenbook-pro:~$ sudo prime-select intel
[sudo] password for dylan:
Info: the current GL alternatives in use are: ['nvidia-387', 'nvidia-387']
Info: the current EGL alternatives in use are: ['nvidia-387', 'nvidia-387']
Info: selecting nvidia-387-prime for the intel profile
update-alternatives: using /usr/lib/nvidia-387-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in manual mode
update-alternatives: using /usr/lib/nvidia-387-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in manual mode
update-alternatives: using /usr/lib/nvidia-387-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in manual mode
update-alternatives: using /usr/lib/nvidia-387-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in manual mode
dylan@zenbook-pro:~$ sudo prime-select nvidia
Info: the current GL alternatives in use are: ['nvidia-387-prime', 'nvidia-387-prime']
Info: the current EGL alternatives in use are: ['nvidia-387-prime', 'nvidia-387-prime']
Info: selecting nvidia-387 for the nvidia profile
update-alternatives: using /usr/lib/nvidia-387/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in manual mode
update-alternatives: using /usr/lib/nvidia-387/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in manual mode
update-alternatives: using /usr/lib/nvidia-387/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in manual mode
update-alternatives: using /usr/lib/nvidia-387/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in manual mode

Changed in nvidia-prime (Ubuntu):
status: Incomplete → New
Dylan Borg (borgdylan)
description: updated
Revision history for this message
Alberto Milone (albertomilone) wrote :

Can you reproduce the problem on the same exact system (kernel, etc.) when using the 375 driver?

Revision history for this message
Dylan Borg (borgdylan) wrote :

Is a version of 375 that supports 1050Ti available in the repos (ubuntu or graphics PPA)?

Revision history for this message
Dylan Borg (borgdylan) wrote :

The version of nvidia-375 I am seeing points to nvidia-384. So I cannot install nvidia-375 without breaking my system (i.e. using a .run file that wouldn't work with nvidia-prime anyways)

Revision history for this message
Dylan Borg (borgdylan) wrote :

Coming to think of it I have not tried nvidia 381. Should I?

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

You can remove nvidia-384 and the transitional packages for nvidia-385, then you can download 375 from the following PPA, and install the deb packages manually:
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

Revision history for this message
Dylan Borg (borgdylan) wrote :

nvidia-381 drove both my fans to max :/

Revision history for this message
Dylan Borg (borgdylan) wrote :

I have used force version in synaptic to use the PPA version of the packages.

Revision history for this message
Dylan Borg (borgdylan) wrote :

With nvidia-375 from the PPA I get the same issue + the fans at max issue as with nvidia-381.

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

It could be a kernel issue. I have seen other systems not playing well with bbswitch disabling the dGPU. I'll see if I can reproduce the problem here.

Revision history for this message
Dylan Borg (borgdylan) wrote :

I have seen it happen with both the 4.13.4 kernel currently in artful-proposed as well as the 4.13.5 upstream kernel. I am currently on the upstream kernel since 4.13.4 has an annoying shutdown hang and 4.13.5 does not.

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

what is the newest kernel you can't reproduce the problem with? (you can use the kernel mainline PPA if you want to help testing)

Revision history for this message
Dylan Borg (borgdylan) wrote :

None. I cannot even try 4.14 because of some GPL symbol issue which results in the DKMS build of the nvidia driver to fail. As of now, the latest kernel series that support teh binary driver is 4.13.

Revision history for this message
Dylan Borg (borgdylan) wrote :

Looking at: https://github.com/Bumblebee-Project/bbswitch/issues/140 indicates that this has been broken since 4.8 when new power management code was enabled for PCIE ports. They suggest using pcie_port_pm=off in teh kernel command line. I will try that whenever I can and see where that leaves me.

Revision history for this message
Dylan Borg (borgdylan) wrote :

That kernel boot parameter did not work for me. Also in teh non functional intel mode I am getting fans at maximum even with the recent nvidia drivers. Some GPU switching is really going wrong in intel mode.

Revision history for this message
Dylan Borg (borgdylan) wrote :

Could it be that the mesa GL libraries are incorrectly installed or that some library is not in the search path when redirecting calls?

Revision history for this message
Dylan Borg (borgdylan) wrote :

For referece, the bbswitch load log:
[ 4.492602] bbswitch: version 0.8
[ 4.492606] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[ 4.492611] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
[ 4.492699] bbswitch: detected an Optimus _DSM function
[ 4.492708] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on

Revision history for this message
Dylan Borg (borgdylan) wrote :

list of gl libraries loadable in intel mode

Revision history for this message
Dylan Borg (borgdylan) wrote :

list of gl libraries loadable in nvidia mode

Revision history for this message
Dylan Borg (borgdylan) wrote :

Looks like libGLX is only lodable in nvidia mode, some library paths may be missing in the intel prime profile

Revision history for this message
Dylan Borg (borgdylan) wrote :

I found an alternate implementation of prime-select, and modified it slightly. With it, if I switch to intel mode , then reboot I manage to login with the integrated graphics getting used as expected.

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

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

Changed in nvidia-prime (Ubuntu):
status: New → Confirmed
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.