Search the Community

Hello, I installed Retroarch from the repos, tried to install a "core" from the Retroarch updater but no cores were available. I searched about that if the installed version is too old no cores will be available, so I added the Retroarch ppa and installed the newest version, but got the same problem. Does Retroarch work under Armbian? Do I need to manually install "core" binaries? If so, where can I get them? Thanks.

My NanoPi M4V2 wont boot. It has a solid red light no green at all. I cant access it with SSH. I went through the troubleshooting checklist available for the NanoPi in regards to the red light. Nothing was solved. I tried different SD cards with different types of images and different types of burners. Nothing works. I know that the SD cards, images, and burners are not the problem cuz I tested it on a Raspberry Pi with no problems.

Hi I`m trying to set NAS server (OMV) on nanopi M4v2 with sata HAT and eMMC. I have instaled OMV but it is working realy slow and I want to make another clean install. I`m using Armbian Buster from here https://www.armbian.com/nanopi-m4-v2/ I`m tryng now for 4 hours to boot from fresh made SD card but I always end up on eMMC module. If I unplug module I can boot from SD card. I was trying Recovery key and PWR key combination but with no luck What can I try next. Thank you for help!

Hello! I have NanoPi M4 V2 4GB with EMMC installed (no sd card currently) and i got device bricked after installing updates. Here is the logs via TTL : Seems to be following errors are important: Loading Environment from EXT4... ** File not found /boot/boot.env ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC ERROR: Did not find a cmdline Flattened Device Tree FDT and ATAGS support not compiled in - hanging Guys please help! How can it be happened and how can i fix it? Thank you for advance!

Hello, I had a NanoPi M4v2 running 5.10.63 (buster) for a while without issue. Both I2C and SPI were working perfectly fine and the system was stable. Today apt updated the kernel to 5.15.25 and it broke multiple things, the first issue was that the network wasn't working properly, yellow light but not green one / no IP requested from the local DHCP server. The overlays on this system were: overlays=dwc3-0-host i2c7 i2c8 spi-spidev overlays=dwc3-0-host i2c7 i2c8 spi-spidev I connected the eMMC moule to a card reader and removed the overlays one by one and found out that `i2c8` was breaking my boot / network: overlays=dwc3-0-host i2c7 spi-spidev Although the rest of them weren't breaking anything they didn't work. SPI wasn't showing up under `/dev/spidev1.0` nor the remaining I2C devices. Important notes: Since the board wasn't connected to any network I was unable to create an armbian log or recover any further information; There seems to be a related issue with another board: https://forum.armbian.com/topic/20033-51525-breaks-spi-on-nanopi-neo-and-does-not-create-devspidev00 I tried a fresh image of "bullseye" and got the same issues as soon as I enabled the overlays; I ended up downgrading the kernel and everything is working fine now.

Got this error this morning doing apt upgrade! Not sure what the issue is, there seems to be plenty of space. _ _ ____ _ __ __ _ ___ ______ | \ | | _ \(_) | \/ | || \ \ / /___ \ | \| | |_) | | | |\/| | || |\ \ / / __) | | |\ | __/| | | | | |__ _\ V / / __/ |_| \_|_| |_| |_| |_| |_| \_/ |_____| Welcome to Armbian 21.08.5 Focal with Linux 5.10.63-rockchip64 Calculating upgrade... Done The following packages will be upgraded: armbian-bsp-cli-nanopim4v2 armbian-config armbian-firmware linux-libc-dev 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 9,657 kB of archives. After this operation, 126 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://armbian.tnahosting.net/apt focal/focal-utils arm64 armbian-bsp-cli-nanopim4v2 arm64 21.08.5 [419 kB] Get:3 http://mirror.12z.eu/pub/linux/armbian/apt focal/main arm64 armbian-firmware all 21.08.5 [7,933 kB] Get:2 http://armbian.tnahosting.net/apt focal/main arm64 armbian-config all 21.08.5 [126 kB] Get:4 http://mirror.12z.eu/pub/linux/armbian/apt focal/main arm64 linux-libc-dev arm64 21.08.4 [1,179 kB] Fetched 9,657 kB in 3s (3,863 kB/s) (Reading database ... 84278 files and directories currently installed.) Preparing to unpack .../armbian-bsp-cli-nanopim4v2_21.08.5_arm64.deb ... Unpacking armbian-bsp-cli-nanopim4v2 (21.08.5) over (21.08.3) ... Preparing to unpack .../armbian-config_21.08.5_all.deb ... Unpacking armbian-config (21.08.5) over (21.08.3) ... Preparing to unpack .../armbian-firmware_21.08.5_all.deb ... Unpacking armbian-firmware (21.08.5) over (21.08.3) ... Preparing to unpack .../linux-libc-dev_21.08.4_arm64.deb ... Unpacking linux-libc-dev:arm64 (21.08.4) over (21.08.2) ... Setting up linux-libc-dev:arm64 (21.08.4) ... Setting up armbian-bsp-cli-nanopim4v2 (21.08.5) ... Setting up armbian-config (21.08.5) ... Setting up armbian-firmware (21.08.5) ... Processing triggers for initramfs-tools (0.136ubuntu6.6) ... update-initramfs: Generating /boot/initrd.img-5.10.63-rockchip64 update-initramfs: Converting to u-boot format E: Write error - ~LZMAFILE (28: No space left on device) Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. pi@data:~$ df /tmp -h Filesystem Size Used Avail Use% Mounted on tmpfs 1.9G 4.0K 1.9G 1% /tmp pi@data:~$ df / -h Filesystem Size Used Avail Use% Mounted on /dev/mmcblk2p1 15G 4.1G 9.5G 30% /

