From: Andreas Ziegler <br015@umbiko.net>
To: ct clmsn <ct.clmsn@gmail.com>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] kernel install from buildroot
Date: Wed, 23 Apr 2025 05:15:03 +0000 [thread overview]
Message-ID: <cf10fd11d7fe76e4614eb2a6d401fd4c@umbiko.net> (raw)
In-Reply-To: <CAN4Cwatp=c58JzpGD3SZS8692m0TtYd879jON2B7D_vn=PqJcA@mail.gmail.com>
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
next prev parent reply other threads:[~2025-04-23 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2025-04-23 12:06 ` ct clmsn
2025-04-18 20:03 ct clmsn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf10fd11d7fe76e4614eb2a6d401fd4c@umbiko.net \
--to=br015@umbiko.net \
--cc=buildroot@buildroot.org \
--cc=ct.clmsn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox