Bug 7330

Summary:	Nvidia driver breaks use of GLX for integrated Intel graphic on optimus notebooks
Product:	Mageia	Reporter:	Alfred Kretschmer <alfred.kretschmer>
Component:	RPM Packages	Assignee:	Anssi Hannula <anssi.hannula>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	High	CC:	denis.robel, rverschelde
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	nvidia-current	CVE:
Status comment:

Description Alfred Kretschmer 2012-09-03 22:44:01 CEST

Description of problem:

Installing the proriatery Nvidia-Driver(304.xx) from the repos breaks the use of GLX for the integrated Intel card on optimus notebooks. The Nvidia installer has an option to prevent this behaviour "--no-opnegl-files". Could this option implemented in the nvidia-driver-package in any way when installing the driver on an optimus machine?

Alfred

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Manuel Hiebel 2012-09-11 22:08:20 CEST

Assignee: bugsquad => anssi.hannula
Source RPM: (none) => nvidia-current

Denis Robel 2013-04-22 19:39:03 CEST

Priority: Normal => High
CC: (none) => denis.robel

Comment 1 Denis Robel 2013-04-22 20:06:42 CEST

The same state in Mageia 3 RC:
when I install bumblebee and the Nvidia-Drivers then the GLX output of intel card is broken.

Denis

Target Milestone: --- => Mageia 3
Severity: enhancement => major

Comment 2 Rémi Verschelde 2014-03-18 11:50:21 CET

Is this still valid in Mageia 4 or in cauldron?

CC: (none) => remi
Target Milestone: Mageia 3 => ---

Comment 3 Rémi Verschelde 2014-03-18 11:51:28 CET

Could you also give a procedure to reproduce this bug? I'm running on an optimus laptop with nvidia-current, and I don't notice big issues with the intel driver.

Comment 4 Alfred Kretschmer 2014-03-18 15:09:14 CET

(In reply to Rémi Verschelde from comment #2)
> Is this still valid in Mageia 4 or in cauldron?

Well, I see, I should have been more precise. It was the fact when configuring the xserver for the use of bumblebee. But it's no longer necessary doing so since you packaged bumblebee and all the dependecies for MGA4 and Cauldron. 

So, for me the bug has gone and is neither valid for Cauldron nor for MGA4 :)

Comment 5 Rémi Verschelde 2014-03-18 15:29:44 CET

Thanks, then it was likely a bug linked with the bumblebee package you used and not with the nvidia driver (I guess).

Please mention it when you use external packages which might have an influence :)

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 6 Alfred Kretschmer 2014-03-18 15:46:27 CET

(In reply to Rémi Verschelde from comment #5)
> Thanks, then it was likely a bug linked with the bumblebee package you used
> and not with the nvidia driver (I guess).
> 
Maybe, but the time i posted the bug i tested with the nvidia-driver from repo and from Nvidia directly. Only instllaling the driver from Nvidia with option "--no-opengl-files" left the intel-glfiles untouched. Maybe it was more the way how bumblebee was configured that time.
> Please mention it when you use external packages which might have an
> influence :)
Well that was the official mga bumblebee-package ;)

Alfred

Comment 7 Rémi Verschelde 2014-03-18 15:59:18 CET

Then let's say is OLD and not INVALID ;-)

Resolution: INVALID => OLD

Comment 8 Rémi Verschelde 2014-03-18 15:59:31 CET

s/is/it's/

Comment 9 Alfred Kretschmer 2014-03-18 16:02:51 CET

(In reply to Rémi Verschelde from comment #7)
> Then let's say is OLD and not INVALID ;-)

agreed ;)