Hello, I bought myself a NanoPi M4V2 and 4x SATA HAT for NanoPi M4, hoping to make a small home made server with some docker containers. I installed Armbian buster 5.10.21, downloaded from your site and managed to boot the OS from an attached SATA drive. I have some experience with linux (mostly Ubuntu/Debian), I own and I’ve played with Raspberry boards and I wrote small python scripts to work with GPIO on raspberry pi (how to blink a led or how to connect and display some text on an I2C 16x2 LCD). I thought that might be a nice project if I could connect an I2C LCD to nanopi and display some text text from python script, but here where I hit a brick wall. I found and read on this forum some discussion about user space GPIO, installing WiringPi, sysfs, tried them all, but none worked. Regarding user space GPIO, I have no idea where to start; sysfs seems to be deprecated (I don’t care), however I have no /sys/class/gpio/gpio50 (or any other pin); wiringpi has no Hardware line in /proc/cpuinfo and gpio readall responds with wiringPiSetup: Unknown model. I’ve managed to work with GPIO pins (from Python script) on FriendlyElec official OS and using WiringPi library, but I prefer Armbian because I can make it boot from SATA drive (which I don’t know if is possible with FriendlyElec OS). Let me know if you need more hardware infos and how I can get them for you. Thank you. Radu

Hello, I'm trying to use the NanoPi M4v2 SPI however it doesn't seem to work. I used armbian-config to enable the gpio overlay: [ ] dwc3-0-host [ ] i2c7 [ ] i2c8 [*] pcie-gen2 [ ] rk3328-opp-1.4ghz [ ] rk3328-opp-1.5ghz [ ] rk3399-opp-2ghz [ ] spi-jedec-nor [*] spi-spidev [ ] uart4 [ ] w1-gpio And the SPI isn't showing up on /dev: ls /dev/spi* ls: cannot access '/dev/spi*': No such file or directory Wasn't this enough to be able to use the SPI1 on this board? SBC: NanoPi M4V2 System: 5.10.35-rockchip64 #21.05.1 SMP PREEMPT Fri May 7 13:53:11 UTC 2021 aarch64 GNU/Linux Thank you.

Last week I updated the Armbian on my NanoPi M4V2 to the latest version (Armbian 21.08.1 Buster with Linux 5.10.60-rockchip64) and started noticing some issues with my Zigbee2MQTT local install. With the help of the Zigbee2MQTT main developer, we managed to confirm that the issue was reproducible on 5.10.60, but everything was working fine on previous kernels like 5.4. Other users not on Armbian (Raspbian) also confirmed that they were experiencing this problem with the latest kernel but was working fine on previous versions. We realized a bug was introduced for the CH341 driver in 5.10.60, that seems to have been fixed now on 5.10.62. The kernel bug is tracked here: https://bugzilla.kernel.org/show_bug.cgi?id=214131 Z2M is tracking that bug here: https://github.com/Koenkk/zigbee2mqtt/issues/8663 My question now is what can I do to fix this? Is there a way I can rebuild that driver or will this only go away with an upgrade of the kernel? What is the best course of action? Thanks in advance!!

