Comment 41 for bug 1369216

Revision history for this message
Alex R (abr28) wrote :

I'm on 16.04.1 with nvidia 378 (from ppa) and am getting these errors too. So "/etc/modprobe.d is not a file" is safe to ignore. What about "update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf" ?

# systemctl status gpu-manager.service
● gpu-manager.service - Detect the available GPUs and deal with any system changes
   Loaded: loaded (/lib/systemd/system/gpu-manager.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Thu 2017-02-09 19:09:47 GMT; 17min ago
  Process: 1254 ExecStart=/usr/bin/gpu-manager --log /var/log/gpu-manager.log (code=exited, status=0/SUCCESS)
 Main PID: 1254 (code=exited, status=0/SUCCESS)

Feb 09 19:09:46 sparrow systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Feb 09 19:09:46 sparrow gpu-manager[1254]: /etc/modprobe.d is not a file
Feb 09 19:09:46 sparrow gpu-manager[1254]: /etc/modprobe.d is not a file
Feb 09 19:09:46 sparrow gpu-manager[1254]: /etc/modprobe.d is not a file
Feb 09 19:09:46 sparrow gpu-manager[1254]: /etc/modprobe.d is not a file
Feb 09 19:09:46 sparrow gpu-manager[1254]: /etc/modprobe.d is not a file
Feb 09 19:09:47 sparrow gpu-manager[1254]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Feb 09 19:09:47 sparrow systemd[1]: Started Detect the available GPUs and deal with any system changes.