Jump to content

Search the Community

Showing results for tags 'nanopineoplus2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 24 results

  1. Sorry for the minimal info provided in this report but, due to the possible data corruption which the bug may cause, I'm not willing to reproduce this again on my board which runs in production. One week ago, I experienced data corruption happening on the nanopi. Actually it was some time (more than one month) that I saw the board acting weird: - long ssh transfers would sometime brake (via https://github.com/dooblem/bsync) - `apt update` reported invalid keys for the official armbian repository - on rare occasions, the board would freeze (not respond to ssh, requiring manual power cycle) After experiencing data corruption, I though the board was broken but decided to switch to the legacy image via `armbian-config` as a last resort. When running `armbian-config` and selecting "Other" to switch kernel, the kernel crashed. I tried again and I was successful. With the legacy image `5.4.88-sunxi64 #21.02.3` the board works great, and all the reported issues do not occur any more. So it seems like there is a bug in the "current" image (it should be version 5.15.25), possibly in a module linked to the encryption. This is all the info I can provide for this report. Hope it helps
  2. gpio load i2c modprobe: FATAL: Module i2c-sunxi not found in directory /lib/modules/4.14.111 By looking at example of WiringPI (for Raspberry), I tried the above command, result is shown. I'm newbie, so I need to figure out how to send commands via i2c to an external device. But first, how do I even enable i2c on Neo Plus2? Or is it enabled on default? I saw on this forum suggestion to add: a line "overlays=i2c0 i2c1" in /boot/armbianEnv.txt However, my boot directory is full, so and I get error 514 whenever I try to add anything to armbianEnv.txt (which is empty) Here's disk usage: I added 10K pull up resistors between Pin #1 SYS_3.3V and Pin #3 I2C0_SDA / GPIOA12 and Pin #5 I2C0_SCL / GPIOA11. Result of i2cdetects: However, when I tried to output from I2C0_SCL pin the following: sudo i2cset -y 3 0x30 255 (writes the byte value 255 to the I2C device at address 30 hex on the i2c-3 bus) And I was checking with scope the pins I2C0_SDA and I2C0_SCL, and nothing was shown there, other than 3.3V. Also, I'm not sure where bus 3 is, I mean don't pins I2C0_SDA and I2C0_SC correspond bus to i2c-3? There are no other pins for other I2c buses...
  3. Can someone post the printenv for a NEO PLUS2 because i think i f*** up my device and doesn't boot from SD or USB .... the only i get is the boot menu. Or any ideas to help me to fix this ?
  4. My device is nanopi neo plus2 h5 soc with armban Buster server installed. I have realtek rtl8812au mt7612u two wireless network cards. I found that armbain's wifi driver is relatively old, how do I compile the latest driver https://github.com/aircrack-ng/rtl8812au https://github.com/openwrt/mt76 I tried to download the latest rtl8812au driver and compile it, but an error occurred device FriendlyARM nanopi neo plus2 0S armbian PRETTY_NAME="Armbian 20.08.3 Buster" allwinnertech h5 chip kernel Linux nanopi 5.8.10-sunxi64 CC [M] /root/rtl8812au/hal/phydm/halrf/rtl8814a/halrf_iqk_8814a.o CC [M] /root/rtl8812au/hal/phydm/rtl8814a/phydm_regconfig8814a.o CC [M] /root/rtl8812au/hal/phydm/halrf/rtl8814a/halrf_8814a_ce.o CC [M] /root/rtl8812au/hal/phydm/rtl8814a/phydm_rtl8814a.o CC [M] /root/rtl8812au/hal/phydm/txbf/haltxbf8814a.o CC [M] /root/rtl8812au/platform/platform_ops.o CC [M] /root/rtl8812au/core/rtw_mp.o LD [M] /root/rtl8812au/88XXau.o MODPOST /root/rtl8812au/Module.symvers ERROR: modpost: "__stack_chk_guard" [/root/rtl8812au/88XXau.ko] undefined! make[2]: *** [scripts/Makefile.modpost:111: /root/rtl8812au/Module.symvers] Error 1 make[2]: *** Deleting file '/root/rtl8812au/Module.symvers' make[1]: *** [Makefile:1667: modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.8.10-sunxi64' make: *** [Makefile:2312: modules] Error 2 My mediatek mt7612u works normally under ubuntu20.04, but it cannot be used at all under armbian, and an error log appears in dmesg. So, I just want to recompile the latest mt76 driver, I am sure it is not the problem of usbmodeswitch, because my wifi card does not have windows free driver disk
  5. Dear maintainers, I have my sensors configured to reboot every night via a user cronjob (0 0 * * * /sbin/reboot), 14 sensors do this without a problem. I've fixed the nanopi neo+2 reboot from NAND some months ago (by re-using friendlyarm first stage u-boot). I just stumbled upon a failed reboot with one of my nanopi neo+2 nodes, after two successful reboots. Looking at the /var/log.hdd/syslog, it got stuck in the shutdown procedure when the watchdog reported a failure. The /var/log.hdd/syslog.1 extracts below show the start of the watchdog, and the stop of the watchdog and its failure. After the failure the system doesn't come up anymore, it needed a powercycle, which is quite inconvenient since it is installed at a hard to access remote location. Sep 18 00:03:26 EnexisVT2-1 systemd[1]: Starting watchdog daemon... Sep 18 00:03:26 EnexisVT2-1 systemd[1]: Reached target Graphical Interface. Sep 18 00:03:26 EnexisVT2-1 systemd[1]: Starting Update UTMP about System Runlevel Changes... Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: starting daemon (5.15): Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: int=1s realtime=yes sync=no load=0,0,0 soft=no Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: memory not checked Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: ping: no machine to check Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: file: no file to check Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: pidfile: no server process to check Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: interface: no interface to check Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: temperature: no sensors to check Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: no test binary files Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: no repair binary files Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: error retry time-out = 60 seconds Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: repair attempts = 1 Sep 18 00:03:26 EnexisVT2-1 watchdog[2212]: alive=[none] heartbeat=[none] to=root no_act=no force=no Sep 18 00:03:26 EnexisVT2-1 systemd[1]: Started watchdog daemon. ... Sep 19 00:00:01 EnexisVT2-1 CRON[6188]: (dennis) CMD (/sbin/reboot) ... Sep 19 00:00:02 EnexisVT2-1 systemd[1]: Stopping Authorization Manager... ... Sep 19 00:00:02 EnexisVT2-1 watchdog[2212]: stopping daemon (5.15) Sep 19 00:00:02 EnexisVT2-1 systemd[1]: Stopping watchdog daemon... ... Sep 19 00:00:02 EnexisVT2-1 systemd[1]: watchdog.service: Control process exited, code=exited, status=1/FAILURE Sep 19 00:00:02 EnexisVT2-1 systemd[1]: watchdog.service: Failed with result 'exit-code'. Sep 19 00:00:02 EnexisVT2-1 systemd[1]: Stopped watchdog daemon. Sep 19 00:00:02 EnexisVT2-1 systemd[1]: watchdog.service: Triggering OnFailure= dependencies. Sep 19 00:00:02 EnexisVT2-1 systemd[1]: Requested transaction contradicts existing jobs: Transaction for wd_keepalive.service/start is destructive (armbian-zram-confi g.service has 'stop' job queued, but 'start' is included in transaction). Sep 19 00:00:02 EnexisVT2-1 systemd[1]: watchdog.service: Failed to enqueue OnFailure= job, ignoring: Transaction for wd_keepalive.service/start is destructive (armbi an-zram-config.service has 'stop' job queued, but 'start' is included in transaction). Sep 19 00:00:02 EnexisVT2-1 systemd[1]: Stopped target Multi-User System. Sep 19 00:00:02 EnexisVT2-1 systemd[1]: Stopping rng-tools.service... Sep 19 00:00:02 EnexisVT2-1 systemd[1]: Stopping OpenBSD Secure Shell server... Sep 19 00:00:02 EnexisVT2-1 systemd[1]: Stopping LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons)... Sep 19 00:00:02 EnexisVT2-1 ntpd[1396]: ntpd exiting on signal 15 (Terminated) ... cold reboot Sep 19 00:00:09 EnexisVT2-1 kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] Sep 19 00:00:09 EnexisVT2-1 fake-hwclock[406]: Sat 19 Sep 2020 12:00:03 AM UTC After this the system didn't boot anymore, and we had to manually cold-boot it. So, I've stopped&disabled the watchdog for now, also had to set run_wd_keepalive=0 in /etc/default/watchdog, since the watchdog also failed to stop from the commandline (also on other systems): Sep 23 11:33:59 EnexisVT2-1 systemd[1]: Starting watchdog daemon... Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: starting daemon (5.15): Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: int=1s realtime=yes sync=no load=0,0,0 soft=no Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: memory not checked Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: ping: no machine to check Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: file: no file to check Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: pidfile: no server process to check Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: interface: no interface to check Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: temperature: no sensors to check Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: no test binary files Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: no repair binary files Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: error retry time-out = 60 seconds Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: repair attempts = 1 Sep 23 11:33:59 EnexisVT2-1 watchdog[3236]: alive=[none] heartbeat=[none] to=root no_act=no force=no Sep 23 11:33:59 EnexisVT2-1 systemd[1]: Started watchdog daemon. ... Sep 23 11:34:03 EnexisVT2-1 watchdog[3236]: stopping daemon (5.15) Sep 23 11:34:03 EnexisVT2-1 systemd[1]: Stopping watchdog daemon... Sep 23 11:34:03 EnexisVT2-1 systemd[1]: watchdog.service: Control process exited, code=exited, status=1/FAILURE Sep 23 11:34:03 EnexisVT2-1 systemd[1]: watchdog.service: Failed with result 'exit-code'. Sep 23 11:34:03 EnexisVT2-1 systemd[1]: Stopped watchdog daemon. Sep 23 11:34:03 EnexisVT2-1 systemd[1]: watchdog.service: Triggering OnFailure= dependencies. Note that I froze the armbian upgrades on all these sensors on armbian 20.02.7, to avoid having to recompile my kernel modules on every upstream update. I noticed that the systemd package got an update recently, unsure if this update may mitigate the problem. systemd-sysv/stable 241-7~deb10u4 arm64 [upgradable from: 241-7~deb10u3] systemd/stable 241-7~deb10u4 arm64 [upgradable from: 241-7~deb10u3] dennis@EnexisVT2-1:~$ dpkg -l "*current*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-========================================-============-============-============================================================ ii linux-buster-root-current-nanopineoplus2 20.02.1 arm64 Armbian tweaks for buster on nanopineoplus2 (current branch) hi linux-dtb-current-sunxi64 20.02.7 arm64 Linux DTB, version 5.4.28-sunxi64 hi linux-headers-current-sunxi64 20.02.7 arm64 Linux kernel headers for 5.4.28-sunxi64 on arm64 hi linux-image-current-sunxi64 20.02.7 arm64 Linux kernel, version 5.4.28-sunxi64 hi linux-u-boot-nanopineoplus2-current 20.02.1 arm64 Uboot loader 2019.10
  6. Hi, I want to use g_ether on NanoPi Neo Plus2. For Neo Air, I have already figured out how to do this and I can see usb0 in config. But with armbian 5.85 (4.19.38-sunxi64), the same instructions fail at sudo ifconfig usb0 up with the message "usb0: ERROR while getting interface flags: No such device". Could somebody tell me how to activate USB OTG on NanoPi Neo Plus2 and then use g_ether. I think the same holds true for g_serial. This could be an alternative, but I would prever ethernet connection. My target: Connect NanoPi Neo Plus2 with NanoPi Neo Air via Ethernet Thank you for your help! Steps I followed for g_ether:
  7. Hello I am using NPiNeoPlus2 board (ordered Neo2 but they send me Neo Plus2) I red this is not officially supported but it works some way The image works from TF but when I write it to eMMC it boots it works but can't reboot I type reboot and I get (serial) $ sudo reboot [sudo] password for onir: [ OK ] Stopped target Timers. [ OK ] Stopped Daily apt upgrade and clean activities. Stopping Authorization Manager... [ OK ] Stopped Stopping Session 2 of user onir. [ OK ] Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. [ OK ] Stopped Daily rotation of log files. [ OK ] Stopped target System Time Synchronized. [ OK ] Stopped target Multi-User System. [ OK ] Stopped Resets System Activity Data Collector. Stopping Regular background program processing daemon... Stopping LSB: Advanced IEEE 802.11 management daemon... Stopping LSB: Set sysfs variables from /etc/sysfs.conf... Stopping rng-tools.service... Stopping chrony, an NTP client/server... [ OK ] Stopped target Login Prompts. Stopping Serial Getty on ttyS0... Stopping Getty on tty1... Stopping OpenBSD Secure Shell server... Stopping System Logging Service... Stopping Dispatcher daemon for systemd-networkd... Stopping Unattended Upgrades Shutdown... [ OK ] Stopped Regular background program processing daemon. [ OK ] Stopped Dispatcher daemon for systemd-networkd. [ OK ] Stopped System Logging Service. [ OK ] Stopped chrony, an NTP client/server. [ OK ] Stopped OpenBSD Secure Shell server. [ OK ] Stopped Unattended Upgrades Shutdown. [ OK ] Stopped Authorization Manager. [ OK ] Stopped Getty on tty1. [ OK ] Stopped Serial Getty on ttyS0. [ OK ] Stopped Save/Restore Sound Card State. [ OK ] Stopped LSB: Advanced IEEE 802.11 management daemon. [ OK ] Stopped rng-tools.service. [ OK ] Stopped Session 2 of user onir. Stopping User Manager for UID 1000... Stopping Manage Sound Card State (restore and store)... [ OK ] Removed slice system-serial\x2dgetty.slice. [ OK ] Stopped /etc/rc.local Compatibility. [ OK ] Stopped target Network is Online. [ OK ] Stopped Network Manager Wait Online. [ OK ] Removed slice system-getty.slice. Stopping Login Service... [ OK ] Stopped User Manager for UID 1000. [ OK ] Stopped LSB: Set sysfs variables from /etc/sysfs.conf. [ OK ] Stopped Manage Sound Card State (restore and store). Stopping LSB: set CPUFreq kernel parameters... Stopping User Runtime Directory /run/user/1000... [ OK ] Stopped Login Service. [ OK ] Unmounted /run/user/1000. [ OK ] Stopped User Runtime Directory /run/user/1000. [ OK ] Removed slice User Slice of UID 1000. Stopping Permit User Sessions... [ OK ] Stopped Permit User Sessions. [ OK ] Stopped LSB: set CPUFreq kernel parameters. Stopping LSB: Load kernel …d to enable cpufreq scaling... [ OK ] Stopped target Network. Stopping Network Manager... Stopping Raise network interfaces... Stopping WPA supplicant... [ OK ] Stopped LSB: Load kernel m…ded to enable cpufreq scaling. [ OK ] Stopped Network Manager. [ OK ] Stopped target Remote File Systems. [ OK ] Stopped Raise network interfaces. [ OK ] Stopped WPA supplicant. Stopping D-Bus System Message Bus... [ OK ] Stopped D-Bus System Message Bus. [ OK ] Stopped target Basic System. [ OK ] Stopped target Paths. [ OK ] Stopped target Slices. [ OK ] Removed slice User and Session Slice. [ OK ] Stopped target Sockets. [ OK ] Closed Syslog Socket. [ OK ] Closed D-Bus System Message Bus Socket. [ OK ] Stopped target System Initialization. Stopping Update UTMP about System Boot/Shutdown... [ OK ] Stopped Apply Kernel Variables. [ OK ] Stopped Load Kernel Modules. [ OK ] Stopped target Local Encrypted Volumes. [ OK ] Stopped Dispatch Password …ts to Console Directory Watch. [ OK ] Stopped Forward Password R…uests to Wall Directory Watch. Stopping Entropy daemon using the HAVEGE algorithm... Stopping Restore / save the current clock... Stopping Armbian memory supported logging... [ OK ] Stopped Entropy daemon using the HAVEGE algorithm. [ OK ] Stopped Restore / save the current clock. Stopping Load/Save Random Seed... [ OK ] Stopped Update UTMP about System Boot/Shutdown. [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Stopped Load/Save Random Seed. [ OK ] Unmounted /var/log. [ OK ] Unmounted /var/log.hdd. [ OK ] Stopped Armbian memory supported logging. Stopping Armbian ZRAM config... [ OK ] Stopped Armbian ZRAM config. [ OK ] Stopped target Local File Systems. Unmounting /tmp... [ OK ] Unmounted /tmp. [ OK ] Stopped target Local File Systems (Pre). [ OK ] Stopped Create Static Device Nodes in /dev. [ OK ] Stopped Create System Users. [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Stopped target Swap. [ OK ] Reached target Shutdown. Deactivating swap /dev/zram1... [ OK ] Deactivated swap /dev/zram1. [ OK ] Reached target Unmount All Filesystems. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 228.568922] reboot: Restarting system U-Boot SPL 2019.10-armbian (Feb 07 2020 - 12:55:56 +0100) DRAM: 1024 MiB Trying to boot from MMC2 and it waits... what for? Image Armbian_20.02.1_Nanopineoplus2_buster_current_5.4.20 it happens the same on every kernel used
  8. Hello, I've been trying to install Raspotify on my NeoPlus2. While it seems to be install OK, I can't find my device available in the list of Spotify-connect capable devices. journalctl -u raspotify reports: gtj@nanopineoplus2:~$ journalctl -u raspotify -- Logs begin at Mon 2020-05-04 02:26:25 UTC, end at Mon 2020-05-04 02:43:52 UTC May 04 02:26:32 nanopineoplus2 systemd[1]: Starting Raspotify... May 04 02:26:32 nanopineoplus2 systemd[1]: Started Raspotify. May 04 02:26:32 nanopineoplus2 librespot[963]: [2020-05-04T02:26:32Z INFO libre May 04 02:26:33 nanopineoplus2 librespot[963]: thread 'main' panicked at 'called May 04 02:26:33 nanopineoplus2 librespot[963]: stack backtrace: May 04 02:26:33 nanopineoplus2 librespot[963]: 0: 0x10b13a4 - backtrace::bac May 04 02:26:33 nanopineoplus2 librespot[963]: at /cargo/ May 04 02:26:33 nanopineoplus2 librespot[963]: 1: 0x10b13a4 - backtrace::bac May 04 02:26:33 nanopineoplus2 librespot[963]: at /cargo/ May 04 02:26:33 nanopineoplus2 librespot[963]: 2: 0x10b13a4 - std::sys_commo May 04 02:26:33 nanopineoplus2 librespot[963]: at src/lib May 04 02:26:33 nanopineoplus2 librespot[963]: 3: 0x10b13a4 - <std::sys_comm May 04 02:26:33 nanopineoplus2 librespot[963]: at src/lib May 04 02:26:33 nanopineoplus2 librespot[963]: 4: 0x10d3ca4 - core::fmt::wri May 04 02:26:33 nanopineoplus2 librespot[963]: at src/lib May 04 02:26:33 nanopineoplus2 librespot[963]: 5: 0x10abff0 - std::io::Write May 04 02:26:33 nanopineoplus2 librespot[963]: at src/lib May 04 02:26:33 nanopineoplus2 librespot[963]: 6: 0x10b3954 - std::sys_commo May 04 02:26:33 nanopineoplus2 librespot[963]: at src/lib May 04 02:26:33 nanopineoplus2 librespot[963]: 7: 0x10b3954 - std::sys_commo May 04 02:26:33 nanopineoplus2 librespot[963]: at src/lib May 04 02:26:33 nanopineoplus2 librespot[963]: 8: 0x10b3954 - std::panicking lines 1-23...skipping... -- Logs begin at Mon 2020-05-04 02:26:25 UTC, end at Mon 2020-05-04 02:43:52 UTC. -- May 04 02:26:32 nanopineoplus2 systemd[1]: Starting Raspotify... May 04 02:26:32 nanopineoplus2 systemd[1]: Started Raspotify. May 04 02:26:32 nanopineoplus2 librespot[963]: [2020-05-04T02:26:32Z INFO librespot] librespot (raspotify v0.14.0) 3672214 (2020-01-30). Built on 2020-02-16. May 04 02:26:33 nanopineoplus2 librespot[963]: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 19, kind: Other, message: "N May 04 02:26:33 nanopineoplus2 librespot[963]: stack backtrace: May 04 02:26:33 nanopineoplus2 librespot[963]: 0: 0x10b13a4 - backtrace::backtrace::libunwind::trace::hb1e9954dcc6e7c1f May 04 02:26:33 nanopineoplus2 librespot[963]: at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunw May 04 02:26:33 nanopineoplus2 librespot[963]: 1: 0x10b13a4 - backtrace::backtrace::trace_unsynchronized::h1b198a73034a9734 May 04 02:26:33 nanopineoplus2 librespot[963]: at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs May 04 02:26:33 nanopineoplus2 librespot[963]: 2: 0x10b13a4 - std::sys_common::backtrace::_print_fmt::hf691518b63d0b79d May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/sys_common/backtrace.rs:84 May 04 02:26:33 nanopineoplus2 librespot[963]: 3: 0x10b13a4 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::he6a16924 May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/sys_common/backtrace.rs:61 May 04 02:26:33 nanopineoplus2 librespot[963]: 4: 0x10d3ca4 - core::fmt::write::hc426988e4c4119a8 May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libcore/fmt/mod.rs:1025 May 04 02:26:33 nanopineoplus2 librespot[963]: 5: 0x10abff0 - std::io::Write::write_fmt::h34e90dde595ba7cd May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/io/mod.rs:1426 May 04 02:26:33 nanopineoplus2 librespot[963]: 6: 0x10b3954 - std::sys_common::backtrace::_print::h406863a8800396cd May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/sys_common/backtrace.rs:65 May 04 02:26:33 nanopineoplus2 librespot[963]: 7: 0x10b3954 - std::sys_common::backtrace::print::hec570bc9fdd6a536 May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/sys_common/backtrace.rs:50 May 04 02:26:33 nanopineoplus2 librespot[963]: 8: 0x10b3954 - std::panicking::default_hook::{{closure}}::hf187be78db8e291b May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/panicking.rs:193 May 04 02:26:33 nanopineoplus2 librespot[963]: 9: 0x10b35b4 - std::panicking::default_hook::h9634e45fc0d61ba6 May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/panicking.rs:210 May 04 02:26:33 nanopineoplus2 librespot[963]: 10: 0x10b4030 - std::panicking::rust_panic_with_hook::h35923fdea5783220 May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/panicking.rs:471 May 04 02:26:33 nanopineoplus2 librespot[963]: 11: 0x10b3c48 - rust_begin_unwind May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/panicking.rs:375 May 04 02:26:33 nanopineoplus2 librespot[963]: 12: 0x10cfac0 - core::panicking::panic_fmt::hd74e307162bc16e5 May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libcore/panicking.rs:84 May 04 02:26:33 nanopineoplus2 librespot[963]: 13: 0x10cfbac - core::result::unwrap_failed::h36f73057b442c0eb May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libcore/result.rs:1188 May 04 02:26:33 nanopineoplus2 librespot[963]: 14: 0xbeb5e0 - librespot::main::h0ed06a728ac2479f May 04 02:26:33 nanopineoplus2 librespot[963]: 15: 0xbec980 - std::rt::lang_start::{{closure}}::h3ecc962e3fb4564b May 04 02:26:33 nanopineoplus2 librespot[963]: 16: 0x10b3ac4 - std::rt::lang_start_internal::{{closure}}::hc02935a73664ebd0 May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/rt.rs:52 May 04 02:26:33 nanopineoplus2 librespot[963]: 17: 0x10b3ac4 - std::panicking::try::do_call::h9ca5184b6b3cc62d May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/panicking.rs:292 May 04 02:26:33 nanopineoplus2 librespot[963]: 18: 0x10bb220 - __rust_maybe_catch_panic May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libpanic_unwind/lib.rs:78 May 04 02:26:33 nanopineoplus2 librespot[963]: 19: 0x10b4484 - std::panicking::try::hc53e4a11b02f3299 May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/panicking.rs:270 May 04 02:26:33 nanopineoplus2 librespot[963]: 20: 0x10b4484 - std::panic::catch_unwind::ha972c7f8a413a94c May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/panic.rs:394 May 04 02:26:33 nanopineoplus2 librespot[963]: 21: 0x10b4484 - std::rt::lang_start_internal::hdf6cc497202d2594 May 04 02:26:33 nanopineoplus2 librespot[963]: at src/libstd/rt.rs:51 systemctl status raspotify reports: ● raspotify.service - Raspotify Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-05-04 02:43:10 UTC; 7min ago Main PID: 2278 (librespot) Tasks: 3 (limit: 1022) Memory: 840.0K CGroup: /system.slice/raspotify.service └─2278 /usr/bin/librespot --name raspotify --backend alsa --bitrate 320 --disable-audio-cache --enable-volume-normalisation --linear-volume --initi May 04 02:43:10 nanopineoplus2 systemd[1]: Starting Raspotify... May 04 02:43:10 nanopineoplus2 systemd[1]: Started Raspotify. May 04 02:43:10 nanopineoplus2 librespot[2278]: [2020-05-04T02:43:10Z INFO librespot] librespot (raspotify v0.14.0) 3672214 (2020-01-30). Built on 2020-02-16 gtj@nanopineoplus2:~$ apt update Reading package lists... Done E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied) E: Unable to lock directory /var/lib/apt/lists/ W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied) W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied) gtj@nanopineoplus2:~$ sudo apt update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://httpredir.debian.org/debian buster InRelease Get:3 http://httpredir.debian.org/debian buster-updates InRelease [49.3 kB] Get:5 http://httpredir.debian.org/debian buster-backports InRelease [46.7 kB] Hit:4 https://apt.armbian.com buster InRelease Get:6 http://httpredir.debian.org/debian buster-backports/main arm64 Packages.diff/Index [27.8 kB] Get:7 http://httpredir.debian.org/debian buster-backports/main armhf Packages.diff/Index [27.8 kB] Get:8 http://httpredir.debian.org/debian buster-backports/main armhf Contents (deb).diff/Index [27.9 kB] Get:9 http://httpredir.debian.org/debian buster-backports/main arm64 Contents (deb).diff/Index [27.9 kB] Get:10 http://httpredir.debian.org/debian buster-backports/main arm64 Packages 2020-05-04-0201.50.pdiff [860 B] Get:11 http://httpredir.debian.org/debian buster-backports/main armhf Packages 2020-05-04-0201.50.pdiff [860 B] Get:12 http://httpredir.debian.org/debian buster-backports/main armhf Contents (deb) 2020-05-04-0201.50.pdiff [265 B] Get:10 http://httpredir.debian.org/debian buster-backports/main arm64 Packages 2020-05-04-0201.50.pdiff [860 B] Get:11 http://httpredir.debian.org/debian buster-backports/main armhf Packages 2020-05-04-0201.50.pdiff [860 B] Get:12 http://httpredir.debian.org/debian buster-backports/main armhf Contents (deb) 2020-05-04-0201.50.pdiff [265 B] Get:13 http://httpredir.debian.org/debian buster-backports/main arm64 Contents (deb) 2020-05-04-0201.50.pdiff [264 B] Get:13 http://httpredir.debian.org/debian buster-backports/main arm64 Contents (deb) 2020-05-04-0201.50.pdiff [264 B] Fetched 210 kB in 13s (16.5 kB/s) ^C gtj@nanopineoplus2:~$ Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 26, in <module> col.create(db) File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 94, in create self._fill_commands(con) File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 132, in _fill_commands self._parse_single_contents_file(con, f, fp.stdout) File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 230, in _parse_single_contents_file l.startswith('bin') or l.startswith('sbin')): KeyboardInterrupt and finally systemctl status raspotify reports: ● raspotify.service - Raspotify Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset Active: activating (auto-restart) (Result: exit-code) since Mon 2020-05-04 03 Process: 3005 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=ex Process: 3006 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify Process: 3008 ExecStart=/usr/bin/librespot --name ${DEVICE_NAME} $BACKEND_ARGS Main PID: 3008 (code=exited, status=1/FAILURE) May 04 03:05:38 nanopineoplus2 librespot[3008]: uses. May 04 03:05:38 nanopineoplus2 librespot[3008]: --enable-volume-normalis May 04 03:05:38 nanopineoplus2 librespot[3008]: Play all May 04 03:05:38 nanopineoplus2 librespot[3008]: --normalisation-pregain May 04 03:05:38 nanopineoplus2 librespot[3008]: Pregain May 04 03:05:38 nanopineoplus2 librespot[3008]: --linear-volume May 04 03:05:38 nanopineoplus2 librespot[3008]: increase May 04 03:05:38 nanopineoplus2 librespot[3008]: --autoplay autoplay May 04 03:05:38 nanopineoplus2 systemd[1]: raspotify.service: Main process exite May 04 03:05:38 nanopineoplus2 systemd[1]: raspotify.service: Failed with result lines 1-18/18 (END) ● raspotify.service - Raspotify Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Mon 2020-05-04 03:05:38 UTC; 32ms ago Process: 3005 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS) Process: 3006 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SU Process: 3008 ExecStart=/usr/bin/librespot --name ${DEVICE_NAME} $BACKEND_ARGS --bitrate ${BITRATE} $CAC Main PID: 3008 (code=exited, status=1/FAILURE) May 04 03:05:38 nanopineoplus2 librespot[3008]: uses. May 04 03:05:38 nanopineoplus2 librespot[3008]: --enable-volume-normalisation May 04 03:05:38 nanopineoplus2 librespot[3008]: Play all tracks at the same volume May 04 03:05:38 nanopineoplus2 librespot[3008]: --normalisation-pregain PREGAIN May 04 03:05:38 nanopineoplus2 librespot[3008]: Pregain (dB) applied by volume nor May 04 03:05:38 nanopineoplus2 librespot[3008]: --linear-volume May 04 03:05:38 nanopineoplus2 librespot[3008]: increase volume linear instead of May 04 03:05:38 nanopineoplus2 librespot[3008]: --autoplay autoplay similar songs when your m May 04 03:05:38 nanopineoplus2 systemd[1]: raspotify.service: Main process exited, code=exited, status=1/F May 04 03:05:38 nanopineoplus2 systemd[1]: raspotify.service: Failed with result 'exit-code'. Any help with this will be greatly appreciated!
  9. Hello, I have a NanoPi Neo Plus 2 I used to run Ubuntu Core on it but i wanted to switch out as i had less storage space available 4.7gb out of 8 and other issues as it was also out of date. I installed Armbian first on SD then on eMMC but the problem i am facing is that only 479mb of ram is available. Now in the first post on this board by Stanislav Sinyagin on July 18, 2017 it was stated that only 512 mb of ram was available but later on i saw posts of people with the whole 1Gb of ram being used. Due to the limited ram i get compilation problems among other things i am using this board headless as a server. i flashed all versions for download multiple times along with trying to compile a new 4.14 kernel like mention in the arch wiki but it just wouldn't boot. I have spent a few days trying to figure it out. It would be really helpful if someone could point me in the right direction. Thank You
  10. anyone running a neo+ 2. don't bother with neo2 image, it doesn't recognise emmc or wifi card the nanopi K1plus image works beautifully and supports both emmc and wifi module
  11. Dear all, Starting from NAND memory used to work fine on the nanopi neo plus2, however with the new boards (both v1.2 and v2.0 revision) we just obtained it frequently doesn't want to reboot, while a cold boot works fine (I tried also earlier u-boot versions (2019.04, 2018.11) without much success for the reboot from NAND). The re-boot process stops at this point (from the serial console): [ OK ] Reached target Shutdown. [ 152.452083] reboot: Restarting system U-Boot SPL 2019.10-armbian (Jan 25 2020 - 19:56:27 +0100) DRAM: 1024 MiB Trying to boot from MMC2 I suspected the problem to be in the u-boot, since the friendlyarm on NAND reboots without a hitch. I found a work-around for the latest stretch image (Armbian_20.02.0-rc1_Nanopineoplus2_stretch_current_5.4.14.7z), by doing the following: boot friendlyarm image from NAND and copy the sunxi-spl.bin: sudo dd if=/dev/mmcblk2 of=sunxi-spl-friendlyarm.bin count=4 bs=8k skip=1 boot armbian from NAND and update u-boot: switched to linux-image-next-sunxi64=5.90 kernel via armbian-config / System / Other / switch dd if=sunxi-spl-friendlyarm.bin of=/dev/mmcblk2 count=4 bs=8k seek=1 conv=fsync The atached armbianmonitor -u upload is from after a fresh reboot with the working configuration. Kind regards, Dennis
  12. Recently I wanted to give another try to a NanoPi NEO Plus2 but I noticed that it is marked as not supported and there is no Armbian Bionic image for it (the links in https://www.armbian.com/nanopi-neo-plus2/ return 404). So I checked about other FriendlyElec H5 boards: https://www.armbian.com/download/?tx_soc=h5&tx_maker=friendlyelec (I had to edit the URL as otherwise one cannot add multiple filters) And I picked the K1 plus as a close relative; the Bionic image seems working without any issue, I will keep testing and report back. The only minor issue that I could find so far is that htop will show 0 Mhz for all cores. I have reported in the past about issues with the 2nd USB however this is also not reproducible with the K1 plus image. May I suggest to add it at least as a testable image, with the proper tailoring? Other relevant thread:
  13. Hi, I am new here and searched the forums for an answer to my questions regarding the NanoPi NEO2 and NEO Plus2. Most answers I could find, but a few were left open. The NEO Plus2 is marked as WIP. Why? What do I have to expect not to work? Both boards are similarly old, from what I could find. Will the Plus2 move up to "supported" eventually or does it currently more look like the route is going towards CSC? Do common features like GPIO access, SPI, I2C ... work with current images? Do specific features where the Plus2 differs from the NEO2 like WiFi, Bluetooth, ... work? I already found out, that the second USB port should work fine. If someone could answer one ore all of those questions that would be much appreciated. Also if you have any other input towards rather buying one or the other SBC, that would be great. Thank you! Frank
  14. Hi, I'm using 4.19.57-sunxi64 on a NanoPi NEO Plus2 and I'm wondering if there's a way to change some USB configurations just like I'd do with the cmdline.txt file on a RPi? I want to do some testing with USB over IP and for that I'd like to tweak the usb modules for better performance, liability. My armbianEnv.txt is as follows: Thanks in advance!
  15. Hi, I just got a NanoPi Neo Plus2 for which I must prepare an image for our software. Basically I must have a working Ethernet-over-USB, Wifi and NIC. I started with your current Debian image compiled with uses Armbian v8.75 and Linux kernel v4.19.20. In this image Wifi works, but loading the g_ether module does not seem to work. I assume I need to patch the kernel to make this happen, which means I need to build my own images. So I created a Virtualbox environment as described in the documentation, and compiled an image with all the defaults (apart from a date-tag I add to the kernel name for identification). I installed the image to the eMMC and booted. In this image there is no wifi interface and g_ether also does not work. The armbianmonitor output for my new image is attached to this query (http://ix.io/1H9v), but I also created an armbianmonitor output for your Debian image (http://ix.io/1H9u) in which the Wifi interface does appear. Wifi: Comparing the dmesg output, it is obvious that firmware fails to load into the AP6212 wifi unit on my image. I've downloaded and installed firmware from several sites (official and other) to try and fix, but nothing solves the problem. Any ideas? Is this a regression in the Linux kernel (4.19.20 -> 4.19.36)? OTG: Configuration of the USB-OTG for the Ethernet-over-USB gadget is usually done in the DTS files on ARM processors (I think - a bit rusted). I've noticed that there are several patches applied to the kernel from other boards such as the OrangePi, so maybe someone already has a patch for another H5 based board which will work for the NanoPiNeo+2? Regards, LJB
  16. Hi, I got one of those cheap 300Mbps wifi dongles with 8192EU chip How can we enable this in Armbian? Only lsusb has the following https://ibb.co/gYxyYT
  17. Hi, I tried to add the mcp251x overlay for Nanopi-NEO-Plus2 (Allwinner H5) using armbian-add-overlay command but got the error below. Does anybody know why? Below, you can find the dts file. Any help would be appreciated. Compiling the overlay dtc: livetree.c:521: get_node_by_phandle: Assertion `(phandle != 0) && (phandle != -1)' failed. /usr/sbin/armbian-add-overlay: line 76: 2078 Aborted dtc -@ -q -I dts -O dtb -o ${temp_dir}/${fname}.dtbo $1 Error compiling the overlay spi-mcp251x.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { target-path = "/clocks"; __overlay__ { #address-cells = <1>; #size-cells = <1>; can0_osc_fixed: can0_osc_fixed { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <8000000>; }; }; }; fragment@1 { target = <&pio>; __overlay__ { can0_pin_irq: can0_pin_irq { pins = "PA7"; function = "irq"; bias-pull-up; }; }; }; fragment@2 { target = <&spi1>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; mcp2515 { reg = <0>; compatible = "microchip,mcp2515"; pinctrl-names = "default"; pinctrl-0 = <&can0_pin_irq>; spi-max-frequency = <10000000>; interrupt-parent = <&pio>; interrupts = <0 7 2>; /* PA7 IRQ_TYPE_EDGE_FALLING */ clocks = <&can0_osc_fixed>; status = "okay"; }; }; }; };
  18. I noticed the Neo+ 2 has a blue LED: line 10: unnamed "nanopi:green:pwr" output active-high [used] line 20: unnamed "nanopi:blue:status" output active-high [used] It's not doing the heartbeat flash like the NanoPi Duo. uname -a Linux nanopineoplus2 4.14.15-sunxi64 #95 SMP Wed Jan 24 10:55:45 CET 2018 aarch64 GNU/Linux
  19. Hello. Has anybody tried to encode h264 on h5 via ffmpeg cedrus264? any help would be appropriated. thanks in advnace.
  20. Hello, guys! I'm trying to make use of gpio-poweroff procedure. I'm trying to understand the consequences of the approach I've used. Here's what I did 1) Added power_ctrl: power_ctrl { compatible = "gpio-poweroff"; gpios = <&pio 6 11 GPIO_ACTIVE_HIGH>; force; }; to arch/arm64/boot/dts/allwinner/sun50i-h5-nanopi-neo-plus2.dts 2) Recompiled the device tree blob and put it where it belongs The gpio-poweroff's code got probed but failed due to `pm_poweroff_handler` being set to something. So I figured it out that it's set to `psci_sys_poweroff` in [drivers/firmware/psci.c](https://github.com/friendlyarm/linux/blob/sunxi-4.x.y/drivers/firmware/psci.c#L518). 3) I commented this line out 4) Rebooted with a new kernel and issued `poweroff` on command line 5) The GPIO was driven high as expected 6) The board is switched off by external circuitry I'm very eager to know if this is an OK thing to do on an embedded system? It seems like I do something nasty. The only reasonable approach that comes to mind is to use some kind of chain of callbacks with GPIO poweroff handler's priority set to low. So that I could toggle GPIO and then use the PSCI logic to properly shutdown. But the RFC with this approach got rejected and nobody seems to be stepping in. Another solution is to make an ugly hack in gpio-poweroff.c and save the old callback to a variable and call it after gpio toggled. So what do you guys think?
  21. Hi I have the following question which I have asked both to someone from Armworks and also #friendlyelec on free node. I haven't got the solution but it has lead me towards the answer. So my problem is in not being able to get xserver running that it indicates the driver "sun8i-de2" can not be found. As far as I can find not having the driver is the entire problem, however I can't find where I can get it. Below I have posted my full problem below: I have been having problems getting things to display on the LCD display using Xserver. I have been successful displaying images using fbi though. The board the we have it the NanoPi-Neo Plus2. Currently we are attempting to get Xserver to on the nanoPi, we would like to use it so we can display a page we have created. We are trying to use chromium to display it. The problem occurs when trying to start Xserver, it indicates that it can not open the driver. I have searched the path it is looking for and it is not there. Though I did find drivers in another path, however the one it is looking for is not there and I can not find it online. The Method I used to setup everything is as follows: 1. run command "sudo apt-get install xserver-xorg xinit x11-server-utils unclutter chromium-browser" (Note: x11-server-utils didn't get the package so I just left that out for now) 2. add a file called /etc/X11/Xwrapper.config which contains "allowed_users=anybody" (this should allow any user to start xserver) 3. Add a .xinitrc file to my home folder that contains the following, which causes chromium to start on xserver unclutter & chromium-browser --window-size=1920,1080 --kiosk --incognito http://localhost:3000 Now to run it, I go to my home folder and use the command "startx", this produces the following outputs, which can be seen it gives mainly just errors relating to the "sun81-de2" driver failing to load. What I am hoping for is either a solution for this problem, do you know of any? The other thing that would help is a known method for getting xserver to run chromium on the nanoPi, even if it means installing a different set of packages. Thanks for your help in getting this to work! Let me know if there are any additional details you need in order to properly help.
  22. I am trying to setup a 5ghz access point on D-Link DWA-171(according to wikidevi, it's 8811au) + NanoPI NEO PLUS2. I use the testing armbian image with latest update. The hostapd can enable the 802.11a 5ghz AP mode with ht_enabled (but it says this chip doesn't support 802.11ac) I can see the SSID shows in the phone. If I try to connect it, it will fail and says the station is out of range. When the phone is trying to connect this AP, hostapd doesn't output any connection log even in debug mode. Also, although I set the channel to 40, the WIFI analyzer on the phone shows it is using 38. dmesg Hostapd config Hostapd log
  23. Hi, I've tried setting up an SD Card to boot from and I'm getting the strangest issues. I've tried multiple images and even compiled my own and I'm getting the same issue. I'm booting from SD Card because I have the stock ubuntu running on the emmc right now and I don't want to flash that until I know the image works the way I want it to. Here are the logs I've got from the console on boot. I followed the directions with 7z and Etcher from the documentation page. Thanks for the help! 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 mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3100 bytes read in 196 ms (14.6 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 143 bytes read in 158 ms (0 Bytes/s) ** File not found /boot/dtb/allwinner/sun50i-h5-nanopi-neo-plus2.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 529 ms (0 Bytes/s) Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 538 ms (0 Bytes/s) Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Error applying DT overlays, restoring original DT ** File not found /boot/dtb/allwinner/allwinner/sun50i-h5-nanopi-neo-plus2.dtb ** 5254590 bytes read in 528 ms (9.5 MiB/s) 12957704 bytes read in 897 ms (13.8 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 5254526 Bytes = 5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot.scr reading /boot.scr 850 bytes read in 20 ms (41 KiB/s) ## Executing script at 4fc00000 ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... Device 0: device type unknown ... is now current device ** Bad device usb 0 ** ** Bad device usb 0 ** No ethernet found. missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found No ethernet found. No ethernet found. =>
  24. FriendlyARM has recently launched a new board in its NEO family: NanoPi NEO Plus2 As of Armbian_5.32.170704_Nanopineo2_Ubuntu_xenial_dev_4.11.8.img, few things aren't working: out of 1GB RAM, only 512MB is visible the USB socket closer to the edge (USBN1) is not visible, even with overlays Wifi and Bluetooth are not visible (AP6212A) (it's not a complaint, but just a statement
×
×
  • Create New...