JoeyBeelinkX2

If Wireless is handled by a router that should be very simple: a web server as Apache or nginx, desired software and a compatible connected camera (ip or usb).

Enviado desde mi Jolla mediante Tapatalk

It is also possible to use VNC Client on the PC and server on orange pipc+ to get the Screen of kodi to the PC. http://www.tightvnc.com/download/2.8.3/tvnjviewer-2.8.3-bin-gnugpl.zip
extract the file tightvnc-viewer.jar and put it on the desktop or elsewhere to klick on it for starting.
TightVNC is just a single java executable, needs java to be installed on the PC.
 
On orange pi:
 
sudo apt-get -y install x11vnc vnc4server xinetd vnc-java xfonts-base
sudo x11vnc -storepasswd yourpassword /etc/x11vnc.pass
This two lines are for starting.  You can but this also to etc/rc.local so VNC starts every time the Linux is rebooted.  
vncserver # first time use a password has to be setup as well, just follow the Questions presented after invoking
x11vnc -display :0 & 
 
My be this works fort you too.

After talking about "the crazy idea" of use of this boards like light desktops in other thread with @JoeyBeelinkX2 :
I start reading about ways to improve the performance.
In this way I find an alternative scheduler specially conceived by responsiveness of desktop use, is called MuQSS http://ck-hack.blogspot.com.es/2016/10/muqss-multiple-queue-skiplist-scheduler.html
I also find a kernel ready to use on x86 architectures (includes de MuQSS scheduler instead of CFS and BFQ instead of CFQ, while also adding more tweaks for responsiveness like proper QoS over TCP to avoid TCP congestion): https://liquorix.net/#install
And my final questions:
Can this kernel improve the Desktop performance or responsiveness? Can be included on the Desktop images?  

All this stuff run under old kernels and proprietary drivers and blobs. I'm agree with you about the slow response running Chrome (Chromiun) under armbian and the performance you can obtain using the same or equivalent Chrome under Android.
But is a matter of freedom, real freedom, vs a limited but good user experience.
 
This video is recorded using kazam https://launchpad.net/kazam on an Orange Pi One (only 512MB RAM) at the same time I use the system to show his capacities. Is not an intel Skull Canyon NUC http://amzn.to/2qR3YjY but can be useful in some scenarios.
 
 

are part of Armbian's base install. It's as simple as https://forum.armbian.com/index.php?/topic/4221-toggle-cpu-frequency-with-shortcuts/&do=findComment&comment=31321 if people want to adjust defaults for whatever reason.  
 

I use a BeelinkX2 as a light/cheap desktop replacement, mainly because is the best way to manage my others headless ARM boards by SSH sessions. Sometimes I perform flac to mp3 conversions in this machine without worrying about heat, as long time ago say @tkaiser : H3 is not an animal or a human being that gets hurt by temperatures exceeding 40°C. It's a chip rated for up to 125°C  → 
Related to CPU throtling in the past I use some CPU desktop pluging monitor on Ubuntu but I d'ont know if working in this case: https://apps.ubuntu.com/cat/applications/quantal/indicator-cpufreq/
Also in the past I use on ODROID boards cpufrequtils like showed in this post: http://odroid.us/mediawiki/index.php?title=Use_cpufrequtils_to_Adjust_Processor_Settings

Why don't you simply adjust the config file and let throttling do the work later?
ENABLE=true MIN_SPEED=480000 MAX_SPEED=912000 GOVERNOR=interactive Monitoring can be done with 'armbianmonitor -m' or 'armbianmonitor -r' and to adjust settings every now and then (for reasons I fail to understand) there's the cpufreq-set command.

Don't know if it's relevant, but I always use Webmin to configure samba on my boards running armbian (debian). For those who don't know Webmin: Webmin provides a web-based management console for linux computers
 
In combination with the authentic theme (needs separate installation) Webmin provides a reasonable modern user interface for all kinds of linux management tasks. It also includes a module for samba.
 
