Bug 16412

Summary:	bumblebee-nvidia forces nvidia-current, a nvidia340 version is needed
Product:	Mageia	Reporter:	Pavel Kreuzt <pkreuzt>
Component:	RPM Packages	Assignee:	Rémi Verschelde <rverschelde>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	email, marja11
Version:	5
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	bumblebee-3.2.1-14.20150120.2.src.mga5	CVE:
Status comment:

Description Pavel Kreuzt 2015-07-19 11:50:22 CEST

Description of problem: I'm using a optimus laptop with a nvidia gt310m discrete graphics card, which needs nvidia340 driver. When installing bumblebee-nvidia, it depends on nvidia-current and has no option to choose another driver for older cards. I can install it manually, but everytime I want to launch anything with nvidia card, it loads only "nvidia" driver instead of "nvidia340". Trying to uninstall nvidia-current also uninstalls bumblebee and primus.
Also, I configured bumblebee.conf with KernelDriver=nvidia340 and appropiate XorgModulePath to search in /usr/lib*/nvidia340/xorg, but it doesn't work anyway.


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


How reproducible: Using older card not covered by nvidia-current driver and with optimus.


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Comment 1 Rémi Verschelde 2015-07-19 11:52:59 CEST

Indeed, that's something I've left aside until now but that I should probably try to handle. Maybe by creating a bumblebee-nvidia340 package that one could install instead of bumblebee-nvidia.

Assignee: bugsquad => rverschelde

Rémi Verschelde 2015-07-25 00:13:11 CEST

Summary: bumblebee dependency too restrictive => bumblebee-nvidia forces nvidia-current, a nvidia340 version is needed

Adrien D 2015-07-25 00:34:21 CEST

CC: (none) => ghbdtn

Comment 2 Marja Van Waes 2018-04-14 11:55:26 CEST

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change it's status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 3 Marja Van Waes 2018-10-07 15:08:55 CEST

No reply, so closing as OLD since Mageia 5 is no longer maintained.

@ Pavel:

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Comment 4 Marja Van Waes 2018-10-07 17:39:05 CEST

(In reply to Marja Van Waes from comment #3)
> No reply, so closing as OLD since Mageia 5 is no longer maintained.

retrying :-(

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