Raylynn Knight

Thank you for this! Works great on my NanoPi NEO Black. Will be updating a couple of Nano Pi NEO and NEO2 from FriendlyARM to Armbian using this also! Ray

What I find confusing is that both instances of U-Boot report the same version and compile date. Only a slight difference in compile time! Is it actually two different versions of the source code, or different configurations? Ray

I have a 1 GB Renegade board and downloaded Armbian_19.11.3_Renegade_buster_current_5.3.11 image to install. Noticed it was only 510MB of RAM. Relevant extracts from serial log: U-Boot 2017.09-armbian (Nov 19 2019 - 00:09:05 +0100) Model: Firefly ROC-RK3328-CC DRAM: 510 MiB ____ _ | _ \ ___ _ __ ___ __ _ __ _ __| | ___ | |_) / _ \ '_ \ / _ \/ _` |/ _` |/ _` |/ _ \ | _ < __/ | | | __/ (_| | (_| | (_| | __/ |_| \_\___|_| |_|\___|\__, |\__,_|\__,_|\___| |___/ Welcome to Armbian Buster with Linux 5.3.11-rockchip64 System load: 0.10 0.14 0.06 Up time: 2 min Memory usage: 22 % of 472MB IP: 192.168.11.175 CPU temp: 44°C Usage of /: 5% of 29G [ General system configuration (beta): armbian-config ] Last login: Sat Nov 23 22:48:50 2019 Using armbian-config I downgraded to kernel 4.4.198 and I now have 919MB of RAM. U-Boot 2017.09-armbian (Nov 19 2019 - 00:01:47 +0100) Model: Firefly ROC-RK3328-CC DRAM: 1022 MiB ____ _ | _ \ ___ _ __ ___ __ _ __ _ __| | ___ | |_) / _ \ '_ \ / _ \/ _` |/ _` |/ _` |/ _ \ | _ < __/ | | | __/ (_| | (_| | (_| | __/ |_| \_\___|_| |_|\___|\__, |\__,_|\__,_|\___| |___/ Welcome to Armbian Buster with Linux 4.4.198-rockchip64 System load: 0.10 0.09 0.03 Up time: 2 min Memory usage: 8 % of 919MB IP: 192.168.11.173 CPU temp: 43°C Usage of /: 5% of 29G [ General system configuration (beta): armbian-config ] Ray

Perhaps the documentation should be update to prevent hours of frustration for those of us trying to use Vagrant on MacOS! This all used to work just fine on MacOS until recently.

I currently have installed "linux-u-boot-beelinkx2-next 5.34.171121" which boots and runs correctly. apt upgrade is offering "linux-u-boot-beelinkx2-next/stretch 5.37.180119 armhf [upgradable from: 5.34.171121]" which I know from experience will result in an un-bootable situtation.

I've been using a Beelink X2 with Armbian for some time now booting from eMMC. I ran an "apt update; apt upgrade" on the box early on 01/14/2018 and a reboot was suggested at the end. The system did not successfully reboot after this update and it appears that it doesn't recognize uboot on the eMMC. At the time I had other pressing matters so I set it aside to work on today. Today I downloaded the latest image Armbian_5.34.171121_BeelinkX2_Debian_stretch_next_4.13.14_desktop.img, verified it and successfully wrote the image to a 16GB microSD card. This successfully booted the X2, I then did an "apt update; apt upgrade" on the microSD card and rebooted. This then resulted in an un-bootable SD card! Something in the latest update is causing an issue with uboot on the X2. I'm now rewriting the original image to the microSD and will attempt to determine what update is causing the issue!

I ran into this issue after downloading ARMBIAN 5.27 mainline Ubuntu Xenial image. I created an image on a SD card, booted the SD card and then ran the nand-sata-install script to install to the eMMC card on my XU4. After this finished the device didn't appear to boot any longer. I have the USB-UART cable so I connected that and was able to determine that the old uboot was still trying to load the kernel image from a non-existant FAT partition. My forum search turned up this thread. I first tried the "run copy_uboot_sd2emmc" command, but this didn't work because the new uboot no longer contains the script. So reading further I saw the message above from Voiter and solved the issue by rebooting from the SD card, halting the boot script and at the uboot prompt running the following command: mmc dev 0; mmc read 0x50000000 0x1 0xa3e; mmc dev 1 1; mmc write 0x50000000 0x0 0xa3e; mmc dev 1 0 I was then able to switch the boot mode back to eMMC and successfully boot. So adding a copy_uboot_sd2emmc script with the above command should suffice in helping to resolve this issue.