Bug 25178

Summary:	mageia-prime loads nvidia module when configured to intel
Product:	Mageia	Reporter:	Patric Schramm <patric.schramm>
Component:	RPM Packages	Assignee:	Giuseppe Ghibò <ghibomgx>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fri, marja11, nicolas.robaux
Version:	7
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	mageia-prime	CVE:
Status comment:

Description Patric Schramm 2019-07-25 17:52:55 CEST

Installed Mga 7.1 x64 on my notebook yesterday. Afterwards i installed the latest nvidia drivers from the repo and mageia-prime because i have an optimus notebook with an nvidia gtx 950m.

Switching to the nvidia driver works fine without any problems but switching back gives me a warning in the boot process that a kernel module that is loaded is conflicting with the driver that is configured for my  x-server.

A dmesg | grep -i nvidia gives me :

[    2.791644] nvidia: loading out-of-tree module taints kernel.
[    2.791650] nvidia: module license 'NVIDIA' taints kernel.
[    2.802069] nvidia-nvlink: Nvlink Core is being initialized, major device number 247
[    2.802459] nvidia 0000:01:00.0: enabling device (0406 -> 0407)
[    3.001862] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  430.26  Tue Jun  4 17:40:52 CDT 2019
[    3.063258] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  430.26  Tue Jun  4 17:45:09 CDT 2019
[    3.066190] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    3.066191] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1

So i assume that the nvidia module is still loaded.

Morgan Leijström 2019-07-25 21:45:47 CEST

CC: (none) => fri

Comment 1 Marja Van Waes 2019-07-26 09:11:29 CEST

Assigning to our mageia-prime maintainer

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

Comment 2 Patric Schramm 2019-09-01 10:57:23 CEST

Or is this and the additional "warning" after reboot normal. The switching in general does work as ecpected but i thing it would be good to get rid of the warning message on startup to not scare off users.

Comment 3 Nicolas Robaux 2019-10-15 11:06:17 CEST

I also have this message, after removing all nvidia packages, and uninstalling prime, in the boot process that a kernel module that is loaded is conflicting with the driver that is configured for my x-server.

And by the way, I have uninstalled and removed because prime doesn't work at all (X11 can't even start anymore…)

CC: (none) => nicolas.robaux

Comment 4 Aurelien Oudelet 2021-07-06 13:15:38 CEST

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Comment 5 Marja Van Waes 2021-09-07 14:09:10 CEST

Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

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