cmcgaha

Thank you! I downloaded the new image and it worked. I still saw weird characters (is that ascii art?) on the dialog before starting the copy. But it worked. I really appreciate your help!

I am having problems with the NanoPi R1. I loaded the latest Armbian for R1 on flash. All works good. I went to armbian-config to load into eMMC. The last step of the process had weird text on the dialog, I clicked "OK" anyway, and the process seemed to be working. But after removing uSD card and rebooting, the board does not work. The red led stays on solid. Did anyone successfully burn the image from uSD to eMMC using the tool in armbian-config?

The last K1 image I built on Aug 15 was: Armbian_5.59_Nanopik1plus_Debian_stretch_next_4.17.14_desktop.img So far everything I am using is working fine. Let me know if there is something I can test that will help you.

Hi Igor. Yes. That builds now. At least for K1. I will try on other boards tonight. I compiled, burned to uSD and booted on board. Basic stuff seems to work so far. Thanks

same error. I did: rm -fr cache/rootfs ./compile.sh CLEAN_LEVEL=make,images,alldebs,cache,sources,extras BRANCH=next and got the same error Thanks

I tried compiling Debian 9 Full OS Image with Desktop using BRANCH=next and default kernel configs for * NanoPi K1 * Rock64 * OrangePi Plus 2E And all failed at the end: Errors were encountered while processing /tmp/apt-dpkg-install-LTKPXl/621-numix-icon-theme_0.3+922~201711061547~ubuntu16.04.1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [ error ] ERROR in function create_rootfs_cache [ debootstrap-ng.sh:213 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:59 ] [ error ] debootstrap-ng was interrupted I am using the 18.04 minimal image in a virtual box. It worked a month ago. It works today for Ubuntu Full OS image with Desktop and BRANCH=next. Thanks.

Thank you! I tried to follow the directions, it was just not the right directions. I created a Ubuntu 18.04 VirtualBox like you said, changed LIB_TAG to sunxi-4.18 and built and ran mainline 4.17 and touch screen, wifi, GPIO are working. I will test more. So far all is good. I really appreciate everyone's help.

No, that did not work. When I edit config-default.conf and change LIB_TAG="master" to LIB_TAG="sunxi-4.18" and then re-run ./compile.sh EXTERNAL=yes then I get an error message about error: pathspec 'sunxi-4.18' did not match any file(s) known to git do I need to do a different git clone or the standard one?

Hi Igor, The 4.17 Nightly Test version for NanoPi K1 Plus you built for me has WiFi and I got the GUI working with extraargs you suggested, but I could not get multi-touch display to work. The hid-multitouch driver did not load / wasn't detected... I created a VirtualBox using the Ubuntu 16.04 virtual machine and checked out and did ./compile.sh EXPERT=yes to build the latest version 4.17 like you did, but the build failed. See attached screen shot. I built mainline 4.14 Stretch version in the virtual machine and it loaded and display worked. Multi-touch worked. But WiFi driver didn't work... So I am trying to fine a working WiFi and Mutli-Touch display OS version. Please let me know if there were special build parameters you used to get it to work. Thank you.

No. Sorry, I must not have been clear. GPIO works fine on Armbian. There is only an issue with board detection using WiringNP because of difference in /proc/cpuinfo. Thanks for the boot explaination. I really appreciate your help.

Hi Igor, I had done the GPIO test with WiringNP with their nanopi-k1-plus_eflasher_4.14.0_20180511.img. Their WiringNP GPIO library worked on that. I hacked on the WiringNP to use same "board version" (a NanoPi thing) as their OS uses and the GPIO works fine on the K1 armbian nightly test version you made, at least the GPIO stuff for what I am doing. I see on the K1Plus page that the 1080P is marked as fixed. Can you make a new nightly build with this fix or is it checked in and I should make it. Thanks.

Hi Igor, While you are in there, can you please look at the /proc/cpuinfo. If I use the OS from NanoPi for K1 I get a different CPU id. I am able to use WiringNP with the NanoPi OS, but not the Armbian OS. I need to try to hack the WiringPi to make sure only CPU ID and Revision are the problem, but rest of GPIO library works. The NanoPi OS reports as one Hardware and Revision field: Hardware: Allwinnersun50iw2Family Revision: 0 Armbian K1 reports as multiple Hardware and no Revision field: Hardware: sun50iw1p1 and Revision line is missing Since the format of /proc/cpuinfo seems very differnt, not sure who is "right" Thank you. --------------- complete /proc/cpuinfo from NanoPI OS: processor : 0 BogoMIPS : 48.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4 processor : 1 BogoMIPS : 48.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4 processor : 2 BogoMIPS : 48.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4 processor : 3 BogoMIPS : 48.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4 Hardware : Allwinnersun50iw2Family Revision : 0000 Serial : 0000000000000000

Thank you

Hi Viy, Thanks for the suggestion, but that didn't work, or I did something wrong. Below are my steps. I appreciate your help. 1) Burn Armbian_5.46.180622_Nanopik1plus_Debian_stretch_dev_4.17.2_desktop.img to uSD card 2) Power on K1 3) Login as root, create new user 4) command line shows: "Now starting desktop environment..." 5) screen blinks 5 times 6) still at command line 7) connect to wifi (internet) 8) armbian-config 9) System -> Firmware -> Update board firmware <OK> ... Firmware Updated <Reboot> 10) Reboots to command line. Login as root 11) armbian-config -> Software -> Full 12) Esc 13) System -> Desktop -> Enable -> Lightdm 14) Software installs. Screen goes blank

I downloaded the nightly build Igor made on 06/22 and can not get desktop to work. Did like Viy said: 1) Burn to uSD 2) Boot uSD 3) armbian-config to install to eMMC 4) reboot (booting from eMMC) 5) armbian-config to enable desktop 6) Nothing I tried both lightDM and nodm. Neither worked. LightDM causes screen to go to black with no return. nodm causes screen to flash a few times and return to command prompt. I tried on a 1920X1080 FHD HDMI display. I tried on a 1600X1200 HDMI -> VGA display same results: not working. I know the display works. I can use a Rock64, OrangePi Plus 2E, Raspberry Pi, all can use display via HDMI cable. If I run startx at command line I get: MESA-LOADER: failed to load device (see full log below) X.Org X Server 1.19.2 Release Date: 2017-03-02 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.9.0-4-arm64 aarch64 Debian Current Operating System: Linux nanopik1plus 4.17.2-sunxi64 #21 SMP Thu Jun 21 14:39:44 UTC 2018 aarch64 Kernel command line: root=UUID=467fb03c-c302-4b62-8891-84ef761afc8f rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 panic=10 consoleblank=0 loglevel=1 ubootpart= usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=memory swapaccount=1 Build Date: 16 October 2017 08:11:43AM xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support) Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/home/nmi/.local/share/xorg/Xorg.0.log", Time: Thu Jun 21 18:27:23 2018 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" MESA-LOADER: failed to retrieve device information gbm: failed to open any driver (search paths /usr/lib/aarch64-linux-gnu/dri:${ORIGIN}/dri:/usr/lib/dri) gbm: Last dlopen error: /usr/lib/dri/sun4i-drm_dri.so: cannot open shared object file: No such file or directory failed to load driver: sun4i-drm EGL_MESA_drm_image required. (EE) Fatal server error: (EE) AddScreen/ScreenInit failed for driver 0 (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/home/nmi/.local/share/xorg/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error