Igor

I am skipping / postponing Pine64 so it's up to community & maker - our project is open and anyone can start supporting it. arm64 was already brought in and tested with Odroid C2 so initial work was already done. I am aware that having a good Linux support is critical for those boards but can't do much about. Linux is a community project per se while Pine64 ...

Yes it was the same problem. I updatet my Kernel to 4.x without the fstab entry an it works now
 
thank you very much

@HiddenPilot
 
You need to use either DEFAULT or DEV, next (kernel 4.4.6) is not supporting H3 boards ... at this moment. Patches were moved to DEV sections since we had problems with other boards and since under 4.4.6 H3 net support is not working in any case.

I will try to migrate (maybe tomorrow) the PCI driver from 4.4.x to 3.14.60 (fslc). I've confirmed that PCI is working on that kernel.
 
PCI seems to be broken since a lot of version in fslc, according to threads from the web.

@Igor: I need an opinion on the proposed changes to configuration.sh
 
In the meantime I adjusted armhwinfo and firstrun to show identical behaviour with vanilla and legacy kernel (mostly led stuff) and could send a PR for this. But we should wait for the other guys doing mainlining work for H3 (SPI and so on)...

Sorry, my mistake. Merged.

Good news for Me...
The DHCP and SSL server work too ...
Thank You Igor !

Sorry, we both wasted our time with the same task. In the meantime I also found it after reading documentation about Debian kernel packaging. I used your patch and here we are:
 
