Search the Community

EDIT: This seems to be a problem with the OS running on the Mikrotik router. See this thread for a work-around that "shouldn't make a difference". Hi! I've got some trouble with u-boot on an Orange Pi PC+ connecting to a Mikrotik router RB922UAGS-5HPacD, and I'm not sure where I should start digging. Here is what I have so far: Orange Pi PC+ with u-boot 2017.11-armbian installed on eMMC by running nand-sata-install. But instead of booting from eMMC, I'd like to fetch the kernel via tftp, so I modified the bootcmd accordingly. The relevant configuration / commands are: setenv ipaddr 192.168.3.74 setenv serverip 192.168.3.73 tftpboot 0x44000000 some_file.scr The Mikrotik RB922UAGS-5HPacD shall be the tftp server. The relevant configuration is: /ip address add address=192.168.3.73/24 interface=ether1 /interface ethernet set [ find default-name=ether1 ] disabled=no /ip tftp add ip-addresses=192.168.3.0/24 allow-rollover=yes req-filename=some_file.scr real-filename=some_file.scr read-only=yes If I connect Orange Pi and RB922 with a straight ethernet cable, I can see the link coming up on the RB922 (100M-half), but u-boot can't ping the RB922 and tftp times out. If I put a switch between the Orange Pi and the RB922, everything works fine. If I use a different Mikrotik device (CRS125-24G-1S, a 24-port gbit-switch/router) and connect the Orange Pi directly to it, everything works fine, too. Note that in this case the configuration of the CRS125 is not exactly the same as on the RB922, because the CRS125 has more than one port and the ports are configured as a bridge: /interface bridge add admin-mac=XX:XX:XX:XX:XX:XX auto-mac=no fast-forward=no name=bridge-lan /interface bridge port add bridge=bridge-lan interface=ether2 /interface bridge port add bridge=bridge-lan interface=ether3 /interface bridge port add bridge=bridge-lan interface=ether4 etc. /ip address add address=192.168.3.1/24 interface=bridge-lan network=192.168.3.0 /ip tftp add ip-addresses=192.168.3.0/24 allow-rollover=yes req-filename=some_file.scr real-filename=some_file.scr read-only=yes # (yes, I changed "serverip" in u-boot for this test) Once the Linux kernel is up and running, the straight connection between Orange Pi and RB922 works fine (100M-full). It's just u-boot, and only with a direct connection to the RB922. Any clues what I should have a closer look at? Thanks a lot, Hendrik

I've try use the emmc storage on my Orange Pi (which was working on previous kernel). Copy seems to work with latest armbian-config but the boot loop on : Begin: Running /scripts/local-block ... done. Here is the full log : U-Boot 2018.05-armbian (Sep 19 2018 - 12:58:14 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi PC Plus DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Loading Environment from EXT4... MMC: no card present ** Bad device mmc 0 ** Failed (-5) In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 MMC: no card present ** Bad device mmc 0 ** MMC: no card present ** Bad device mmc 0 ** starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 8 ms (452.1 KiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 249 bytes read in 2 ms (121.1 KiB/s) MMC: no card present ** Bad device mmc 0 ** 5099960 bytes read in 250 ms (19.5 MiB/s) 6979808 bytes read in 342 ms (19.5 MiB/s) Found mainline kernel configuration 32641 bytes read in 28 ms (1.1 MiB/s) ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5099896 Bytes = 4.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49b22000, end 49fff178 ... OK reserving fdt memory region: addr=43000000 size=6e000 Loading Device Tree to 49ab1000, end 49b21fff ... OK Starting kernel ... Loading, please wait... starting version 232 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument [ 46.790736] reboot: Restarting system

