Re: New armhf node (Pine64+)
On Thu, Feb 16, 2017 at 12:25:15PM -0800, Vagrant Cascadian wrote: > Just purged the un-unsed kernel packages which didn't have support for > these boards. ah! > I guess you must have installed something that triggered > an "update-initramfs" call on the older kernel versions... I wonder what this was… > Removed your workaround, and re-ran update-initramfs. Should be working > now. thanks. (I had to add two workarounds…) > >> This one is interesting in that it's running an arm64 kernel with armhf > >> userland (like the i386 builders that run amd64 kernels). > > nice! is this the same for p64c too? > Yup. very nice! > Thanks for getting themn into production! my pleasure! :) -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: New armhf node (Pine64+)
On 2017-02-16, Holger Levsen wrote:
> On Mon, Feb 06, 2017 at 01:39:47PM -0800, Vagrant Cascadian wrote:
> linux-image-4.10.0-rc6-arm64-unsigned (4.10~rc6-1~exp1) wird eingerichtet ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-4.10.0-rc6-arm64
> DTB: sun50i-a64-pine64-plus.dtb
> Couldn't find
...
> Can you fix this up ("somehow" on the host…), please?!
Just purged the un-unsed kernel packages which didn't have support for
these boards. I guess you must have installed something that triggered
an "update-initramfs" call on the older kernel versions...
Removed your workaround, and re-ran update-initramfs. Should be working
now.
>> This one is interesting in that it's running an arm64 kernel with armhf
>> userland (like the i386 builders that run amd64 kernels).
>
> nice! is this the same for p64c too?
Yup.
Thanks for getting themn into production!
live well,
vagrant
signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: New armhf node (Pine64+)
On Thu, Feb 16, 2017 at 01:31:55PM +, Holger Levsen wrote:
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> Can you fix this up ("somehow" on the host…), please?!
"fixed" this for now by adding "exit 0" at the beginning of
/etc/initramfs/post-update.d//flash-kernel …
--
cheers,
Holger
signature.asc
Description: Digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: New armhf node (Pine64+)
Hi Vagrant,
sorry for the delay in getting these boards used…!
On Mon, Feb 06, 2017 at 01:39:47PM -0800, Vagrant Cascadian wrote:
> Another arm board ready to be configured for the build farm!
this is now basically setup, however this is quite annoying (as we
expect "apt install" to exit 0…)
on p64b-armhf-rb.debian.net:
linux-image-4.10.0-rc6-arm64-unsigned (4.10~rc6-1~exp1) wird eingerichtet ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.10.0-rc6-arm64
DTB: sun50i-a64-pine64-plus.dtb
Couldn't find
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: Fehler beim Bearbeiten des Paketes linux-image-4.10.0-rc6-arm64-unsigned
(--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
linux-image-4.10.0-rc6-arm64-unsigned
E: Sub-process /usr/bin/dpkg returned an error code (1)
Can you fix this up ("somehow" on the host…), please?!
> Running a non-Debian kernel, but built from the linux-next tree, so
> should be possible to switch to experimental and/or stretch-backports
> when the time comes.
cool!
> This one is interesting in that it's running an arm64 kernel with armhf
> userland (like the i386 builders that run amd64 kernels).
nice! is this the same for p64c too?
> We may not
> have enough of these to do this systematically yet unless we divert some
> of the other arm64 builders, though I'll likely get a few more in this
> configuration set up "soon" regardless.
cool!
> Space is getting a little tight, so if this one
> performs well, I'll probably want to decomission one of the slower
> boards. I've got another Pine64+ that should be ready soon, and *maybe*
> an odroid-c2 as well, and likely some additional board donations
> coming... maybe I should get a bigger UPS and another network switch to
> support another 8 boards...
sounds like it!
> I think it is only configured with ssh keys for holger, but if someone
> else is able to configure it and has the time I can add them as well.
mattia's keys should be there as well now…
--
cheers,
Holger
signature.asc
Description: Digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
