Optionally, archive the installed kernel modules:
$ cd <modules_install_path>
$ tar --owner root --group root -cjf kernel_supplements.tbz2 lib/modules
You can use the installed modules to provide the contents of /lib/modules/<kernel_version>/ on the target system. Before you run apply_binaries.sh, make a copy of this archive to replace the one at this location on the target device:
Linux_for_Tegra/kernel/kernel_supplements.tbz2
I do have modules.order and modules.builtln in both Linux_for_Tegra/kernel/kernel_supplements.tbz2(host machine) and
/lib/modules(target machine)
May I know what’s your use case to disable all dmesg during boot?
It is optional. It is used to allow you package kernel module manually.
Please just copy kernel Image.
Please find the lines you don’t want to have and customize them in kernel source.
e.g.
If you want to remove the messages of “[7.767125] using random self ethernet address”.
You can just remove or customize the following line in ether.c
if (!gether_set_host_addr(net, host_addr))
pr_info("using host ethernet address: %s", host_addr);
if (!gether_set_dev_addr(net, dev_addr))
pr_info("using self ethernet address: %s", dev_addr);
just dont want our customer seeing these dmesg, I tried to search depmod: WARNING or SELinux with vscode search in kernel source folder, but could not find a match
Are those messages showing on the display during boot up and you don’t want the customer see them?
If so, I would suggest just disabling the framebuffer feature through the following kernel config.