Hey guys. I need your help. Since I'm new to linux I don't know what happened and what to do. Latest armbian was installed on my eMMC. Today at morning I woke up and logged in by ssh to my orange pi pc plus and get 'input/output error' for every single command. I've tried to reboot it by powering off and on and after that I could not log in by ssh. (and I noticed that green led not blinking and ethernet port green and orange LEDs was constantly on) I've inserted 16gb SD card with latest armbian installed on it and it works by booting from it(green led is blinking, ethernet port LEDs are also blinking, everything is ok). I've tried to list partitions and drives: and also this: http://ix.io/1nOQ (here we can see that system still detect mmcblk1 for some reason) pls help <3 sorry for my bad english

I've installed a bootable Armbian Ubuntu on an SD card. I plan to copy the SD's OS into multiple OPI PC+ devices. The problem I found was that somehow the HDMI monitor displays a different max resolution depending on which OPI device I'm using. The armbianEnv.txt for the SD card: verbosity=1 logo=disabled console=both #disp_mode=1920x1080p60 disp_mode=1280x720p60 overlay_prefix=sun8i-h3 rootdev=UUID=8bc771e4-1c8a-4bd0-af02-00570c63c5c9 rootfstype=ext4 overlays=uart1 uart2 uart3 extraargs=drm_kms_helper.edid_firmware=edid/1280x720.bin usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u When I boot the SD card on the OPIPC+ displaying the correct max resolution (1920x 720) , these settings are: xrandr --props: Screen 0: minimum 320 x 200, current 1280 x 720, maximum 8192 x 8192 HDMI-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 333mm x 187mm EDID: 00ffffffffffff0031d8000000000000 051601036d211278ea5ec0a4594a9825 20505400000081c00101010101010101 010101010101011d008051d01c204080 35004dbb1000001e000000ff004c696e 75782023300a20202020000000fd003b 3d2b2d08000a202020202020000000fc 004c696e75782048440a202020200094 non-desktop: 0 range: (0, 1) link-status: Good supported: Good, Bad 1280x720 59.65*+ When I boot the SD card on the The OPIPC+ displaying the wrong max resolution (1024x 768) has these settings: xrandr --props: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 HDMI-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm non-desktop: 0 range: (0, 1) link-status: Good supported: Good, Bad 1024x768 60.00* 800x600 60.32 56.25 848x480 60.00 640x480 59.94 uname -a: Linux orangepipcplus 4.17.14-sunxi #9 SMP Mon Aug 13 09:06:31 +08 2018 armv7l armv7l armv7l GNU/Linux The OPICP+ with the wrong max address also currently had a pink screen issue with legacy Armbian images. That's why I changed to the new mainline kernel; to enable HDMI output. On both OPIPC+ devices the EMMC is flashed with Armbian Debian stretch mainline. On both devices the Debian displays the resolution properly (1920x720). I am currently trying to get the Ubuntu OS to work as well.

Hi when I use the orangepi PC plus TRRS audio output (analog), I have some glitches which are linked to the video mouvment. I've tested the connection between ground and video and it seems that on the left ground pin there is a natural link with video output (50 ohms), is this normal? my cable is a 4 pole TRRS. I even tested audio with cable directly plug on soldering but same result. How could I get a clean audio output? note that the hdmi audio output is clean. and my speaker system is clean if I plug it on a MP3 player with an audio jack. I use retrorangepi 4.2 which is based upon Armbian v5.54 (default legacy kernel)

No sound via the hdmi port to hdmi tv port however I can use headphones with the 3.5 mm audio jack and it works fine. Not sure if my board is broken either. I just got it. The only image that works with my orange pi pc plus is Armbian Stretch edition. The ones I have tried thus far are armbian xenial multimedia edition, retrorangepi, android 7 from orangepi website they all don't work haven't tried bionic armbian edition though. But that is for another post just thought to mention that. 1. Logs when you can boot the board: armbianmonitor -u https://pastebin.com/e5xb2gZD

hello there! after update rpimonitor to 2.13-beta6 by Xavier Berger, can't monitor, any temperature , memory usage. But CPU freq, Sd card and network work OK. my spec : Orange pi pc + ARMBIAN 5.38 stable Ubuntu 16.04.5 LTS 3.4.113-sun8i

