wildcat_paris

This will be my last answer for now since you seem to ignore answers anyway.
 
Please check your so called 'very high-quality SDCards' immediately and read through the 'SD card performance' thread I already recommended to you over there: http://forum.armbian.com/index.php/topic/1302-running-apt-get-dist-upgrade-installs-the-new-kernel-but-takes-the-orange-pi-pc-a-really-long-time/
 
Regarding led behaviour it's that easy. All the OS images over at orangepi forums use Allwinner's oudated u-boot 2011.09 (where the led will be powered on immediately) while we use mainline u-boot where the led gets activated later (the time span already increased a lot since most recent mainline u-boot version scans all USB busses for peripherals).
 
Anyway: if Armbian boots slow then your SD card is most probably the culprit. And no, after doing some very extensive testing I don't believe in any marketing claims any more. Counterfeit cards exist, most SD cards used are slow as hell when it's about random IO. Again: Read from here on: http://forum.armbian.com/index.php/topic/954-sd-card-performance/

I'm trying to organize my thoughts, such as the are, on the topic of the LCD with Armbian. Attached is my "mind map" on it. Details are extremely light. I'm uploading the PDF and the Mind Map document for editing. Oop, I'm "not permitted to upload this kind of file" 'round here.
 
I posted the Mind Map .mup file to pastebin: http://pastebin.com/ZnvXMr0K
  Hope that helps to illustrate all that I don't know on this topic.
 
What's missing? I have no idea what the syntax is of the boot_args apart from the ones in my copy of boot.cmd, which modules are required to be loaded, what DT entries need to be created to supply the parameters to the modules or kernel .... 
 
The HDMI is coming up, and I can't see how that's happening from the parameters I know about in the boot.cmd and DTB file for the running kernel.
 
I tried enabling framebuffer@2 like this:
 
                framebuffer@2 {                         compatible = "allwinner,simple-framebuffer", "simple-framebuffer";                         allwinner,pipeline = "de_fe0-de_be0-lcd0";                         clocks = <0x2 0x1 0x3 0x24 0x3 0x2c 0x3 0x2e 0x4 0x19 0x4 0x1a>;                         status = "enabled";                 }; This had no effect AFAIK.   Any pointer would be appreciated.   Thanks   Chris Armbian-LCD-MM-rev0.pdf

How did you get it to show all that info? I'm only able to see temp, when I run the same command.

Oh! I accidentally swapped SDA & SDL... Now it's ok!
i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 

TK, Bazinga! well, TKKT is like TBBT

Oh yes you did the 8/10 thingy, but this site doesn't looks like fun to read, neither understandable to me.
 
 
I have asked now google for: usb 480mbits lie 
 
Now I understand :-)
Well I understand, that it sucks with USB2.0
 
Uhhh, at the end something for you TK:
Hinweis: In einer früheren Version dieses Hotline-Tipps stand, dass Highspeed-USB eine 8-Bit-10-Bit-Kodierung verwendet, doch das stimmt nicht.
USB 3.0 Superspeed hingegen arbeitet tatsächlich mit 8b10b-Scrambling.
 
Bazinga
thank you for enlighten me