Give it a try; I think it makes life easier especially when you do not have a desktop running. Installing is easy and straight forward; start at 'Using the Webmin APT repository' on this page: Webmin
 
After installing start your browser and go to https://yourarmbiancomputer:10000 and Webmin should give you response.
 
I guess it will also work for ubuntu, but have not tried it yet. There is lots of other information and add-ons on the webmin website so give it a try.
 
-End of the commercial break-

Warning: This whole thread is only about historical information now since it's 2018 and we can buy inexpensive and great performing A1 rated SD cards in the meantime. Buying anything else is a mistake so directly jump to the end of the thread for performance numbers and recommendations.
 
 
 
Edit: See an early 2017 update at the end of the thread regarding new SD specs also covering random IO performance.
 
Edit 2: Some thoughts/observations on lifespan/reliability of SBC storage: http://tech.scargill.net/a-question-of-lifespan/ (see also/especially the comments there)
 
Edit 3: CNX Software picked up recent performance reports (eg. by Andreas Spiess) and other important issues around SD cards: http://www.cnx-software.com/2017/06/13/micro-sd-cards-for-development-boards-classes-tools-benchmarks-reliability-and-tips-tricks/
 
Edit 4: See an early 2018 update testing real world A1 performance class products at the end of the thread.
 
Edit 5: See here and there for some rather boring but very important information about Armbian's tries to prevent SD cards wearing out too fast.
 
 

 
Preparations:
 
I tested 8 different SD/TF cards under identical conditions. I created an Armbian 5.07 image to be used on Banana Pi (A20 SoC with 4.4.6 kernel, ext4 rootfs (Armbian defaults == no journal), 960MHz scaling_max_cpufreq, scaling_governor == performance. All test runs were done using 'iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2' and monitored using 'sudo iostat 5' for anomalies (none detected).
  Kernel version matters (since with Allwinner's 3.4 kernel sequential throughput is limited to ~16MB/s, with mainline kernel we get close to Banana Pi SDIO implementation's max: ~23MB/s) and filesystem settings matter too (enabled journal for example slows down 4K writes a lot).   Sequential speeds:     Random I/O:     The 4 Samsung cards were bought within the last 3 weeks and manufactured between 09/2015 and 12/2015 according to the card's metadata. Interesting observation: I used three of these cards the first time and they all show identical behaviour especially regarding writes with small record sizes: pretty slow in the beginning and getting faster over time (the Samsung Pro for example started with only 1400KB/s 4K writes and 3 runs later the same test showed 3270KB/s -- maybe an indication that some sort of calibration happened. Anyway: I know why I always repeat tests and do not rely on a single test run)   Sequential speed mostly irrelevant / random I/O differs and matters a lot!   The SanDisk Extreme Pro has been bought nearly 3 years ago. This card shows superior sequential read/write performance compared to the three Samsung EVOs. But only when used in combination with a host that can make use of these speeds. My MacBook writes 4 times faster an OS image to the Extreme Pro compared to the EVOs. But this doesn't matter at all since the SDIO implementation of the board in question is limited to ~23MB/s (50MHz @ 4 bit). The same sequential write/read speed limitation applies to most SBCs since to be able to exceed this slow mode the voltage the SD/TF card is fed with would've to be adjusted (default 3.3V, the faster modes require a dynamic switch to 1.8V instead which some/most SoCs can perform but if the SBC vendor doesn't implement this you're limited to ~23MB/s).   Therefore cards labeled as being capable of "up to 90MB/s" do not perform different than those that can only do "up to 20MB/s" as long as we're talking about sequential transfers since the SD card interface is already the bottleneck. But since we're using SD/TF cards not in cameras but as storage media for the rootfs of an SBC something different is more important: Random I/O. And here performance of cards that are labeled identical ('class 10' for example) differs a lot.   All 4 Samsungs outperform the other cards easily in this area. The SanDisk Extreme Pro can not compete regarding random I/O compared to superiour (but mostly irrelevant) sequential transfer speeds. And funnily the 3 other cards show horribly slow random write performance, especially with 16k record size. According to card metadata the 2 Intenso are oemid 0x5048 / manfid: 0x000027 (cheap crap known to die way too early) and I would believe the SanDisk 'class 10' card is a fake or at least uses the same controller as the 2 Intenso since 16K random writes are also way slower than 4K writes.   Detailed results (summary table also available as .ods, .xlsx or .txt):   Samsung Pro 64GB (brand new) http://sprunge.us/DEYd   Samsung EVO+ 64GB (brand new) http://sprunge.us/NLQd   Samsung EVO+ 32GB (brand new) http://sprunge.us/heGL   Samsung EVO 64GB (already used some time) http://sprunge.us/DUOS   SanDisk Extreme Pro 8GB (already used some time) http://sprunge.us/ZPFZ   SanDisk 'Class 10' 8GB (already used some time) http://sprunge.us/OHjT   Intenso 'Class 10' 16GB (already used some time) http://sprunge.us/LUMZ   Intenso 'Class 4' 4GB (already used some time) http://sprunge.us/GbAY   Some updates from Igor (still showing superiour EVO results but the clear winner is ODROID's eMMC module with SD card adapter):   Transcend Premium 300x 16GB (almost new) http://sprunge.us/UcSD  
 
 
