Igor

I am not sure if this is what you want to know, but:

- Debian.org or Ubuntu.com officially does not support any of those boards/boxes,
- Armbian userspace has many small but vital performance or security adjustments,
- Armbian fancy some kernel development and a lot of its maintaining. Debian relies on upstream sources for ARM hardware which can be years behind and/or lack of many functions,
- Armbian userspace is lean, clean but 100% Debian (or Ubuntu) compatible
- many stock Debian bugs are fixed on the way, "better than original :)"
- a build system is a central part of this whole ecosystem. You can DIY. Debian much harder.
- dedicated support forums per boards/boxes
- plug and play vs. complicated install scenarios on Stock Debian
- unified development scenarios and user experience vs. mess of different setup instructions scattered all around
 
I must have forgotten many other important points

umm cool, I will give it a try. Thanks for the help. Cheers. 

@martinayotte @hjc Successfully merged. https://github.com/armbian/build/commit/6d82a8974872ee261006d2cdf6726b7d13df5032

Hi Igor. 
Yes. That builds now. At least for K1. I will try on other boards tonight. I compiled, burned to uSD and booted on board. Basic stuff seems to work so far.
Thanks
 

@martinayotte @hjc Successfully merged. https://github.com/armbian/build/commit/6d82a8974872ee261006d2cdf6726b7d13df5032

ok I did install the image and it works with the usb devices I currently need (USB FTDI Serial, USB 4G Modem)
 
Andy

Thanks Igor. I've done the USB solution to activate Wifi and now i can use Putty to play with it.
 
Form factor is perfect for what I have to do but the Orange Pi Zero with H2+ has an horrible Wifi behavior, so I try with the H5 version.
 
Thanks again Igor.

It works! Great
 
FYI: http://ix.io/1jJ5

Fixed now. All is working.

Working on it

Done.

We can simply ask on user creation: "Do you want to have access to GPIO?" ... with some brief description what that means.

Hi @Igor,
 
I study and understand it.
 
At this time, I not have any serial console adapter for collect the logs, sorry.
 
Thanks, see you.

Normal. Board can't really power off properly due to ... cheap design. The only way is to make it into sleep mode with use of the AR100 coprocessor inside H2/H3 chip which support is in this state: http://linux-sunxi.org/AR100

@WarHawk_AVG He probably means this:
http://linux-sunxi.org/USB_Gadget/Ethernet

[WIP]
 
Schematics
 
Pros:
- board vendor actively participates (listens to the community, provides information including schematic and cares about correctness, tries to bridge developer community and chip vendor)
- board vendor take care of their board configuration and submit patches
- board vendor provides dev samples
- yet another A64
- good powering method
 
Cons:
- none specific to this board
 

Change back to the main server. apt.armbian.com

There will be more and more vendors using ARMBIAN as a reference because good support is one of the most important selling points. They will use "Armbian (will) support(s) ..." in their sales speeches even it's a complete fiction. Sales are not engineering
 
We can't do anything if they use that. A threshold for legal actions for abusing trademark is pretty high, it is a lot of work and it is not worth the troubles.

It's sad that they (and others) will just use this solo for their gain without asking and giving something in return.

Thank you @Igor @guidol for your help.
I will try it next week and give you my feedback.

Unfortunately, it is a necessity due to source diversity. Packaging script from kernel 3.4.y is very different from the one from 4.17.y. Then there are small changes in between. If someone would dig into and clean up this mess, we could end up probably with 4 different patches + a patch that differentiate our DEV and NEXT kernel branch naming. Since all this mess works, upstream changes in this sections are extremely rare ... we don't touch it.

Implemented.

I use this procedure to reproduce the issue:
systemctl stop ntp dats -s "2017-07-25T12:34:27+00:00" cd /usr/src/linux-headers-4.14.52-sunxi/ make scripts This result into make doing an infinite loop while complaining about files that has modification time in the future.
Then I tried to use this command to fix the issue:
find scripts/ -type f -exec touch {} \; This reduce the number of complains but still cause an infinite loop. I also tried to touch only make related files, without more success.  Actually the generic way to solve the issue is this command:
find -type f -exec touch {} \; This fix the infinite loop, even if a few complains remains about some files outside of the actual directory. But this is very slow, especially on my low power Orange Pi Zero that is purposely running at the fixed very low 240 MHz processor frequency (USB powered with a lot of sensors).
But I have found that the following command both solve the issue and is very fast:
find -type f -exec touch {} + The execution time go from 311 seconds to only 4.5 seconds,  about 70 time faster !
So I suggest to add this command into the linux-headers package postinst script, just before calling the 'make -s scripts'.

Based your suggestion and after I am in desperation ...
I turn off the machine, remove the cooler and CPU from socket, let them couple hours on my table.
I reassemble the machine... Turn on...  Tadaa... The machine live and heartbeat again... Serial port connect again.
Thank guys 

I am not sure if this is what you want to know, but:

- Debian.org or Ubuntu.com officially does not support any of those boards/boxes,
- Armbian userspace has many small but vital performance or security adjustments,
- Armbian fancy some kernel development and a lot of its maintaining. Debian relies on upstream sources for ARM hardware which can be years behind and/or lack of many functions,
- Armbian userspace is lean, clean but 100% Debian (or Ubuntu) compatible
- many stock Debian bugs are fixed on the way, "better than original :)"
- a build system is a central part of this whole ecosystem. You can DIY. Debian much harder.
- dedicated support forums per boards/boxes
- plug and play vs. complicated install scenarios on Stock Debian
- unified development scenarios and user experience vs. mess of different setup instructions scattered all around
 
I must have forgotten many other important points

I am not sure if this is what you want to know, but:

- Debian.org or Ubuntu.com officially does not support any of those boards/boxes,
- Armbian userspace has many small but vital performance or security adjustments,
- Armbian fancy some kernel development and a lot of its maintaining. Debian relies on upstream sources for ARM hardware which can be years behind and/or lack of many functions,
- Armbian userspace is lean, clean but 100% Debian (or Ubuntu) compatible
- many stock Debian bugs are fixed on the way, "better than original :)"
- a build system is a central part of this whole ecosystem. You can DIY. Debian much harder.
- dedicated support forums per boards/boxes
- plug and play vs. complicated install scenarios on Stock Debian
- unified development scenarios and user experience vs. mess of different setup instructions scattered all around
 
I must have forgotten many other important points