Updated ISO generation for NUC 12

[dsimog01]

Added necessary firmware for WiFi adapter in Intel NUC 12

[3alpha]

We should also think about dropping support for older debian versions.

[dsimog01]

I must check this to know if it is an Intel NUC 12 -> https://www.cyberciti.biz/faq/how-to-find-intel-nuc-bios-version-and-model-on-linux/

[dsimog01]

And I can check if installing certain packages from backports is enough, instead of upgrading

[3alpha]

Take look at this as well. It guides you how to pick specific packages from different repositories. We should use backports only where it is necessary.

[pablomendezroyo]

@dsimog01 great work!

Maybe we should consider creating a new ISO asset (to be implemented in the CI) just for the intel NUC 12, since this backports thingy is going to be temporary: DAppNode-v0.2.59-debian-bullseye-amd64-unattended-intel-12.iso

@3alpha @alexpeterson91 thoughts?

[alexpeterson91]

@dsimog01 great work!

Maybe we should consider creating a new ISO asset (to be implemented in the CI) just for the intel NUC 12, since this backports thingy is going to be temporary: DAppNode-v0.2.59-debian-bullseye-amd64-unattended-intel-12.iso

@3alpha @alexpeterson91 thoughts?

Yup i think that makes sense, at the same time we should just make a cloud ISO with IPFS set to server profile, its just chaning the IPFS .yaml file right? and is the backports gonna be temporary? before this PR was done and i was just researching for a couple weeks i found several just linux questions about these firmwares and answers said due to bullseye's life cycle it may not be for a while that full support is availible. similar issues in ubuntu had the same answers, dont expect anything for a while. like years, but idk just something i read a few times in a few places about multiple distros including debian bullseye

[alexpeterson91]

We should also think about dropping support for older debian versions.

probably should be its own issue as it doesnt make sense in this PR,

