rodolfo

@igor After fresh install of Armbian_5.10 (jessie legacy server) on OPI ONE wireless dongles 8192cu crash kernel. The proven procedure (see previous posts) for Armbian_5.05 does NOT work for Armbian_5.10. Log from failed installation : root@orangepione:~# cd /usr/src/linux-headers-3.4.112-sun8i/ root@orangepione:/usr/src/linux-headers-3.4.112-sun8i# make scripts scripts/kconfig/conf --silentoldconfig Kconfig fs/Kconfig:287: can't open file "fs/fs_compat.kconfig" /usr/src/linux-headers-3.4.112-sun8i/scripts/kconfig/Makefile:33: recipe for target 'silentoldconfig' failed make[2]: *** [silentoldconfig] Error 1 /usr/src/linux-headers-3.4.112-sun8i/Makefile:493: recipe for target 'silentoldconfig' failed make[1]: *** [silentoldconfig] Error 2 make: *** No rule to make target 'include/config/auto.conf', needed by 'scripts'. Stop. root@orangepione:/usr/src/linux-headers-3.4.112-sun8i# cd root@orangepione:~# git clone https://github.com/pvaret/rtl8192cu-fixes Cloning into 'rtl8192cu-fixes'... remote: Counting objects: 438, done. remote: Total 438 (delta 0), reused 0 (delta 0), pack-reused 438 Receiving objects: 100% (438/438), 1.80 MiB | 994.00 KiB/s, done. Resolving deltas: 100% (223/223), done. Checking connectivity... done. root@orangepione:~# cd rtl8192cu-fixes root@orangepione:~/rtl8192cu-fixes# make ARCH=arm make ARCH=arm CROSS_COMPILE= -C /lib/modules/3.4.112-sun8i/build M=/root/rtl8192cu-fixes modules make[1]: Entering directory '/usr/src/linux-headers-3.4.112-sun8i' CC [M] /root/rtl8192cu-fixes/core/rtw_cmd.o /bin/sh: 1: /usr/src/linux-headers-3.4.112-sun8i/scripts/recordmcount: not found scripts/Makefile.build:307: recipe for target '/root/rtl8192cu-fixes/core/rtw_cmd.o' failed make[2]: *** [/root/rtl8192cu-fixes/core/rtw_cmd.o] Error 127 Makefile:1368: recipe for target '_module_/root/rtl8192cu-fixes' failed make[1]: *** [_module_/root/rtl8192cu-fixes] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-3.4.112-sun8i' Makefile:584: recipe for target 'modules' failed make: *** [modules] Error 2 Please advise as to how to proceed in Armbian_5.10 to make 8192cu dongles work again . Thanks.

@igor I noticed wrong board detection for OPI ONE on two occasions when doing a fresh Armbian install. In both cases a Realtek wifi dongle was attached and the board was identified as OPI PLUS. Reflashing and reinstalling without the dongle solved the problem.

@Marc The small arm boards are wonderful for games, entertainment and hand-crafted appliances of all sorts. Pick one supported by excellent Armbian or use a recent Raspi. The boards you own are just fine for that. There is no such thing as "General PC" but you state requirements as - truly silent and very, very low power - desktop for my research/writing. - DTP and graphics - fixed to the rear of a monitor - accelerated video and reliable sound - cost IS a consideration Your OPI PC is cheap, silent, low power with accelerated video and reliable sound when hooked up to HDMI-monitor with speakers. You can also use it for research/writing (even DTP and graphics) , but don't expect stellar performance. You do get quite pleasing performance by using OPI PC ( tested on smaller sibling OPI ONE ) as a capable thinclient accessing a physical (cheap old linux-converted notebook or PC ) or virtual ( virtual private server possibly living in the clowd ) linux server running suitable powerful software, keeping vital data centralized and universally accessible. Does this sound like what you want ? The recipe for your "general PC" is explained at http://forum.armbian.com/index.php/topic/1044-remote-desktop-fun-with-armbian-505-on-opi-one/ Enjoy !

