kernel install from buildroot

Hello,

This should be a pretty trivial question mostly asking to make sure my assumptions are correct.

I'm doing hardware testing with an SBC. I have an SBC that is configured to boot from an NVME-SSD. A vendor encouraged me to use buildroot to compile a new kernel. My preference would be to just update the existing environment on my SBC's NVME-SSD.

Given buildroot/output/target contains the compiled linux kernel with firmware, which directories or files should I be concerned with copying over on the NVME-SSD?

Thanks in advance for the assistance and confirming my back-of-the-envelope verification.

v/r,
ct

Andreas,

Thanks for the prompt response; looks like I miscommunicated the situation. I've build the kernel on the nvme-ssd that is running the kernel I'm hoping to replace with the buildroot compiled kernel. I'm expecting to just copy the portions from /boot, /lib/modules, and /lib/firmware from the buildroot/output/target directory into the appropriate places in the nvme-sdd's '/' (root) directory. Hope this clarifies the situation.

v/r,
Chris

Quoted 34 lines · Andreas Ziegler

Hi ct,

Quoted 14 lines · ct clmsn

Hello,

This should be a pretty trivial question mostly asking to make sure my assumptions are correct.

I'm doing hardware testing with an SBC. I have an SBC that is configured to
boot from an NVME-SSD. A vendor encouraged me to use buildroot to compile a
new kernel. My preference would be to just update the existing environment
on my SBC's NVME-SSD.

Quoted 3 lines

Given buildroot/output/target contains the compiled linux kernel with firmware, which directories or files should I be concerned with copying over on the NVME-SSD?

Buildroot copies the final kernel image to output/images. In addition you need the content of output/target/lib/modules.

Kind regards,
Andreas

Quoted 6 lines

Thanks in advance for the assistance and confirming my back-of-the-envelope
verification.

v/r,
ct

Hi Chris,

[re-added the mailing list]

Quoted 11 lines · ct clmsn

Andreas,

Thanks for the prompt response; looks like I miscommunicated the situation.
I've build the kernel on the nvme-ssd that is running the kernel I'm hoping
to replace with the buildroot compiled kernel. I'm expecting to just copy
the portions from /boot, /lib/modules, and /lib/firmware from the buildroot/output/target directory into the appropriate places in the nvme-sdd's '/' (root) directory. Hope this clarifies the situation.

lib/firmware is nice-to-have, but not mandatory; you can update linux-firmware independently of the kernel.

For a new kernel, you need bzImage and lib/modules/$(uname -r). The location of lib/modules is on the root partition. Depending on the boot configuration, bzImage may reside in /boot or on a separate boot partition. Check your grub.cfg.

If you keep the old kernel and create an additional boot entry for the new one, you have a fallback solution.

Kind regards,
Andreas

Quoted 23 lines

v/r,
Chris

Quoted 17 lines · Andreas Ziegler

Hi ct,

Quoted 14 lines · ct clmsn

Hello,

This should be a pretty trivial question mostly asking to make sure my assumptions are correct.

I'm doing hardware testing with an SBC. I have an SBC that is configured to
boot from an NVME-SSD. A vendor encouraged me to use buildroot to compile a
new kernel. My preference would be to just update the existing environment
on my SBC's NVME-SSD.

Quoted 1 line

Quoted 1 line

Quoted 1 line

Given buildroot/output/target contains the compiled linux kernel

with

Quoted 1 line

Quoted 1 line

Quoted 1 line

firmware, which directories or files should I be concerned with

copying

Quoted 15 lines

Quoted 15 lines

Quoted 1 line

over on the NVME-SSD?

Buildroot copies the final kernel image to output/images. In addition you need the content of output/target/lib/modules.

Kind regards,
Andreas

Quoted 6 lines

Thanks in advance for the assistance and confirming my back-of-the-envelope
verification.

v/r,
ct