which needs to be added as like a separate branch and should be included in releases as a release asset until NUC12s are in our store or more ubiquitous (we've got to prep for the NUC13 too, its been out a month or 2 now and someones gonna buy it, i would have if i didnt get a 12 like 3 weeks before intel released Raptor Lake the 13th gen.)

[alexpeterson91]

resolve conflicts

i know this isnt getting merged yet i just want to confirm conflicts are resolved currently as your review requested.

[tonoli]

Is there any update on this?

[alexpeterson91]

Is there any update on this?

I will update the branch to the latest core from this week and make sure the iso for NUC12 firmwares etc is published. I have to reinstall my own NUC12 anyway so I'll do final tests before it is published.

[alexpeterson91]

Is there any update on this?

If you want to build on your own. Clone the dappnode/dappnode repo (this one). If you have the SDK installed along with docker etc you can generate the ISO yourself by using CLI to enter the cloned repo the navigate into the ISO directory and then run docker compose up this will begin the iso generation process and will create a directory called images and will place the finished ISO there. I Still need to confirm it's all working on our end with the latest updates etc. which is on my list for today.

[tonoli]

Is there any update on this?

If you want to build on your own. Clone the dappnode/dappnode repo (this one). If you have the SDK installed along with docker etc you can generate the ISO yourself by using CLI to enter the cloned repo the navigate into the ISO directory and then run docker compose up this will begin the iso generation process and will create a directory called images and will place the finished ISO there. I Still need to confirm it's all working on our end with the latest updates etc. which is on my list for today.

Thank you very much for you help!

I managed to install by doing that!

I did this:

• Cloned the repo
• Then ran the commands: docker-compose build docker-compose up
• flashed the generated iso that I found images/
• managed to solve the installation problem of Debian not detecting the network material.
• All the installation went smoothly the dappnode runs well!

Thank you!

[alexpeterson91]

@pablomendezroyo @dsimog01 ive been checking in on this PR/branch since D started having me test it, and have been updating the branch for each core release and any other change It currently passes all CI checks, has no conflicts, but still hasnt been merged. I Know Pablo you suggested releasing it as a standalone asset with each release, since its temporary and will be replaced/ improved in the near future. However we have more and more users with NUC12s at home and no way to get them working with our current release assets they're coming up with some messy workarounds, we've had this working for months, this branch's ISOs should be published for the next core release as an additional asset if the backports check is too much to merge to master at this time, and we should upload a NUC12 compatible ISO for the current release as soon as possible.

[dsimog01]

@alexpeterson91 There is a newer Debian version (11.6). I will test if it avoids updating linux-image from backports

[alexpeterson91]

I can test Too my NUc 12 has been out of commission since we were last testing. Mainly due to lack of knowing if it was still needed for more testing and also I needed more IPs I have too many over powered NUCs on ny home connection anyway it made more sense to shelve it till they finalized my new internet service or I needed to test it again. Now I got my dedicated fiber activated this weekend and have several more high end test and production servers coming online very soon. My nuc 12 will likely be the first device active on my new setup. Just let me know if you need me to check anything on my machine it's sitting just waiting to be hooked back up and reinstalled.

[dsimog01]

I can test Too my NUc 12 has been out of commission since we were last testing. Mainly due to lack of knowing if it was still needed for more testing and also I needed more IPs I have too many over powered NUCs on ny home connection anyway it made more sense to shelve it till they finalized my new internet service or I needed to test it again. Now I got my dedicated fiber activated this weekend and have several more high end test and production servers coming online very soon. My nuc 12 will likely be the first device active on my new setup. Just let me know if you need me to check anything on my machine it's sitting just waiting to be hooked back up and reinstalled.

I already tested updating to the latest Debian release (11.6) and it does not fix the issue we are experiencing with NUC 12s, so we still need to update linux image from backports to make it work

[alexpeterson91]

I can test Too my NUc 12 has been out of commission since we were last testing. Mainly due to lack of knowing if it was still needed for more testing and also I needed more IPs I have too many over powered NUCs on ny home connection anyway it made more sense to shelve it till they finalized my new internet service or I needed to test it again. Now I got my dedicated fiber activated this weekend and have several more high end test and production servers coming online very soon. My nuc 12 will likely be the first device active on my new setup. Just let me know if you need me to check anything on my machine it's sitting just waiting to be hooked back up and reinstalled.

I already tested updating to the latest Debian release (11.6) and it does not fix the issue we are experiencing with NUC 12s, so we still need to update linux image from backports to make it work

Well then we need to polish this and add it as a standalone asset for download for releases until its no longer an issue, which feels to me like it could be longer than we want. Users are struggling, some 11s, all 12s, and 13s all have this issue missing the drivers and firmware for the essential components like LAN and WiFi. Right? @pablomendezroyo your thoughts? you suggested it a while ago earlier in this PR, i think its what needs to be done agreed then, and since we still have to deal with backports for now we should just keep the branches on updated to each other save for the changes in this branch which we just publish as a standalone release asset for the current core, and the upcoming versions until its no longer needed.

its a lot of users running into this ow, and some ways people are doing it is really messy and ive tried to tell people not to share those messy methods as they may mess up our normal upgrades and services; as most involve updating and upgrading system files over sh or direct console access with keyboard. I really just wanna get the core versions updated and publish a new ISO for NUC12+ devices since we will only encounter more and more every day

[akill317]

I can test Too my NUc 12 has been out of commission since we were last testing. Mainly due to lack of knowing if it was still needed for more testing and also I needed more IPs I have too many over powered NUCs on ny home connection anyway it made more sense to shelve it till they finalized my new internet service or I needed to test it again. Now I got my dedicated fiber activated this weekend and have several more high end test and production servers coming online very soon. My nuc 12 will likely be the first device active on my new setup. Just let me know if you need me to check anything on my machine it's sitting just waiting to be hooked back up and reinstalled.

I already tested updating to the latest Debian release (11.6) and it does not fix the issue we are experiencing with NUC 12s, so we still need to update linux image from backports to make it work

Well then we need to polish this and add it as a standalone asset for download for releases until its no longer an issue, which feels to me like it could be longer than we want. Users are struggling, some 11s, all 12s, and 13s all have this issue missing the drivers and firmware for the essential components like LAN and WiFi. Right? @pablomendezroyo your thoughts? you suggested it a while ago earlier in this PR, i think its what needs to be done agreed then, and since we still have to deal with backports for now we should just keep the branches on updated to each other save for the changes in this branch which we just publish as a standalone release asset for the current core, and the upcoming versions until its no longer needed.

its a lot of users running into this ow, and some ways people are doing it is really messy and ive tried to tell people not to share those messy methods as they may mess up our normal upgrades and services; as most involve updating and upgrading system files over sh or direct console access with keyboard. I really just wanna get the core versions updated and publish a new ISO for NUC12+ devices since we will only encounter more and more every day

Hello, I run into the NUC12+ problem as well, I tried to compose the iso from this branch, but for some reason, the installation process always failed, how do remove all the messy failed files and restart the installation process, is it simply restart the device with the USB? But it never let me set the user id and password, feel like something is missing.

[alexpeterson91]

I can test Too my NUc 12 has been out of commission since we were last testing. Mainly due to lack of knowing if it was still needed for more testing and also I needed more IPs I have too many over powered NUCs on ny home connection anyway it made more sense to shelve it till they finalized my new internet service or I needed to test it again. Now I got my dedicated fiber activated this weekend and have several more high end test and production servers coming online very soon. My nuc 12 will likely be the first device active on my new setup. Just let me know if you need me to check anything on my machine it's sitting just waiting to be hooked back up and reinstalled.

I already tested updating to the latest Debian release (11.6) and it does not fix the issue we are experiencing with NUC 12s, so we still need to update linux image from backports to make it work

Well then we need to polish this and add it as a standalone asset for download for releases until its no longer an issue, which feels to me like it could be longer than we want. Users are struggling, some 11s, all 12s, and 13s all have this issue missing the drivers and firmware for the essential components like LAN and WiFi. Right? @pablomendezroyo your thoughts? you suggested it a while ago earlier in this PR, i think its what needs to be done agreed then, and since we still have to deal with backports for now we should just keep the branches on updated to each other save for the changes in this branch which we just publish as a standalone release asset for the current core, and the upcoming versions until its no longer needed.

its a lot of users running into this ow, and some ways people are doing it is really messy and ive tried to tell people not to share those messy methods as they may mess up our normal upgrades and services; as most involve updating and upgrading system files over sh or direct console access with keyboard. I really just wanna get the core versions updated and publish a new ISO for NUC12+ devices since we will only encounter more and more every day

Hello, I run into the NUC12+ problem as well, I tried to compose the iso from this branch, but for some reason, the installation process always failed, how do remove all the messy failed files and restart the installation process, is it simply restart the device with the USB? But it never let me set the user id and password, feel like something is missing.

We will be releasing a prebuilt experimental ISO compatible with NUC11 extremes, and NUC12s and 13s shortly. It's been tested a lot but not long term. The issue holding us back right now is that we need a newer kernel to make the drivers for the various peripherals like the NIC cards and WiFi audio drivers on some models and PCIe drivers on top end models. Debian doesn't have this available just yet in a stable form. Debian 12 is what we need to make this workaround install (which works, but is not reliable over the longer term). So it will be an experimental asset and to be used your own risk. It's a stopgap until Debian 12 is released in March as of the last time I checked. They just completed their first freeze on the release so it's not too far away but this "experimental" ISO release will be made available very shortly as a stop gap until Debian 12 is released as stable.

[pablomendezroyo]

What is its current status? are we planning to merge this or just a good to have for building ISOs for nuc 12?

If we wont merge this in the near future, please convert it to draft an add to the title [ ON HOLD ]

@dsimog01

[dsimog01]

It seems like we do not need this anymore as it looks like Debian 12 (https://github.com/dappnode/DAppNode/pull/575) is solving the issues we were having that made this PR necessary.