Igor

This method might not work at present images for download but it has been fixed. If you start with your own image, it should work. BTW. There is a serial console via USB port. Just connect to your USB3(to make sure you get enough power) port and power the board.

With modern kernel.

IMO the best way would be to study overlayroot scripts for Ubuntu and make them work on Debian.

https://invisioncommunity.com/forums/topic/439176-haze-42x-by-ips-themes/?do=findComment&comment=2751318

They are tested. Except the one labeled with nightly. Those are auto made from the trunk and sometimes are broken ... which is normal. Can you provide: - which image did you try - serial console log SPI. Check if all those USB ports that are enabled by default makes any troubles with SPI.

Headers are not source. We pack kernel source but don't upload it to the repository due to space limits. So far I don't see any problem on Armbian side except DKMS might be broken ... but that is not essential to compile a module.

It should be fine now, I made a test build with 4.17.y and it builds O.K. If not, remove the cached image.

I haven't changed yet ... since I am in and out of the (mobile) office. I will try now and change to Bionic on the way ...

It's also possible that some boards are much lower quality than expected with our already conservative settings. It's not just kernel, but also u-boot. Both are changed now.

Try without DKMS. Wrote on mobile

Thanks. https://github.com/armbian/build/blob/master/Dockerfile Probably adding cpio to the package base should do ... Try.

A10, A20, H3, H5, A64, H6, A83T, ... based boards share the same kernel. We build one 32 (linux-image-sunxi-next) and one 64bit (linux-image-sunxi64-next)binary from it. We need to be very sure that upgrade won't break any of the supported board main features and to achieve that, we need to do a lot of, mostly manual, testings. This operation is huge, complex and expensive. From our tiny team perspective. A20 boards are very well supported in a current kernel and don't get much if any advantages with a kernel upgrade. All others.

Development (things are changing all the time) automated builds could be/are partially or fully broken for many reasons. If something doesn't work, you are on your own to fix. A similar notice was written in red text when you first log in to this system. What to do to save time and get things done? Get build tools and make your own NEXT (4.17.y) Stretch build and enable headers in a build config prior to starting. Also stay away from Bionic if you don't want to deal with irrelevant userspace bugs during your mission. Canonical still needs months to make this build stable.

Try now.

Well, video acceleration works out of the box on the legacy A10-A20-H3-A64 builds ... unless you use some weird codecs. Just not with Chromium. Making that possible is too complex/resourceful for the nature of our project.

On my test Ubuntu Xenial, I am getting strange compiler errors (arm-linux-gnueabihf-gcc: internal compiler error: Killed (program cc1) ) when compiling modern kernels (which can be also related to some KVM bugs, hard to say) ... while Ubuntu Bionic host doesn't produce those errors. Since I am unable to look more into this and since recommended host Bionic works, I can only point you to start with Bionic ...

I am looking into this ... but since I am not in the office, this takes much more time with lots of interruptions.

Yes. sunxi-4.18 Allwinner (NEXT & DEV) part will replace the one in the master branch. ASAP. I already cleaned and ported all patches from 4.14.y. The only major known regression is no HDMI at A64 boards.

5.52 is a development branch which is changed only for Allwinner and Odroid XU4, which are under some heavy changes. I also tried to build on a master branch (5.51) and it also builds. I also notice that you are using Ubuntu Xenial builds host. That should not affect this ... Try removing the cache directory, mainly sources, and try again. Also, a clean build script would be a way to go.

None without providing build logs. I was able to build a kernel without any problem: dpkg-deb: building package 'linux-dtb-next-cubox' in '../linux-dtb-next-cubox_5.52_armhf.deb'. dpkg-deb: building package 'linux-headers-next-cubox' in '../linux-headers-next-cubox_5.52_armhf.deb'. dpkg-deb: building package 'linux-image-next-cubox' in '../linux-image-next-cubox_5.52_armhf.deb'. dpkg-genchanges: warning: unknown substitution variable ${kernel:debarch} dpkg-genchanges: warning: package linux-libc-dev-next-cubox in control file but not in files list dpkg-genchanges: info: binary-only upload (no source code included) dpkg-deb: building package 'linux-source-4.14.55-next-cubox' in '/home/igorp/master/.tmp/linux-source-next-cubox_5.52_all.deb'. [ o.k. ] Kernel build done [ @host ] [ o.k. ] Target directory [ /home/igorp/master/output/debs/ ] [ o.k. ] File name [ linux-image-next-cubox_5.52_armhf.deb ] [ o.k. ] Runtime [ 12 min ] You can find them under debug subdirectory.

Absolutely. Only let's start with this feature and testing at sunxi-4.18 branch. Already at this point.

Updated images. https://www.armbian.com/nanopi-fire3 Thanks!

Nothing suspicious to me. Try with limit CPU down to 960000, double check voltage at the board, Another option is to lower DRAM speed, but you will need to rebuild u-boot with lower settings. It's worth trying.

Most board makers will certainly drop support even before, mainstream distribution as well (if they support it at all) but community projects such as ours will continue to maintain support. C1 is an outsider in this sense, but if you look on some old Allwinner or Freescale models, they are still supported. Cubieboard 1, older board than C1, is running Bionic with 4.14.y https://www.youtube.com/watch?v=6-_CF_7Vbe0 Cubieboard 1 is officially end of support in our project, but you can still build images for it and it still receives kernel upgrades. The only difference is, that we don't test, fix board issues (those boards are usually very stable) or provide help. Unless you don't go for exotics and there will be enough support for projects like Armbian, you have nothing to worry about.

One problem at the time. Does it crash?