Black screen after switching to UEFI boot and prime-select nvidia.

Bug #1669469 reported by Hicks
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Note that this issue is reproducible on two computers, both running a fresh install from Xubuntu 16.10. Also, everything was running fine on both computers until recently. Also, running the Nouveau driver works.

When installing any recent version of the nvidia driver (I tried with the 367 and 375 from vanilla repos, then the 375 and 378 from the graphics-driver PPA), I cannot get lightdm to start if `prime-select nvidia` is issued and rebooted. The screen is black with an artifact of a cursor on the top left screen (But it's not blinking, I think it's just a video frame being displayed and not updated at all).

I experimented using various settings, and also installed bumblebee to diagnose. I got the nvidia GPU to work in some circumstances using `primusrun` and `optirun` so I know the card function on both computers.

I'm not sure what to include in this bug report, the logs are rare and don't show very much information.

A bit of interesting fact, is that since the problem is showing the regular XFCE compositor has VSync correctly on the intel card (Is it related?).
Another interesting fact, is that since the problem is showing, having compton's `glx-no-rebind-pixmap` set to true makes menus not appear in chromium-based applications (Is it related?).

Also, but I'm not sure: it might be since I've switched to UEFI boots.

Not sure what else to include in this report, please advise.

-----------------------------------------------
Ubuntu 4.8.0-39.42-generic 4.8.17
-----------------------------------------------
Description: Ubuntu 16.10
Release: 16.10
-----------------------------------------------
[...]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev ff) (prog-if ff)
 !!! Unknown header type 7f
 Kernel modules: nvidiafb, nouveau, nvidia_378_drm, nvidia_378
[...]
-----------------------------------------------
nvidia-378:
  Installed: 378.13-0ubuntu0~gpu16.10.3
  Candidate: 378.13-0ubuntu0~gpu16.10.3
  Version table:
 *** 378.13-0ubuntu0~gpu16.10.3 500
        500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety/main amd64 Packages
        100 /var/lib/dpkg/status
nvidia-settings:
  Installed: 378.09-0ubuntu0~gpu16.10.1
  Candidate: 378.09-0ubuntu0~gpu16.10.1
  Version table:
 *** 378.09-0ubuntu0~gpu16.10.1 500
        500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety/main amd64 Packages
        100 /var/lib/dpkg/status
     367.35-0ubuntu1 500
        500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
nvidia-prime:
  Installed: 0.8.4
  Candidate: 0.8.4
  Version table:
 *** 0.8.4 500
        500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
        100 /var/lib/dpkg/status
---
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: doodloo 3812 F.... pulseaudio
 /dev/snd/controlC1: doodloo 3812 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=e5604457-e1ec-4402-9d6f-958b2a51b6b0
InstallationDate: Installed on 2017-02-27 (3 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Notebook P15SM-A/SM1-A
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic.efi.signed root=UUID=49cb472c-5393-4d6e-86b3-dc463e33c951 ro
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-39-generic N/A
 linux-backports-modules-4.8.0-39-generic N/A
 linux-firmware 1.161.1
Tags: yakkety
Uname: Linux 4.8.0-39-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: P15SM-A/SM1-A
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/16/2014:svnNotebook:pnP15SM-A/SM1-A:pvrNotApplicable:rvnNotebook:rnP15SM-A/SM1-A:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: P15SM-A/SM1-A
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1669469

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Hicks (hickscorp) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected yakkety
description: updated
Revision history for this message
Hicks (hickscorp) wrote : CRDA.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : IwConfig.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : JournalErrors.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : Lspci.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : Lsusb.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : ProcEnviron.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : ProcModules.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : PulseList.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : RfKill.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : UdevDb.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote : WifiSyslog.txt

apport information

Revision history for this message
Hicks (hickscorp) wrote :

I'd like to add this log:

cat /var/log/Xorg.0.log | grep "WW\|EE"
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 85.594] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 85.594] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 85.594] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 85.594] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 85.594] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 85.609] (WW) "glamoregl" will not be loaded unless you've specified it to be loaded elsewhere.
[ 85.773] (WW) evdev: Razer Razer DeathAdder Chroma: ignoring absolute axes.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.1

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Hicks (hickscorp) wrote :

Good afternoon Joseph,

I can for sure try other kernels, yes. Could you please tell me which one?

Best.

Revision history for this message
Hicks (hickscorp) wrote :

Re: I'm installing the 4.10 one with the most recent upload timestamp. Will report back ASAP. Thanks for your help!

Revision history for this message
Hicks (hickscorp) wrote :

Here is what I've done:
- Installed the 4.10 mainline kernel.
- Completelly removed any nvidia-related packages, removed the graphic-drivers ppa.
- Rebooted, installed the nvidia 367 driver.
- Rebooted.

At this point, the bug is different. The deskop loads regardless of what I select using `prime-select intel|nvidia`, but only the `nouveau` driver is loaded, not the intel modeline or nvidia one.

Am I doing something wrong? Tell me what to test, and I'll test it. I cannot however stay on the 4.10, because it seems to be breaking docker.

Best.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Hicks (hickscorp) wrote :

Very sorry for the noise. I've tried something else:

- Still runing the 4.10 mainline kernel.
- Added the graphics driver PPA back, installed the latest 378 nvidia drivers.
- Now the exact same symptoms show, black screen if `prime-select nvidia` is issued. No problem if `prime-select intel` is issued tho.

Revision history for this message
Hicks (hickscorp) wrote :

Small update: installing 16.10 fresh but without the `yakkety-proposed` repo seems to be functional along with the nvidia drivers.

I noticed that if I adhere to `yakkety-proposed`, an update to from 4.8.0-39 to 4.8.0-40 is mandatory, as well as other packages:

  binutils coreutils cups cups-bsd cups-client cups-common cups-core-drivers
  cups-daemon cups-ppdc cups-server-common dbus dbus-user-session dbus-x11
  desktop-file-utils gdb gdbserver gir1.2-gtk-3.0 gnome-software
  gnome-software-common gtk-update-icon-cache klibc-utils lib32z1 libcups2
  libcupscgi1 libcupsimage2 libcupsmime1 libcupsppdc1 libdbus-1-3 libgail-3-0
  libgtk-3-0 libgtk-3-bin libgtk-3-common libklibc libpci3 libthunarx-2-0
  libzmq5 linux-generic linux-headers-generic linux-image-generic
  linux-libc-dev linux-signed-generic linux-signed-image-generic
  linux-tools-common linux-tools-virtual pciutils python3-update-manager
  resolvconf snap-confine snapd sudo thermald thunar thunar-data
  ubuntu-core-launcher update-manager update-manager-core zlib1g

When running without those, I also noticed graphic artifacts (screen corruption, remanent pieces of the frame not being redrawn etc) when using the graphic-drivers 378 nvidia drivers. Everything is fine when using the 367 version from the regular Ubuntu repos.

Please advise on any further test.

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.