Timo Teras <timo.teras_at_iki.fi> wrote:
> On Sat, 19 Mar 2016 20:16:48 +0100
> Fabien Germain <fabien.germain_at_gmail.com> wrote:
>> On Sat, Mar 19, 2016 at 8:43 AM, Timo Teras <timo.teras_at_iki.fi> wrote:
>>> Need to check that. I did test boot an early edge build with the
>>> same kernel config on rpi3 earlier.
>> It seems like I'm not the only one :
> Yes, seems a late mkinitfs change broke rpi boot sequence. I believe
> the 3.3.2 does not boot at all on any rpi.
> We'll bump to new kernels, incorporate that fix, and update the rpi
> firmwares too. You can expect 3.3.3 soonish (probably tomorrow when
> all new kernels are built).
> Unsubscribe: alpine-devel+unsubscribe_at_lists.alpinelinux.org
> Help: alpine-devel+help_at_lists.alpinelinux.org
Thank you -Timo- for your update.
After building a new image, the rpi3 boots alpine just fine.
But, some firmware file/s is/are missing e.g. "brcmfmac43430-sdio.bin".
This is the reason, why currently no wifi is available.
Did I miss to install something or is it just not in the image?
[ 6.321397] cfg80211: Calling CRDA to update world regulatory domain
[ 6.383578] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength init done for chip 43430 rev 1 pmurev 24
[ 6.383969] usbcore: registered new interface driver brcmfmac
[ 6.384142] brcmfmac_sdio mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.bin failed with error -2
[ 6.384150] brcmfmac_sdio mmc1:0001:1: Falling back to user helper
Received on Tue Mar 22 2016 - 13:04:30 GMT