Sandisk Extreme Pro 8Gb (almost new) http://sprunge.us/aDJJ
 
 
 
Hardkernel eMMC 8G via SD reader (brand new) http://sprunge.us/SHXF
 
 
 
Sandisk Ultra 8Gb (old and very used) http://sprunge.us/OWZf
 
 
 
Sandisk 8GB (almost new) http://sprunge.us/iViT
 
 
 
Sandisk 8G (new) http://sprunge.us/XHjj
 
 
 
Transcend 8Gb (used) http://sprunge.us/NTRT
 
 
 
Samsung EVO 32Gb (brand new) http://sprunge.us/bTQh
 
 
    Further readings: http://www.bunniestudios.com/blog/?page_id=1022 http://thewirecutter.com/reviews/best-microsd-card/ http://www.jeffgeerling.com/blogs/jeff-geerling/raspberry-pi-microsd-card http://www.bradfordembedded.com/2014/05/flashbenching/ Conclusions:
If the board's SD card interface is the bottleneck since it's not supporting the faster SDIO modes using expensive cards that exceed the interface's maximum sequential bandwidth is useless. An expensive Samsung Pro Plus won't be faster than a way more cheap EVO when it's about sequential transfer speeds since you will stay at ~22MB/s anyway Sequential read and especially write speeds are all the SD association's speed ratings are about (to ensure reliable recording of videos/images in cameras/recorders) When an SD card is used in an SBC sequential speeds aren't that important. It's all about random I/O, especially with small block sizes (reading and writing small random chunks of data from/to the card) No commonly used 'random I/O' speed ratings exist so you have to check the card in question prior to usage or rely on appropriate benchmarks (see the two links directly above). Again: the 'speed class' won't tell you anything. You can get two different 'class 10' cards that differ by 500% or even more regarding real world storage performance (again: random I/O matters). In the example above the Intenso 'class 10' card is 385 slower compared to the EVOs when it's about 16K random writes (good luck if you have a database running that uses this page size) Interestingly more expensive cards are outperformed by cheaper ones (the EVOs show a better overall performance compared to the Samsung Pro since sequential speeds are limited by the interface) One extreme example: Using an identical cloned installation that was somewhat outdated on the small 4GB Intenso card and on the 64GB EVO resulted in the following times for an 'apt-get upgrade' (+200 packages): EVO less than 6 minutes vs. 390 minutes (yes, ~6.5 hours) with the Intenso. The time to finish depends largely on fast random writes. It's easy to test the card in question when running Armbian since we ship with iozone. Therefore simply execute the iozone call from the first paragraph after logging in as a normal user. Starting with Armbian 5.06 a even better method exists that also tests the whole card for errors: armbianmonitor -c will report precisely both performance and health state of your card