Hi, we have problems with 5 inch display from waveshare. Can somebody help us.

Hi, My applications were running from eMMC when I used Kernel 3.4.113 and Orange Pi PC Plus purchased 6 months back. But on my last week purchase, armbian-config of 3.4.113 does not detect eMMC of Orange Pi PC Plus. I am told by Xunlong to use the latest kernel. This will result in huge development efforts. Are there any patches that can be applied to 3.4.113 to use my same application on latest PCB? Thanks

Hi all, first of all, I really like the dev-tools! I successfully developed my own Image (incl. patches etc.) and it's running great. But now I want to "burn" it to the Orange Pi's emmc directly, without using nand-sata-install ... it's necessary, because the target-image does not allow shell- and/or ssh-access (for purpose). So I flashed a "normal" armbian-image to my sd-card, copied my own image-file to the card, booted the card and wanted to 'dd' my image to /dev/mmcblk1. Everything went fine till now ... after rebooting w/o the sd-card plugged in, the loader hangs in a loop (Rebooting within 10 seconds) :/ I looked into the nand-sata-install-script and found nothing special in there, so I'm missing something? I even tried to flash the bootloader after flashing the image (as done in the nand-sata-install-script), without success, too. I don't have a serial console right now, so if someone maybe knows what to do ... I'm really stuck right now :/ -- Micha

Previously I installed legacy Armbian to an Orange Pi PC Plus device and noted down its eth0 and wlan MAC addresses. Then I installed a Mainline Armbian server image to its EMMC, updated the armbian-config to enable the desktop manager. Now I checked the MAC addresses to be completely different. Why does this happen?

Hello there. I've got an Orange Pi PC+ SBC running desktop Armbian Xenial 5.38 kernel 3.4.113 from its eMMC that showed up pink screen after intermittent Power Up. I was using a 5V power adaptor that became faulty and intermittently became on and off. After replacing the power adaptor and booting up my device to a HDMI monitor, I found out that it now displays nothing but pink screen! Here's what I've done to no avail: 1. Turning on the HDMI monitor before and after I turn on the machine 2. SSHing from UART0 and suing command h3disp -m 5 (or 6 or 33 or 34...). No dice 3. Booting using the same Armbian OS but from SD card. SSH shows me the hostname is different(so same OS but boot from SD card ) but the display remains pink 4. Booting from Android SD card. The monitor works normally, showing the entire Android and all 5. Reflashed the eMMC inside the Orange Pi PC+ using the nand-sata-install from the Armbian SD card. After booting from eMMC the monitor is still pink! I noticed that during bootup, the Uboot output is different compared to the UBoot output of normal images. Normal Uboot utput: Pink Monitor UBoot Output Is this why the pink screen comes up, becauseUboot settings have been changed/corrupted somewhat during the intermittent power interrupt? How does the in, out and err defined? I've checked the files in /boot and couldn't find anywhere that refers to this. I don't understand how the device uses the eMMC UBoot even when it is booting from SD card, and how the problem persists even after I run nand-sata-install. A different Orange PI image works, so is this an Armbian issue? Is there a hardware broken somewhere?

Hello everyone, Is there any utility to deal with overscan when using TVout? I'm using Armbian Legacy kernel. There is a tool called Allwinner_TVOUT_manipulator, anyone have used it?

Hello Everyone! Need your help to difficult task. I'm a newbie to micro-computers. Recently installed Armbian on Orange Pi PC Plus (H3), but can't connect to a TVusing HDMI-VGA adapter. Get just black screen, but once got a pink image (as in attachment). That HDMI-VGA adapter works well with notebook and shows picture on this TV. However, this adapter works well with Orange Pi and my Iiyama computer monitor in VGA mode. So, i completely dont understand why Orange Pi not working especially with my Sharp TV. Native resolution of TV is WXGA (1360x768). I tried many resolutions and got black screens, but in XGA (1024x768) resolution i got pink screen (see image). Thanks for your help! UPD: Solution was in changing the hdmi-vga adapter to another. Works only in XGA resolution now.

