gounthar

I bought two, and the first one doesn't work at all for the OrangePi One Plus (but works for the Raspberry Pi). The second one works for the two of them...

I see. Why not try, thanks a lot @raschid.

The first package downgrade went fine. Unfortunately, the second one does not exist in version 5.31. Which version should I use? sudo apt install linux-u-boot-orangepizero-next=5.31 Reading package lists... Done Building dependency tree Reading state information... Done E: Version '5.31' for 'linux-u-boot-orangepizero-next' was not found root@openstf-orangepi-zero:~# sudo apt install linux-u-boot-orangepizero-next Reading package lists... Done Building dependency tree Reading state information... Done linux-u-boot-orangepizero-next is already the newest version (5.38). 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Thanks.

Thanks to @raschid for giving me the link of this thread, as I may have the same kind of problem with my OrangePi Zero. Is there anything specific to armbian to monitor the memory usage, or a good old /proc/meminfo is the info to use? I know my Zero uses swap, which is a bad thing, but it looks like the discussion about using zram on Armbian for small memory SBC is not over... Here is the diagnosis.

Thanks a lot, will do.

Hi, now that I have Docker up and running, I am facing new problems. After some time, the Zero stops working. I am connected with ssh, and the console is stuck. The port 22 seems to be still opened for nmap, but I can't open a new ssh session anymore. I was trying to monitor it with armbianmonitor -m, and I saw the processor throttling with the temperature rising. Up to 62°C, it stays at 1200MHz, then it goes down to 960MHz, and I saw it once at 480 around 72°C. As I thought that my problems were linked to the heat, I then used a fan and the temperatures stayed at max around 63°C and the CPU at 1200MHz. But the problem still happens. After 7 minutes or so, the Zero stops working: 07:29:57: 1200MHz 3.18 71% 15% 0% 0% 55% 0% 57.2°C 0/8 07:30:11: 1200MHz 6.35 65% 11% 8% 0% 45% 0% 63.0°C 0/8 07:30:17: 1200MHz 5.75 29% 8% 19% 0% 1% 0% 62.1°C 0/8 07:30:22: 1200MHz 5.37 28% 11% 15% 0% 1% 0% 62.4°C 0/8 07:30:27: 1200MHz 5.10 28% 8% 17% 0% 1% 0% 62.7°C 0/8 07:30:32: 1200MHz 4.77 22% 4% 17% 0% 0% 0% 62.6°C 0/8 07:30:38: 1200MHz 4.47 28% 6% 19% 0% 2% 0% 61.0°C 0/8 Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 07:30:43: 1200MHz 4.19 21% 6% 14% 0% 0% 0% 63.5°C 0/8 07:30:48: 1200MHz 3.94 23% 9% 10% 0% 2% 0% 62.4°C 0/8 07:30:54: 1200MHz 3.70 8% 4% 1% 0% 1% 0% 60.6°C 0/8 07:30:59: 1200MHz 3.48 23% 5% 14% 0% 2% 0% 61.3°C 0/8 07:31:04: 1200MHz 3.29 29% 5% 21% 0% 1% 0% 62.7°C 0/8 07:31:09: 1200MHz 3.18 27% 7% 17% 0% 2% 0% 63.0°C 0/8 07:31:15: 1200MHz 3.17 36% 9% 12% 0% 13% 0% 61.2°C 0/8 07:31:21: 1200MHz 2.91 9% 6% 0% 0% 2% 0% 60.6°C 0/8 07:31:27: 1200MHz 2.68 32% 10% 4% 0% 16% 0% 61.7°C 0/8 07:31:32: 1200MHz 2.71 18% 9% 5% 0% 2% 0% 60.1°C 0/8 07:31:37: 1200MHz 2.49 8% 4% 2% 0% 0% 0% 60.6°C 0/8 07:31:48: 1200MHz 2.29 29% 12% 1% 0% 14% 0% 61.0°C 0/8 07:32:46: 1200MHz 4.86 78% 32% 0% 0% 45% 0% As you can see in the logs, the load is heavy, but the temperature is low. What could I check to know more about these crashes? Is there a message I could find in the logs after rebooting? Is there anything I could use to know more about that? Is there anything I could do to prevent that? Thanks.

