Subject: [alpine-devel] RPI3 doesn't boot on Alpine Linux 3.3.2

From: Fabien Germain <[email-masked]>
Date: Fri, 18 Mar 2016 17:18:06 +0100

Hello,

Thanks for releasing v3.3.2 ! I saw that
http://bugs.alpinelinux.org/issues/5197 was closed with it, and had a try
to boot the new Raspberry Pi 3 with this new 3.3.2 version, but
unfortunately it does not work.

Whereas if I get the official kernel.img from
https://github.com/raspberrypi/firmware/blob/master/boot/kernel.img and
modify config.txt to use it instead of the kernel provided by Alpine Linux,
it does boot.

Am I missing something ?

Fabien

---

From: Timo Teras <[email-masked]>
Date: Sat, 19 Mar 2016 09:43:48 +0200

On Fri, 18 Mar 2016 17:18:06 +0100
Fabien Germain <[email-masked]> wrote:

> http://bugs.alpinelinux.org/issues/5197 was closed with it, and had a
> try to boot the new Raspberry Pi 3 with this new 3.3.2 version, but
> https://github.com/raspberrypi/firmware/blob/master/boot/kernel.img
> and modify config.txt to use it instead of the kernel provided by
> Alpine Linux, it does boot.
> 
> Am I missing something ?

Need to check that. I did test boot an early edge build with the same
kernel config on rpi3 earlier.

---
Unsubscribe:  [email-masked]
Help:         [email-masked]
---

---

From: Fabien Germain <[email-masked]>
Date: Sat, 19 Mar 2016 20:16:48 +0100

> kernel config on rpi3 earlier.

It seems like I'm not the only one : http://bugs.alpinelinux.org/issues/5296

Fabien

---

From: Timo Teras <[email-masked]>
Date: Mon, 21 Mar 2016 11:34:13 +0200

On Sat, 19 Mar 2016 20:16:48 +0100
Fabien Germain <[email-masked]> wrote:

> > Need to check that. I did test boot an early edge build with the
> > same kernel config on rpi3 earlier.
> >  
> 

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).

/Timo

---

---

From: Fabien Germain <[email-masked]>
Date: Thu, 24 Mar 2016 18:19:02 +0100

Hello,

> all new kernels are built).

Indeed I can confirm that now RPI3 works fine with v3.3.3. Thanks :-)

Fabien

---

From: Roger Newman <[email-masked]>
Date: Tue, 22 Mar 2016 13:04:30 +0100

> Help:         [email-masked]

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?

dmesg:

...
[ 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
...

-- 
Roger Newman

---

---

From: Timo Teras <[email-masked]>
Date: Tue, 22 Mar 2016 17:51:21 +0200

On Tue, 22 Mar 2016 13:04:30 +0100
Roger Newman <[email-masked]> wrote:

> 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?
> 
> dmesg:
> 
> ...
> [ 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 ...

the firmware is not upstream yet. we are tracking the wlan support
separately in bug:
 http://bugs.alpinelinux.org/issues/5297

---