I have a M4V2, and want to build a mini NAS with OpenMediaVault 5 under Armbian (OMV5 can only run under Armbiam/Debian, but not in Ubuntu) The M4V2 has a SATA hat, and it can support up to 4 hard drives (2.5 inches size), so the SATA hat is powered separately, and I guess this is why this hat always gets overheat. There is a 12V fan interface (2pin) on this SATA hat, just right biside the power button. And I found that there are already some solution in this forum, all kinds of scripts, can drive the Fan according to the CPU's temperature, or even SSD/HDD's temperature, this are so amazing. And then when I tried these scripts, I realized this PWM scripts won't solve the issue I am facing. bacause the SATA hat is getting heater and heater, whilr at this time the CPU's temperature remains in 100F, and the fan is not running. I guess if I can let the fan keep running in full speed, this issue would be solved. So I went to the FriendlyARM's Wiki page, and found they did provide a scrips to change working method of the FAN, here is the code: #!/bin/bash echo 0 > /sys/class/pwm/pwmchip1/export sleep 1 echo 0 > /sys/class/pwm/pwmchip1/pwm0/enable echo 50000 > /sys/class/pwm/pwmchip1/pwm0/period echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable echo 45000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle I have tried this script with the image name "Friendly Core" (branch of Ubuntu 18.04) image, it works fine. When system lights up, the fan will keep running, when system is done, the fan will shut down also. (before I have try the GPIO with another 5V fan, while in this case, the fan wont shutdown even the system is poweroff ) And now my problem is, this script can only run under Ubuntu, how can I make it available in Armbian also? Will be really appreciate to hear any response from you. Thanks, J.K.

Few days ago i saw an issue after i added rule to auto-reboot device once a day, every time it's reboot it's losses connection with sata hat - no more sata controler after typing "lspci" and some nasty output after "dmesg | grep pcie". I tried reboot manually, when i reboot just after powering on (like up to 2 min), pcie goes back up and there is no issue, but if device stay on for longer and i reboot it then there is pcie training issue and mervell sata controller don't get recognized anymore, further rebooting don't fix the problem, i even tried to connect drives power straight through SATA Hat, but it had changed nothing. The only fix is to shutdown device instead of reboot, after shutdown and powering it on using power button on hat or board itself (without physically disconnecting power to the board) its going up correctly with pcie visible. I searched here and there about this issues but i didn't saw anything helpful (some hardware issues related with nvme risers on rockpi forum, but it shouldn't be the case here because without rebooting hardware works great). Someone saw this issue before or know how to solve it ? Overall board works great, except of this issue and of crashing on mainline (at least when i tried it few months back, so thats why i'm staying with legacy, someone knows if it's already heve been fixed ?).

Hi all, unfortunately the USB power port on my Nanopi has broken off and I can't see a way to reattach it - it looks like it's just a push fit onto the board on 4 little tabs no solder involved no wonder it eventually fell off. I've heard that it's possible to power the Nano via the GPIO pins - anyone here done that ? I'm thinking I could make a cable to connect to the pins

Hello all, I have this board running in a k3s kubernetes cluster, and almost everyday, different time, the board reboots. Please, could you help me to figure out which is the problem? The armbianmonitor output is bellow: http://ix.it/2OOZ Many Thanks,

I have an FriendlyElec M4v2 board without eMMC card. (so i only use SD card) I tried this image: Armbian_21.02.1_Nanopim4v2_focal_current_5.10.12_desktop.img I Wrote to SD with Balena Etcher. After the new installation I turning on my board, I see my two attached .jpg file contents on the screen and after my screen flashes and immediately turns off my monitor (with no signal text on the screen) and if then I can only see Armbian again if I turn my monitor off and after on. So the Armbian is booting in the background, just need an HDMI channel refresh with a monitor physical off and after on. Then I installed all updates ('apt update' after 'apt upgrade') but it didn't help anything,,, ,,, in fact, it got worse because the system became unstable. The OS screen did not return to the monitor four times. I tried 6 times turns off the monitor and turn back on. I tried with Buster image,,, same problem. I tried the FriendElec images (FriendlyDesktop and Android10), all work well (so no hardware problem), only the two Armbian images do not (Focal and Buster). Please write me how I can solve it so that after I turn on my board the next image should be on the Armbian login screen without monitor turn off-on. I made a short video, maybe it can help: ' Before updates, Newly installed system, second power on.avi ' https://www.dropbox.com/s/8m72sm1a2t5guk5/Before updates%2C Newly installed system%2C second power on.avi?dl=1 left photo = Newly installed system Before updates.jpg right photo = Newly installed system After all updates.jpg

