kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #65078
[Bug 1327598] [NEW] running bumblebee in Ubuntu 14.04 results in call trace in logs
Public bug reported:
I tried installing bumblebee with nvidia-337 graphics driver. Bumblebee
does not work.
# Configuration file for Bumblebee. Values should **not** be put between
quotes
## Server options. Any change made in this section will need a server restart
# to take effect.
[bumblebeed]
# The secondary Xorg server DISPLAY number
VirtualDisplay=:8
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
KeepUnusedXServer=false
# The name of the Bumbleblee server group name (GID name)
ServerGroup=bumblebee
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
TurnCardOffAtExit=false
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
NoEcoModeOverride=false
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=nvidia-337
# Directory with a dummy config file to pass as a -configdir to secondary X
XorgConfDir=/etc/bumblebee/xorg.conf.d
## Client options. Will take effect on the next optirun executed.
[optirun]
# Acceleration/ rendering bridge, possible values are auto, virtualgl and
# primus.
Bridge=auto
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=proxy
# List of paths which are searched for the primus libGL.so.1 when using
# the primus bridge
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?
AllowFallbackToIGC=false
# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
# bbswitch - new in BB 3, recommended if available
# switcheroo - vga_switcheroo method, use at your own risk
# none - disable PM completely
# https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia-337
PMMethod=auto
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
attached is the dmesg log
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: trusty
** Attachment added: "dmesg"
https://bugs.launchpad.net/bugs/1327598/+attachment/4127225/+files/dmesg
** Description changed:
I tried installing bumblebee with nvidia-337 graphics driver. Bumblebee
does not work.
+ # Configuration file for Bumblebee. Values should **not** be put between
+ quotes
+
+ ## Server options. Any change made in this section will need a server restart
+ # to take effect.
+ [bumblebeed]
+ # The secondary Xorg server DISPLAY number
+ VirtualDisplay=:8
+ # Should the unused Xorg server be kept running? Set this to true if waiting
+ # for X to be ready is too long and don't need power management at all.
+ KeepUnusedXServer=false
+ # The name of the Bumbleblee server group name (GID name)
+ ServerGroup=bumblebee
+ # Card power state at exit. Set to false if the card shoud be ON when Bumblebee
+ # server exits.
+ TurnCardOffAtExit=false
+ # The default behavior of '-f' option on optirun. If set to "true", '-f' will
+ # be ignored.
+ NoEcoModeOverride=false
+ # The Driver used by Bumblebee server. If this value is not set (or empty),
+ # auto-detection is performed. The available drivers are nvidia and nouveau
+ # (See also the driver-specific sections below)
+ Driver=nvidia-337
+ # Directory with a dummy config file to pass as a -configdir to secondary X
+ XorgConfDir=/etc/bumblebee/xorg.conf.d
+
+ ## Client options. Will take effect on the next optirun executed.
+ [optirun]
+ # Acceleration/ rendering bridge, possible values are auto, virtualgl and
+ # primus.
+ Bridge=auto
+ # The method used for VirtualGL to transport frames between X servers.
+ # Possible values are proxy, jpeg, rgb, xv and yuv.
+ VGLTransport=proxy
+ # List of paths which are searched for the primus libGL.so.1 when using
+ # the primus bridge
+ PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
+ # Should the program run under optirun even if Bumblebee server or nvidia card
+ # is not available?
+ AllowFallbackToIGC=false
+
+
+ # Driver-specific settings are grouped under [driver-NAME]. The sections are
+ # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
+ # detection resolves to NAME).
+ # PMMethod: method to use for saving power by disabling the nvidia card, valid
+ # values are: auto - automatically detect which PM method to use
+ # bbswitch - new in BB 3, recommended if available
+ # switcheroo - vga_switcheroo method, use at your own risk
+ # none - disable PM completely
+ # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
+
+ ## Section with nvidia driver specific options, only parsed if Driver=nvidia
+ [driver-nvidia]
+ # Module name to load, defaults to Driver if empty or unset
+ KernelDriver=nvidia-337
+ PMMethod=auto
+ # colon-separated path to the nvidia libraries
+ LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
+ # comma-separated path of the directory containing nvidia_drv.so and the
+ # default Xorg modules path
+ XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
+ XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
+
+ ## Section with nouveau driver specific options, only parsed if Driver=nouveau
+ [driver-nouveau]
+ KernelDriver=nouveau
+ PMMethod=auto
+ XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
+
+
attached is the dmesg log
** Summary changed:
- running bumblebee in Ubuntu 14.04 resutls in call trace in logs
+ running bumblebee in Ubuntu 14.04 results in call trace in logs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598
Title:
running bumblebee in Ubuntu 14.04 results in call trace in logs
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
I tried installing bumblebee with nvidia-337 graphics driver.
Bumblebee does not work.
# Configuration file for Bumblebee. Values should **not** be put
between quotes
## Server options. Any change made in this section will need a server restart
# to take effect.
[bumblebeed]
# The secondary Xorg server DISPLAY number
VirtualDisplay=:8
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
KeepUnusedXServer=false
# The name of the Bumbleblee server group name (GID name)
ServerGroup=bumblebee
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
TurnCardOffAtExit=false
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
NoEcoModeOverride=false
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=nvidia-337
# Directory with a dummy config file to pass as a -configdir to secondary X
XorgConfDir=/etc/bumblebee/xorg.conf.d
## Client options. Will take effect on the next optirun executed.
[optirun]
# Acceleration/ rendering bridge, possible values are auto, virtualgl and
# primus.
Bridge=auto
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=proxy
# List of paths which are searched for the primus libGL.so.1 when using
# the primus bridge
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?
AllowFallbackToIGC=false
# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
# bbswitch - new in BB 3, recommended if available
# switcheroo - vga_switcheroo method, use at your own risk
# none - disable PM completely
# https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia-337
PMMethod=auto
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
attached is the dmesg log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+subscriptions
Follow ups
-
[Bug 1327598] Re: [Dell Vostro 3300] running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Sayantan Das, 2014-07-11
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Christopher M. Penalver, 2014-06-12
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Sayantan Das, 2014-06-12
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Christopher M. Penalver, 2014-06-11
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Sayantan Das, 2014-06-10
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Christopher M. Penalver, 2014-06-10
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Sayantan Das, 2014-06-10
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Christopher M. Penalver, 2014-06-10
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Sayantan Das, 2014-06-09
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Sayantan Das, 2014-06-09
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Christopher M. Penalver, 2014-06-09
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Christopher M. Penalver, 2014-06-09
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Sayantan Das, 2014-06-08
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] WifiSyslog.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] UdevLog.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] UdevDb.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] RfKill.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] PulseList.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] ProcModules.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] ProcInterrupts.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] ProcEnviron.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] ProcCpuinfo.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] Lsusb.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] Lspci.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] IwConfig.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] CurrentDmesg.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] CRDA.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] BootDmesg.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] AlsaInfo.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] WifiSyslog.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] UdevLog.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] UdevDb.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] RfKill.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] PulseList.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] ProcModules.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] ProcInterrupts.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] ProcEnviron.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] ProcCpuinfo.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] Lsusb.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] Lspci.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] IwConfig.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] CurrentDmesg.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] CRDA.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] BootDmesg.txt
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Sayantan Das, 2014-06-07
-
[Bug 1327598] Missing required logs.
From: Brad Figg, 2014-06-07
-
[Bug 1327598] [NEW] running bumblebee in Ubuntu 14.04 results in call trace in logs
From: Sayantan Das, 2014-06-07
References