Igor

https://github.com/armbian/build/blob/master/lib/general.sh#L541-L554 by adding a parameter NO_HOST_RELEASE_CHECK="yes"

... or you add an "override" parameter EXPERT="yes" and you unlock all options.

Check FAQ at the download section.

yes

It should work this way: https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-truncate-logs # write to SD /usr/lib/armbian/armbian-ramlog write >/dev/null 2>&1 # rotate logs on "disk" chown root.root -R /var/log.hdd /usr/sbin/logrotate --force /etc/logrotate.conf # truncate /usr/bin/find /var/log -name '*.log' -or -name '*.xz' -or -name 'lastlog' -or -name 'messages' -or -name 'debug' -or -name 'syslog' | xargs truncate --size 0 /usr/bin/find /var/log -name 'btmp' -or -name 'wtmp' -or -name 'faillog' | xargs truncate --size 0 # remove /usr/bin/find /var/log -name '*.[0-9]' -or -name '*.gz' | xargs rm >/dev/null 2>&1 triggered by cron job: */15 * * * * root /usr/lib/armbian/armbian-truncate-logs Where is the problem?

It's related to wireless drivers, probably showing firmware loading progress. In any case safe to ignore.

ATF for building H6 boards is broken and building stops. Somebody needs to fix.

Yes, let's do that and compare a bit to understand changes you made. I can do some observation earlier next week to figure out what adjustments do we need to make. @TonyMac32 This can be done in a second phase. The same as we did with, perhaps some older kernel might as well be abandoned ... but I don't have this know-how.

Not yet. This is all I know now. Its kind of strange ... need to check on pure mainline upstream source if that change anything else digging in. Now real life problems Wrote on mobile

@gamelaster If you will try with our patchset, disable those and Pinebook should boot: general-add-overlay-compilation-support.patch general-enable-kernel-dtbs-symbol-generation.patch general-sunxi-overlays.patch

Great progress!!! We need to keep one kernel for many hw and that's why patches are a must. Current situation is still messy and I only find out that some of my additional patches are causing Pinebook to hang at boot. I also plan to merge a dozent of patches, some sent upstream to make it easier to maintain. I was working whole day yesterday and the day before and the day before ... I can add new updated test image, but it is much better for me to do nothing for a few days. When things are merged in, images can be produced automatically. No need to rush anywhere. Production ready images shell go out when DEV branch is tested very well and is moved to NEXT. We still miss suspend / resume, right? This is a must function for notebooks. I haven't saw if there is a solution developed for that?

1st build: https://dl.armbian.com/pinebook-a64/Debian_stretch_dev_desktop.7z (still cleaning patches)

Currently it's broken (DEV) on both. No need to test ATM. Will be probably resolved later today ... when kids go to sleep

Perhaps those warnings can be cleared out even they are harmless ... @guidol tnx. I am getting close to Pinebook(s) problems.

Talk to OMV people to develop OMV cleaner. We will certainly not. This has nothing to do with Armbian/Debian. Use some sort of virtualization for the future to avoid such troubles.

In case you were installing INSTALL_HEADERS="yes" you could run out of space. Affected Ubuntu builds and was fixed. But this systemd problem remains.

Which functionality are you missing?

Yes. Sorry good enough. Will mark this as tested. Danke

Me neither but its pretty irrelevant. I noticed that building of Ubuntu(s) is/are failing with lots of errors and systemd has this issue. It is highly possible that this is related. I can give you detail report in a few weeks, but then it will be irrelevant again.

Still needed testings: Orange Pi R1 Sopine A64 Pine64 Olimex Lime 2 eMMC https://github.com/armbian/testings

Probably path in the kernel source is pointing elsewhere, to /etc/lib/firmware perhaps? In any case its safe to ignore.

Start here: https://docs.armbian.com/

Upstream problems. Not possible to build Ubuntu ATM.

I noticed that both Ubuntu's are breaking building. Perhaps that is related.

Well, we have to wait that problems are solved upstream.