Date: Thu, 6 Aug 2020 13:46:16 +0200 From: =?utf-8?Q?S=C3=B8ren_Schmidt?= <soren.schmidt@gmail.com> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: RockPro64 with latest image fails to boot? Message-ID: <1B879FDB-31EA-4C53-90E3-E30CE51DF55D@gmail.com> In-Reply-To: <20200806121314.7b877e777f518db36c69f8a4@bidouilliste.com> 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> <3D9B8A33-D537-4B21-B0BD-5E550A2294D7@gmail.com> <20200806121314.7b877e777f518db36c69f8a4@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 6 Aug 2020, at 12.13, Emmanuel Vadot <manu@bidouilliste.com> wrote: >=20 > On Sun, 2 Aug 2020 11:30:00 +0200 > S=C3=B8ren Schmidt <soren.schmidt@gmail.com = <mailto:soren.schmidt@gmail.com>> wrote: >=20 >>=20 >>=20 >>> 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). >>=20 >> Thats where I startet to see the problem, with my own minimal kernel = config, to make certain I hadn?t goofed it up I tried the latest stock = image. >>=20 >> I have tried different SD cards and PSU's to rule those out (and yes = it boots every time on a NetBSD image). >>=20 >> 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?s) I don?t think its a HW problem, but more likely a race of sorts = since it did boot once. >>=20 >> The same issue is with my pinebookpro, it behaves exactly the same, = but no output on the display at all, just console.. >=20 > There is no support for eDP in mainline u-boot. > Some patches are around to add support but I don't think that they > have been submitted upstream. > There is another issue with eDP and FreeBSD kernel, u-boot set the > CPLL to 600Mhz (iirc) but the DTS have it set to 800Mhz so when we > process the assigned-clocks property and set it to 800Mhz the eDP > clock (which is derived from CPLL) isn't correct anymore and we lose > the display. OK, I=E2=80=99ll look around a bit and see what gives.=E2=80=99 >=20 >> I?ll try to backstep -current to where it did work and se it that = brings any light over the issue? >=20 > Did you find anything ? Yeah VirtualBox managed to crash my Mac into oblivion, so I=E2=80=99m = just about finished getting things back together again (timemachine is = nice :) ) However, it also fails with my previously good -current release, so that = points pretty squarely at u-boot 2020.07. I=E2=80=99ll try to go back to = 2020.04 (plus patches to find 4G etc). --S=C3=B8ren sos@deepcore.dk / sos@freebsd.org "So much code to hack, so little time"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1B879FDB-31EA-4C53-90E3-E30CE51DF55D>