10th Gen NUC BXNUC10i5FNK1 Drivers Kernel
-
@dangbird If you are still keen to build your own kernel there is the most current wiki article on it that should still work: https://wiki.fogproject.org/wiki/index.php?title=Build_TomElliott_Kernel#Build_TomElliott_Kernel_for_FOG_0.33b_and_newer
-
cross link post, probably the same issue: https://forums.fogproject.org/topic/14528/intel-nuc10i3fnk-network-adapter-intel-i219-v-10-100-1000-mbps-ethernet-not-detected
-
@george1421 Thank you will test this shortly for you.
-
@Sebastian-Roth Thank you, will take a crack at this if @george1421 option does not work. I can do it, but not the sharpest tool in the shed when going this far…
-
@dangbird I can help you build a one off kernel too. Its not that hard as long as your compiler computer is setup correctly. But I’m pretty sure (at least one of) my kernel will work for you.
-
@george1421 Ok your instructions from other post…WORKED FLAWLESS with the bzImage5618.
How do we get that kernel to be the “main” so I can just deploy image without having to register each NUCs MAC individually?
Can I build a PXE Menu Item that uses that special kernel?BY THE WAY, have been trying to fix this for 2 months, and have 1000 NUCs to deploy, so you have changed my world.
-
@dangbird There is two ways (three ways if you take the unrecommended approach) you can go about changing it for all
- In the fog settings -> fog configuration hit the expand all button then search for bzImage. In that location replace bzImage with bzImage5618.
- For all of the NUCs if they are in a fog group, you can use the fog group to set all of the host kernel parameters to bzImage5618
- (unrecommended approach) in /var/www/html/fog/service/ipxe directory rename the current bzImage to bzImage.sav and then rename bzImage5618 to bzImage. Just realize this is the quickest and easiest approach, but understand the next time you update fog this bzImage file will be overwritten, with what ever version is shipping at the time FOG 1.5.9 is released.
While this kernel hasn’t been fully tested it “should” work fine for all hardware platforms. The developers just won’t release it until the user community has a chance to use it to deploy to see how it works on a range of hardware platforms.
-
@george1421 Did Option #1 and worked perfectly. Again I appreciate you responding and the effort put into this IT infrastructure tool.
-
@george1421 I’m trying this method option 1 with my NUC10i3fnk1, and it gets past loading bzImage5618 and init.xz and hangs without moving forward. I’m on version 1.5.9 of FOG. I feel so close but so far away on this. Thanks for any help you could provide.
-
@ccfrederick said in 10th Gen NUC BXNUC10i5FNK1 Drivers Kernel:
it gets past loading bzImage5618
Understand its now a year later…
What I would do in your case is to use the FOG Configuration->Kernel update utility to upgrade to FOS Linux 5.10.x and then make sure you set back the default kernel to bzImage and bzImage32. The dev image bzImage5618 was a temp kernel until the linux developers released the next LTS version of linux, which ended up being 5.10.x.
-
@george1421 Thanks for the reply on such an old thread! I have already tried 5.10 with no success, unfortunately. After doing some digging I found an official hardware list that only includes a few Intel NUC chipsets, so it would appear that this is dead on arrival for me. Too bad as I really like Fog as an imaging solution. Thanks again for your help!
-
@ccfrederick said in 10th Gen NUC BXNUC10i5FNK1 Drivers Kernel:
only includes a few Intel NUC chipsets, so it would appear that this is dead on arrival for me. Too bad as I really like Fog as an imaging solution. Thanks again for your help!
We are far from dead in the water. First make sure the firmware is up to date on the nuc. The problem seems to be the hand off from ipxe to FOS linux. If this is the case we can bypass ipxe and boot directly into FOS Linux. There are some caveats with this approach as well as you lose some functionality (like multicast imaging). But for unicast imaging booting into FOS Linux will work just fine.
-
@ccfrederick Disregard the last message, I was installing the wrong 5.10 kernel. I grabbed the standard 64bit 5.10.34 and all is well. Hope this helps someone!
-
Hi there,
I’m having issues booting into the fog menu with both UEFI and Legacy
can you reccomend a kernel to use for
Intel NUC10i7FNHThanks
-
@chris_unit I just went into my FOG Gui, clicked Fog Config->Kernel Update->Kernel 5.10.50 Tom Elliot 64(Third One I think) and then I clicked Download on the right. It installed. I rebooted for good measure and all worked.
-
@dangbird Thanks for the tip
i’ve now done the same, do i now have to specificy that kerner for my NUC’s in the hosts info (bzImage)
Is this kernel both legacy and UEFI ?
-
@chris_unit As long as it is default NO. Otherwise you have to change it to bzimage and bzimage32 in fog system settings TFTP Server
