Date: Sun, 2 Aug 2020 11:30:00 +0200 From: =?utf-8?Q?S=C3=B8ren_Schmidt?= <soren.schmidt@gmail.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: Emmanuel Vadot <manu@bidouilliste.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: RockPro64 with latest image fails to boot? Message-ID: <3D9B8A33-D537-4B21-B0BD-5E550A2294D7@gmail.com> In-Reply-To: <F4716F7B-E445-45FD-8B16-79B994A84BB9@lists.zabbadoz.net> References: <C063D3D8-07AE-4A0A-9A75-A42C7DAA6F36@gmail.com> <20200801185716.a1c5a2972fdcf3a05902f256@bidouilliste.com> <010E3738-FB70-4A58-82A6-391252EB7A4B@gmail.com> <F4716F7B-E445-45FD-8B16-79B994A84BB9@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 1 Aug 2020, at 23.55, Bjoern A. Zeeb = <bzeeb-lists@lists.zabbadoz.net> wrote: >=20 >=20 > In case you would be willing to try building a kernel yourself, try = something with a lot of non-essential modules (e.g. the allwinner = modules) removed and see what happens (just trying to make the size of = the kernel smaller). Thats where I startet to see the problem, with my own minimal kernel = config, to make certain I hadn=E2=80=99t goofed it up I tried the latest = stock image. I have tried different SD cards and PSU's to rule those out (and yes it = boots every time on a NetBSD image). However from 20+ boots I can say that it dies in different places but = close to the original post here. BUT it did manage to boot once (without = HDMI). As the HW boots my older custom kernel just fine (and the other BSD=E2=80=99= s) I don=E2=80=99t think its a HW problem, but more likely a race of = sorts since it did boot once. The same issue is with my pinebookpro, it behaves exactly the same, but = no output on the display at all, just console.. I=E2=80=99ll try to backstep -current to where it did work and se it = that brings any light over the issue=E2=80=A6 -S=C3=B8ren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D9B8A33-D537-4B21-B0BD-5E550A2294D7>