Public bug reported: 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. The specified module exists as shown by `modinfo`: $ modinfo nvidia_352 filename: /lib/modules/4.1.0-040100rc7-generic/updates/dkms/nvidia_352.ko alias: char-major-195-* version: 352.09 supported: external license: NVIDIA alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: drm vermagic: 4.1.0-040100rc7-generic SMP mod_unload modversions parm: NVreg_Mobile:int parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_UpdateMemoryTypes:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_MapRegistersEarly:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_CheckPCIConfigSpace:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_MemoryPoolSize:int parm: NVreg_RegistryDwords:charp parm: NVreg_RmMsg:charp parm: NVreg_AssignGpus:charp 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 ** Affects: bumblebee (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Description changed: 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. + [ 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. + + The specified module exists as shown by `modinfo`: + + $ modinfo nvidia_352 + filename: /lib/modules/4.1.0-040100rc7-generic/updates/dkms/nvidia_352.ko + alias: char-major-195-* + version: 352.09 + supported: external + license: NVIDIA + alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* + alias: pci:v000010DEd*sv*sd*bc03sc02i00* + alias: pci:v000010DEd*sv*sd*bc03sc00i00* + depends: drm + vermagic: 4.1.0-040100rc7-generic SMP mod_unload modversions + parm: NVreg_Mobile:int + parm: NVreg_ResmanDebugLevel:int + parm: NVreg_RmLogonRC:int + parm: NVreg_ModifyDeviceFiles:int + parm: NVreg_DeviceFileUID:int + parm: NVreg_DeviceFileGID:int + parm: NVreg_DeviceFileMode:int + parm: NVreg_UpdateMemoryTypes:int + parm: NVreg_InitializeSystemMemoryAllocations:int + parm: NVreg_UsePageAttributeTable:int + parm: NVreg_MapRegistersEarly:int + parm: NVreg_RegisterForACPIEvents:int + parm: NVreg_CheckPCIConfigSpace:int + parm: NVreg_EnablePCIeGen3:int + parm: NVreg_EnableMSI:int + parm: NVreg_MemoryPoolSize:int + parm: NVreg_RegistryDwords:charp + parm: NVreg_RmMsg:charp + parm: NVreg_AssignGpus:charp 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 + 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464928 Title: [xorg-edgers] optirun tries to load driver with specified name ignoring _ and - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1464928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs