Thanks Peter. I did figure that out yesterday. Symlink seemed to work. I also pulled in https://github.com/RPi-Distro/firmware-nonfree/blob/master/brcm/brcmfmac43455-sdio.txt as well.
I did run into issues with wifi, but I'd like to test when the upstream is patched.
On Wed, Aug 12, 2020 at 4:19 AM Peter Robinson <pbrobinson@gmail.com> wrote:
> Taking a stab at fedora 32 on a R Pi 3A+. Looks like there's missing firmware. Based on the FAQ the wifi should work out of the box but it doesn't seem to be the case:
>
> [ 43.501327] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt failed with error -2
> [ 43.501632] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.txt failed with error -2
>
> I do not see this file in: /usr/lib/firmware/brcm. I do see one for model b: "brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt"
So that's an admission, must have missed that when we pushed the NVRAM
upstream. The NVRAM is device specific, it's not really a firmware,
but we know all the 3A module is the same as the B+ so you can
actually just do:
ln -s /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
/lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt
I'll organise a PR for upstream to fix that.
> Used the following for firmware:
> arm-image-installer --image=Fedora-Server-armhfp-32-1.6-sda.raw.xz --target=rpi3 --media=/dev/sdf
>
> Let me know what additional info you might need, and I'm happy to test.
> _______________________________________________
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-leave@lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
No comments:
Post a Comment