hanni76 Posted June 5, 2017 Posted June 5, 2017 Hello guys, I built OS with legacy kernel for Orange Pi One using github framework https://github.com/armbian/build . Everything went fine and I got a resulting img file. I copied it to 16GB SD card (7Samsung EVO class 10) and powered up my device but it couldn't start. Below is the log I got from UART console. You can see from it that my device was retrying boot sequence over and over unsuccessfully. Can you help with the problem, please ? P.S. I also built Armbian with mainline kernel and it loaded fine, i.e. problem exists only with legacy kernel ------------------------------------------------------------------------------------------- U-Boot 2017.05-armbian (Jun 05 2017 - 15:22:02 +0300) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi One DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 38518 bytes read in 144 ms (260.7 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 3565 bytes read in 196 ms (17.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 115 bytes read in 156 ms (0 Bytes/s) 5172433 bytes read in 520 ms (9.5 MiB/s) 4805832 bytes read in 520 ms (8.8 MiB/s) Found legacy kernel configuration 34704 bytes read in 476 ms (70.3 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5172369 Bytes = 4.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 512MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2c00081! ion_reserve_common: ion reserve: [0x56000000, 0x60000000]! Loading, please wait... starting version 229 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.27.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1 has unsupported feature(s): metadata_csum e2fsck: Get a newer version of e2fsck! fsck exited with status code 8 done. Warning: File system check failed but did not detect errors mount: mounting /dev/mmcblk0p1 on /root failed: Invalid argument done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 No init found. Try passing init= bootarg. Rebooting automatically due to panic= boot argument -----------------------------------------------------------------------------------------------------------------
Recommended Posts