* Re: [Buildroot] kernel install from buildroot [not found] <mailman.3.1745064001.375107.buildroot@buildroot.org> @ 2025-04-19 15:26 ` Andreas Ziegler [not found] ` <CAN4Cwatp=c58JzpGD3SZS8692m0TtYd879jON2B7D_vn=PqJcA@mail.gmail.com> 0 siblings, 1 reply; 4+ messages in thread From: Andreas Ziegler @ 2025-04-19 15:26 UTC (permalink / raw) To: ct clmsn; +Cc: Buildroot Hi ct, On 2025-04-18 16:03, ct clmsn wrote: > > 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? Buildroot copies the final kernel image to output/images. In addition you need the content of output/target/lib/modules. Kind regards, Andreas > Thanks in advance for the assistance and confirming my > back-of-the-envelope > verification. > > v/r, > ct _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <CAN4Cwatp=c58JzpGD3SZS8692m0TtYd879jON2B7D_vn=PqJcA@mail.gmail.com>]
* Re: [Buildroot] kernel install from buildroot [not found] ` <CAN4Cwatp=c58JzpGD3SZS8692m0TtYd879jON2B7D_vn=PqJcA@mail.gmail.com> @ 2025-04-23 5:15 ` Andreas Ziegler 2025-04-23 12:06 ` ct clmsn 0 siblings, 1 reply; 4+ messages in thread From: Andreas Ziegler @ 2025-04-23 5:15 UTC (permalink / raw) To: ct clmsn; +Cc: buildroot Hi Chris, [re-added the mailing list] On 2025-04-22 14:07, ct clmsn wrote: > 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 > v/r, > Chris > > On Sat, Apr 19, 2025 at 11:26 AM Andreas Ziegler <br015@umbiko.net> > wrote: > >> Hi ct, >> >> On 2025-04-18 16:03, ct clmsn wrote: >> > >> > 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? >> >> Buildroot copies the final kernel image to output/images. In addition >> you need the content of output/target/lib/modules. >> >> Kind regards, >> Andreas >> >> > Thanks in advance for the assistance and confirming my >> > back-of-the-envelope >> > verification. >> > >> > v/r, >> > ct >> _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Buildroot] kernel install from buildroot 2025-04-23 5:15 ` Andreas Ziegler @ 2025-04-23 12:06 ` ct clmsn 0 siblings, 0 replies; 4+ messages in thread From: ct clmsn @ 2025-04-23 12:06 UTC (permalink / raw) To: Andreas Ziegler; +Cc: buildroot [-- Attachment #1.1: Type: text/plain, Size: 2441 bytes --] Excellent, just like the standard routine I'm familiar with - thanks! ct On Wed, Apr 23, 2025, 1:15 AM Andreas Ziegler <br015@umbiko.net> wrote: > Hi Chris, > > [re-added the mailing list] > > On 2025-04-22 14:07, ct clmsn wrote: > > 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 > > > v/r, > > Chris > > > > On Sat, Apr 19, 2025 at 11:26 AM Andreas Ziegler <br015@umbiko.net> > > wrote: > > > >> Hi ct, > >> > >> On 2025-04-18 16:03, ct clmsn wrote: > >> > > >> > 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? > >> > >> Buildroot copies the final kernel image to output/images. In addition > >> you need the content of output/target/lib/modules. > >> > >> Kind regards, > >> Andreas > >> > >> > Thanks in advance for the assistance and confirming my > >> > back-of-the-envelope > >> > verification. > >> > > >> > v/r, > >> > ct > >> > [-- Attachment #1.2: Type: text/html, Size: 3355 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] kernel install from buildroot @ 2025-04-18 20:03 ct clmsn 0 siblings, 0 replies; 4+ messages in thread From: ct clmsn @ 2025-04-18 20:03 UTC (permalink / raw) To: buildroot [-- Attachment #1.1: Type: text/plain, Size: 621 bytes --] 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 [-- Attachment #1.2: Type: text/html, Size: 784 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2025-04-23 12:06 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <mailman.3.1745064001.375107.buildroot@buildroot.org>
2025-04-19 15:26 ` [Buildroot] kernel install from buildroot Andreas Ziegler
[not found] ` <CAN4Cwatp=c58JzpGD3SZS8692m0TtYd879jON2B7D_vn=PqJcA@mail.gmail.com>
2025-04-23 5:15 ` Andreas Ziegler
2025-04-23 12:06 ` ct clmsn
2025-04-18 20:03 ct clmsn
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox