Bug 30781 - kernel 5.19.3 from backports conflicts with dkms-nvidia-current-470.141.03
Summary: kernel 5.19.3 from backports conflicts with dkms-nvidia-current-470.141.03
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 30814
Blocks:
  Show dependency treegraph
 
Reported: 2022-08-28 20:43 CEST by Oleg Bosis
Modified: 2022-09-10 22:35 CEST (History)
3 users (show)

See Also:
Source RPM: kernel-5.19.3-1.mga8, nvidia-current-470.141.03-1.mga8
CVE:
Status comment:


Attachments

Description Oleg Bosis 2022-08-28 20:43:07 CEST
Description of problem:
I have a laptop with nvidia GF 650M video card and the latest proprietary nvidia driver that supports it is 470 series.

If i try to install latest kernel from backports repository I get the following error message:

The following packages have to be removed for others to be upgraded:
dkms-nvidia-current-470.141.03-1.mga8.nonfree.x86_64
 (due to conflicts with kernel-desktop-5.19.3-1.mga8-1-1.mga8.x86_64)
nvidia-current-cuda-opencl-470.141.03-1.mga8.nonfree.x86_64
 (due to unsatisfied kmod(nvidia-current.ko) == 470.141.03)
x11-driver-video-nvidia-current-470.141.03-1.mga8.nonfree.x86_64
 (due to unsatisfied kmod(nvidia-current.ko) == 470.141.03,
  due to unsatisfied nvidia-current-cuda-opencl == 470.141.03-1.mga8.nonfree) (y/N)

Version-Release number of selected component (if applicable):
kernel-desktop-5.19.3-1.mga8-1-1
nvidia-current-470.141.03-1

How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Marja Van Waes 2022-08-28 23:29:09 CEST
Assigning to our kernel and drivers maintainers.
You might want to try whether it is any better with kernel-5.19.4-1.mga8 from
Mageia 8 core/backports_testing

Source RPM: (none) => kernel-5.19.3-1.mga8, nvidia-current-470.141.03-1.mga8
CC: (none) => marja11
Assignee: bugsquad => kernel
Summary: kernel 5.19.3 conflicts with dkms-nvidia-current-470.141.03 => kernel 5.19.3 from backports conflicts with dkms-nvidia-current-470.141.03

Comment 2 Dave Hodgins 2022-08-29 02:39:40 CEST
Most likely the nvidia driver will have to be removed and switch to nouveau
to use the backports kernel as support ended for the 460 and 470 series cards
in Oct, 2021.

Either that or switch to the core updates version of the kernel for the rest
of Mageia 8.

I'll leave it to the kernel team to confirm.

CC: (none) => davidwhodgins

Comment 3 Thomas Backlund 2022-08-29 05:42:28 CEST
Sorry, it's a fallout of backporting 5.19 bits from Cauldrom.

In Cauldron / upcomimg Mageia 9 the nvidia R470 driver is called nvidia470, and the kernel has proper conflicts against dkms-nvidia470.

the nvidia-current in Cauldron / upcoming Mga9 is based on R515 and has a conflict against too old R5xx driver...

That's why you hit this issue...

I've fixed it in svn so it will be part of next backports build ( > 5.19.4-1.mga8 )
Comment 4 Thomas Backlund 2022-08-29 05:53:40 CEST
I've just submitted a  kernel-5.19.4-2.mga8 to backports_testing that should fix this issue...
Comment 5 Morgan Leijström 2022-08-29 10:03:55 CEST
I missed this issue while testing kernel 5.19.3 as I had the backports nvidia-current installed...

Now OK with non-backport nvidia-current;

$ uname -a
Linux svarten.tribun 5.19.4-desktop-2.mga8 #1 SMP PREEMPT_DYNAMIC Mon Aug 29 03:52:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ dkms status | grep 19.4
virtualbox, 6.1.36-1.mga8, 5.19.4-desktop-2.mga8, x86_64: installed 
nvidia-current, 470.141.03-1.mga8.nonfree, 5.19.4-desktop-2.mga8, x86_64: installed

I guess there will be a separate kernel backport bug to report in.

CC: (none) => fri

Comment 6 Oleg Bosis 2022-08-29 22:20:49 CEST
Yes, kernel 5.19.4 installs normally without conflict. Thank you :)
Thomas Backlund 2022-09-06 00:51:49 CEST

Depends on: (none) => 30814

Comment 7 Thomas Backlund 2022-09-10 22:35:05 CEST
fixed in backports with kernel-5.19.7-1.mga8

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


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