After creating my own initramfs using this command from a chroot-ed environment

sudo update-initramfs -t -u -k `uname -r`

 

And rebooting, I get the following error:

Found U-Boot script /boot/boot.scr
3708 bytes read in 126 ms (28.3 KiB/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
202 bytes read in 80 ms (2 KiB/s)
5731772 bytes read in 668 ms (8.2 MiB/s)
6790944 bytes read in 759 ms (8.5 MiB/s)
Found legacy kernel configuration
** File not found /boot/script.bin **
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5731708 Bytes = 5.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
EHCI failed to shut down host controller.
   Loading Ramdisk to 49a88000, end 49fff57c ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x42000820).

Available machine support:

ID (hex)        NAME
ffffffff        Generic DT based system
ffffffff        Allwinner sun9i Family
ffffffff        Allwinner sun8i Family
ffffffff        Allwinner sun7i (A20) Family
ffffffff        Allwinner sun6i (A31) Family
ffffffff        Allwinner sun4i/sun5i Families

Please check your kernel config and/or bootloader.

 

I chroot from a SD card with Armbian 5.35.installed to a eMMC with armbian 5.35 installed, with an encrypted LUKS partition (and a boot ext4 partition containing my boot files, including the initramfs).

 

I am missing something but could not find it.

 

What is the right way to update initrd ?

 

53 minutes ago, lauhub said:

Found legacy kernel configuration ** File not found /boot/script.bin **

Are you booting legacy 3.4.y kernel? Then lack of script.bin is a problem.

Thanks for your answer

 

No it is 4.13.x kernel compiled on November 29

50 minutes ago, lauhub said:

Thanks for your answer

 

No it is 4.13.x kernel compiled on November 29

I assume you are using your own build?

 

11 minutes ago, Igor said:

I assume you are using your own build?

Yes

I completely erased the eMMC and re-installed everything: it now works

 

As I have modified partitions I may have destroyed something while using fdisk with a wrong value

 

I noticed that the first sector of boot partition had changed to 8192

 

Is there a reason for that ?

 

Is it still a right way to re-install u-boot using the following command ?

dd if=/usr/lib/linux-u-boot-next-lime2_5.35_armhf/u-boot-sunxi-with-spl.bin of=/dev/mmcblk1 bs=1k seek=8