Comment 0 for bug 1464928

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

Specifying a `KernelDriver` containing `_` or `-` in the `nvidia` driver section of `/etc/bumblebee/bumblebee.conf` causes `optirun bash` to fail with

    [ 533.997079] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nvidia352" (module does not exist, 0)

    [ 533.997196] [ERROR]Aborting because fallback start is disabled.

if `nvidia_352` or `nvidia-352` has been specified. Futhermore this is impossible to debug without massive loss of sanity if `optirun` doesn't tell where configuration options have been picked up from if a critical error occured. `grep -r 'nvidia352' /etc/bumblebee/` returns no result.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: bumblebee 3.2.1-7
Uname: Linux 4.1.0-040100rc7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jun 14 00:53:57 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-06-08 (5 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: bumblebee
UpgradeStatus: Upgraded to vivid on 2015-06-09 (4 days ago)
mtime.conffile..etc.bumblebee.bumblebee.conf: 2015-06-14T00:53:00.911443
mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-06-09T20:38:24.773993
mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-06-14T00:43:34.468919