USB 2.0 means a rather inefficient encoding scheme called 8b/10b therefore you end up with sequential speeds of 40 MB/s max (didn't I already tried to explain that exactly to you? Twice?). Then sequential transfer speeds aren't everything since there's random I/O also that is for many use cases more important. Here SATA has an advantage as does UASP when compared to USB's BOT mode (see below).
 
Regarding your questions simply rely on 'TK on sunxi' and then do the math (eg. thinking about using more than one disk attached to the board's USB ports): 
http://linux-sunxi.org/Sunxi_devices_as_NAS#New_opportunities_with_mainline_kernel http://linux-sunxi.org/USB/UAS In the meantime I tested also the USB OTG port on H3 when changing the role to 'host mode' (running Armbian 5.11 with this kernel: Linux orangepiplus2e 3.4.112-sun8i #38 SMP PREEMPT Wed May 18 15:04:11 MSK 2016 armv7l GNU/Linux):
 
 
 
 
In other words: OTG port almost as fast as normal host ports so you can use 4 USB disks with this device together with GbE. If I find the time I'll write an article explaining how to combine a bunch of disks with different size to a nice mixture between mdraid and btrfs' own RAID implementation (combining striping/mirroring to max out GbE Ethernet performance and provide full disk redundancy).

hi widcat , I have installed the WiringOP typing 
git clone https://github.com/zhaolei/WiringOP.git -b h3 At the moment the gpio for C/C++ seems to work , just I want to start e new project in netbeans 8.1 and link to these .h header libraries

Strange. Since Orange Pi PC costs less (15$ + 3.50$) and is faster if you run heavy workloads (since throttling will happen later due to the better voltage regulator there). Further reading regarding NanoPI M1: http://forum.armbian.com/index.php/topic/1015-nanopi-m1/ and http://forum.armbian.com/index.php/topic/1213-ov5640-camera-with-orange-pi/  (camera stuff).
 
Regarding NanoPi M3: Better avoid at all: http://www.cnx-software.com/2016/05/20/35-nanopi-m3-octa-core-64-bit-arm-development-board-is-powered-by-samsung-s5p6818-processor/

Then provide a stable power source and don't think about temperatures (throttling will jump in if load peaks make it necessary). Apart from that it might help with longevity if temperatures are lower (disclaimer: I'm no hardware guy) and in case you have an instable power source improving heat dissipation is always counterproductive since then throttling isn't that aggressive and since voltage drops occur under high loads chances increase that CPU gets clocked higher, is driven with a higher VDD_CPUX core voltage and then the critical supplied DC-IN voltage falls below a certain treshold.
 
This is what seems to be hard to understand. The relationship between higher VDD_CPUX voltage (the SoC is fed with through a programmable voltage generator switching from eg. 1.1V to 1.3V which increases consumption) and dropping DC-IN voltage (eg. from 4.6V down to 4.3V which might already insufficient). The only relationship with temperatures is the aforementioned one: Improve heat dissipation only if you can provide a stable power source with stabilised 5V.
 
On Banana Pi (A20/AXP209) it's easy to measure since drivers are available for the PMU: http://forum.lemaker.org/forum.php?mod=viewthread&tid=8312&extra=page%3D1  and the difference between a crappy USB cable with AWG 26 or 28 rating and good short one with only AWG 20 can be seen here: http://goughlui.com/2014/10/01/usb-cable-resistance-why-your-phonetablet-might-be-charging-slow/
 
H3 has no PMU so you would need a multimeter to measure. And unfortunately the FriendlyARM folks chose the crappy Micro USB connector to power the board. In case you run into stability issues think about providing power through the GPIO header (pin 4: 5V, pin 6: GND)

Small update: The really friendly FriendlyARM people were the first to react on the Allwinner sun8i legacy kernel security alert we informed all affected vendors about. In the meantime they also tested our Armbian image and confirmed that it works.
 
Unfortunately due to our still broken H3 board auto detection NanoPi M1 will currently be treated as either Orange Pi One or PC (depending on DRAM size). Major drawbacks until we fix auto detection (hopefully with next release):
change /etc/hostname so that it reads nanopim1 fix dvfs settings manually in /boot/bin/nanopim1.bin as outlined here (I made a mistake when trying to improve dvfs settings prior to 5.10 release) then do as root a 'ln -sf /boot/bin/nanopim1.bin /boot/script.bin' -- this will lead to lower temperatures since appropriate voltage switching based on CPU clockspeed will be back again At least dvfs (settings dynamic voltage frequency scaling) will be fixed with next release and I hope also the board auto detection issues will be resolved then.

Cool cool. I've just ordered a Plus 2E (and a $12 Plus). I'd still prefer they'd make it 4 USB ports, instead of adding the OTG port. I'm not sure what WiFi adds to cost ($2?), but I wish they could make some tweaks and bump it even more; Either with even more eMMC, or down to $30 instead of $35.

Well, regarding the latter I'm not so sure whether this is the right target audience here
 
But testing WiFi and DRAM reliability would ge great. I just prepared lima-memtester for Plus 2/2E (and OPi Lite/2 also): http://kaiser-edv.de/tmp/IXGNsR/
 
Simply unpack the archive and use the contained fel-boot-lima-memtester-on-orange-pi-plus-2e script as outlined by ssvb: https://github.com/ssvb/lima-memtester/releases/tag/20151207-orange-pi-pc-fel-test
 
BTW: To enter FEL mode you have to hold the button between microphone and serial console next to the Micro USB OTG jack.

I think I order the NanoPi M3 . I found a lot of interesting properties . Actually , GPIO is compatible with all other boards (40pin banana, raspi, orange...) . But , there is something interesting to read : http://wiki.friendlyarm.com/wiki/images/8/8b/SEC_S5P6818X_Users_Manual_preliminary_Ver_0.00.pdf
SPDIF - TX and RX, LVDS, HDMI and MIPI, ADC (!) & more.... and, and, and...
 
And 45 bucks (with shipping) are 40 Yuros   That I can still afford ( for fun )  
The T3 would be better, but it costs more than twice M3
 
And ... this is completely different than the 'banana' or 'orange' (at least for me)   Great
eternal

MicroUSB power connector !?!
Why didn't you go for any other H3 SBC ?

my opi 2e arrived today.
 
so i should
* run and document dram test
* see if the untested wifi driver works
* make a dorky unboxing video
 
 
... anything else of value I can do in the name of armbian?
 
Sent from my SM-G920V using Tapatalk

Sorry, I've overseen that. No I don't and am not that much interested in a sample since everything is already known (except of WiFi but that's absolutely useless for my use cases and most probably as crappy as on the other Oranges or on all SBC that use slow SDIO implementations only capable to use the 2.4Ghz band).
 
Another linux-sunxi team member ordered one, I will prepare a fex file based on my above assumptions, he'll test and report back and then we will add OPi Plus 2E to Armbian.

Depends on the SoC and its target market in question. Who needs SATA in a smartphone, tablet or an OTT box? Most probably no one so SoCs for these segments lack SATA.
 
Allwinner added native SATA to A10/A20 more by accident than by design (which might explain the slow write performance) and it seems a faster dual core successor called A20E will be ready soon. If you need faster I/O choose the right board. Since repeating the same stuff over and over again is a bit boring, please read through http://linux-sunxi.org/Sunxi_devices_as_NAS#Differentiation_to_other_devices (just added Annapurna Labs a minute ago)

Just FYI: Orange Pi Plus 2E is now available for $35 and shipping costs remain the same (pretty low compared to some competitors): 
 
http://aliexpress.com/store/product/Orange-Pi-Plus-2-E-H3-Quad-Core-1-6GHZ-2GB-RAM-4K-Open-source-development/1553371_32665196281.html
 
Please remember that this board was designed based on community requests (dropping the slow GL830 USB-to-SATA bridge and the internal USB hub and exposing all 4 USB ports physically to the outside) and should make up for a really nice server with 2 GB DRAM, Gbit Ethernet and 4 USB ports (3 real hosts ports and one Micro OTG).
 
So now we have the following H3 boards with Gigabit Ethernet:
 
Banana Pi M2+ for $33 (1 GB RAM, 8 GB eMMC, no USB hub / no shared bandwidth, only 2 USB host ports useable) OPi Plus 2E for $35 (2 GB RAM, 16 GB eMMC, no USB hub / no shared bandwidth, 3 USB host ports useable) OPi Plus for $39 (1 GB RAM, 8 GB eMMC, GL830 slow USB-to-SATA, internal USB hub / shared bandwidth) OPi Plus 2 for $49 (2 GB RAM, 16 GB eMMC, GL830 slow USB-to-SATA, internal USB hub / shared bandwidth)   SinoVoip said to release also a cost down version of M2+ without eMMC and WiFi that might be then the cheapest GbE equipped board. But since there you only get 1 GB DRAM (which might be totally ok for most use cases -- please compare with http://www.linuxatemyram.com if in doubt) and they don't use a programmable voltage regulator and always feed the SoC with 1.3V VDD_CPUX core voltage IMO spending a few bucks more to get OPi Plus 2E with twice the RAM/eMMC size, 1 more USB port, more performance and also lesser temperature/consumption is the better idea.   BTW: WiFi capabilities not mentioned intentionally since in my opinion those cheap SDIO 2.4 GHz implementations are all not worth a look (or time/efforts to get the crappy drivers running)

Thanks for your fast reply,
 
As for the power supply its a 5V 2.5A (the official raspberry one)... The wired thing is I tried different images, (Bananian, Armbian) and the only thing I got running is the precompiled Limaker one...

I just found the problem. I was following the guide on my mac - never had any problems with that so far, all rasbpian flasshing worked fine.... But somehow the flashing of armbian does not work...
 
I did set up parallels and flashed it using linux... everything works now

Hope for what?
 
For another board with microUSB connector for power input? (Though it can be powered through GPIO pins too)
Or for another SoC with no mainline support in near future (Samsung S5P6818)?
 
I don't see that many common use cases for 8 cores with 1GB RAM, no native SATA or USB 3.0 or at least USB2.0+UAS, especially for its price.

More about NanoPi M3 - USB ports are behind USB hub...
 
Very specific board with high enough price, "Applications" tab on their site tells enough use cases where this price is OK. Unless you need FPGA  or RISC co-processor and you know how to work with this stuff, you don't need this board.
 
Using as headless server: NAS with 2 HDD drives for storing stuff (Samba, rsync, syncthing), headless music server (mpd controlled via IR remote or Android app).
 
Waiting for Ethernet and USB support in mainline kernel, meanwhile it's useful for testing intermediate Armbian releases.
 
Waiting for the bright future (at least mainline u-boot with SPL and basic support in mainline kernel).
 
Turn lights on and off with IR remote using connected IR sensor and nRF24L01+ module
Display stuff (weather forecast, date&time, new e-mail notifications and some other things) on HD44780-compatible LCD display.

Hi again,
I found great article about swap folow link below. But I must mention something important. Swap file does not contain any valuable information. So it has not sense to move it. We just delete old, create new one and change path if it is a file somewhere on filesystem or UUID if it is partition in fstab.
I do prefer to create swap partition on the end of sdcard or microsd because even value on label of card says it is 8GB every brand has different capacity. And this difference can be sometimes more than 100MB. So I decided to shrink root partition to 7.5GB and rest of capacity is swap partition. When I need to clone whole microsd I delete swap partition first, then I use simple dd command to clone it with bootloader and everything and for last I do create new swap partition.
 
Somebody can say I can do same with simple script which can resize root and left swap like originally was inside root because we do not want to use swap at all on slow these cards and it is here for emergency.
 
Answer is you have right. Swapfile on microsd card is for emergency cases only because it has low I/O bandwitch and I personally do prefer using swap partition if it is necessary on singleboard computers with sata port attached ssd's (even somebody can protest we do swaps on spindle drives because it do not lower it's lifetime).
 
https://www.linux.com/news/all-about-linux-swap-space

Hi Igor and wildcat_paris,
 
Many thanks for pointing this out to me. I read over the documentation last night, but glossed over that section because I didn't think of my unit as bricked. Sorry for the foolish question, but thank you again for the help, and for all the hard work you've put into this project!
 
Best,
Matteo