After several reboots, docker seem to work now (without any further modifications). Go figure... docker images REPOSITORY TAG IMAGE ID CREATED SIZE <none> <none> b12376e7113c About a minute ago 7.79MB armhf/alpine latest 15ed6d4bf10d 12 months ago 3.6MB

Hi, I'm very happy to have my OrangePi Zero working (at last!) with Armbian. It looks like docker installed properly on the latest Armbian Stretch mainline kernel 4.14.y, but for some reason, it won't start. Here are the logs I have: systemctl enable docker Synchronizing state of docker.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable docker root@orangepizero:~# systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. root@orangepizero:~# systemctl status docker.service ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2018-06-03 12:43:49 UTC; 8s ago Docs: https://docs.docker.com Process: 20147 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 20147 (code=exited, status=1/FAILURE) CPU: 990ms Jun 03 12:43:48 orangepizero systemd[1]: docker.service: Unit entered failed state. Jun 03 12:43:48 orangepizero systemd[1]: docker.service: Failed with result 'exit-code'. Jun 03 12:43:49 orangepizero systemd[1]: docker.service: Service hold-off time over, scheduling restart. Jun 03 12:43:49 orangepizero systemd[1]: Stopped Docker Application Container Engine. Jun 03 12:43:49 orangepizero systemd[1]: docker.service: Start request repeated too quickly. Jun 03 12:43:49 orangepizero systemd[1]: Failed to start Docker Application Container Engine. Jun 03 12:43:49 orangepizero systemd[1]: docker.service: Unit entered failed state. Jun 03 12:43:49 orangepizero systemd[1]: docker.service: Failed with result 'exit-code'. root@orangepizero:~# uname -a Linux orangepizero 4.14.14-sunxi #1 SMP Thu Jan 25 12:20:57 CET 2018 armv7l GNU/Linux Is there anything I can do to get it working? Here are the diagnosis: diagnosis. Thanks.

Today, I finally managed to get it running. Don't ask why, I didn't change anything... But I am now logged (and have other issues).

Very kind of yours to let me know. Thanks a lot! Edit: I received the cable today, and nothing happened when I plugged it in. Is there any other kernel version that can handle it?

