I've loaded Armbian onto my Udoo Dual and am having issues getting it past starting the kernel. I really like this OS on my other sbc's and have had no issues before this. I'm mostly a Linux noob with an elementary grasp of compiling the kernel. I have had this problem for about a week and am finally asking the pro's on how to fix this. Any help would GREATLY appreciated. Below is what I get from the U-Boot startup. Thanks!
U-Boot SPL 2015.10-armbian (Jun 13 2017 - 15:51:16)
U-Boot 2015.10-armbian (Jun 13 2017 - 15:51:16 +0200)
CPU: Freescale i.MX6DL rev1.1 at 792 MHz
Reset cause: POR
Board: UDOO DualLite
DRAM: 1 GiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment
auto-detected panel HDMI
Display: HDMI (1280x720)
In: serial
Out: serial
Err: serial
Net: using phy at 6
FEC [PRIME]
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc
Found U-Boot script /boot.scr
** File not found /boot.scr **
** Unrecognized filesystem type **
Found U-Boot script /boot/boot.scr
1757 bytes read in 99 ms (16.6 KiB/s)
Running bootscript from mmc ...
## Executing script at 12000000
Booting from SD
** File not found /boot/armbianEnv.txt **
** Unrecognized filesystem type **
4765629 bytes read in 363 ms (12.5 MiB/s)
6234592 bytes read in 440 ms (13.5 MiB/s)
0 bytes read in 70 ms (0 Bytes/s)
37690 bytes read in 393 ms (92.8 KiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x5f21e0 ]
## Loading init Ramdisk from Legacy Image at 14800000 ...
Image Name: uInitrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 4765565 Bytes = 4.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800c339
Starting kernel ...
Question
Tyler Vaught
I've loaded Armbian onto my Udoo Dual and am having issues getting it past starting the kernel. I really like this OS on my other sbc's and have had no issues before this. I'm mostly a Linux noob with an elementary grasp of compiling the kernel. I have had this problem for about a week and am finally asking the pro's on how to fix this. Any help would GREATLY appreciated. Below is what I get from the U-Boot startup. Thanks!
Link to comment
Share on other sites
5 answers to this question
Recommended Posts