Hello, I have following issue with HDMI resolution 1024x768. As soon as kernel starts loading, little light-green box 6x4px appears at the bottom-left corner of the screen and never goes away. The box always stays on top of everything including mouse pointer and vdpau-accelerated video, not visible on screenshots. Also HDMI sound is full of clicks in this resolution only. Other resolutions are ok. Seems that there is no problem with DVI 1024x768 (entire screen is greenish when connected by HDMI but i see that mouse pointer is visible in that area). First seen this on TV 42PC1RR which has native resolution 1024x768, also reproduced on fullhd monitor S24D390 in 1024x768 mode. Both screens work fine with other 1024x768 sources with same HDMI cables. Problem visible on latest Armbian Xenial 5.38, also on Armbian Xenial 5.24.

After a long time of happyness I got careless and did an apt-get upgrade on one of the OrangePiPcPlus, and I my Eizo FlexScan S1921 Monitor does not sync anymore. I need a Resolution of 1280*1024 at 60 Hz with a pll_video of 432 Mhz. I tried to reselect -m33 on h3disp but this did not change anything. Is h3disp even supported anymore? Have there been changes to the legacy kernel or the way resolution is selected? Before: root@JugOpi:~# uname -a Linux JugOpi 3.4.113-sun8i #18 SMP PREEMPT Thu Jun 15 02:16:06 CEST 2017 armv7l GNU/Linux root@JugOpi:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepipcplus BOARD_NAME="Orange Pi PC +" VERSION=5.31 LINUXFAMILY=sun8i BRANCH=default ARCH=arm IMAGE_TYPE=stable Afterwards: root@JagOpi:~# uname -a Linux JagOpi 3.4.113-sun8i #18 SMP PREEMPT Wed Jan 24 22:10:49 CET 2018 armv7l GNU/Linux root@JagOpi:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepipcplus BOARD_NAME="Orange Pi PC +" BOARDFAMILY=sun8i VERSION=5.38 LINUXFAMILY=sun8i BRANCH=default ARCH=arm IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage root@JagOpi:~#

Hi, I have some issues regarding the Orange Pi becoming non responsive and only accessible. When I look at the log, i just see an sudden stop of writing to the logfile. And this line: [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B Is the mmc failing? I currently have 80 orange pi's installed. 20 of them have this issue. Is this an PSU problem? Some external persons said that they had an problem with installing two Orange Pi's on the same electricty net. But was not confirmed by me. I've added an logfile logfile.txt

I have been searching the net trying to find out how to set up the WiFi interface on an Orange Pi or a Raspberry Pi 3B as an access point. I have to have an access point for a project I have in hand. I found the instructions by Lim Han Yang but they just failed entirely on two out of three candidate boards with the third, an Orange Pi PC Plus, producing a point that is visible to an Android tablet but refused to authenticate. I tried the create_ap procedure from github but that crashed on all three boards when dnsmasq hung. I tried ‘armbian_config’ on the Orange Pi PC Plus which was running the appropriate Armbian image. That didn’t do anything usable. Reasoning that the distributed software assumes that the board will always be used as a WiFi client and that a lot of the setup and software aimed at that would interfere with setting WiFi up to be an access point, I decided to strip away all of the networking software and rebuild it using related versions of programs that have worked for me on desktop linux machines. I tried this on the Orange Pi PC plus first - AND IT WORKED. I tried it again on an Orange Pi Zero, which is the platform I want to use for my project – AND IT WORKED. Here is how I did it. My aim in doing this is to have just a WiFi access point without connection to anywhere else for a project that may be solar-powered a few hundred klicks into the outback and just as far from an internet connection. The boards I am looking at also have a CAT5 connection but my only interest in that is maintenance and software updates, so any possibility of bridging between the two is viciously suppressed. If I were trying to set up a bridged connection, I would use ‘iptables’ to create the appropriate routing. The Wifi is set up with a static IP and a dhcp server to provide connecting clients with an IP address and the hostapd binary to manage connection and WPA2 authentication. The CAT5 point is set up as a dhcp client, although that could have been given a static address also and may get one if remote-area maintenance with a laptop requires it. Install an Armbian image on your platform of choice. Other distros may work but I haven’t used them as I want a simple CLI linux. Assuming that your board automatically connects to the internet, do ‘apt upgrade’ to bring everything up to date. If your board’s internet connection and console access is through WiFi then things may get sticky for you. I used either an SSH connection through CAT5 wiring or the Orange Pi boards debug serial interface at 115200 baud via a 3.3Volt (5Volt WILL destroy the board!) TTL serial to USB interface for console access during these modifications. Login as the default user and if it is not root, do ‘sudo passwd root’ and create a password for root. This will enable you to log in as root and remove the need to use sudo (which I forget to do half the time – annoying). Either delete or ‘chmod a-x’ the wpa_supplicant, dhclient and dnsmasq (if installed) binaries. The scripts which invoke these will still be active and will fail – an untidy situation but I don’t care. Use whereis to find them. Do ‘apt install dhcpcd5 udhcpd hostapd’ (apt-get may work too). You may want to ‘apt install’ a text editor at this point, ‘nano’ is a good choice but I prefer ‘joe’ as I’ve been using it for years. ‘vi’ is long overdue for relegation to the deepest pits of hell. cd to ‘/etc/default’ and edit ‘hostapd’ to add DAEMON_CONF="/etc/hostapd/hostapd.conf" edit ‘udhcpcd’ to read: DHCPD_ENABLED="yes" DHCPD_OPTS="-S" remove dnsmasq if it exists. cd to ‘/etc/network’ and make ‘interfaces’ , ‘interfaces.hostapd’, ‘ interfaces.r1’, ‘interfaces.r1router’ and ‘interfaces.r1switch’ as in the attachments. Bear in mind that IP numbers, net masks etc. in these files are chosen to suit my preferences, your mileage may differ. cd to ‘/etc’ , do ‘rm –r dnsmasq.d’ and ‘rm –r dhcp’ and create or modify dhcpcd.conf and udhcpd.conf to be as in the attachments. Once again, IP numbers etc. are my preferences. This might be a good time to edit ‘hostname’ to be something you want it to be. cd to ‘/etc/hostapd’ and create ‘hostapd.conf’ as in the attachments. You may want to add telnet capabilities, in which case do ‘apt install inetd telnet’ then ‘update-inetd –-enable telnet’ then if you want to login as ‘root’ over telnet, edit ‘/etc/securetty’ to include ‘pts/0’ and ‘pts/1’ etc. . NOTE THAT TELNET IS AN INSECURE COMMUNICATION METHOD but it suits my purposes. The above setup has been running reliably for a couple of months now and (touch wood) I see no reason other than hardware failure that would change that. ConfigurationFiles.zip

With an earlier version of Armbian (Server) I was able to use my Orange Pi Pc + to feed data back to Flightaware, Flight Radar, Planefinder, ADSB Exchange. An upgrade put an end to that in the latest version. Is it possible to get this working in future Upgrades of Armbian? Piaware Install

Hi. The following happened. When power is suddenly cut off in emmc, the file contents created by fopen (), fprintf (), fflush()　and fclose () are not saved after rebooting. It seems that it has not been physically written out while being cached. If display the file before cutting off the power, the contents are correctly saved. In addition, if it is normally reboot it is saved correctly.

Hi I only have an old monitor, and I thus need to use a HDMI-to-VGA-converter to work with my Orange Pi PC Plus. When powering the Orange Pi on, the green LED on the board is constantly ligthened. On the monitor, I get a black screen, after 4 s (or so) a totally red screen. No text. No graphics. Then after about 15 s, on the board the red LED starts to double blink. The red screen remains for ever. I have tested the Raspbian and Debian images available on http://www.orangepi.org/downloadresources/. They work fine with the converter. Alas, the preferred OS, "Orange OS" armbian, seems not to work. Board: Orange Pi PC Plus Image: Armbian_5.38_Orangepipcplus_Ubuntu_xenial_default_3.4.113_desktop.img downloaded from https://www.armbian.com/orange-pi-pc-plus/ I'm using a high quality SD card from Transcend (32GB, *400, class 10). The SD card was checked with H2testw: Okay! The SC card was formatted (no quick format) with "SD Formater". The checksum of the downloaded image had been verified with 7-Zip: Okay! The image was burnt and successfully validated using Etcher. And I only get a red screen when powering the system on :-( What can I do?

I want to know something about the physical connection in the integrated CVBS video output. I use a jack of 3.5 mm of 4 pins. I see that the last 2 pins of the Orange pi Pc plus are the two audio outputs (Left and Rigth). other two are ground, and the other , the first one, I suppose that is the video output. but physically when I connect the jack to the video output and audio output of the orange, I can measure continuity between the supposed video output and ground. I want to know if something is wrong with that, and if I must be configure something internal in the orange for change this. in summary the audio video output have 5 connections: 2 of audio, 2 grounds and one video output, when I connect the jack, 3 of this 5 pins have continuity. Thank you for your attention. A newbie.

I have just received an Orange Pi PC Plus, and am mostly happy with it. Linux orangepipcplus 4.14.18-sunxi is installed on a microSD card. There is a minor problem with IP addresses. When I first turned it on I forgot to plug in the network cable, so naturally ifconfig showed no IP address. I plugged in the cable, waited a minute, and tried again. Still no address. Maybe it's not hot-pluggable. Reboot, and I got an address. Since it was outside the range my server accepts I assigned a static address in the router, and rebooted the router. ifconfig still showed the first address, even though the router's client list showed the new static address. Another reboot was needed. All my other systems update an address change automatically. Some day I hope to be able to stream live TV (currently I get 5fps) but it's not a priority.

Hi all, I recently purchased an orange pi after developing on the raspberry pi (just for convenience). I got it mainly because the integrated memory could be a real asset both because SD are faulty when making lots of memory accesses and emmc can provide a nice layer of code protection when giving the board to somebody else. I set-up everything without issue and I used the nand-sata-install to move everything to emmc...it worked like a charm. I then placed all my proprietary code on emmc and executed without issues. Problem is, I can obviously still insert an SD card and then mount the emmc and access my code since the SD is booted before the emmc. 1. Is it possible to change this boot order or to just completely disable SD boot and thus deliver an emmc only device to a client? 2. How does the boot for H3 works? I read about u-boot and similar but it is not very clear to me what is the boot sequence and where it starts from. 3. As an alternative, should I just unsolder the SD tray or is there any other HW mod I could do to block sd cards? I considered (and I will probably use it for some other layers of protection) using some encryption, but in general that uses lots of resources. Any help would be really appreciated, thanks in advance.

Hello, I'm following this project : I was recently spending time on the activities to do with children, 3D printing and robotics, and in order to be able to try to follow https://docs.armbian.com/Developer-Guide_Build-Preparation/ i have bought a new laptop which respect the requirements (SSD, ram...). So now my next goal is to try to make a custom version of armbian dedicated to the schools. To start, for the first step, I would like to try make a localized version of armbian in French by default, in order to be more easier for the French speaking user. With the new evolutions of armbian for OrangePiPC+, there is an ubuntu desktop version, and now a Debian version (thanks for the armbian team for these improvements). I would like to know if there is recommendations, pros and cons for choosing ubuntu or Debian. The context that can maybe have an impact on the choice could be : - the compatibility with VGA screen (as it's for schools lot of old screen are used) ; - the computer will be used for 3D activities (blender, openscad...) ; - I have never made a compilation of an OS (but I'm motivate to learn it with the armbian doc). Is there any advice to choose ubuntu legacy or Debian stretch ? Thanks, Best regards