X-Original-To: alpine-user@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id CBBC1F858B2 for ; Thu, 3 Jan 2019 13:14:13 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 2CAE69E1ECF; Thu, 3 Jan 2019 13:14:13 +0000 (GMT) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 578B59E1E49; Thu, 3 Jan 2019 13:14:11 +0000 (GMT) Date: Thu, 3 Jan 2019 14:14:07 +0100 From: Natanael Copa To: paul gauret Cc: "alpine-user@lists.alpinelinux.org" Subject: Re: [alpine-user] Can't boot linux-vanilla on armhf Message-ID: <20190103141407.1299dd2e@ncopa-desktop.copa.dup.pw> In-Reply-To: <581900963.13520645.1546517250292@mail.yahoo.com> References: <581900963.13520645.1546517250292.ref@mail.yahoo.com> <581900963.13520645.1546517250292@mail.yahoo.com> X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.32; x86_64-alpine-linux-musl) X-Mailinglist: alpine-user Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi! On Thu, 3 Jan 2019 12:07:30 +0000 (UTC) paul gauret wrote: > I can't boot the Alpine linux kernel on my armhf boards (tested on Cubieb= oard and OrangePI Plus with similar results). > Sample u-boot session below, messages stop after "Starting kernel" and bo= ard requires a hard reset: > ----- > =3D> setenv bootargs earlyprintk console=3DttyS0,115200 root=3D/dev/mmcbl= k0p2 rw rootwait=3D> env set fdt_high ffffffff=3D> fatload mmc 0 0x46000000= vmlinuz-vanilla3834368 bytes read in 310 ms (11.8 MiB/s)=3D> fatload mmc 0= 0x49000000 linux-4.19.13-0-vanilla-sun4i-a10-cubieboard.dtb22448 bytes rea= d in 4 ms (5.4 MiB/s)=3D> bootz 0x46000000 - 0x49000000## Flattened Device = Tree blob at 49000000=A0 =A0Booting using the fdt blob at 0x49000000=A0 =A0= Using Device Tree in place at 49000000, end 490087af =20 > Starting kernel ... > ----- >=20 > For reference I can boot my custom built mainline kernel using the above = commands without any trouble. > What I've already tried without success:- Use mainline u-boot rather than= the Alpine u-boot for cubieboard- boot through extlinux- user older versio= ns of the Alpine vanilla kernel > Am I doing something wrong here or shall I open a bug?=A0 > Happy to help with troubleshooting if needed. >=20 I'm pretty sure this is a bug. Please create an issue on bugs.alpinelinux.o= rg. It would also be good if you could share your kenrel config that you know w= orks. Thanks! -nc --- Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org Help: alpine-user+help@lists.alpinelinux.org ---