08-10-2020, 02:40 AM
Probably a boot-loader problem.
I tried using another boot-loader (mainline-base).
As a result, it starts normally as follows.
I tried using another boot-loader (mainline-base).
As a result, it starts normally as follows.
Code:
=> run bootcmd_mmc1
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
890 bytes read in 5 ms (173.8 KiB/s)
## Executing script at 00500000
37171712 bytes read in 1612 ms (22 MiB/s)
50174 bytes read in 11 ms (4.3 MiB/s)
8339435 bytes read in 367 ms (21.7 MiB/s)
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f9f21000, end fa714feb ... OK
Loading Device Tree to 00000000f9f11000, end 00000000f9f20fff ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.8.0-1-ARCH (builduser@leming) (aarch64-unknown-linux-gnu-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34) #1 SMP Sun Aug 9 00:03:44 UTC 2020
[ 0.000000] Machine model: Pine64 Rock64
[ 0.000000] earlycon: uart8250 at MMIO32 0x00000000ff130000 (options '')
[ 0.000000] printk: bootconsole [uart8250] enabled
[ 0.000000] efi: UEFI not found.
[ 0.000000] cma: Reserved 64 MiB at 0x00000000fb000000
[ 0.000000] Zone ranges:
...
Arch Linux 5.8.0-1-ARCH (ttyS2)
alarm login:
root@alarm:~# uname -a
Linux alarm 5.8.0-1-ARCH #1 SMP Sun Aug 9 00:03:44 UTC 2020 aarch64 GNU/Linux
