weyou

Found the same bug on RockPi4, the solution "Cost: 10" does switch the compress method from "lz4" to "gz". but just like @blood said, it doesn't make any difference, the "apt search" still very slow.

Thank you. I have figure it out from an topic about pine64. I modified and recompiled the boot.cmd. Now everything is Okay.

My RPi PC2 was flashed the armbian OS which was downloaded from the main page ARMBIAN about 3 months ago. Yesterday, I found some packages update are available with "apt update". So I did the command "apt upgrade" . But from then on, the board never be boot up. From the console, the U-Boot version has been upgraded to 2017-09-rc4 from the old version 2017.01-rc1-g5df570f-dirty. I'd appreciate it if anyone could help with this or give me some suggestion. U-Boot SPL 2017.09-rc4-armbian (Sep 11 2017 - 03:34:11) DRAM: 1024 MiB Trying to boot from MMC1 NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):aa75c8d NOTICE: BL3-1: Built : 03:34:04, Sep 11 2017 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 2017.09-rc4-armbian (Sep 11 2017 - 03:34:11 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: OrangePi PC 2 DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 38518 bytes read in 132 ms (284.2 KiB/s) Unknown command 'bmp' - try 'help' switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3362 bytes read in 190 ms (16.6 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 116 bytes read in 159 ms (0 Bytes/s) ** File not found /boot/dtb/allwinner/allwinner/sun50i-h5-orangepi-pc2.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 4179 bytes read in 409 ms (9.8 KiB/s) Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 44000000 5681602 bytes read in 488 ms (11.1 MiB/s) 12285960 bytes read in 894 ms (13.1 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 5681538 Bytes = 5.4 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... 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 Device 0: device type unknown ... is now current device ** Bad device usb 0 ** ** Bad device usb 0 ** BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 BOOTP broadcast 4 BOOTP broadcast 5 BOOTP broadcast 6 BOOTP broadcast 7 BOOTP broadcast 8 BOOTP broadcast 9 BOOTP broadcast 10 BOOTP broadcast 11 BOOTP broadcast 12 BOOTP broadcast 13 BOOTP broadcast 14 BOOTP broadcast 15 BOOTP broadcast 16 BOOTP broadcast 17 Retry time exceeded; starting again missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-01-b3-6f-d0-61 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default *** ERROR: `serverip' not set Config file not found BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 BOOTP broadcast 4 Abort BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 BOOTP broadcast 4 Abort

I got an new SD card today. At first, I flashed the latest nightly build of armbian. Reboot it with "reboot" command or power cycle multiple times. The same issue happened again and again. The probability of occurrence is about 60%. Then, I flashed the stock image Debian_Server_jessie_PC2_V0_9_1.img which is downloaded from the office website of OPi. Reboot the OPi PC2 20 times, every time it can boot up successfully. Does this mean the u-boot used by armbian has some issue?

Thank you, joselalf. I will try to order the recommended AC adapter If I failed the SD card replacement.

I'm using the Samsung/RaspberryPi chargers with a USB to barrel connector cable. I didn't use the OTG(MicroUSB) interface .

I will try to find another mircoSD to write a new image. Will report back later. Thanks for your help.

I have tested it with a power supply of raspberry pi (5v/1.5a). But still get the same issue. I also measured the electric current is about 300mA during the system boot. Even during the stress test (stress -c 4 -i 4 -m 2), the peak current is less than 600mA. I find another phenomenon: If the uboot has about 3 second pause after printing "Trying to boot from MMC1". it will get stuck at the statement "INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9" later. For a success boot up, there is no pause after printing "Trying to boot from MMC1".

Thank you. I will try to change a new power supply. I was not intent to making multiple posts, it was just an accident Maybe my network issue, the edit page didn't have any response after my first clicking on the submit button. So I clicked twice... And I didn't find how to delete the duplicate one.

I got my OPi PC2 last week and flashed the latest armbian server version. Every time I enter "reboot" on SSH to reboot the system, or plug in the power cable. The system can not boot up with a great probability. My power source is the charger for SAMSUNG smartphone. The specification indicates it can provide 5V/2A current. With the UART, I found the uboot process was stuck after the statement "INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9". The LED is OFF in that moment. After plugging out/in the power cable multiple times, the system can be boot up successfully finally and works very well. I'd like to know anyone has the same problem? How can I solve this issue?