Bug 31147 - dkms nvidia-5.15.xxxx not build with kernel > 6.0
Summary: dkms nvidia-5.15.xxxx not build with kernel > 6.0
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard: MGA8TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-18 11:05 CET by Xavier BERTAUX
Modified: 2022-11-23 09:37 CET (History)
2 users (show)

See Also:
Source RPM: kernel-desktop-6.0.x-y
CVE:
Status comment:


Attachments

Description Xavier BERTAUX 2022-11-18 11:05:27 CET
with new kernel > 6.0 dkms-nvidia-5.15xxxx don't build
Xavier BERTAUX 2022-11-18 11:05:38 CET

CC: (none) => bertauxx

Comment 1 Xavier BERTAUX 2022-11-18 11:08:35 CET
idem on Mageia8
Comment 2 Lewis Smith 2022-11-19 21:22:50 CET
Thank you for the report, and the confirmation about Mageia 8 also.

It is curious that this has not been reported sooner, because these kernels have been out for some time now (at least beginning of November).

Assigning to kernel; there may be a simple explanation.

Source RPM: (none) => kernel-desktop-6.0.x-y
Whiteboard: (none) => MGA8TOO
Assignee: bugsquad => kernel

Comment 3 Thomas Backlund 2022-11-19 21:35:07 CET
there was a temporary hicup with kerrnel 6.0.8-2, but that was fixed some 6-10 hours later in 6.0.8-3
Comment 4 Xavier BERTAUX 2022-11-19 23:53:41 CET
it's idem with latest kernel 6.0.9
Comment 5 Thomas Backlund 2022-11-20 00:41:50 CET
then you need  to show the build log, attach it to this bugreport
Comment 6 Thomas Backlund 2022-11-23 01:36:55 CET
Fixed with nvidia-current-515.86.01-1.mga8.nonfree in backports_testing

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

Comment 7 Morgan Leijström 2022-11-23 09:37:40 CET
(In reply to Lewis Smith from comment #2)
> It is curious that this has not been reported sooner, because these kernels
> have been out for some time now (at least beginning of November).

None assigned QA until 2022-11-19

Maybe we should announce better on QA mailing list  - and dev and maybe other, when internal testing is wanted.

And IMO it would be good anyway to make a bug report to track the testing, even if it say it is not meant to land in updates repo.

CC: (none) => fri


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