Hi, I have troubled to set an u-boot environment variable of NanopiM4V2. I have tried changing the rootdelay parameter by making /etc/fw_env.config file. However, I don't know how to get the number I have to write in it. NanopiM4V2 is booted from microSD card. ("cat /proc/mtd" is none) If anyone know how to set the /etc/fw_env.config file with booting from microSD card??

Hi, My Nanopi M4V2 often gets unresponsive. I cannot reach the nginx server when that happens. SSH also stops working. The red led is on, and the green led stops blinking when it happens. Any tips on what I can try? Running: Armbian buster with Linux 5.4.49-rockchip64 with heatsink from EMMC. http://ix.io/2u4O

Hello. I'm using a NanoPi M4V2 with 4GB of LPDDR4. Before installing Armbian, I tried FriendlyElec and the total amount of 4GB of RAM was detected. When moving to Armbian Buster with kernel 5.9.14-rockchip64, the system is detecting only 2GB of RAM (MemTotal: 1964780 kB). I searched the forum to see if anyone else was having this problem but strangely I found no more reports of this issue. I also tried Armbian Focal, but the problem remains. Thank you.

What am I missing ? Just flashed Armbian_20.11.7_Nanopim4v2_buster_legacy_4.4.213_desktop on a SD card and the NanoPi does not boot. I get a steady red led and no flashing green and nothing on the HDMI. I don't get that problem when Flashing the eMMC...the problem is that I don't have that eMMC anymore and I am looking for a way to install Armbian on my NanoPi's NVMe SSD drive from the SD card. Any hints would be appreciated.

To try the new goodies I've tried to install Buster Legacy on my M4V2 but it always hung on [---] A start job is running for Bluetooth Rockpi (many minutes / no limit) https://redirect.armbian.com/region/EU/nanopim4v2/Buster_legacy_desktop I downloaded it multiple times and no change. I'll try the mainline image and then regress kernel to legacy.

I don't know if it's of any use. Just noticed this issue of reboot not working on Buster legacy. Seems to be hdmi related. When I pull out hdmi for a few seconds then it does start booting. I remember this used to be the same on bionic mainline. Don't know why it's here now. I'm on NanoPi M4V2.

My NanoPi M4V2 is currently being used completely headless just to run a few Docker containers (AdGuard Home, Home Assistant, Zigbee2Mqtt, etc.) and I've been noticing more and more crashes happening... sometimes they occur while I have an open SSH terminal, and I get a glimpse of a "kernel panic" type error... Here's the output from armbianconfig: http://ix.io/2vFX Any ideas on what this is or how to fix it? Thanks in advance!

I have installed Armbian distrubution focal i am running with boot from sd and system on nvme I installed gnome disks and i did a benchmark. drive/ model number Transcend 512GB NVMe PCIe Gen3 x4 MTE220S M.2 TS512GMTE220S advertised speeds 3100 read/2100 write The results where as followed: 750 mbs read >>>inline with epectations 150 mbs >>> way below expectations for the drive is there a atch availeble?

I have a new nanopi m4v2 and I downloaded the latest focal version today Armbian_20.08.1_Nanopim4v2_focal_current_5.8.6_desktop.img.xz Boots with uboot successfully, but after showing the message "Starting kernel ...", serial is blank. Green SYS LED glows couple of times and then both LEDs are off. I assume the system has powered off as there are no more signs of being up. I am using the usbttl from friendly elec and a samsung EVO 32G microsd. I am attaching the last uboot logs until "start kernel ..." msg Any clue as to why the board is not booting? m4v2_uboot_log.txt

I am thinking to buy NanoPi M4v2 and i want to use with nvme SSD. RockPi 4 support Gen 2.0. What about NanoPi? NanoPi only support Gen1? And what is the maximum theoretical speed for nvme SSD on NanoPi M4v2 ? I am between NanoPi M4v2 vs RockPi 4 and NanoPc T4. I like NanoPi M4 design and box, I don't like rock pi ssd hat and box, and NanoPc price is expensive, not compact like NanoPi, ram is LPDDR3 others LPDDR4, but x4 lane and support Gen 2.1 is good. I am so confused..

Hi all, today I used rsync to copy some music files from an attached USB drive to my NVME M2 SSD drive and noticed the Nanopi was getting very hot. I have it housed in an official metal case with a fan. The fan didn't come on despite the temperature of 80 + , the case was very hot to the touch. I turned it off in the end in case it got damaged. Any suggestions appreciated. The board is running the latest Buster from here.