Bug 19570 - please create a temporary "solution" for bug 13986 (was:drakx11 can generate a bad xorg.conf on hybrid graphics systems)
Summary: please create a temporary "solution" for bug 13986 (was:drakx11 can generate ...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-12 14:12 CEST by aguador
Modified: 2019-02-24 11:38 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description aguador 2016-10-12 14:12:02 CEST
Mageia E20 system installed via net on Asus A53S laptop with nVidia graphics.

Defaults were accepted for graphics in installation and the nouveau driver installed. However, right edge bindings do not work on this machine with the nouveau driver, so bumblebee was installed with the proprietary driver was installed later and drakx11 used to configure it. In playing with drakx11 I have found the following:

1) Drakx11 does not specifically say that the on-board Intel graphics need to be configured first, then nVidia. However, if you use drakx11 post installation to configure only the nVidia card, it is listed as Device 1, and it will hang the system.

2) Drakx11 will ask if you want to use the proprietary driver. However, the resulting xorg.conf file will specify the nouveau driver (at least if present on the system), not the nVidia driver

3) It appears that the nouveau driver will always be present as drakx11 installs it if NOT present *even after* you confirm that you want to use the proprietary driver! (Yes, I uninstalled the nouveau driver at one point.)

4) The only way to get the Optimus technology working properly with bumblebee is to eliminate the xorg.conf file as noted in comment 9 of Bug 13986.

I know multiple bug reports have been filed and comments made regarding hybrid graphics systems, including the bug just cited that is targeted for correction in Mageia 7. However, I am filing this separately as it seems that there could be some interim corrective action:

a) Automatic removal or renaming of xorg.conf if Optimus technology is detected.

b) Failing an automatic solution, a warning/notice about eliminating xorg.conf could be added to drakx11

NOTE regarding installation: As I installed Couldron on the only system I have with hybrid graphics, I did not think about the need to configure that card separately -- and I am not new to Linux or installing distros. However, having at least a warning about the hybrid system during installation would be helpful for folks even less skilled/knowledgeable than I.
Marja Van Waes 2016-10-13 11:53:06 CEST

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

Comment 1 aguador 2016-11-14 23:32:32 CET
See also Bug 19572 for details about Optimus and xorg.conf files.
Comment 2 Marja Van Waes 2016-11-15 11:00:08 CET
(In reply to Roy Reese from comment #0)

> 
> I know multiple bug reports have been filed and comments made regarding
> hybrid graphics systems, including the bug just cited that is targeted for
> correction in Mageia 7. However, I am filing this separately as it seems
> that there could be some interim corrective action:
> 
> a) Automatic removal or renaming of xorg.conf if Optimus technology is
> detected.
> 
> b) Failing an automatic solution, a warning/notice about eliminating
> xorg.conf could be added to drakx11
> 
<snip>
> having at least a warning about the hybrid system during installation would
> be helpful for folks even less skilled/knowledgeable than I.

Adjusting the summary accordingly

Summary: drakx11 can generate a bad xorg.conf on hybrid graphics systems => please create a temporary "solution" for bug 13986 (was:drakx11 can generate a bad xorg.conf on hybrid graphics systems)

Comment 3 aguador 2019-02-24 11:38:15 CET
Have just closed this as old as I believe that documentation improvements have helped and I do not recall more problems with this on my Optimus machine, where I have now changed drivers twice in recent months: from nVidia current to nVidia-390 to nouveau.

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


Note You need to log in before you can comment on or make changes to this bug.