Date: Thu, 16 Nov 2017 01:40:07 -0800 From: Mark Millard <markmi@dsl-only.net> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: Andreas Schwarz <freebsd.asc@strcmp.org>, freebsd-arm@FreeBSD.org Subject: Re: PINE64 - 12.0-CURRENT r324563 - ntpd can't keep time Message-ID: <4C01F5D2-BBEA-4E2A-8414-0F503BDD7917@dsl-only.net> In-Reply-To: <20171116094901.752e8b0f4ca15eb1349ef1fd@bidouilliste.com> References: <d85f883f-84c2-5051-1996-2a0e73a2c1e7@restart.be> <4BF75B1E-318C-414A-B5D4-4BA7D6578316@dsl-only.net> <1509029871.56824.49.camel@freebsd.org> <c2bff518-89ce-4956-2548-e56afab5d83d@restart.be> <4af740148ca.47a474e3@mail.schwarzes.net> <04b67007-a95a-9e40-28b4-764adf8b2ded@restart.be> <FCA144E8-121A-48A5-8CDB-101FBDE6E84C@dsl-only.net> <dceb4702-8ede-aadd-17d8-ed41436955ad@restart.be> <4aff37249b6.70779c93@mail.schwarzes.net> <4AB259A5-F00A-408F-968A-26AD8D776708@dsl-only.net> <4aff62bc14e.1f031cb6@mail.schwarzes.net> <20171115094739.2dbd2a345738be42e56ff772@bidouilliste.com> <4b007e1861e.7facb1c6@mail.schwarzes.net> <20171116094901.752e8b0f4ca15eb1349ef1fd@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-Nov-16, at 12:49 AM, Emmanuel Vadot <manu at bidouilliste.com> = wrote: > On Wed, 15 Nov 2017 22:18:31 +0100 (CET) > Andreas Schwarz <freebsd.asc at strcmp.org> wrote: >=20 >> On 15.11.17, Emmanuel Vadot wrote: >>=20 >>> On Wed, 15 Nov 2017 02:09:06 +0100 (CET) >>> Andreas Schwarz <freebsd.asc@strcmp.org> wrote: >>>=20 >>>> Latest u-boot-sunxi-with-spl.bin was not working for me, I'm using = an older=20 >>>> one. Maybe a dtb processing problem, mine is up to date (created = from the=20 >>>> dts). >>>>=20 >>>> -asc >>>=20 >>> What was the problem with the ports ? >>> Up to date with what ? sys/dts/arm64/ (sys/boot/fdt/dts/arm64) ? >>>=20 >>> The current u-boot ports provide the DTS (it came from upstream = Linux) >>> and doesn't have the PMU (Power Management Unit) or the cpu-supply >>> property for the cpu node while the one from sys/dts/arm64 does. >>=20 >> This makes the difference, the u-boot port which I have in use, is = loading=20 >> the dtb from the fat partition. It's probably the u-boot port, which = was=20 >> provided with the pine64 image from the raspbsd.org page. This was my >> "starting point", in the meantime I've tried to replace the related = blocks=20 >> with differnt u-boot images, but not successful. >>=20 >> -asc >=20 > Could you try the same setup that you have now but removing 1200000 > 1300000 from the operating_point table in sys/dts/arm64/a64.dtsi > please ? > I'm not sure that the pine64 is stable enough at this frequency. Just FYI: whatever frequency ends up being used based on the u-boot-master based u-boot has worked fine for me on the Pine64+ 2GB. -j4 buidlworld, buildkernel. (clang full and extras, lldb, lld bootstrapped and normal all being included.) Also poudriere building ports allowing the job to use all 4 cores. I build gcc7 and what it depends on, for example. But I have a case with a fan for cooling and heatsinks. The power supply is one for an official rpi3 one as well. (So, it has a slightly higher voltage than normal: 5.1V.) The fan gets power from the Pine64+ 2GB. But the USB SSD is via a powered hub. The hub is the only USB device plugged in. Ethernet present and sometimes used. FYI: my last from-scratch buildworld buildkernel on the Pine64+ 2GB took a little under 18 hr + 10 min and was of -r325700 (built by -r325700 that was from a cross-build). =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C01F5D2-BBEA-4E2A-8414-0F503BDD7917>