Bug 21089 - Bumblebee not working - Cannot access secondary GPU - error: Could not load GPU driver
Summary: Bumblebee not working - Cannot access secondary GPU - error: Could not load G...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-14 16:43 CEST by Marcello Anni
Modified: 2017-07-02 16:35 CEST (History)
1 user (show)

See Also:
Source RPM: bumblebee-3.2.1-18.20161107.1.mga6.nonfree.src.rpm
CVE:
Status comment:

Attachments
Bumblebee.conf (2.95 KB, text/plain)
2017-06-14 18:26 CEST, Marcello Anni 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Marcello Anni 2017-06-14 16:43:10 CEST 
Hi,

when i try to run any application with Bumblebee (optirun app), i receive this error log:

[marcello@localhost ~]$ optirun glxspheres64 
[ 5243.452964] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver

[ 5243.452988] [ERROR]Aborting because fallback start is disabled.

can you help me to fix this issue? thanks


Regards,
Marcello
Comment 1 Rémi Verschelde 2017-06-14 17:06:42 CEST 
Is your user part of the "bumblebee" group? https://wiki.mageia.org/en/Bumblebee
Comment 2 Marcello Anni 2017-06-14 18:26:21 CEST 
Created attachment 9413 [details]
Bumblebee.conf

i've already added my user to that group in drakconf, i've redone it via konsole and i've also installed some packages i've found in the wiki, but nothing has changed. i attach the bumblebee configuration file. thanks in advance

cheers,
Marcello
Marja Van Waes 2017-06-15 21:10:55 CEST

CC: (none) => marja11
Assignee: bugsquad => rverschelde

Comment 3 Marcello Anni 2017-07-02 16:35:31 CEST 
after recent updates bumblebee works fine. 


cheers,
Marcello

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.