Bug 28561 - Latest kernel-firmware-nonfree stops wireless from working on rpi4 model b
Summary: Latest kernel-firmware-nonfree stops wireless from working on rpi4 model b
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: aarch64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7TOO MGA7-64-OK MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2021-03-08 23:11 CET by Dave Hodgins
Modified: 2021-03-12 02:27 CET (History)
3 users (show)

See Also:
Source RPM: kernel-firmware-nonfree-20210223-1.mga8.nonfree
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Dave Hodgins 2021-03-08 23:11:14 CET 
After rebooting with kernel-firmware-nonfree-20210223-1.mga8.nonfree.noarch.rpm
installed, the wifi device was no longer found on my rpi4b.

dmesg shows ...
[  585.364428] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[  586.423532] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[  587.433630] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50


Downgrading to kernel-firmware-nonfree-20201230-2.mga8.nonfree.noarch.rpm
and rebooting makes it available again.
Comment 2 Dave Hodgins 2021-03-09 02:43:41 CET 
Yes
Morgan Leijström 2021-03-09 10:39:54 CET

CC: (none) => fri

Comment 3 Thomas Backlund 2021-03-09 16:48:48 CET 
ok, will roll new firmware tarballs so all can get the fix
Comment 4 Thomas Backlund 2021-03-10 20:14:17 CET 
Advisory:
kernel-firmware-nonfree update in MGASA-2021-0103 and MGASA-2021-0104
caused wifi to stop working on Raspberry Pi 4B. This update fixes the
NVRAM file so it starts working again. It also adds or updates the
following firmwares:

* kernel-firmware-nonfree:
  - brcm: add missing symlink for BananaPi M3
  - brcm: Add symlink for BananaPi M2 to brcmfmac43430-sdio config
  - brcm: Fix Raspberry Pi 4B NVRAM file
  - mediatek: add frimware for mediatek bluetooth chip (MT7921)
  - Mellanox: Add new mlxsw_spectrum firmware xx.2008.2406
  - silabs: add new firmware for WF200

* iwlwifi-firmware:
  - iwlwifi: update 7265D firmware
  - iwlwifi: update 9000-family firmwares
  - iwlwifi: add new (cc, Qu, QuZ, ty) FWs from core59-66 release
    (api 62, not in use yet)


Mga7:
SRPMS:
kernel-firmware-nonfree-20210310-1.mga7.nonfree.src.rpm

noarch:
iwlwifi-firmware-20210310-1.mga7.nonfree.noarch.rpm
kernel-firmware-nonfree-20210310-1.mga7.nonfree.noarch.rpm
ralink-firmware-20210310-1.mga7.nonfree.noarch.rpm
rtlwifi-firmware-20210310-1.mga7.nonfree.noarch.rpm


Mga8:
kernel-firmware-nonfree-20210310-1.mga8.nonfree.src.rpm

noarch:
iwlwifi-firmware-20210310-1.mga8.nonfree.noarch.rpm
kernel-firmware-nonfree-20210310-1.mga8.nonfree.noarch.rpm
ralink-firmware-20210310-1.mga8.nonfree.noarch.rpm
rtlwifi-firmware-20210310-1.mga8.nonfree.noarch.rpm

Assignee: kernel => qa-bugs
Whiteboard: (none) => MGA7TOO

Comment 5 Morgan Leijström 2021-03-10 21:55:57 CET 
mga7 64 bit OK on My workstation "svarten": Mainboard: Sabertooth P67, CPU: i7-3770.

Clean update, reboot, no errors in journal, no regression noted in my normal use.
Comment 6 Dave Hodgins 2021-03-10 23:54:07 CET 
Confirmed the fix for wireless on rpi4 model b is working.
Comment 7 Dave Hodgins 2021-03-11 01:25:22 CET 
No regressions found in Mageia 7 or 8 x86_64.
Comment 8 Dave Hodgins 2021-03-11 21:40:41 CET 
No regressions reported by others, so adding the ok and validating.

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

Comment 9 Aurelien Oudelet 2021-03-11 23:21:39 CET 
Advisory committed to SVN.

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

Comment 10 Mageia Robot 2021-03-12 02:27:17 CET 
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2021-0040.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.