Unable to flash after kernel config disable

[WayneWWW]

refer to this post. Basically the same situation.

Can Jetson orin nx 8g disable CONFIG_PCI_IOV in kernel config?

No, there is no document. Only some modules are located in initrd. initrd image is under Linux_for_Tegra/bootloader mkdir initrd; cd initrd; sudo gunzip -c …/l4t_initrd.img.orig | sudo cpio -i → update the files you want to update sudo find . | sudo cpio --quiet -H newc -o | sudo gzip -9 -n > …/l4t_initrd.img

[bharath.gk]

thanks for the inputs @WayneWWW .

[bharath.gk]

Hello @WayneWWW ,

sorry, still we getting same error, as in attached screenshot in previous message,
below are the steps we followed to do config changes and update Kernel Image and modules.

1. after making below changes in config file
   CONFIG_DEBUG_KERNEL=n
   CONFIG_FTRACE=n
   CONFIG_TRACING=n

2. build kernel:
   ====================
   $ export CROSS_COMPILE=/home/bharath.gk@happiestminds.com/36.3/l4t-gcc/aarch64–glibc–stable-2022.08-1/bin/aarch64-buildroot-linux-gnu-
   $ make -C kernel

$export INSTALL_MOD_PATH=/Linux_for_Tegra/rootfs
$sudo -E make install -C kernel
$cp kernel/kernel-jammy-src/arch/arm64/boot/Image /Linux_for_Tegra/kernel/Image

for above config changes in point 1 do we need to do that initrd update? if yes then we wounder how it was working for other config changes.
considering ur suggestion, what more commands we can add in between the highlighted palce in below pic.

[WayneWWW]

HI,

Just to clarify. You should think more on your side… these are not difficult things.

Initrd has some ko files inside of it and they are in use when doing initrd flash.

If you rebuild the kernel image and causes error, it means your kernel image is updated, but your kernel modules are not.

What you need to do now is check what ko files are under initrd and you need to put your newly-built ko files to replace them…

[bharath.gk]

yeah @WayneWWW , we already doing it from our side, we followed the same steps which are provided in official documentation for kernel update, weather it is easy/difficult task steps should be followed right?
without steps mentioned its hard to proceed for us.

FYI: In our case we are not adding any new kernel modules, instead we are removing. but you are asking remove, please clarify where to remove and what to remove.’

and for other kernel changes without initrd changes, we are able to flash and see the changes, we worried only about these DEBUG, TRACING and FTRACE disable.

[WayneWWW]

I didn’t ask you to remove anything.

The issue here is kernel image and kernel modules are paired. Already explained this multiple times.

The problem seems to be you just updated kernel image but not modules.

When doing initrd flash, those modules are loaded from initrd but not rootfs. What we suspect here is the ko files in initrd didn’t get updated.

What you need to do now is just unpack the initrd and search what ko files are under there and replace them with the newly-built ko files built along with your new kernel image…

[WayneWWW]

If you still cannot get my point, unpack your initrd image first, enter to it and go to the lib/modules path.

[bharath.gk]

we got your point, do you meen repalce all these .ko modules?

[bharath.gk]

Hello @WayneWWW, even after applying the suggestions we facing the same issue while flashing,

we guess its something related to partition size, we are, from the first comment also i have attached the screenshot, there also seeing some size related error as below screenshot

please clarify if its same or something else.

FYI: this timewe did config changes
CONFIG_EXPERT=y
-CONFIG_FRAMEBUFFER_CONSOLE=y
+CONFIG_FRAMEBUFFER_CONSOLE=n

does above CONFIG_EXPERT enabling has any impact on this error?