← Back to team overview

bumblebee team mailing list archive

issue with nvidia 650m

 

Hi,

I am writing to log an issue I am having with the following system:
baseboard-manufacturer: Alienware
baseboard-product-name: M14xR2
baseboard-version     : A03
system-manufacturer   : Alienware
system-product-name   : M14xR2
system-version        : A03
bios-vendor           : Alienware
bios-version          : A03
bios-release-date     : 03/07/2012

The machine is running
Distro: Ubuntu 12.04
Kernel: Linux 3.2.0-25-generic #40-Ubuntu SMP x86_64 GNU/Linux
and has a nvidia 2GB gt 650m graphics card

I have followed the instructions from here:
https://wiki.ubuntu.com/Bumblebee on a fresh 12.04 install and upgraded to
nvidia-current 295.59 to get 650m support.   I am running Bumblebee v3.0

I have seen on some sites that upgrading to 295.59 can break bumblebee, but
I'm not sure if this is the issue --- or if there is a specific set of
steps that i should follow to avoid breaking bumblebee when doing this.

===================================

The problem I am having is that when I run optirun glxspheres I get the
following errors.
$ optirun -vv glxspheres
[DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[INFO]Configured driver: nvidia
[DEBUG]Skipping auto-detection, using configured driver 'nvidia'
[DEBUG]Process /sbin/modinfo started, PID 4292.
[DEBUG]Hiding stderr for execution of /sbin/modinfo
[DEBUG]SIGCHILD received, but wait failed with No child processes
[DEBUG]Active configuration:
[DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[DEBUG] X display: :8
[DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia-current:/usr/lib32/nvidia-current
[DEBUG] Socket path: /var/run/bumblebee.socket
[DEBUG] VGL Compression: proxy
[DEBUG]optirun version 3.0 starting...
[INFO]Response: No - error: [XORG] (EE) NVIDIA(0): Failed to initialize the
NVIDIA GPU at PCI:1:0:0.  Please

[ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(0): Failed
to initialize the NVIDIA GPU at PCI:1:0:0.  Please

[DEBUG]Socket closed.
[ERROR]Aborting because fallback start is disabled.
[DEBUG]Killing all remaining processes.

===============================

with the following being logged in syslog:
Jun 27 16:48:09 jmcd-m14x acpid: client 4293[0:1001] has disconnected
Jun 27 16:48:09 jmcd-m14x acpid: client connected from 4300[0:1001]
Jun 27 16:48:09 jmcd-m14x acpid: 1 client rule loaded
Jun 27 16:48:13 jmcd-m14x bumblebeed[1078]: [XORG] (EE) NVIDIA(0): Failed
to initialize the NVIDIA GPU at PCI:1:0:0.  Please
Jun 27 16:48:13 jmcd-m14x bumblebeed[1078]: [XORG] (EE) NVIDIA(0):
check your system's kernel log for additional error
Jun 27 16:48:13 jmcd-m14x bumblebeed[1078]: [XORG] (EE) NVIDIA(0):
messages and refer to Chapter 8: Common Problems in the
Jun 27 16:48:13 jmcd-m14x bumblebeed[1078]: [XORG] (EE) NVIDIA(0):
README for additional information.
Jun 27 16:48:13 jmcd-m14x bumblebeed[1078]: [XORG] (EE) NVIDIA(0): Failed
to initialize the NVIDIA graphics device!
Jun 27 16:48:13 jmcd-m14x bumblebeed[1078]: [XORG] (EE) Screen(s) found,
but none have a usable configuration.
Jun 27 16:48:13 jmcd-m14x kernel: [ 4175.783144] NVRM: RmInitAdapter
failed! (0x26:0xffffffff:1170)
Jun 27 16:48:13 jmcd-m14x kernel: [ 4175.783152] NVRM: rm_init_adapter(0)
failed
Jun 27 16:48:13 jmcd-m14x bumblebeed[1078]: X did not start properly


If there is other information that I can provide please let me know. Also,
since it is a fresh install, wiping the system and starting from scratch is
not a big issue at the moment --- in case that helps.

Thanks & regards,
John McDonald.

Attachment: bumblebee-bugreport-20120627_162213.tar.gz
Description: GNU Zip compressed data