Orange Pi PC (H3) FEL/NFS booting:
[ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. Starting LSB: set CPUFreq kernel parameters... [ OK ] Started LSB: set CPUFreq kernel parameters. Starting LSB: Set sysfs variables from /etc/sysfs.conf... [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. [ OK ] Started LSB: Armbian gathering informations about hardware. Starting LSB: PLEASE BE PATIENT AND DO NOT INTERRUPT...FIRST REBOOT... Debian GNU/Linux 8 orangepih3 ttyS0 orangepih3 login: (native Ethernet). Now I have to think about which patches to submit since I don't want to break everything as I did 2 weeks before

Hello all
And firstly I would like to congratulate you and thank you for a cracking little distro.
 
I recently purchased an OrangePi-One amid all the hype of the Pi-Zero to give the Opi a try out. after having tried the images available on the manufacturers site and learning there shortcomings I resolved to build my own image. I was pointed to your site by a member over at http://forum.doozan.com and I must say I am blown away by what you have achieved and distribute!!!
 
You have saved me the pain of building my own OS by applying all the relevant patches. I will be testing your images out for my own needs and should I be able to make any contribution over and above "testing" I will do so.
 
 
KUDOS to the Devs and Contributors!
 
 

I tried with lowering the DRAM speed in u-boot and lowered it to 384 MHz.
 
Compiled for Armbian_5.07_Lime2_Debian_jessie_4.4.6, with u-boot (v2015.10) and modified A20_OlinuXino-Lime2_defconfig
 
No freezing issues any more 
 
Thank you very much, Igor.

It might be time for some release line. Let's put together what was done in past few month, need to be done, was forgotten and it's worth mentioning. I sure missed stuff out ... so just add it.
 
IMAGES / KERNEL:
- all 3.10+ kernels are Docker ready
- added Odroid C2 CLI and desktop, kernel upgraded to 3.14.65
- Udoo Neo wireless works
- legacy kernel for Allwinner boards was upgraded to 3.4.111
- legacy kernel for iMx6 boards was upgraded to 3.14.65
- vanilla images comes with kernel 4.4.6
- Clearfog comes with 3.10.101 and 4.4.6
- added Armbianmonitor which knows ....
- fixes for SPDIF / I2S audio driver in legacy kernel
- added USB camera section
- added fix for slow SD cards
- changed first boot procedure and force user creation
- all A10/A20/H3 comes with HW acccelerated video playback in desktop build
- Bluetooth on Cubietruck works well, both kernels
- verbose / no verbose boot works almost on all boards
- added wifi radar to desktop
- desktop jessie only
- enabled I2S on sun8i
 
BUILD SCRIPT:
- Added Belink X2 as WIP target (H3 based media player)
- Added Odroid C1 as WIP target
- introducted CLI_TARGET per board
- prepared FEL boot
- prepared Xenial target
- GCC 5 support for vanilla and allwinner legacy
 
BUGS:
- Udoo Neo reboots takes a while, 1min+
- C1 does not boot
https://github.com/igorpecovnik/lib/issues
 
NEED TO BE FIXED IN THIS RELEASE:
- vanilla build for H3 with working EMAC / GMAC
- nand installer for H3 eMMC
 
DUE DATE: 30.4.2016
 
------------
Copy paste / add and remove this text. Just add to the topic

Common Edimax dongle EW-7811UN is now fully working by following Igor's procedure for Armbian-5.05.. Thanks !  After configuring wlan0 and testing the connection I disabled old / enabled new WIFI driver
/etc/modules-load.d/modules.conf #----------disable standard Armbian driver # 8189es #----------enable fixed WIFI driver for EDIMAX EW-7811UN 8192cu The board now reliably starts up and connects to configured wireless network. Performance is adequate in a noisy busy environment, iperf reaches 87 mbps.
 
Problem SOLVED !

BTW: I fixed packaging script so this "make scripts" is done on headers install and will not be needed any more ... adding later today.

Use armbianmonitor for the following tasks: armbianmonitor -b switches between verbose and normal boot armbianmonitor -c /path/to/test performs disk health/performance tests armbianmonitor -d tries to upload debug disk info to improve armbianmonitor armbianmonitor -m provides simple CLI monitoring armbianmonitor -r tries to install RPi-Monitor armbianmonitor -u tries to upload armhwinfo.log for support purposes This is currently possible.

That means that boot loader is patched / prepared and we did a manual boot. For installer we need to create / adjust scripts and make few tests. This is scheduled for next release - in 2-3 weeks. This info is valuable for users who knows how to do it manually.
 
http://forum.armbian.com/index.php/topic/881-prepare-v51-v201604/

4.5, hopefully. We wait for Ethernet support to become stable.

BTW: I fixed packaging script so this "make scripts" is done on headers install and will not be needed any more ... adding later today.

Use armbianmonitor for the following tasks: armbianmonitor -b switches between verbose and normal boot armbianmonitor -c /path/to/test performs disk health/performance tests armbianmonitor -d tries to upload debug disk info to improve armbianmonitor armbianmonitor -m provides simple CLI monitoring armbianmonitor -r tries to install RPi-Monitor armbianmonitor -u tries to upload armhwinfo.log for support purposes This is currently possible.

That was fast Igor.
 
Thank you very much..

BTW: I fixed packaging script so this "make scripts" is done on headers install and will not be needed any more ... adding later today.

That means that boot loader is patched / prepared and we did a manual boot. For installer we need to create / adjust scripts and make few tests. This is scheduled for next release - in 2-3 weeks. This info is valuable for users who knows how to do it manually.
 
http://forum.armbian.com/index.php/topic/881-prepare-v51-v201604/

Don't have any smart idea ... perhaps try lowering DRAM speed in u-boot.
 
BTW: Armbian forum is running Armbian Wheezy on Lime2, legacy 3.4.106 ... it never hanged. All downtime was made by human error

If you are reading this you've probably discovered that there are a few things about 
the Orange Pi series of boards that can be frustrating.  I know I have been..
 
I purchased an Orange Pi PC and two Orange Pi Ones anticipating Pi bliss at a 
fraction of the cost of the Raspberry equivalent.  I tried, and tried hard, to 
load distro after distro of various linux flavors onto micro SD cards with many 
a blank screen or an aborted boot attempt.. Orange Pi site distros, 
laboris distros, Armbian distros.. nothing seemed to make a difference.
 
Reading about power supply issues, ornery boot processes, and overscan issues 
I was really beginning to think this was money poorly spent, after all the boards 
weren't much use as intert bricks.. too small and light to make for a decent paper 
weight or door stop.. no practical use at all.. perhaps I could crush them with 
a lump hammer to derive some satisfaction for fruitless hours spent trying to get 
these things to work..
 
Then it dawned on me.. perhaps there was something to the advice I was seeing 
on the forum.. Out of curiosity I tried a decent USB-lithium battery pack instead 
of the little 5v wall wart I was using to power my Orange Pi PC and low and behold 
the thing booted reliably. Go figure.. all this time I was blaming the board when 
it was really the #$!#!@ underpowered wall-wart causing the issue.. try the OPI-One..
same deal, it booted.. try the next One.. same deal, it booted happily.
 
I then measured the current draw during the boot process and found that the Quad 
core board was actually a hungry little bugger.. peaking out at almost 600ma 
at one point in the boot process with no accessories attached.. before settling 
down to around 240ma at an idle. Lesson learned: Don't cheap out on your 
power supply for these boards... and you've made it over the first hurdle.
 
Next hurdle..  the damn video is overscanning my LG HDMI monitor.. no adjustment 
on the monitor to scale the desktop image to fit the screen size, and no easy boot 
config file like RPi to turn underscanning on in the linux OS. This means I can't 
see the menus at the top of the screen.. I didn't have this issue with the RPi.. 
but hey the RPi cost more, has a user base of 6 million users and a dedicated, paid 
software development team with 4 years under its belt.
 
Put it in perspective.. OPI is a smaller community and it takes time to develop 
code and work out the kinks in a product.. so a bit of patience is in order.
Thank you to the Armbian developers and testers, your efforts are appreciated.
 
 
 
So what to do about the overscan issue.. well I happened to have an HDMI to VGA 
adapter with a 3.5mm audio jack output on the side.. so I added it into the mix, 
and lo and behold the overscan issue was dimished a great deal..not perfect, 
but much more usable desktop real estate. 
 
Then I tried the MPV media player with Armbian distro to play canned mp4 videos 
and was favorably impressed with the play quality with the built in Mali hardware 
graphics acceleration.. easily as good as the RPi and Omxplayer.. perhaps even 
with better controls in the MPV media player app.. score one for OPI.. 
things were looking up.. this was along way from the inert brick I owned earlier in the day.
 
So what about the overscan issue.. yes it is annoying, but perhaps over time there will
be a software fix developed to make it go away.. patience.
 
What else to do in the mean time?  
 
Well it is likely that the OPI in you life is not the only computer you have at 
your disposal..  so why not VNC into your OPI..?  You can set the X-window defaults 
to a reasonable screen size.. and have your OPI desktop arrive in a window on 
your other computer..  
 
Googling RPi VNC I found xtightvncviewer and xtightvncserver install instructions.. 
I installed, and went with a desktop size of 1280x600 for a comfortable fitting window 
on my RPI desktop..  and soon had a serviceable non-overscanned OPI remote desktop 
from my RPI..  hooray!
 
No hardware accelerated video through the VNC session.. but a decent desktop experience 
for most other pursuits.
 
Lesson learned.. OPI software is in it's infancy, and with time and effort spent, 
and some temporary workarounds.. it will find many uses.
 
If you want closer to perfection out of the box than what OPI has to offer? Pay more and benefit from a 
more developed product.. however, if you want to work the line a bit -  between cost and functionality -
perhaps you have more time than money available at the moment - don't dispair at your purchase.. 
persist a while before you opt for the lump hammer option.. and you may get what you need out of 
the RPi's clone-family with a bit of effort spent..  Good Luck.
 
 

Just a small post about how to connect the PL2303HX RS-232 adaptor cable and the Real Time Clock. Do not trust the Banana pi photos as the I2C bus in the Lamobo/Banana PI R1 is inverted.
 
As they say a picture is better than a thousand words. Often the online Banana PI/Lamobo PI diagrams can be confusing, and do not even try to guide yourself by Banana PI pinouts / photos of placement of hardware products/extensions. I will reiterate again, as this can be a source of confusion, the Banana PI is a rebranded Lamobo product, and the GPIO bus is different/rotated 180º.
 

 
To scan the GPIO:
 
$sudo i2cdetect -l
i2c-0 i2c       mv64xxx_i2c adapter             I2C adapter
i2c-1 i2c       mv64xxx_i2c adapter             I2C adapter
$sudo i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
$sudo i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --
 
The 68 is the RTC.
 
For the  PL2303HX I also have in /etc/inittab:
 
T0:2345:respawn:/sbin/getty -L ttyS0 115200 vt100
 
and add to the kernel bootargs in /boot/boot.scr :
 
setenv bootargs "console=tty1 console=ttyS0,115200n8 
 
and to finish:
 
$sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

Possible.
 
I don't have the board but can assist in bringing things together if there is an interest.