There are many ways to watch accelerated youtoube videos on stock Armbian legacy install. Just not within a browser.
 
youtube-dl, mpv, ...
You don't need any windows based download tool. 
https://forum.armbian.com/index.php?/topic/499-bananapipro-video-accelerated-no-work/&page=2#comment-28237

It's to avoid Android on those boards since it's crappy and unsupported. Luckily we have a well maintained Openelec fork if you seek multimedia OS.

I have a 5" 800x480 TFP401 display which the current armbian can't drive, and I have no idea how to fix that. My EDID is identical to his.
 
I'm a total armbian noob and half linux noob and have no idea where to start or what all the used terms mean (u-boot, dpms, ...) or they come with random patches or links to github changesets that I have no idea what to begin with. All I know is how to compile Igor's kernel, change existing patches in his repo, and burn it (as image, not u-boot) to an SD card, all because there is a nice tutorial for it. When people start talking about anything else I have no idea what to do with that information.
 
I tried to modify the patch starting with 0026_ and edited video_timing[] with the parameters I got from EDID, but this doesn't work. I suspect I also have to edit video_timing[] but don't have enough information. (WereCatf's question about this was never answered).
 
I've already plowed through these resources without results (or with more questions than results, see my first rant above)
https://forum.armbian.com/index.php?/topic/752-tutorial-h3disp-change-display-settings-on-h3-devices/&page=2 https://forum.armbian.com/index.php?/topic/2874-adding-display-manager-in-armbian-and-attaching-hdmi-monitor/ https://github.com/igorpecovnik/lib/issues/594 https://github.com/igorpecovnik/lib/issues/443 https://forum.armbian.com/index.php?/topic/3671-adafruit-tfp401-hdmidvi-converter-doesnt-scale-screen800x480/

Download pages are not perfect. Zador already helped make them better, but I guess, none of us is UX design pro. I think they should be as simple as possible, while important data should be close to / exposed at download buttons area. Well, perhaps staring into download page for few hours strait might bring up some ideas
 
BTW. Yesterday I put together torrent server and all stable images can be download via torrent. We will have few dedicated seed spots around the globe, but at the moment, we seed them only at download server. This adds another item to the download page  

Most probably not. Orange Pi Plus 2 has no SATA, just a crappy/broken/ultra-slow USB-to-SATA catastrophe called GL830: http://www.cnx-software.com/2017/03/16/suptronics-x800-2-5-sata-drive-expansion-board-and-cases-for-raspberry-pi-23-and-odroid-c2-boards/#comments

Is OPI ONE a toy or a toy ? Yes and yes and a fun one too ! The following experiment shows the OPI ONE in use as a Virtual Desktop Server AND Virtual Desktop Client.
 
 
Setup as Virtual Desktop Server ( remotely access headless OPI ONE desktop )
 
OPI ONE  : install xrdp and tightvncserver
<clients>  : install and configure remote desktop  ( rdesktop on linux, aRDP on android - not yet tested on OS-X or WIN )
 
Setup as Virtual Desktop Client ( OPI ONE securely accesses a remote linux desktop )
 
OPI ONE  : install x2goclient
<server>  : install x2goserver on linux server ( physical or virtual ) of choice
 
 
This document explains the experiment ( you have to click/enlarge pictures in your browser .. sorry )
 

 
And here is a screenshot of the actual session :
 
Red : Linux server desktop connecting to OPI ONE via rdesktop / xrdp
Orange : OPI ONE desktop connecting to UK virtual server via x2goclient/x2goserver
Purple : virtual server (UK) desktop running libreoffice
White : actual document being edited ( incl. drawings ! ) in window
 
( Headline : Italian guy in Switzerland abuses OPI ONE to edit nerd stuff in the UK )
 
 

 
Remote desktop access from smartphone ( cheap Wiko Lenny 2 ) for touch-fumbling nano-fingers
 

 
Remote desktop access from tablet ( Galaxy Note 8.0  ) using pen
 

 
 
There are numerous use cases covered with the simple techniques employed.Thanks to the Armbian team and the forum buddies for their excellent job in making OPI ONE usable.
 
Have fun !

Unfortunately it doesn't work for me. My monitor gets unresponsive on reboot. It's probably due to my hdmi to vga-converter. Still, great work from the Armbian-developers!

Not with h3disp, then you would have to use bin2fex/fex2bin manually. The 'normal' Armbian way is to let the device boot while connected to Ethernet, then login through SSH from another machine on the network (if your router provides both DHCP and DNS, then in most cases a simple 'ssh root@orangepipc' should work for initial login and on H3 devices you should also be pointed to h3disp functionality then)

Hi,
 
I've managed to get my screensettings to 1280x1024 by filling out fb0_width = 1280 and fb0_height = 1024 in the script.fex file. And than rebuild my script.bin. It allready performes a lot better on my monitor. But there is no refresh rate (0,0) so the fonts are very blurry. Is there a way to adjust the refresh rate in the fex file? By the way, I'm using a hdmi-vga connector.
 
Thanks for all your great work on Armbian!! 

Here is a short instruction how to enable S/PDIF digital audio output on NanoPI M1 board running Debian Jessie with legacy kernel.  This instruction can be applied to other H3 based boards but connect S/PDIF output hardware to GPIOA17 can be tricky (soldering miniature camera connector pins). Operations can be done over serial console or ssh.   Login as root Get a .fex file and open it in editor: bin2fex /boot/script.bin /tmp/script.fex nano /tmp/script.fex Search a csi0 (camera) section an disable it: [csi0] vip_used = 0 Search a S/PDIF section and enable it: [spdif0] spdif_used = 1 Get the name of the file pointed by the /boot/script.bin link and convert modified .fex to it: ls -la /boot/script.bin ----- /boot/script.bin -> bin/nanopim1.bin fex2bin /tmp/script.fex /boot/bin/nanopim1.bin Open /etc/modules to instruct Jessie to load S/PDIF modules at boot: nano /etc/modules Add module names near the end of file: sunxi_spdif  sunxi_spdma   sndspdif   sunxi_sndspdif Reboot system: sync reboot After reboot login as root again Get the list of ALSA devices available: aplay -l **** List of PLAYBACK Hardware Devices **** card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0 []   Subdevices: 1/1   Subdevice #0: subdevice #0 card 1: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0 []   Subdevices: 1/1   Subdevice #0: subdevice #0 card 2: sndspdif [sndspdif], device 0: SUNXI-SPDIF sndspdif-0 []   Subdevices: 0/1   Subdevice #0: subdevice #0  
To connect board S/PDIF output to my favorite DAC i use an optical S/PDIF module soldered out from dead DVD player:
 

 
There are 3 wires connected to board 40-pin connector: GND (pin 6), VDD_5V (pin 2) and SPDIF-OUT/GPIOA17 (pin 26)
 

 
Module pinout can be found in datasheet http://www.mouser.com/catalog/specsheets/totx177(f,t).pdf
 
Modules come in 2 types: 6-MBit (up to 24 bit / 96KHz) and 15-MBit (up to 24 bit / 192KHz). Most likely from DVD or SAT receiver You get the 6-MBit module. 15-MBit modules can be purchased at Digikey, etc.
 
When listening to music, I faced with spontaneous fadings. This is due to some problem of the CPU speed switching. To this do not happen, I banned the clock frequency of 240 MHz in the /etc/default/cpufrequtils:
MIN_SPEED=480000