# In-place updates: kernel, firmware etc **URL:** \ **Category:** NXP LX2160\ **Created:** [December 6, 2021, 12:25am UTC](https://community.solid-run.com/t/in-place-updates-kernel-firmware-etc/200 "2021-12-06T00:25:23Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![alex9373](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alex9373](https://community.solid-run.com/u/alex9373)\ **Post date:** [December 6, 2021, 12:25am UTC](https://community.solid-run.com/t/in-place-updates-kernel-firmware-etc/200/1 "2021-12-06T00:25:23Z")
Hi In Honeycomb with the Ubuntu supplied from the built images, I’m free to update the userland (have updated to Ubuntu 21.10, and plan to update to 22.04 LTS next year). [SFP+ - What am I looking for? - #5 by jnettlet](https://community.solid-run.com/t/sfp-what-am-i-looking-for/193/5) explains that kernel 5.14 will natively support the network hardware (5.13 is the latest available in Ubuntu 21.10). I can re-build an image and deploy onto the machine using [GitHub - SolidRun/lx2160a\_build: Scripts to build basic images for LX2160A COM express type 7 modules](https://github.com/SolidRun/lx2160a_build). This would wipe out my installation. So, my question is about in-place updates for both the firmware and the kernel. I can build the UEFI firmware from [GitHub - SolidRun/lx2160a\_uefi: Parent build repository for generating UEFI firmware for the LX2160a](https://github.com/SolidRun/lx2160a_uefi)? Not sure how the image then gets installed. For the kernel do I need one of the tags in [Commits · SolidRun/linux-stable · GitHub](https://github.com/SolidRun/linux-stable/commits/master)? ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [December 6, 2021, 7:11am UTC](https://community.solid-run.com/t/in-place-updates-kernel-firmware-etc/200/2 "2021-12-06T07:11:33Z")
I believe you are mixing two separate OS support methods. You can either use lx2160a\_build which is a reference BSP based on NXP’s board support package. It boots with u-boot and then uses device-tree with a custom BSP kernel. This has been integrated with Ubuntu to provide initial support that customers can use to test and validate their hardware. A quick get up and running, however this is not expected to follow Ubuntu’s development cycle. Our edk2 based firmware image is our SystemReady ES firmware that is intended to boot off the shelf distros. This does require mainline kernel support before patches will filter down into the recent distros. If you would like to track the latest distro releases then I would recommend you use a standard distro install and then use one of the community package repositories that bundle the kernel and other specific patched software that is not merged into mainline yet. ---
**Author:** ![alex9373](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alex9373](https://community.solid-run.com/u/alex9373)\ **Post date:** [December 7, 2021, 12:40pm UTC](https://community.solid-run.com/t/in-place-updates-kernel-firmware-etc/200/3 "2021-12-07T12:40:23Z")
Ah - I wasn’t aware of that distinction! Thanks ---
**Author:** ![alex9373](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alex9373](https://community.solid-run.com/u/alex9373)\ **Post date:** [February 21, 2022, 12:23am UTC](https://community.solid-run.com/t/in-place-updates-kernel-firmware-etc/200/4 "2022-02-21T00:23:36Z")
For anyone else, here’s what I did: - Got a UEFI image from [SolidRun Images](https://images.solid-run.com/LX2k/lx2160a_uefi) matching RAM speed, SD card type - write to SD card - write Ubuntu Jammy (with kernel 5.15) to USB drive, server edition because I don’t have a graphics card - set DIP switches to SD card boot, set serial console preference, select USB drive, edit linux command-line with arm-smmu.disable\_bypass=0 iommu.passthrough=1 as demonstrated in [SolidRun DevCuts - HoneyComb Distro Install - YouTube](https://www.youtube.com/watch?v=1rkMUZFYEkY) - install Ubuntu, edit /etc/defaults/grub with command line, sudo update-grub Things I’ve yet to figure out - How to get the 10G network working again - How to apply UEFI firmware to eMMC/SPI ---
**Author:** ![alex9373](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alex9373](https://community.solid-run.com/u/alex9373)\ **Post date:** [February 21, 2022, 1:42am UTC](https://community.solid-run.com/t/in-place-updates-kernel-firmware-etc/200/5 "2022-02-21T01:42:33Z")
This article helped me on the 10G network [SFP+ - What am I looking for? - #6 by sudrien](https://community.solid-run.com/t/sfp-what-am-i-looking-for/193/6) ---
**Author:** ![heksterb](https://avatars.discourse-cdn.com/v4/letter/h/ac91a4/32.png) [@heksterb](https://community.solid-run.com/u/heksterb)\ **Post date:** [May 4, 2025, 8:08pm UTC](https://community.solid-run.com/t/in-place-updates-kernel-firmware-etc/200/6 "2025-05-04T20:08:27Z")
Trying to do the same thing; and getting as far as the Ubuntu installer, but it’s not showing the eMMC as an installation option. NVMe is, but I don’t want to install there 🙂 The eMMC shows in UEFI, but as a “UEFI Misc Device 2”; alongside the SDHC , which appears as “UEFI Misc Device”. In the UEFI Shell the eMMC lists as ```auto FS0: Alias(s):HD0b:;BLK1: eMMC(0xCA)/HD(1,GPT,B698DBB5-9D2B-46DF-8A34-ADCDEC514FE3,0x800,0x21980 0) BLK2: Alias(s): eMMC(0xCA)/HD(2,GPT,3238391D-677C-49F7-B6DF-D4AF6BA5C2C1,0x21A000,0x74 55800) ``` Any ideas how to get the eMMC to show in the Ubuntu 22 installer? **Update** I think my question is already answered [here](https://community.solid-run.com/t/honeycomb-distro-installation-part-1-and-2/301): there is no ACPI support for SDHC/MMC. ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [May 5, 2025, 4:24am UTC](https://community.solid-run.com/t/in-place-updates-kernel-firmware-etc/200/7 "2025-05-05T04:24:26Z")
correct. I responded to the other thread.