Hi, I bought a OrangePi Zero, burned the latest image on a good SD card, and started it. I bought a hat with a video output, but I don't have the right cables yet. So... I'm trying to set it up without any display for the time being. It looks like the port 22 is not opened, or any other ports, depending on the nmap command I use: $ nmap -sS -O -PI -PT 192.168.0.15 Starting Nmap 7.50 ( https://nmap.org ) at 2018-06-01 07:33 ope Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 5.05 seconds $ ssh root@192.168.0.15 ssh: connect to host 192.168.0.15 port 22: Connection timed out At one time, I plugged it in my Windows machine, and it was seen as a serial gadget. I tried to contact it with Putty, but never managed to start a session. Does anynone have the reference of a cable/adapter I could plug in it so that I can log from my PC onto it? Thanks a lot.

Pretty cool, thanks for the link.

O2 compilation doesn't work either: [ o.k. ] Downloading sources [ o.k. ] Checking git sources [ u-boot v2017.11 ] [ .... ] Remote URL does not match, removing existing local copy [ .... ] Creating local copy [ .... ] Fetching updates fatal: dumb http transport does not support --depth [ .... ] Checking out error: pathspec 'FETCH_HEAD' did not match any file(s) known to git. [ o.k. ] Checking git sources [ linux-mainline linux-4.14.y ] [ .... ] Remote URL does not match, removing existing local copy [ .... ] Creating local copy [ .... ] Fetching updates remote: Counting objects: 65206, done. remote: Compressing objects: 100% (60889/60889), done. remote: Total 65206 (delta 5987), reused 26047 (delta 3343) Receiving objects: 100% (65206/65206), 172.40 MiB | 1.09 MiB/s, done. Resolving deltas: 100% (5987/5987), done. From https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable * branch linux-4.14.y -> FETCH_HEAD * [new branch] linux-4.14.y -> origin/linux-4.14.y [ .... ] Checking out [ o.k. ] Checking git sources [ sunxi-tools master ] [ .... ] Up to date [ o.k. ] Checking git sources [ rkbin-tools master ] [ .... ] Up to date [ o.k. ] Checking git sources [ marvell-tools A3700_utils-armada-17.10 ] [ .... ] Up to date [ o.k. ] Checking git sources [ odroidc2-blobs master ] [ .... ] Up to date [ o.k. ] Cleaning output/debs for [ odroidc2 next ] [ o.k. ] Cleaning [ u-boot/v2017.11 ] grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory [ o.k. ] Compiling u-boot [ 0 ] [ o.k. ] Compiler version [ aarch64-linux-gnu-gcc 7.2.1 ] [ .... ] Checking out sources error: pathspec 'HEAD' did not match any file(s) known to git. [ o.k. ] Cleaning [ u-boot/v2017.11 ] [ o.k. ] Started patching process for [ u-boot odroidc2-odroidc2-next ] [ o.k. ] Looking for user patches in [ userpatches/u-boot/u-boot-odroidc2-next ] make: *** No rule to make target 'odroid-c2_defconfig'. Stop. make: *** No targets specified and no makefile found. Stop. [ error ] ERROR in function compile_uboot [ compilation.sh:156 ] [ error ] U-boot compilation failed [ o.k. ] Process terminated root@ac4835d78610:/build#

Today, I was able to build the kernel/u-boot for the ODroid XU4: ll output/debs/ total 331688 drwxrwxr-x 4 root root 4096 May 17 14:02 ./ drwxrwxr-x 7 root root 4096 May 17 13:24 ../ drwxrwxr-x 2 root root 4096 May 15 13:32 extra/ -rw-r--r-- 1 root root 76886 May 17 14:00 linux-dtb-next-odroidxu4_5.41_armhf.deb -rw-r--r-- 1 root root 10319274 May 17 14:00 linux-headers-next-odroidxu4_5.41_armhf.deb -rw-r--r-- 1 root root 16401116 May 17 14:01 linux-image-next-odroidxu4_5.41_armhf.deb -rw-r--r-- 1 root root 312550324 May 17 14:02 linux-source-next-odroidxu4_5.41_all.deb -rw-r--r-- 1 root root 268070 May 17 13:58 linux-u-boot-next-odroidxu4_5.41_armhf.deb drwxrwxr-x 2 root root 4096 May 17 13:46 stretch/ So I thought that my image was not good at building whole images, juste kernel/u-boot. I then gave a try to the OrangePI One kernel/u-boot building, and it also failed: [ o.k. ] Cleaning [ u-boot/v2017.11 ] grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory [ o.k. ] Compiling u-boot [ 0 ] [ o.k. ] Compiler version [ arm-linux-gnueabihf-gcc 7.2.1 ] [ .... ] Checking out sources error: pathspec 'HEAD' did not match any file(s) known to git. [ o.k. ] Cleaning [ u-boot/v2017.11 ] [ o.k. ] Started patching process for [ u-boot sunxi-orangepizero-next ]

Hi, I made a container based on xenial. ./compile.sh BOARD=orangepizero BRANCH=next KERNEL_ONLY=no RELEASE=stretch [ o.k. ] Using config file [ config-default.conf ] [ o.k. ] This script will try to update remote: Counting objects: 10, done. remote: Compressing objects: 100% (6/6), done. remote: Total 10 (delta 4), reused 6 (delta 4), pack-reused 0 Unpacking objects: 100% (10/10), done. From https://github.com/armbian/build 579e17a..e8906ed development -> origin/development Already up-to-date. Already on 'master' Your branch is up-to-date with 'origin/master'. [ o.k. ] Command line: setting BOARD to [ orangepizero ] [ o.k. ] Command line: setting BRANCH to [ next ] [ o.k. ] Command line: setting KERNEL_ONLY to [ no ] [ o.k. ] Command line: setting RELEASE to [ stretch ] [ o.k. ] Preparing [ host ] [ o.k. ] Build host OS release [ xenial ] [ o.k. ] Running in container [ docker ] mount: permission denied mount: permission denied update-binfmts: warning: Couldn't mount the binfmt_misc filesystem on /proc/sys/fs/binfmt_misc. mount: permission denied update-binfmts: warning: Couldn't mount the binfmt_misc filesystem on /proc/sys/fs/binfmt_misc. [ .... ] Downloading [ gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux ] ################################################# 68.7% I don't know if this information is meaningful: [ o.k. ] Checking git sources [ u-boot v2017.11 ] [ .... ] Remote URL does not match, removing existing local copy [ .... ] Creating local copy [ .... ] Fetching updates fatal: dumb http transport does not support --depth [ .... ] Checking out error: pathspec 'FETCH_HEAD' did not match any file(s) known to git. Because later on, I have [ o.k. ] Cleaning output/debs for [ orangepizero next ] [ o.k. ] Cleaning [ u-boot/v2017.11 ] grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory grep: /build/cache/sources/u-boot/v2017.11/Makefile: No such file or directory [ o.k. ] Compiling u-boot [ 0 ] [ o.k. ] Compiler version [ arm-linux-gnueabihf-gcc 7.2.1 ] [ .... ] Checking out sources error: pathspec 'HEAD' did not match any file(s) known to git. [ o.k. ] Cleaning [ u-boot/v2017.11 ] [ o.k. ] Started patching process for [ u-boot sunxi-orangepizero-next ] [ o.k. ] Looking for user patches in [ userpatches/u-boot/u-boot-sunxi ] [ warn ] * [l][c] 0020-sunxi-call-fdt_fixup_ethernet-again-to-set-macaddr-f.patch [ failed ] [ warn ] * [l][c] 4kfix-limit-screen-to-full-hd.patch [ failed ] [ warn ] * [l][c] Add-A20-Olimex-SOM204-EVB-board.patch [ failed ] [ warn ] * [l][c] add-a20-olinuxino-micro-emmc-support.patch [ failed ] [ warn ] * [l][c] add-a20-optional-eMMC.patch [ failed ] [ warn ] * [l][c] add-bananapi-bpi-m2-zero.patch [ failed ] [ warn ] * [l][c] add-beelink-x2.patch [ failed ] [ warn ] * [l][c] add-nanopi-air-emmc.patch [ failed ] [ warn ] * [l][c] add-nanopi-duo.patch [ failed ] [ warn ] * [l][c] add-nanopi-m1-plus2-emmc.patch [ failed ] [ warn ] * [l][c] add-nanopineoplus2.patch [ failed ] [ warn ] * [l][c] add-orangepi-plus2-emmc.patch [ failed ] [ warn ] * [l][c] add-orangepi-zeroplus.patch [ failed ] [ warn ] * [l][c] add-orangepi-zeroplus2_h3.patch [ failed ] [ warn ] * [l][c] add-sunvell-r69.patch [ failed ] [ warn ] * [l][c] add-tritium.patch [ failed ] [ warn ] * [l][c] add_emmc_olinuxino_a64.patch [ failed ] [ warn ] * [l][c] add_emmc_orangepiwin.patch [ failed ] [ warn ] * [l][c] adjust-default-dram-clockspeeds.patch [ failed ] [ warn ] * [l][c] adjust-small-boards-cpufreq.patch [ failed ] [ warn ] * [l][c] enable-DT-overlays-support.patch [ failed ] [ warn ] * [l][c] enable-autoboot-keyed.patch [ failed ] [ warn ] * [l][c] fdt-setprop-fix-unaligned-access.patch [ failed ] [ warn ] * [l][c] fix-mmc-phase-timings.patch [ failed ] [ warn ] * [l][c] fix-sunxi-gpio-driver.patch [ failed ] [ warn ] * [l][c] fix-usb1-vbus-opiwin.patch [ failed ] [ warn ] * [l][c] h3-Fix-PLL1-setup-to-never-use-dividers.patch [ failed ] [ warn ] * [l][c] h3-enable-power-led.patch [ failed ] [ warn ] * [l][c] h3-set-safe-axi_apb-clock-dividers.patch [ failed ] [ warn ] * [l][c] lower-default-DRAM-freq-A64-H5.patch [ failed ] [ warn ] * [l][c] lower-default-cpufreq-H5.patch [ failed ] [ warn ] * [l][c] sun8i-set-machid.patch [ failed ] [ warn ] * [l][c] video-fix-vsync-polarity-bits.patch [ failed ] [ warn ] * [l][b] workaround-reboot-is-poweroff-olimex-a20.patch [ failed ] make: *** No rule to make target 'orangepi_zero_defconfig'. Stop. sed: can't read .config: No such file or directory make: *** No targets specified and no makefile found. Stop. [ error ] ERROR in function compile_uboot [ compilation.sh:156 ] [ error ] U-boot compilation failed [ o.k. ] Process terminated I have to work behind a corporate proxy, but I managed to clone U-boot. I don't know if these previous errors mean there was a problem with retrieving U-boot source code. root@ac4835d78610:/build# git clone git://git.denx.de/u-boot.git Cloning into 'u-boot'... Checking connectivity... done. root@ac4835d78610:/build# ll u-boot/ total 492 drwxr-xr-x 25 root root 4096 May 15 17:02 ./ drwxr-xr-x 1 root root 4096 May 15 16:54 ../ -rw-r--r-- 1 root root 684 May 15 17:02 .checkpatch.conf drwxr-xr-x 8 root root 4096 May 15 17:02 .git/ -rw-r--r-- 1 root root 880 May 15 17:02 .gitignore -rw-r--r-- 1 root root 1383 May 15 17:02 .mailmap -rw-r--r-- 1 root root 13335 May 15 17:02 .travis.yml drwxr-xr-x 3 root root 4096 May 15 17:02 Documentation/ -rw-r--r-- 1 root root 1863 May 15 17:02 Kbuild -rw-r--r-- 1 root root 16062 May 15 17:02 Kconfig drwxr-xr-x 2 root root 4096 May 15 17:02 Licenses/ -rw-r--r-- 1 root root 14940 May 15 17:02 MAINTAINERS -rw-r--r-- 1 root root 59836 May 15 17:02 Makefile -rw-r--r-- 1 root root 182029 May 15 17:02 README drwxr-xr-x 2 root root 4096 May 15 17:02 api/ drwxr-xr-x 15 root root 4096 May 15 17:02 arch/ drwxr-xr-x 186 root root 4096 May 15 17:02 board/ drwxr-xr-x 6 root root 4096 May 15 17:02 cmd/ drwxr-xr-x 5 root root 4096 May 15 17:02 common/ -rw-r--r-- 1 root root 2256 May 15 17:02 config.mk drwxr-xr-x 2 root root 65536 May 15 17:02 configs/ drwxr-xr-x 2 root root 4096 May 15 17:02 disk/ drwxr-xr-x 10 root root 12288 May 15 17:02 doc/ drwxr-xr-x 53 root root 4096 May 15 17:02 drivers/ drwxr-xr-x 2 root root 4096 May 15 17:02 dts/ drwxr-xr-x 2 root root 4096 May 15 17:02 env/ drwxr-xr-x 4 root root 4096 May 15 17:02 examples/ drwxr-xr-x 13 root root 4096 May 15 17:02 fs/ drwxr-xr-x 28 root root 16384 May 15 17:02 include/ drwxr-xr-x 16 root root 4096 May 15 17:02 lib/ drwxr-xr-x 2 root root 4096 May 15 17:02 net/ drwxr-xr-x 5 root root 4096 May 15 17:02 post/ drwxr-xr-x 6 root root 4096 May 15 17:02 scripts/ -rw-r--r-- 1 root root 17 May 15 17:02 snapshot.commit drwxr-xr-x 11 root root 4096 May 15 17:02 test/ drwxr-xr-x 14 root root 4096 May 15 17:02 tools/