Hello, It seems that the kernel 5.5.4-1 is in conflicts with package dkms-broadcom-wl[< 6.30.223.271-55] $urpmf --conflicts kernel-desktop-5.5.4-1 kernel-desktop-5.5.4-1.mga7:btrfs-progs[< 5.1.1-1] kernel-desktop-5.5.4-1.mga7:dkms-broadcom-wl[< 6.30.223.271-55] kernel-desktop-5.5.4-1.mga7:dkms-nvidia-current[< 430.64-4] kernel-desktop-5.5.4-1.mga7:dkms-nvidia304[< 304.137-3] kernel-desktop-5.5.4-1.mga7:dkms-nvidia340[< 340.108-2] kernel-desktop-5.5.4-1.mga7:dkms-nvidia390[< 390.132-2] kernel-desktop-5.5.4-1.mga7:dkms-virtualbox[< 6.0.16-2] kernel-desktop-5.5.4-1.mga7:dkms-xtables-addons[< 3.8-1] kernel-desktop-5.5.4-1.mga7:efibootmgr[< 16-3] kernel-desktop-5.5.4-1.mga7:grub2[< 2.02.0-15] kernel-desktop-5.5.4-1.mga7:grub2-efi[< 2.02.0-15] kernel-desktop-5.5.4-1.mga7:kernel-firmware-nonfree[< 20190603-1] kernel-desktop-5.5.4-1.mga7:mageia-gfxboot-theme[< 4.5.14.10-1] kernel-desktop-5.5.4-1.mga7:microcode[< 0.20190514-1] kernel-desktop-5.5.4-1.mga7:radeon-firmware[< 20190603-1] kernel-desktop-5.5.4-1.mga7:x11-driver-input-vmmouse[< 13.1.0-1] But it seems that the broadcom package is still in the updates_testing repository. Therefore, users updating to 5.5.4-1 kernel might lose there wifi connexion due to removal of 6.30.223.271-53. Note: i can't test as i don't have the hardware.
Ah, we tested if some code fixes would help for bug 25884, but that didn't help. As the fixes are valid and confirmed in bug 25884 that the driver is still working, flushing this out type: bugfix subject: Updated broacom-wl packages fix bugs src: 7: nonfree: - broadcom-wl-6.30.223.271-55.mga7.nonfree description: | Updated broadcom-wl driver fixes kernel warnings, a mac profile discrepancy and allows normal users to send ioctl requests. references: - https://bugs.mageia.org/show_bug.cgi?id=26246
CC: (none) => tmb, sysadmin-bugsKeywords: (none) => advisory, validated_updateWhiteboard: (none) => MGA7-64-OK
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2020-0062.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED