X-Original-To: alpine-devel@mail.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail.alpinelinux.org (dallas-a1.alpinelinux.org [127.0.0.1]) by mail.alpinelinux.org (Postfix) with ESMTP id 1A680DC7E3E for ; Tue, 22 Mar 2016 12:05:47 +0000 (UTC) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id E00CBDC7DAF for ; Tue, 22 Mar 2016 12:05:46 +0000 (UTC) Received: from cotinga.riseup.net (unknown [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 90CE11A3590; Tue, 22 Mar 2016 12:05:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1458648345; bh=inYsAVrPY5LDZdJfdZBnCeI1ZcCGRXw/DmOb41s5mzo=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=pXmNlKpuLwK+SwQE6bINLnsHOlbIYbNbuWFGJts6ztwpTp0NKAueZuqzbs4WoVBpM 3bnZ7oM4uiETAvi84RWHHByDBz2o6pgCZ5oWC2AOa1dgD4238CJdR3iaV1z7UR5cPH 5FzL3uDLwGJcQWCOjmCPsW6+ROvu3NKg6r5Z1XMw= Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: roger.newman) with ESMTPSA id 443264001E Subject: Re: [alpine-devel] RPI3 doesn't boot on Alpine Linux 3.3.2 To: Timo Teras References: <20160319094349.0667344c@vostro> <20160321113413.66bd0282@vostro.util.wtbts.net> Cc: alpine-devel From: Roger Newman Message-ID: <56F134CE.4050200@riseup.net> Date: Tue, 22 Mar 2016 13:04:30 +0100 X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 In-Reply-To: <20160321113413.66bd0282@vostro.util.wtbts.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.99 at mx1.riseup.net X-Virus-Status: Clean X-Virus-Scanned: ClamAV using ClamSMTP Timo Teras wrote: > On Sat, 19 Mar 2016 20:16:48 +0100 > Fabien Germain wrote: > >> On Sat, Mar 19, 2016 at 8:43 AM, Timo Teras 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 : >> http://bugs.alpinelinux.org/issues/5296 > > 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 > > > --- > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org > Help: alpine-devel+help@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? 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 --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---