Hello,
I’m trying to run bumblebee with nvidia and nouveau but always get the same error, Cannot access secondary GPU.
I googled and try many possible solutions without luck.
I’m using defaults repositories.
This are the messages errors.
dxrxaxx@linux-zji5:~> optirun glxspheres
2073.821424] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
2073.821470] [ERROR]Aborting because fallback start is disabled.
dxrxaxx@linux-zji5:~> systemctl status bumblebeed
bumblebeed.service - Bumblebee C Daemon
Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled)
Active: active (running) since Sat 2014-11-22 17:40:58 CLST; 34min ago
Main PID: 839 (bumblebeed)
CGroup: /system.slice/bumblebeed.service
└─839 /usr/sbin/bumblebeed
dxrxaxx@linux-zji5:~> primusrun glxspheres
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
Yeah…
The question is whether it makes any sense to do it.
You mainly need the nvidia chip for full 3D performance, and this practically implies the proprietary driver.
Poor performance when using the Nouveau card Right now, Nouveau does not support reclocking and other power management feature. This cripples the performance of the GPU a lot along with increasing the power consumption compared to the proprietary driver.
Using Prime with Nouveau may not result in any performance gain right now, but it should in a not-so-distant future.
I thought there was a heat problem with it ie the NVIDIA chip never shut down and it drank battery and over heated. But that was a while back. That is why bumblebee and NVIDIA-bumblebee were needed. Then again maybe just bumblebee was needed to control the hardware. I don’t know it is been a while and I don’t own such Rube Goldberg machines LOL
With NVIDIA-bumblebee i’ve the same result.
If i try to install de NVIDIA packages the boot process take more than 3 minutes… the Xorg log fills with the message:
dxrxaxx@linux-zji5:~> systemctl status bumblebeed
bumblebeed.service - Bumblebee C Daemon
Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled)
Active: active (running) since Sun 2014-11-23 20:57:06 CLST; 7min ago
Main PID: 2924 (bumblebeed)
CGroup: /system.slice/bumblebeed.service
└─2924 /usr/sbin/bumblebeed
dxrxaxx@linux-zji5:~>
I’ve try both repo without success…
I think the problem is a recent opensuse update… with the first release of opensuse 13.2 (with previous proprietary NVIDIA driver) bumblebee works ok.
With the current release of NVIDIA driver my notebook take nearly 3 minutes to start.
Try to revert all updates one-by-one to see what causes it.
Strange though that nobody else has reported something like that yet. If it would be a general problem caused by some official update, (at least some) other people must have the same problem.
And what do you mean with “previous proprietary NVIDIA driver”? AFAIR 343.22 was already the latest (and in the Bumblebee repo) before 13.2 was released. And I just checked, the last change to the nividia-bumblebee package was made 2 months ago…
What does “systemd-analyze blame” say when your notebook takes 3 minutes to start?
NVIDIA in Bumblebee repo never have worked in my notebook (HP Envy15). The proprietary NVIDIA driver actually is 340.58. With proprietary version 343.22 bumblebee work.
That would be expected the normal NVIDA driver change a program called mesa which is important to the graphic stack That change breaks the Intel driver. Uninstalling it put mesa back to normal and the Intel driver can work. You can not use the normal NVIDA driver you must use either the NVIDIA-bumblebee driver or the OS driver.It does not make sense to use the nouveau driver since 3D performance may actually be worse then the Intel’s and some 3D game won’t work because not all the extensions expected are there. In any case bumblebee itself is need to control the hardware. Without it you may have over heat and/or short battery life.
You must first of all remove any trace of the normal NVIDIA driver be sure all packages with NVIDIA in the name are removed.
You must then go to the referenced Bumblebee page and follow exactly the instructions in the order they appear. Do not improvise or follow instruction from any where else.
Baring that you will have to turn off one or the other GPU in the BIOS if it is possible for your hardware. If that does not work I’d mention the problem to the idiots that made the machine since they did it wrong. Ok be nicer then that
You mean nvidia-bumblebee?
But that just downloads the .run installer (343.22) from nvidia and installs it in a way that’s compatible with XOrg,Mesa and Bumblebee.
And it sets up dkms so you don’t have to bother re-installing the driver after kernel updates.
The proprietary NVIDIA driver actually is 340.58.
No. The proprietary NVIDIA driver is available different versions.
The current ones are 343.22, 340.58 (G03), 304.123 (G02).
If you meant the version in the nvidia repo, then yes, the G03 in there is 340.58 at the moment.
And it cannot just be upgraded to 343, as 343 dropped support for many cards not supported by the G02 driver, everything below GF400.
And AFAIK you should never install the standard driver on a Bumblebee system, as it breaks the Intel driver’s OpenGL support.
With proprietary version 343.22 bumblebee work.
Where did you install that from now?
Download from nvidia’s site?
Maybe that’s what caused your problem.
Try to reinstall it. Some updates overwrite files from nvidia, that nvidia overwrote in the first place.
But still, I would rather recommend to install nvidia-bumblebee.
It should work. What problem did you have with that?
Maybe your issue is caused by the broken intel driver.
systemd-analyze show me a loop with this lines:
Doesn’t show any “hang” unfortunately.
And “systemd-analyze critical-chain”?
I agree with you, The HP UEFI bios is made for Windows. You can´t manage the discrete GPU from bios.
My first option was use nvidia-bumblebee, but the system can´t create the device /dev/dri/card1 (i change the bumblebee-nvidia config file adding the PCI:01:00:1 line). Because of this i try the NVIDIA proprietary driver. With early NVIDIA Opensuse repo. and a fresh Opensuse 13.2, bumblebee work.
Wolfi, NVIDIA driver (from opensuse repo) works when Opensuse 13.2 was released. Later came an update for NVIDIA and blumblebee stop working.
I clean up the system from NVIDIA but nvidia-bumblebee can’t load de nvidia driver.
I re-install Opensuse without luck.
If i check the dev/dri directory there is only card0.
Maybe you had Intel driver black listed. LOL Not sure that would work since the NVIDIA actually renders through the Intel So the Intel has to be in the hardware chain If I understand Optimus right. But there is no way for the Intel driver to work when the NVIDIA driver is installed because the NVIDIA driver has always (in recent memory at least) modified the mesa program and the modified mesa will not work with the Intel. So if you had it actually running it was a fluke since there is no way it should work with the Intel.It might work if you managed to not load or use the Intel driver and only use the NVIDIA. But in that case you are covering ground not covered here before. SO far all that have followed the bumblebee instruction exactly have had success. even though it may have taken a bit to get them to that point LOL. Why it is not working for you I don’t know I do know that there were a few rough edges when bumblebee first arrived but they have all seemed to have been fixed. So have you actually tried the bumblebee install or did you skip it because it did not work sometime in the past???