Thanks for keeping it simple. Armbian is just fine the way it is. Starting from a simple but powerful basic distro is much easier for any sort of customized versions. And as there are as many different tastes as there are people, a basic distro is just fine for everybody. The rest is apt-get whatever...

@dony71 x2go is simply remoting graphics. In a test setup, I connected to OPI ONE with x2go. I then installed mpv on an OPI ONE, connected a cheap webcam to it and just ran mpv tv:// in a terminal window. Slow, but no problem. Here's a screenshot of the experiment. OPI ONE is run on battery and the webcam pointed at the x2goclient screen. Your problem most likely is setup/options of mpv player, codecs used etc.... Sorry, cannot help you with that. The topic here is remote desktop. Good luck.

@boobypi You're welcome. X2goserver on OPI is definitely on my wishlist and your information is very much appreciated. For pure linux environments I prefer x2goserver/x2goclient over xrdp/rdesktop, except for android clients which lack x2goclient capabilities. I'll try your recipe to get a working x2goserver on arm and report back. Just set up a working x2goserver installation as per your instructions. Thanks, you are my hero ! Screenshot of x2goclient running in (virtual) windows7 connected to x2goserver running on OPIONE. Have a nice day.

@dony71 What exactly are you trying to do ? I tested mpv player on a debian jessie linux host running x2goserver by connecting to the dektop with x2goclient running on an OPI ONE. I could sort of watch a video running at the remote host, but of course not at the necessary framerates.

The following USB-dongles are tested and work with Armbian_5.05 on OPI ONE ( little brother of OPI PC, uses same USB-firmware ) : USB Device ID 0bda:8176 Realtek RTL8188cus ( cheap $1.70 dongle from Aliexpress ) 0bda:0179 Realtek RTL8188eu ( cheap $1.60 dongle from Aliexpress ) 7392:7811 Edimax EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] ( rather expensive, promoted for Raspberry Pi ) all three dongles work reliably, expect speeds of up to 80mbps ( depending on environment ) as compared to stable 95mbps on LAN. Follow the steps in http://forum.armbian.com/index.php/topic/749-orange-pi-pc-wireless-module-8192cu/ ( By the way - this forum post is edited in Iceweasel running on OPI ONE remotely accessed via xrdp/rdesktop. Connection is wireless and typing is without any lag ) For more wireless fun, have a look at http://forum.armbian.com/index.php/topic/1044-remote-desktop-fun-with-armbian-505-on-opi-one/ Good luck

