Bug 29133 - Setting Offloading mode does not regenerate the xorg.conf file, even if mageia-prime-uninstall was done before
Summary: Setting Offloading mode does not regenerate the xorg.conf file, even if magei...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Giuseppe Ghibò
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-15 07:11 CEST by Pierre Bonneau
Modified: 2024-08-22 22:59 CEST (History)
1 user (show)

See Also:
Source RPM: mageia-prime-0.4-12.mga8.nonfree.src.rpm
CVE:
Status comment:


Attachments

Description Pierre Bonneau 2021-06-15 07:11:34 CEST
Description of problem:
When you run mageia-prime-install, a config file is generating and stored in the /etc/X11 folder for later use. That file is also used if you execute mageia-prime-install -p even if the content should be different.

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

How reproducible:
Execute mageia-prime-install
reboot to nvidia config
#nvidia card used
Execute mageia-prime-uninstall
reboot to intel config
#intel card used
execute mageia-prime-install -p
#the wrong file is used.
reboot
#nvidia card used
execute mageia-prime-uninstall
reboot to intel mode
#intel card used
remove the file xorg.conf.nvidiaprime.preserve
execute mageia-prime-install -p
#intel card used with nvidia offloading

it's working as expected.
Comment 1 Aurelien Oudelet 2021-06-15 10:54:41 CEST
Hi, as far as I read, if /etc/X11/xorg.conf was previously set by mageia-prime, the offloading doesn't work, you need to remove "xorg.conf.nvidiaprime.preserve" even after do 'mageia-prime-uninstall'...

Assigning to Giuseppe.

Assignee: bugsquad => ghibomgx
CC: (none) => ouaurelien
Source RPM: Mageia-prime => mageia-prime-0.4-12.mga8.nonfree.src.rpm
Summary: Offloading mode don't regenerate the config file => Setting Offloading mode does not regenerate the xorg.conf file, even if mageia-prime-uninstall was done before

Comment 2 Giuseppe Ghibò 2021-06-15 13:25:47 CEST
After having unconfigured try the offload configuration adding the -f option (so mageia-prime-install -f -p).

By default mageia-prime-uninstall preserves the working xorg.conf file after
unconfiguring. In this way a subsequent call to mageia-prime-install can re-use
such file without having to regenerate one. The '-f' option permits to override this behaviour and thus create always a fresh xorg.conf, without having to re-use the preserved one.
Comment 3 Pierre Bonneau 2021-06-15 13:52:48 CEST
Hello,

Thank you for your quick feedback.

I still think it would be nice for the tool to detect that the saved configuration is not accurate. It's quite difficult to know what the system is doing, and it took me 3 days to figure out that issue.

I'm going to update the mageia wiki with your answer.

Also, if I might, it would be nice when starting the tool with a command line to start by a comment line that explain in plain English what will be done.

Ex : 
mageia-prime-install -p -f
#Installing Discret card in offloading mode.
#Forcing generation of configuration file
...
Comment 4 Marja Van Waes 2024-08-22 22:59:12 CEST
We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

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


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