Bug 30726 - dkms-bbswitch: Fix compatibility with kernel 5.18+
Summary: dkms-bbswitch: Fix compatibility with kernel 5.18+
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2022-08-08 22:16 CEST by Rémi Verschelde
Modified: 2022-08-13 04:33 CEST (History)
4 users (show)

See Also:
Source RPM: dkms-bbswitch-0.8-13.mga8
CVE:
Status comment:


Attachments

Description Rémi Verschelde 2022-08-08 22:16:26 CEST
According to a report by aguador on the dev ML, dkms-bbswitch fails building with kernel 5.18:
https://ml.mageia.org/l/arc/dev/2022-08/msg00052.html

I added a patch provided by Juan Magallón to fix it.

Advisory:
========

Updated dkms-bbswitch to fix support for kernel 5.18+

  This update adds a patch to fix support for kernel 5.18 and later in
  dkms-bbswitch.

SRPM in core/updates_testing:
=============================

dkms-bbswitch-0.8-13.1.mga8

RPM in core/updates_testing:
============================

dkms-bbswitch-0.8-13.1.mga8
Comment 1 aguador 2022-08-09 15:43:33 CEST
Patched version works perfectly in Cauldron...

CC: (none) => waterbearer54

Comment 2 Thomas Andrews 2022-08-12 04:13:20 CEST
No optimus here, and all the bumblebees are outside, so I can't test this for function in MGA8. But, I can say that it built successfully with kernel-desktop 5.18.15.

So, following guidance from earlier updates, I'm giving this an OK and validating. Advisory in Comment 0.

CC: (none) => andrewsfarm, sysadmin-bugs
Whiteboard: (none) => MGA8-64-OK
Keywords: (none) => validated_update

Dave Hodgins 2022-08-12 21:45:11 CEST

CC: (none) => davidwhodgins
Keywords: (none) => advisory

Comment 3 Mageia Robot 2022-08-13 04:33:34 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0110.html

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


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