Ok. The best and brightest learn constantly every single day. As I do not personally know everybody "that ever visited a forum since the dawn of the internet" I humbly suggested to document the steps needed to post images on the forum. The procedure is rather strange and far from intuitive. ( In the last millenium we did some drag'n drop, but the forum software cannot handle simple base64 stuff ). If I stepped on your toes I sincerely apologize. Have a nice day.

1. Select your images ( attach files -> button : choose files ) and upload them to the forum 2. Insert the displayed attachments into the forum text (Add to Post) 3. Preview and upload the post

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 !

Nope - just x2goclient on Armbian. Successfully installed xrdp/tightvnc on OPI ONE and accessed it via rdesktop client from linux and aRDP from android. For graphical access to OPI ONE running remotely through firewalls, I tunnel and relay the rdesktop-session via ssh/x2goserver running on a x86 server. see http://forum.armbian.com/index.php/topic/1044-remote-desktop-fun-with-armbian-505-on-opi-one/

@zamar19 I am a simple man and I love stably running boards 7x24 with no hassles. As to peripherals, drivers etc.. I test them - actually I give a *%&? about what should work. If it works, it works. So far I am successfully using Openelec and Armbian_5.05 with legacy kernels on OPI ONEs, both wired and wireless. Thinclient access of linux hosts from Armbian/x2goclient is performant and low-power LXDE-desktops via XRDP are fun to run on smartphones, tablets or notebooks. Tested real life performance is better than on Raspi A+/B+/2. I do understand that the Armbian team may not be too enthusiastic about patching all the broken drivers/firmware for all the broken hardware for vendors circumventing the rules of GNU software. The "inherent potential" in 4.x will simply be a stable basis. No more and no less. Thanks to the Armbian team for keeping up the good work ! Maybe you could invest some of your time and efforts to remind Xunlong/Allwinner about their obligations to the guys that turn their half-baked cookies into real usable products.

From an engineering viewpoint Igor's approach definitely is the BEST. To build a house, you need a foundation, some walls and a roof - interior decoration will make it liveable. Considering the "premium Chinese" support by Xunlong/Allwinner, Armbian is quite a marvel. From what I gather from the discussions on the forum, kernel 4.x is being pushed. This will unleash the inherent potential of the H3 boards and make it much easier to find proper drivers for a broad range of peripherals as well.

Thanks for posting the Windows joke.

An additional step improves performance of module 8192cu ( Proven Edimax EW-7811UN as well as $1.60 China-crapdongles from Aliexpress ) nano /etc/modprobe.d/8192cu.conf options 8192cu rtw_power_mgnt=0 rtw_enusbss=0 This stops erroneous power management ( dmesg flooded with attempted power switches ). After network reload/restart you get about up to 90mbps from EW-7811UN and gain much stability with the ChinaWifi-crapdongle at up to 60-70mbps, performances measured with iperf ( 4m open space from access point ). Before correction, values were at 12mbps for ChinaWifi. Edimax performs way better than the cheap dongles, but with the options set they are quite useful too . AP mode is not solved yet, might have to wait for saner drivers in mainline.

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 !

Please, please spare us any sort of "auto-configuration" and thank you for keeping Armbian straight and simple! I am currently testing Armbian_5.05 on OrangePiOne using the jessie server version as a basis. Adding needed packages one by one, the restricted ressources should be best used for production use cases. By far the easiest ways to "find" a headless server is to look at the end of the serial console cable attached to it or ssh to a STATIC IP configured in /etc/network/interfaces.

SDcard Cloning SDcard cloning is simply done with dd if=<source-device> of=<target-device> If your target device is smaller ( 8GB ) than your source device ( 16GB ) and the net content (<=8GB) fits onto the target device you first have to move/resize your partitions and the data contained within to the beginning of the source drive with gparted. After cloning, you may expand the partitions on the target SDcard again with gparted. The smart solution is to start with master SDcards of SMALL capacities ( 4 GB ) before your shiny new system is reasonably stable and then maybe copy to larger production SDcard. Keep your basic system small and use readily available other storage for data ( usb flash, hdd, network drives ). Backup/Restore Backup/restore of partition data is simply done with rsync. By using hardlinks you can achieve a fully versioned backup-solution allowing complete disaster restores ( somebody - certainly not you - did "nothing" and everything blew up ) from generations of FULL backups. You are also able to restore a file from three days ago ( before you were struck by a bright solution ) into your de-repaired running system.

Wow - you probably used up your budgets already discussing wild testing scenarios. I would never ever buy the "best" solution, I would just opt for something workable and do some very basic tests ( testing ONE thing at a time, as tkaiser constantly reminds you ) What do I get from an OrangePiOne torrent box running stock Armbian_5.05 ? - 4 cores sanely volted+clocked (running without heatsink) -> enough horsepower for processing - Fast ethernet 100 with tested 95mbps -> 10 MB/s data exchange - SATA-HDD on USB2 via cheap adapter -> 30/30 MB/s data write/read ( single-powered directly from port ) ( USB2-Stick on USB2 via OTG-adapter -> 5/10 MB/s data write/read ) ( USB3-Stick on USB2 via OTG-adapter -> 12/25 MB/s data write/read ) Assuming you are hooking this up to a home network with limited uplink to the Internet, this setup will suffice at an unbeatable price.

Instead of participating in a soldering contest I looked at the OrangePiOne board and found two fully functioning USB ports ( regular and microUSB dubbed OTG ) ready to be used. Two fast connections or one fast and several slower ones via external hub for testing are usually plenty. If you need more - the solution is called OrangePiPc. Please let us know who won the soldering competition and post some pictures of successfully added DIY USB host ports before hotgluing the mess to a repurposed old X86 PC with spare USB ports

Strange indeed. I've just successfully tested OrangePiOne with Armbian_5.05 on any old crappy sdcards ( "class" 4,6,10 4G ). Cards were prepared on a linux host ( dd ), installed on OrangePiOne and heavily used ( actually misused ) with random reboots, shutdowns, disconnecting power. Despite some (probably erroneous) error messages (mmc) the boards booted without any problems and even heavy abuse did not corrupt the sdcards. I've noticed some other phenomena which are HW-related. Crappy power cables or crappy power supplies lead to erratic boot behaviour. Attach the serial console and run the board power cable through a voltmeter/ammeter. During a normal boot you'll notice current going up from <100mA to >200mA. I've traced all boot failures to problems with power supply. Practical jokes like powering an USB-attached disk from the USB connection yield rather strange results too By the way - use a cheap working any-old-class 4G sdcard for testing until you are satisfied with a working basic image. Create a backup image and use this as a basis for copying to a "high class zillion-G" sdcard. Expanding is so much more fun than shrinking.

@igor Thanks for the info and keep up the good work. I'll try to contribute in areas I'm knowledgeable about, mainly testing, documenting and high level use cases.

The armbian-5.05 builds for OrangePiOne ( simple/xfce - versions ) both fail with 8192cu wifi-dongle EW-7811Un. Armbian seems to try to register the module twice and causes fatal crashes when using the installed driver(s). ====================================================== dmesg ----- [ 6641.758850] rtl8192cu: Chip version 0x10 [ 6641.843455] rtl8192cu: MAC address: 80:1f:02:84:da:34 [ 6641.843475] rtl8192cu: Board Type 0 [ 6641.843697] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1 [ 6641.843819] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin [ 6641.844488] usbcore: registered new interface driver rtl8192cu [ 6641.872716] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' [ 6641.874212] rtlwifi: wireless switch is on [ 6641.901717] rtl8192cu driver version=v4.0.2_9000.20130911 [ 6641.901746] Error: Driver 'rtl8192cu' is already registered, aborting... [ 6642.110495] systemd-udevd[1176]: renamed network interface wlan0 to wlan1 lsmod ----- Module Size Used by rtlwifi 46169 0 rtl8192c_common 33409 0 mac80211 366795 2 rtlwifi,rtl8192c_common 8192cu 520853 0 8189es 896688 0 lsusb ----- Bus 002 Device 012: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] /etc/udev/rules.d/70-persistent-net.rules -------------------------------------------------- # USB device 0x:0x (rtl8192cu) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:e0:4c:81:92:de", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0" # USB device 0x:0x (rtl8192cu) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="80:1f:02:84:da:34", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan1" ============================================== The same dongle works flawlessly in the latest Openelec-build from orangepi.org. It would be very helpful to have working wifi with proven reliable USB-dongles. Ethernet works fine in armbian5.05 with speeds of 94Mbs. Will wifi be available in legacy or will we have to wait for 4.x ? Thanks for the good work, OrangePiOne is starting to look like a real contender !

I just tested and confirm working xrdp accessed from Linux hosts , Android tablet and smartphone . Installation on OPIONE / armbian 5.05 -------------------------------------------------- $> sudo apt-get install xrdp tightvncserver Test Remote Desktop on Debian Jessie Host (OK) ------------------------------------------------------------------- $> rdesktop <orangepione-ip> Test Remote Desktop via x2goclient on Debian Jessie Host (OK) -------------------------------------------------------------------------------------- Configure x2goclient for direct RDP-connection to OrangePiOne Test Remote Desktop on Tablet Samsung GT-N5110 / Android 4.4.2 (OK) ------------------------------------------------------------------------------------------------- Install working app ( M$ has problems as usual ) : aRDP Free Test Remote Desktop on al-cheapo Smartphone Wiko Lenny2 / Android 5.1 (OK) ----------------------------------------------------------------------------------------------------------- Install working app : aRDP Free @aseok Please change title to "No problem with xrdp in opi one" Have fun