i.MX8MP initramfs failed to take effect in kernel

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

i.MX8MP initramfs failed to take effect in kernel

1,589件の閲覧回数
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.

ラベル(1)
0 件の賞賛
返信
2 返答(返信)

1,561件の閲覧回数
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 件の賞賛
返信

1,551件の閲覧回数
jimmyli
Contributor IV

Hi Harvey,

      Get it.

      Thanks very much.

      I will try as your suggestion.

0 件の賞賛
返信