Search the Community

Showing results for tags 'mainline'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 820 results

  1. I just got a Nanopi NEO2 512MB, installed Armbian Ubuntu Bionic. It works fine, except for the DVB-T/C stick. It is affected by Kernel 4.10+ problems. I wonder if I can downgrade to an older kernel, like 4.4.0 for example, where everything works perfectly? If yes, how? There is a patch that perhaps would resolve the problem, how could I apply this patch to an of the available releases of Armbian? This patch Please, help me with this. Many thanks!
  2. I will describe my problem with NanoPi Neo Core2: I installed the system on eMMc I installed WiringNP I installed the USB drive Everything worked, also Putty via USB I wanted to connect the external module via SPI. The module requires setting the transfer frequency to 20 MHz. I decided to look at the file sun50i-h5-nanopi-neo-core2.dtb . For this purpose, I decompiled to a file . dts . Due to late night time I made a cardinal error, that is before these activities I did not copy the file . dtb I just played on the operating system. After the power is turned off NanoPi and the next day the system is not raised. Red power LED is lit green while not depicted close. Router does not see NanoPi and was obviously seen. Replacing the power supply did not help. I recorded the system card ( DietPi , Armbian , FriendlyElec ) . After inserting into NanoPi the system also did not start. I tried different combinations: start with ethernet and without, with putty (serial), with different SD cards and nothing. I read on the forum that NanoPi with the H3 processor always tests the presence of an SD card in the first place and if it is in the bootable version it starts the system from it. Probably NanoPi Neo Core2 with H5 processor this rule does not apply. Please help me solve the problem of SETTING UP BOOT FROM SD CARD !
  3. I'm trying to get TFTP support into U-Boot but it insists that 'no ethernet found'. I've added a couple of nodes to the device tree such that it has 'status = "okay" and mac-address = [00 00 00 00 00 00]; I've also added a top level alias in sun50i-h5-nanopi-k1-plus.dts (as added by @martinayotte following this thread) as below. Not sure if the U-Boot config needs changing in any way but the network components are certainly being built. Any thoughts most welcome. AATIA. aliases { serial0 = &uart0; ethernet0 = &emac; }; U-Boot dump of the loaded DTB on running system follows: => bdinfo arch_number = 0x00000000 boot_params = 0x40000100 DRAM bank = 0x00000000 -> start = 0x40000000 -> size = 0x80000000 baudrate = 115200 bps TLB addr = 0xBFFF0000 relocaddr = 0xBDF4B000 reloc off = 0x73F4B000 irq_sp = 0xB9F27590 sp start = 0xB9F27590 Early malloc usage: 2d8 / 400 fdt_blob = 00000000b9f275a8 => fdt addr 00000000b9f275a8 => fdt print ethernet0 ethernet@1c30000 { compatible = "allwinner,sun8i-h3-emac"; syscon = <0x0000000e>; reg = <0x01c30000 0x00010000>; interrupts = <0x00000000 0x00000052 0x00000004>; interrupt-names = "macirq"; resets = <0x00000005 0x0000000c>; reset-names = "stmmaceth"; clocks = <0x00000005 0x0000001b>; clock-names = "stmmaceth"; #address-cells = <0x00000001>; #size-cells = <0x00000000>; status = "okay"; mac-address = [00 00 00 00 00 00]; mdio { #address-cells = <0x00000001>; #size-cells = <0x00000000>; compatible = "snps,dwmac-mdio"; phandle = <0x0000000f>; }; mdio-mux { compatible = "allwinner,sun8i-h3-mdio-mux"; #address-cells = <0x00000001>; #size-cells = <0x00000000>; mdio-parent-bus = <0x0000000f>; mdio@1 { compatible = "allwinner,sun8i-h3-mdio-internal"; reg = <0x00000001>; #address-cells = <0x00000001>; #size-cells = <0x00000000>; ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0x00000001>; clocks = <0x00000005 0x00000043>; resets = <0x00000005 0x00000027>; }; }; mdio@2 { reg = <0x00000002>; #address-cells = <0x00000001>; #size-cells = <0x00000000>; }; }; };
  4. Has anyone had success getting the Marvell 88W8897 setup as a hotspot? It seems to work fine as a Supplicant, but I'm having challenges getting it to work as a hotspot. I've been trying to get the card to work as a hotspot via armbian-config without success. Does anyone have any suggestions?
  5. Hi! I was using armbian 5.60 with 4.14.70 kernel and WiFi AP worked flawsessly. Today I had to rebuild my sd card, so I downloaded the latest available build Armbian Stretch mainline kernel 4.19.y I can connect to WiFi from the board, also able to setup a WiFi AP on the board. But when I try to connect to the new AP I see the following message in terminal and the connecting device fails after several seconds: Message from syslogd@localhost at Jan 17 18:20:38 ... kernel:[ 349.842020] Internal error: Oops: 96000004 [#1] SMP Message from syslogd@localhost at Jan 17 18:20:38 ... kernel:[ 350.021242] Process RTW_CMD_THREAD (pid: 607, stack limit = 0x0000000068aba9f4) Message from syslogd@localhost at Jan 17 18:20:38 ... kernel:[ 350.069577] Code: f9405ae0 a90a0ba0 11000421 8b02001b (b8626800)
  6. I'm running some stress test on the NanoPi neo2 512mb, CPU heating reached 75-76 degrees, and it's stable, the problem that I faced is that the computer changed it's IP suddenly (after 55 minutes of test running), I guess it's because of a network card reset. Did anyone face the following issue? Is it related to the stress test? Or it's another networking problem? The test I'm running is with the "stress" tool, running long time stress on 4 CPUs. In addition, does anyone have any insights regarding this device? good or bad?
  7. Hello guys, at first I want to says thanks for the great OS that you deliver. I use it since 8 months on a bunch of nano-pi neo2's and it runs rock solid. However i rebuild from time to time the image I use from scratch in order to see that the installation is reproducable and repeatable. Today it has encountered that the installation of 'apt-get install python:armhf python-dev:armhf' failed with: # dpkg --add-architecture armhf # sudo apt-get update .... Reading package lists... Done # sudo apt-get install -y python-pip python:armhf python-dev:armhf Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python-dev:armhf : Depends: libpython-dev:armhf (= 2.7.12-1~16.04) but it is not going to be installed Depends: python2.7-dev:armhf (>= 2.7.12-1~) but it is not going to be installed E: Unable to correct problems, you have held broken packages. I use armbian_5.38_Nanopineo2_Ubuntu_xenial_next_4.14.14.img. The reason I do this, is that I want to use Segger Debugger on the platform, but Segger only provides armhf-libs (used by Pylink-square). Asking Segger to release arm64 libraries already failed. Thanks in advance, Axel.
  8. We have deployed the zero for an integrated MCU on one of our products, and in rare occasions we are experience random lockups of the MCU (possibly related to overheating). Its pretty much impossible to debug this since it happens very rarely, but we are trying to mitigate all possible causes. The MCU is controlling a bigger and more expensive board and a fan. If there are internal failsafes that are being triggered by the MCU and locking it up (like temp) we want to disable as many of them as possible (we would rather have the MCU burn up than our main board). Anyone have any insights on orange pi zero OTP or OCP in kernel or uboot parameters we can disable?
  9. hello after updating from cat /proc/version Linux version 4.14.84-sunxi ( (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #3 SMP Sat Dec 1 07:18:41 CET 2018 to Linux version 4.19.13-sunxi ( (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #5.70 SMP Sat Jan 12 15:43:21 CET 2019 my one wire thermometer stopped working - is there some additional steps needed now? I didn't change my configuration overlays=w1-gpio param_w1_pin=PB10 param_w1_pin_int_pullup=0  and now I have dmesg [ 1174.451457] w1_master_driver w1_bus_master1: Attaching one wire slave 00.e80000000000 crc 2b [ 1174.456242] w1_master_driver w1_bus_master1: Family 0 for 00.e80000000000.2b is not registered. [ 1234.023523] w1_master_driver w1_bus_master1: Attaching one wire slave 00.180000000000 crc 5f [ 1234.029428] w1_master_driver w1_bus_master1: Family 0 for 00.180000000000.5f is not registered. ... ls /sys/bus/w1/devices 00-180000000000 00-580000000000 00-980000000000 w1_bus_master1 (00-... directories names and count changes after every minute) cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-40 ( |ahci-5v ) out hi gpio-224 ( |cd ) in lo IRQ gpio-225 ( |cd ) in lo IRQ gpio-227 ( |usb2-vbus ) out hi gpio-228 ( |usb0_id_det ) in hi IRQ gpio-230 ( |usb1-vbus ) out hi gpio-244 ( |cubieboard2:green:us) out lo gpio-245 ( |cubieboard2:blue:usr) out lo gpio-271 ( |onewire@0 ) in lo gpiochip1: GPIOs 413-415, parent: platform/axp20x-gpio, axp20x-gpio, can sleep: there is no "gpio-42" line, old was cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-40 ( |ahci-5v ) out hi gpio-42 ( |w1 ) in hi gpio-224 ( |cd ) in lo IRQ gpio-225 ( |cd ) in lo IRQ gpio-227 ( |usb2-vbus ) out hi gpio-228 ( |usb0_id_det ) in hi IRQ gpio-230 ( |usb1-vbus ) out hi gpio-244 ( |cubieboard2:green:us) out lo gpio-245 ( |cubieboard2:blue:usr) out lo gpiochip1: GPIOs 413-415, parent: platform/axp20x-gpio, axp20x-gpio, can sleep:
  10. Good day! Tell me if there is support for hardware acceleration Orange PI WIN PLUS Cortex-A64 ?? I try to run a video (vlc,mpv) but it is very slow =(
  11. hi orangepi 2e+ with ARMBIAN 5.65 stable Ubuntu 18.04.1 LTS 4.14.84-sunxi syslog I want to mount my external hard disks with cat /etc/udev/rules.d/91-intenso.rules KERNEL=="sd?1", SUBSYSTEMS=="usb", ATTRS{serial}=="31700000000000007023", SYMLINK+="Intenso", ACTION=="add", RUN+="/bin/mount /dev/Intenso /mnt/Intenso" Normally no problem, tested with Armbian_5.65_Orangepiplus2e_Ubuntu_xenial_default_3.4.113 and Workstation PC Linux 4.15.0-43-generic #46~16.04.1-Ubuntu. With my current version, I have a problem. The udev-rule is/seem ok LINK 'Intenso' /etc/udev/rules.d/91-intenso.rules:1 RUN '/bin/mount /dev/Intenso /mnt/Intenso' /etc/udev/rules.d/91-intenso.rules:1 But orangepi@orangepiplus2e:~$ ls /mnt/Intenso/ orangepi@orangepiplus2e:~$ But If I mount manually orangepi@orangepiplus2e:~$ sudo mount /dev/Intenso /mnt/Intenso/ orangepi@orangepiplus2e:~$ ls /mnt/Intenso/ Filme FRITZ lost+found Musik recup_dir.86 Serien Where is my fault ? Bye nepo
  12. Hi, I am new to Orange Pi ecosystem. I have a Orange Pi PC 2 running armbian and some times raspbian. I want to use a wifi adapter to this. Since there has been many discussions on which adapter to chose and how to chose I am really confused. Please help me select a wifi adapter which could be installed easily considering that I am a rookie.
  13. Greetings to all, Preamble: Thanks to all that have worked to make the Armbian project what it is today. It is greatly appreciated! I have done numerous hours of reading and searching (due diligence). I know I could run a benchmarks and all but that means even more delay reaching the objective. Some brief guidance from those who have gone before would save a lot of time and would be greatly appreciated. Looking at the datasheets wasn't real helpful in guesstimating optimum performance configuration - especially since there are so many other factors that have an impact. Background: My objective is to achieve a reliable, long life system and avoid big performance hits along the way. The host is for home automation so the most of the storage activity will be logging and playing back canned sounds and serving up web pages consistent with HMI functions by my estimation. Other activity will be from Node-Red, MQTT broker, The automation web server, etc. I also maintain a NAS in the house so logs backups and databases associated with the HA system will be copied or backed up there. I have done so much reading and a fair bit of testing that I am a bit unsure as I write if Armbian supports logging to ramdisk or some such. If so, this would also be part of the picture for me. I would either sense the UPS power state or come up with a supercap or other power storage scheme and sense power loss and push ramdisk to NV storage... This is a little off topic but is relevant to the extent that I don't want to loose data that has been collected and the safest place for it is not in ram but in flash. I am guessing that for this context with a limited number (15?) of devices connected to via browser such as tablets, phones, and PCs alongside a few dozen other devices that are I/O nodes, not a lot of disk I/O will be needed. Room for growth is important (I hope) as well as avoiding performance degradation as a consequence of it. It is troublesome to have to deal with 'users' noticing slowdowns! Though of course I wouldn't consider hobbling the system now and loosening the reins later to deal with extra load... As I see it, if I use eMMC at all, I need to be using some kind of wear leveling (f2fs), minimize writes to it, and don’t fill it too full. A better option if performance will allow is to use sda1 instead for the root file system. I assume the M.2 device will have wear leveling and other features which along with much larger capacity (largely empty) in concert with brtfs file system is the best I can do to get performance and reliable operation over the M.2 /USB interface. Since M.2 is replaceable it is reasonable to expect that the system will not become permanently unusable due to flash wear failures in the near and mid term - I can simply restore to new M.2 device if it fails. Long term fiscal and technology issues are another matter. Question 1: Which would yield a more responsive system? The os residing on the eMMC or M.2? I see that the eMMC is using an 8 bit parallel interface (data and address must be using same path) vs the M.2 slot which is connected via a JMS567-LGBB1A chip. I read here that it at least has the potential to be a good performer. The context there was USB3 which is not used on the FA shield. The shield uses USB2 so there is still some question about how it will perform (there are other factors as well of course). Question 2: If I end up using eMMC for root, and assuming logs are being written to m.2, what recommendations to monitor and make sure writes to eMMC are minimized? I would probably want to do some monitoring anyway later on for lots of reasons. Pointers on how to set up brtfs (f2fs as well actually) for root to maintain speed and health in this context would also be appreciated. Regards and thanks again to all that have and will contribute, Q
  14. Hi i have a problem trying to load the drivers of this camera, could you help me? Issue: mobprobe: FATAL: Module ov5647 not found in directory /lib/modules/4.14.84-sunix Board: Orange Pi Lite Camera sensor: OV5647 fisheye OS: Ubuntu - Armbian 5.65
  15. I started first with orangepi pc2 (H5) but now trying the same thing on orangepi one (h3) - trying to make ili9340 module work it works flawlesly on rpi with raspbian so the hw module works (and the fb_ili9340 module in kernel talks to it properly) debug info I pulled from rpi pi@octopi:~ $ uname -a Linux octopi 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux root@octopi:~# lsmod Module Size Used by xt_tcpudp 16384 1 iptable_mangle 16384 1 xt_DSCP 16384 1 bnep 20480 2 hci_uart 36864 1 btbcm 16384 1 hci_uart serdev 20480 1 hci_uart bluetooth 368640 24 hci_uart,bnep,btbcm ecdh_generic 28672 1 bluetooth fb_ili9340 16384 0 fbtft 45056 1 fb_ili9340 syscopyarea 16384 1 fbtft sysfillrect 16384 1 fbtft sysimgblt 16384 1 fbtft fb_sys_fops 16384 1 fbtft stmpe_ts 16384 0 joydev 20480 0 evdev 24576 4 brcmfmac 307200 0 brcmutil 16384 1 brcmfmac cfg80211 573440 1 brcmfmac rfkill 28672 6 bluetooth,cfg80211 snd_bcm2835 32768 0 gpio_backlight 16384 0 i2c_bcm2835 16384 0 snd_soc_bcm2835_i2s 16384 0 snd_soc_core 188416 1 snd_soc_bcm2835_i2s snd_compress 20480 1 snd_soc_core snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 98304 4 snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_bcm2835,snd_soc_core spi_bcm2835 16384 0 snd_timer 32768 1 snd_pcm snd 69632 5 snd_compress,snd_timer,snd_bcm2835,snd_soc_core,snd_pcm uio_pdrv_genirq 16384 0 fixed 16384 0 uio 20480 1 uio_pdrv_genirq ip_tables 24576 1 iptable_mangle x_tables 32768 4 iptable_mangle,ip_tables,xt_tcpudp,xt_DSCP ipv6 425984 45 root@octopi:~# root@octopi:/dev/input# ls -la total 0 drwxr-xr-x 4 root root 220 Jan 3 02:59 . drwxr-xr-x 15 root root 3420 Jan 3 02:59 .. drwxr-xr-x 2 root root 120 Jan 3 02:59 by-id drwxr-xr-x 2 root root 140 Jan 3 02:59 by-path crw-rw---- 1 root input 13, 64 Jan 3 02:59 event0 crw-rw---- 1 root input 13, 65 Jan 3 02:59 event1 crw-rw---- 1 root input 13, 66 Jan 3 02:59 event2 crw-rw---- 1 root input 13, 67 Jan 3 02:59 event3 crw-rw---- 1 root input 13, 63 Jan 3 02:59 mice crw-rw---- 1 root input 13, 32 Jan 3 02:59 mouse0 crw-rw---- 1 root input 13, 33 Jan 3 02:59 mouse1 root@octopi:/dev/input# root@octopi:/dev/input# udevadm info -q all /dev/input/event3 P: /devices/platform/soc/3f204000.spi/spi_master/spi0/spi0.1/stmpe-ts/input/input3/event3 N: input/event3 S: input/by-path/platform-3f204000.spi-platform-stmpe-ts-event E: DEVLINKS=/dev/input/by-path/platform-3f204000.spi-platform-stmpe-ts-event E: DEVNAME=/dev/input/event3 E: DEVPATH=/devices/platform/soc/3f204000.spi/spi_master/spi0/spi0.1/stmpe-ts/input/input3/event3 E: ID_INPUT=1 E: ID_INPUT_TOUCHSCREEN=1 E: ID_PATH=platform-3f204000.spi-platform-stmpe-ts E: ID_PATH_TAG=platform-3f204000_spi-platform-stmpe-ts E: MAJOR=13 E: MINOR=67 E: SUBSYSTEM=input E: USEC_INITIALIZED=5285899 on the armbian, no matter what I do I can't get the fb_ili9340 to create /dev/fb1 the module loads ok and displays no errors but no /dev/fb1 dmesg shows ... [ 139.389950] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 139.395122] fb_ili9340: module is from the staging directory, the quality is unknown, you have been warned. root@orangepione:~# I see fb0 (hdmi monitor) and spidev0.0 devices root@orangepione:~# ls -la /dev/fb* /dev/spi* crw-rw---- 1 root video 29, 0 Jan 5 23:28 /dev/fb0 crw------- 1 root root 153, 0 Jan 5 23:28 /dev/spidev0.0 root@orangepione:~# I modified armbianEnv root@orangepione:/boot# cat armbianEnv.txt verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=e753a023-12c8-405e-b8f7-6b4e3ae873d0 rootfstype=ext4 overlays=spi-spidev spi-add-cs1 param_spidev_spi_bus=0 param_spidev_max_freq=32000000 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@orangepione:/boot# tried without spi-add-cs1 too, without max_freq... it's based on stretch and mainline ... I can try old kernel too if that makes sense.. ___ ____ _ ___ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) / _ \ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | | | | '_ \ / _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | | |_| | | | | __/ \___/|_| \__,_|_| |_|\__, |\___| |_| |_| \___/|_| |_|\___| |___/ Welcome to ARMBIAN 5.46 user-built Debian GNU/Linux 9 (stretch) 4.14.48-sunxi System load: 1.47 1.15 0.51 Up time: 3 min Memory usage: 15 % of 493MB IP: CPU temp: 60°C Usage of /: 30% of 3.4G root@orangepione:/boot# uname -a Linux orangepione 4.14.48-sunxi #2 SMP Wed Jun 6 01:50:17 CEST 2018 armv7l GNU/Linux
  16. Armbian Legacy 5.56 Kernel 3.10 boots and installs to the eMMC (as long as ext2fs is picked). Armbian Dev 5.56 Kernel 4.19 does not boot from the SD Card at all (power LED and black screen). I don't have the serial console adapter (yet) so I don't know if there is something useful there.
  17. Hello, No bluetooth device in my Armbian... Banana Pi M2+ ARMBIAN 5.65 stable Ubuntu 18.04.1 LTS 4.14.84-sunxi dpkg-query -Wf '${Version}\n' bluez 5.48-0ubuntu3.1 No Bluetooth device(hci0): rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Which refers to the error: systemctl status ap6212-bluetooth.service ● ap6212-bluetooth.service - LSB: Patch firmware for ap6212 adapter Loaded: loaded (/etc/init.d/ap6212-bluetooth; generated) Active: failed (Result: exit-code) since Tue 2019-01-08 09:18:38 UTC; 1min 2s ago Docs: man:systemd-sysv-generator(8) Process: 2553 ExecStart=/etc/init.d/ap6212-bluetooth start (code=exited, status=1/FAILURE) Jan 08 09:18:28 bananapim2plus systemd[1]: Starting LSB: Patch firmware for ap6212 adapter... Jan 08 09:18:38 bananapim2plus ap6212-bluetooth[2553]: Initialization timed out. Jan 08 09:18:38 bananapim2plus ap6212-bluetooth[2553]: bcm43xx_init Jan 08 09:18:38 bananapim2plus ap6212-bluetooth[2553]: Can't get device info: No such device Jan 08 09:18:38 bananapim2plus systemd[1]: ap6212-bluetooth.service: Control process exited, code=exite Jan 08 09:18:38 bananapim2plus systemd[1]: ap6212-bluetooth.service: Failed with result 'exit-code'. Jan 08 09:18:38 bananapim2plus systemd[1]: Failed to start LSB: Patch firmware for ap6212 adapter. In the scrip this command failed: hciattach /dev/ttyS1 bcm43xx 115200 flow bdaddr 43:29:B1:55:01:01 bcm43xx_init Initialization timed out. Can you help me? Thanks, gemesif
  18. I have 1 "Customised Olimex Lime A20 SBC with RTL-SDR chip installed in the board (AirNav XRANGE). Currently the OS I'm using is the Lime A20 Armbian Stretch 4.14.84, everything is works fine except for the 2 GPIO LED. I have no idea how to let it work. I have the edited "sun7i-a20-olinuxino-lime.dtb" from Armbian Jessie 4.11.5 which is mainly for the board. May I know is there a way to incorporated the "Armbian Jessie 4.11.5's sun7i-a20-olinuxino-lime.dtb into the A20 Armbian Stretch 4.14.84 so that the 2 LEDs will work again? The edited dtc for LEDs to work "sun7i-a20-olinuxino-lime.dtb" attached. Hope to get some experts to assist me on this matter. Thanks in advance. Regards, SaiHou sun7i-a20-olinuxino-lime.dtb 4.14.84 - sun7i-a20-olinuxino-lime.dtb
  19. Greetings all, See my last post in thread for method I found to get around issues. EDIT: This may be limited to is an apt issue DNS seems ok after all. Use nmtui to edit network config not armbian-config None of what follows should be taken as complaining. I am only trying to get some help, give some observations from a non-expert viewpoint and possibly help ID a bug. Not being an expert, I am looking for confirmation. I am trying to get the NanoPi NEO core-2 LTS set up and am having some issues with apt. I haven't gone past that because the first thing after getting properly booting install (for me anyway) is to install webmin. This makes it relatively easier for me to have visibility into the system, edit config files etc. etc. My /etc/apt/sources.list seems to be correct but when I do apt install webmin I get "no candidate". on another system running Linux 4.14.0 on aarch64 (also a FA NanoPi NEO2 (+) variant, the webmin package is there. apt clean, apt update, apt --fix-broken install have all been done. I changed to GB sources in armbian config utility but that domain wasn't responding. The other system is using dietpi, is on the same network, uses an identical sources.list (for all intents) and works fine. This is what lead me eventually to look at DNS and network as possible causes. Using armbian-config, I set my system up with static IP and if I found a place to enter dns I use and (I don't use domain names inside my network) . I couldn't find a place to do that. If I ping from command line on NEO, it works. If I ping I get a response. if I ping I don't (more later).EDIT: This was a bad ping target. I wasn't watching closely enough to see that dns resolved the IP and that the IP is what gets pinged directly. I learned something today! I tried editing nano /etc/NetworkManager/NetworkManager.conf and replacing dns=default with dns=none and then putting entry for in my resolve.conf. to no avail. domain names are working for the rest of my network so I am inclined to think something is wrong with this particular system. I do not use IPv6 so I opted to turn that off in armbian-config (I don't understand why apt and IPv6 are associated). Again, IPv4 static IP, correct gateway IP, correct mask, and I could find no option to enter DNS servers. Wifi is not in use Wired does work at least a little (I can ping google). But beyond that I am not confident in the state of the network configuration. When selecting clear network interfaces I did see DNS masquerading option not loaded error. It is not clear to me if that is important. I also went to "advanced|edit /etc/network/interfaces and the file shown has no entry for eth0 but does have an comment "#Network is managed by Network manager" along with the local loopback entries. There seems to be an issue with the armbian-config menu system (at least in my mind) in that when selecting an action, the only route back from any action is to cancel. This is not optimal - or I am missing something here? For some menu items the current status of the item is displayed as part of the menu (enabled vs disabled) for others, it is not and when you select the menu item (select static vs dynamic) the screen refreshes to show enable and disable options but does not indicate the current state. Cancel does what in that case? Also, I tried reverting to dhcp and leaving IPv6 disabled as indicated in config menu. After reboot IPv6 address is present in Ifconfig (below)! Still disabled in Armbian-config. Toggling IPv6 does remove IPv6 address from ifconfig but only 'till reboot. Disable does not survive reboot. Regardless of presence of IPv6 address, I am unable to ping but can ping Again, both visible from other devices on my network. not working eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet netmask broadcast inet6 fe80::XXXX:YYYY:1cc:1220 prefixlen 64 scopeid 0x20<link> # I mangled address ether MAC REMOVED txqueuelen 1000 (Ethernet) RX packets 1729 bytes 185731 (181.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 169 bytes 14605 (14.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 24 Working Nano eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet netmask broadcast ether MAC REMOVED txqueuelen 1000 (Ethernet) RX packets 4295815 bytes 468858671 (447.1 MiB) RX errors 0 dropped 2467577 overruns 0 frame 0 TX packets 38465 bytes 22491765 (21.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 28 Seems like there are two separate but closely related issues here. Control over IPv6 and DNS. With a third less critical being ambiguous configuration menu functions and display. Thanks for taking the time to read this far. Hope you can help. Q
  20. I'm running an updated armbian stretch mainline on a nanopi neo and hitting a wall where I thought there would be no obstacles in my path. I'm using 433Mhx Tx and Rx devices so I'm building WiringNP (from FriendlyArm) and rfoutlet (from I'm getting errors such as wiringPi ISR: Not implemented when running RFSniffer. [This is the current error, it's been one after another]. My mind is muddled at the moment since I've done this kind of thing several times in the past on other devices including the Orange Pi Zero. Can someone tell me if this is me, or if it's a NanoPi Neo-thing? Shouldn't this be straight-forward? cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=nanopineo BOARD_NAME="NanoPi Neo" BOARDFAMILY=sun8i VERSION=5.65 LINUXFAMILY=sunxi BRANCH=next ARCH=arm IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.5 (stretch) Release: 9.5 Codename: stretch
  21. Working from the documentation here: Not much luck so far with an FA NanoPi K1 Plus. Please see below for details. TIA.
  22. Dear experts, I would like to make my OrangePi PC on board LEDs works like power (Green: Default ON) and status (Red:heartbeat blinking). root@orangepipc:~# ls -1 /sys/class/leds/ orangepi:green:pwr orangepi:red:status root@orangepipc:~# Any experts can assist me on this matter on edit in /etc/rc.local to get it works. Thanks in advance and appreciated your help. Regards, Sai Hou
  23. Preamble: I have done numerous hours of reading and searching (due diligence). See end. I have a FA NanoPi NEO Core-2 LTS with shield and 64G M.2 (This shield uses JMS567-LGBB1A chip USB to sata for M.2 access). I have successfully installed Armbian from SD to and booted from the eMMC. Armbian Stretch mainline kernel 4.14.y - This image armbianmonitor -u results Logs indicate formatting did occur correctly as far as I can tell. The volumes are formatted as I selected - along with an 'extra' ext4 volume that looks like it is just for boot. NOTE: Since I could not boot, I re-tried using default ext4 for both which works. System now boots Armbian without TF. ATM OS resides on sda1. Console output: INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State ON INFO: AffInst: Level 0, MPID 0x2, State ON INFO: AffInst: Level 0, MPID 0x3, State ON U-Boot SPL 2018.05-armbian (Oct 27 2018 - 08:32:18 +0200) DRAM: 1024 MiB Trying to boot from MMC2 NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):c9f55c0 NOTICE: BL3-1: Built : 08:32:12, Oct 27 2018 NOTICE: DT: sun50i-h5-nanopi-neo-core2 NOTICE: SCPI: dummy stub handler, implementation level: 000000 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 U-Boot 2018.05-armbian (Oct 27 2018 - 08:32:18 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO Core 2 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: No ethernet found. 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 scanning bus 0 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 3090 bytes read in 4 ms (753.9 KiB/s) ## Executing script at 4fc00000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 208 bytes read in 2 ms (101.6 KiB/s) MMC: no card present ** Bad device mmc 0 ** 30102 bytes read in 11 ms (2.6 MiB/s) 504 bytes read in 17 ms (28.3 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo 504 bytes read in 14 ms (35.2 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo 4179 bytes read in 13 ms (313.5 KiB/s) Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 44000000 4923549 bytes read in 247 ms (19 MiB/s) 13148168 bytes read in 649 ms (19.3 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 4923485 Bytes = 4.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49b4d000, end 49fff05d ... OK reserving fdt memory region: addr=4fa00000 size=6d000 Loading Device Tree to 0000000049add000, end 0000000049b4cfff ... 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: Will now check root file system ... fsck from util-linux 2.29.2 done. mount: Invalid argument done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... mount: No such file or directory mount: invalid option -- done. mount: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 No init found. Try passing init= bootarg. Rebooting automatically due to panic= boot argument To elaborate on the process, after writing TF card and booting, I ran armbian-config selecting option "eMMC boot | USB/SATA/NVMe root install" and selected format of btrfs for sda1. Also, "Select filesystem type for eMMC /dev/mmcblk2" ... "Formating /dev/mmcblk2 to f2fs ... please wait". The utility responded with the appropriate warnings (about erasing/formatting) and appeared to execute correctly, returning no errors and prompting for reboot at end of process. I shutdown, removed card, powered up and system did not come up properly. I saw no special advisories about additional manual steps etc. Question: Did I miss a step when using the alternative disk format options on this platform? Are they a WIP? Should I file a bug report? 'Bibliography:' Nearly all NanoPi NEO2 forum posts here Many others...
  24. Hello Community! File /boot/orangepi/OrangePiH5orangepi.dts is not self-explanatory.. :-( Is there any documentation on how to define GPIO.21 for example for DIGITAL OUTPUT with initial "Logical ONE" at a BOOT time? It will control Triac with 220 Volts on it. IT MUST BE EXACTLY AT HIGH LEVEL AT A BOOT TIME. How to do this? It should be in OUT mode. Any help appreciated!... Regards, Ellad
  25. I had an annoying issue with the WiFi of this board with Armbian 5.65 Ubuntu and Stretch. Sometimes it would spontaneous lose its WiFi connection. After researching it for a while I noticed that the wlan0 interface sometimes lost it's IP address. At first I thought it had something to do with the DHCP lease or sleep mode of the adapter. I just couldn't get my head around it and I ended up removing network-manager and going back to creating an interfaces.conf file for setting up my network interfaces. Somehow this solved the issue, the WiFi connection hasn't failed since! To do this, first create the wpa supplicant configuration file: ~# wpa_passphrase "YOUR_SSID" "YOUR_SUPER_SECRET_WPA_KEY" > /etc/wpa_supplicant.conf This creates a wpa_supplicant.conf file that looks like this: network={ ssid="YOUR_SSID" #psk="YOUR_SUPER_SECRET_WPA_KEY" <- YOU SHOULD REMOVE THIS COMMENT!! psk=A_VERY_LONG_HASH_OF_YOUR_SECRET_KEY } Than create an /etc/network/interfaces file that is suitable for your network like this example: auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet dhcp # With a DHCP address allow-hotplug wlan0 iface wlan0 inet dhcp wpa-conf /etc/wpa_supplicant.conf # Or with a static IP address allow-hotplug wlan0 iface wlan0 inet dhcp address netmask gateway # (Cloudflare Secure DNS, another tip ;-) dns-nameservers After this you need to remove networkmanager: ~# apt remove network-manager and after rebooting your device you should be able to connect to it.