Public bug reported:

NVidia card not properly initialized after reboot.

After analyzing log files it seems that when updating the color profile,
garbage is written to the syslog and the update process fails.

Several reboots later, the boot process continues and completes.

A workaround that seems to work effectively:
boot into recovery and continue the boot without any further steps.
(sometimes that has to be selected twice, the first time, the procedure returns)

Maybe a similar bug as #1643997 (not quite sure from the description
there)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nvidia-367 367.57-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec  6 16:23:57 2016
InstallationDate: Installed on 2016-10-22 (45 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: nvidia-graphics-drivers-367
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.modprobe.d.nvidia-367_hybrid.conf: [deleted]

** Affects: nvidia-graphics-drivers-367 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug yakkety

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1647768/+attachment/4788148/+files/syslog

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu.
https://bugs.launchpad.net/bugs/1647768

Title:
  NVidia card not properly initialized

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  New

Bug description:
  NVidia card not properly initialized after reboot.

  After analyzing log files it seems that when updating the color
  profile, garbage is written to the syslog and the update process
  fails.

  Several reboots later, the boot process continues and completes.

  A workaround that seems to work effectively:
  boot into recovery and continue the boot without any further steps.
  (sometimes that has to be selected twice, the first time, the procedure 
returns)

  Maybe a similar bug as #1643997 (not quite sure from the description
  there)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nvidia-367 367.57-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec  6 16:23:57 2016
  InstallationDate: Installed on 2016-10-22 (45 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nvidia-graphics-drivers-367
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-367_hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1647768/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to