i.MX8MP initramfs failed to take effect in kernel

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

i.MX8MP initramfs failed to take effect in kernel

1,581 Views
jimmyli
Contributor IV

Hi,

      Below is my steps to build initramfs on i.mx8mp platform, but failed.

      Can you help to check and fix it ?

      Thanks very much.

1>Steps:

a. Create initramfs file directory,using busybox init to boot;

b. Make initramfs file system;

     find ./initramfs | cpio -H newc -o | gzip -9 -n > ./initramfs.cpio.gz

c. Copy initramfs.cpio.gz to kernel project in usr file

d. Open kernel initramfs configuration;

e. Build the kernel

    make Image -j30

 

2>File Tree:

root@Ubuntu-X64:/mnt/rfs# ./tree initramfs

initramfs

├── bin

   ├── ash -> busybox

   ├── busybox

   ├── cat -> busybox

   ├── chmod -> busybox

   ├── cp -> busybox

   ├── date -> busybox

   ├── dd -> busybox

   ├── df -> busybox

   ├── dmesg -> busybox

   ├── echo -> busybox

   ├── false -> busybox

   ├── getopt -> busybox

   ├── grep -> busybox

   ├── gzip -> busybox

   ├── hostname -> busybox

   ├── kill -> busybox

   ├── ln -> busybox

   ├── login -> busybox

   ├── ls -> busybox

   ├── lsof -> busybox

   ├── mkdir -> busybox

   ├── mknod -> busybox

   ├── more -> busybox

   ├── mount -> busybox

   ├── mv -> busybox

   ├── netstat -> busybox

   ├── nice -> busybox

   ├── ping -> busybox

   ├── ping6 -> busybox

   ├── ps -> busybox

   ├── pwd -> busybox

   ├── rm -> busybox

   ├── sed -> busybox

   ├── sh -> busybox

   ├── sleep -> busybox

   ├── switch_root -> busybox

   ├── sync -> busybox

   ├── tar -> busybox

   ├── touch -> busybox

   ├── true -> busybox

   ├── umount -> busybox

   ├── uname -> busybox

   ├── usleep -> busybox

   └── vi -> busybox

├── boot

├── config

├── data

├── dev

   ├── console

   └── null

├── etc

   ├── group

   ├── gshadow

   ├── host.conf

   ├── hosts

   ├── init.d

   │   ├── rcS

   │   └── udev-post

   ├── inittab

   ├── moduli

   ├── nsswitch.conf

   ├── passwd

   ├── profile

   ├── resolv.conf

   ├── shadow

   ├── shells

   ├── ssh_config

   ├── sshd_config

   ├── sysctl.conf

   └── udev

       ├── rules.d

       └── udev.conf

├── home

├── init -> bin/busybox

├── lib

   ├── libc-2.33.so

   ├── libc.so.6 -> libc-2.33.so

   ├── libm-2.33.so

   ├── libm.so.6 -> libm-2.33.so

   ├── libresolv-2.33.so

   └── libresolv.so.2 -> libresolv-2.33.so

├── media

├── mnt

├── phone

├── proc

├── run

├── sbin

   └── init

├── sys

├── tmp

├── usr

   ├── bin

   ├── driver

   ├── lib

   ├── sbin

   ├── scripts

   │   └── init.sh

   └── share

└── var

 

Note: attachments are relevant config and boot log.

Labels (1)
0 Kudos
Reply
2 Replies

1,553 Views
Harvey021
NXP TechSupport
NXP TechSupport

Hi @jimmyli 

According to the Kernel panic, suggest to check the followings:

if build the fs for the partition on a Linux OS or not.

if the partition (mmcblk2p7) is correctly set as root or not.

 

Best regards

Harvey

 

 

0 Kudos
Reply

1,543 Views
jimmyli
Contributor IV

Hi Harvey,

      Get it.

      Thanks very much.

      I will try as your suggestion.

0 Kudos
Reply