Date: Thu, 6 Aug 2020 13:51:46 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: =?ISO-8859-1?Q?S=F8ren?= Schmidt <soren.schmidt@gmail.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: <20200806135146.913617530d4e17ebcf133fb9@bidouilliste.com> In-Reply-To: <1B879FDB-31EA-4C53-90E3-E30CE51DF55D@gmail.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> <1B879FDB-31EA-4C53-90E3-E30CE51DF55D@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 6 Aug 2020 13:46:16 +0200 S=F8ren Schmidt <soren.schmidt@gmail.com> wrote: >=20 >=20 > > On 6 Aug 2020, at 12.13, Emmanuel Vadot <manu@bidouilliste.com> wrote: > >=20 > > On Sun, 2 Aug 2020 11:30:00 +0200 > > S=F8ren Schmidt <soren.schmidt@gmail.com <mailto:soren.schmidt@gmail.co= m>> wrote: > >=20 > >>=20 > >>=20 > >>> On 1 Aug 2020, at 23.55, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.n= et> wrote: > >>>=20 > >>>=20 > >>> In case you would be willing to try building a kernel yourself, try s= omething with a lot of non-essential modules (e.g. the allwinner modules) r= emoved and see what happens (just trying to make the size of the kernel sma= ller). > >>=20 > >> Thats where I startet to see the problem, with my own minimal kernel c= onfig, 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 i= t 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 HD= MI). > >> 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 d= id boot once. > >>=20 > >> The same issue is with my pinebookpro, it behaves exactly the same, bu= t 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. >=20 > OK, I?ll look around a bit and see what gives.? >=20 > >=20 > >> I?ll try to backstep -current to where it did work and se it that brin= gs any light over the issue? > >=20 > > Did you find anything ? >=20 > Yeah VirtualBox managed to crash my Mac into oblivion, so I?m just about = finished getting things back together again (timemachine is nice :) ) >=20 > However, it also fails with my previously good -current release, so that = points pretty squarely at u-boot 2020.07. I?ll try to go back to 2020.04 (p= lus patches to find 4G etc). What patches are you talking about ? > --S=F8ren >=20 > sos@deepcore.dk / sos@freebsd.org > "So much code to hack, so little time" >=20 --=20 Emmanuel Vadot <manu@bidouilliste.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200806135146.913617530d4e17ebcf133fb9>