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

Closed
olipoh opened this Issue Feb 12, 2014 · 7 comments

Projects

None yet

4 participants

olipoh commented Feb 12, 2014

Hello everyone,

when I run optirun glxgears I have this error message
[ERROR]Cannot access secondary GPU - error: XORG NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please

In Ubuntu 13.10 with the same computer (laptop) I never had any problem.
Distro: Debian 7.4 Wheezy

Kernel: Linux centaurus 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux

Manufacturer and model:
baseboard-manufacturer: TOSHIBA
baseboard-product-name: Portable PC
baseboard-version : MP
system-manufacturer : TOSHIBA
system-product-name : SATELLITE P870
system-version : PSPLFE-028009FR
bios-vendor : Insyde Corp.
bios-version : 6.20
bios-release-date : 12/12/2012

Bumblebee version: optirun (Bumblebee) 3.2.1

I tried a workaround found on the internet : GRUB_CMDLINE_LINUX="acpi=force" in grub, but it didn't work.

Thank you for your help

Contributor

You need to use a newer kernel or build a special branch of bbswitch: https://github.com/Bumblebee-Project/bbswitch/tree/hack-lenovo

s-ol commented Feb 16, 2014

Bumlbebee used to work 9/10 times, now it works 1/5 reboots. Trying to primusrun yields this:

$ dmesg | grep -i NV
[    0.000000]  BIOS-e820: 00000000caeef000 - 00000000caf9f000 (ACPI NVS)
[    0.000000] ACPI: SSDT 00000000cafe3000 00B43 (v01 NvORef NvOptTbl 00001000 INTL 20061109)
[    0.926324] PM: Registering ACPI NVS region at caeef000 (720896 bytes)
[    1.793684] \_SB_.PCI0:_OSC invalid UUID
[    1.817419] \_SB_.PCI0:_OSC invalid UUID
[    1.817475] \_SB_.PCI0:_OSC invalid UUID
[    2.296372] rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[  186.883848] nvidia: module license 'NVIDIA' taints kernel.
[  187.122029] nvidia 0000:01:00.0: power state changed by ACPI to D0
[  187.137483] nvidia 0000:01:00.0: power state changed by ACPI to D0
[  187.137491] nvidia 0000:01:00.0: enabling device (0006 -> 0007)
[  187.137511] nvidia 0000:01:00.0: setting latency timer to 64
[  187.137802] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  304.88  Wed Mar 27 14:26:46 PDT 2013
[  314.537899] nvidia 0000:01:00.0: power state changed by ACPI to D0
[  314.537908] nvidia 0000:01:00.0: power state changed by ACPI to D0
[  314.537928] nvidia 0000:01:00.0: setting latency timer to 64
[  314.538133] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  304.88  Wed Mar 27 14:26:46 PDT 2013
[  324.532246] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
[  324.598503] NVRM: RmInitAdapter failed! (0x26:0xffffffff:1200)
[  324.598517] NVRM: rm_init_adapter(0) failed

(nvidia driver)

When I restart bumblebeed after that, the error message changes to primus: fatal: Bumblebee daemon reported: error: Could not enable discrete graphics card.

dmesg:

[  536.933088] nvidia 0000:01:00.0: power state changed by ACPI to D0
[  536.948391] nvidia 0000:01:00.0: Refused to change power state, currently in D3
[  536.948409] nvidia 0000:01:00.0: power state changed by ACPI to D0
[  545.101905] nvidia 0000:01:00.0: power state changed by ACPI to D0
[  545.116276] nvidia 0000:01:00.0: Refused to change power state, currently in D3
[  545.116296] nvidia 0000:01:00.0: power state changed by ACPI to D0

about 5-10min after that the system suddenly crashes b/c of heat issues. Debian wheezy x64

Edit: it seems the problem only/mostly happens when launching Counter Strike: Source via steam, glxgears works fine most of the time (before attempting CS:S). I will try to launch steam via primusrun now.

Owner

Is there any news from any of you there?

s-ol commented Apr 2, 2014

I only found that I can avoid it by starting steam with primusrun right away.

Owner

Sorry for not answering for so long. Have you considered adding the rcutree thing to your cmdline (see #455)? I might be the issue you’re facing. If not, please consider opening another issue (since anyway this wasn’t the issue of the original poster).

s-ol commented Oct 26, 2014

My old debian setup died with the HDD and I didn't get around setting anything up again, also CS:GO is now natively linux compatible. I will still try and gather more info on this should I end up with another wheezy install, but I guess I will switch to arch or something now....

Owner

Ok, that’s fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment