ASUS NUC14MNK fos kernel no netwerk drivers

[Eazis]

I’m discovering a missing network driver inside the latest FOS kernel (6.6.69) for the ASUS NUC14MNK.
Is there a way to add this driver?

NIC: Realtek PCIe 2.5GbE Family Controller

[george1421]

@Eazis said in ASUS NUC14MNK fos kernel no netwerk drivers:

ASUS NUC14MNK.

Using either windows or linux can we get the hardware ID of that nic. In windows its under the device manager and the hardware ID. It should be two series of hex numbers. Under linux you would use lspci -nn | grep -i net in this form the code we need looks like [8088:14dc] (made up number). That will tell us if there is a driver in the linux kernel for that.

[Eazis]

@Eazis I have made a screenshot in Windows 11 >

[george1421]

@Eazis will you check to see if the beta version 6.12.x series fixes the issue? https://github.com/FOGProject/fos/releases

If not we will need compile a special kernel with the current realtek driver installed. The linux mainstream kernel drivers typically lags current hardware.

[Eazis]

@george1421 said in ASUS NUC14MNK fos kernel no netwerk drivers:

@Eazis will you check to see if the beta version 6.12.x series fixes the issue? https://github.com/FOGProject/fos/releases

If not we will need compile a special kernel with the current realtek driver installed. The linux mainstream kernel drivers typically lags current hardware.

I will try tomorrow and let you know.

[Eazis]

@george1421 I have tried Linux kernel 6.12.25 unfortunately this didn’t fix the NIC driver problem.

[george1421]

@Eazis Ok A little google-fu shows this is not an 8169 nic but a 8125 (2.5GbE) nic. (I personally really dislike realtek because of this BS).

So now we need to figure out how to add 8125 native nic support to the FOS kernel.

[Eazis]

@george1421 said in ASUS NUC14MNK fos kernel no netwerk drivers:

@Eazis Ok A little google-fu shows this is not an 8169 nic but a 8125 (2.5GbE) nic. (I personally really dislike realtek because of this BS).

So now we need to figure out how to add 8125 native nic support to the FOS kernel.

It seems the FOS kernel is misleading us
Windows already reports the hardware ID as 8125.

Is there any chance of getting this driver included in the FOS kernel?

For now, I have a workaround using USB-to-LAN to boot into FOS, but it’s far from ideal.
MAC address swapping inside the GUI etc.

[Tom Elliott]

@Eazis It looks, to me, there’s a firmware that we may need to add to the kernel for these nics, but I don’t know what version? I see

rtl8125a-3
rtl8125b-1
rtl8125b-2
rtl8125bp-2
rtl8125d-1
rtl8125d-2

I suppose we could attempt to add all of them, but we don’t know which one applies to your specific device.

[Tom Elliott]

@Eazis Can you please try with this file:

https://drive.google.com/file/d/1RuMF_xvYLfJwjlXAYk9ZN1VUG004Uk85/view?usp=sharing

I know it’s google drive. It’s my personal one and this link is available for anyone.

It’s simply the 64bit kernel file (we generally name bzImage) Please can you try this?

It’s got a few drivers added that appear (to me) to have been missing. If this works, I’ll try to get this into the fos repository.

[george1421]

@Tom-Elliott said in ASUS NUC14MNK fos kernel no netwerk drivers:

I suppose we could attempt to add all of them, but we don’t know which one applies to your specific device.

Also if we booted into debug mode and after the error is presented search syslog for the key word ‘firmware’ the kernel should post anything its missing. grep -i -e firm /var/log/syslog

[Eazis]

@Tom-Elliott

Thanks i tried your version but now i got this inside the FOS kernel.
The normal FOS kernel can boot into other pc’s except for the ASUS NUC.

[george1421]

@Eazis Will you do a few things to help us try to sort this out?

Schedule a capture or deploy to this computer, but before you do tick the debug checkbox before scheduling the task. If you don’t have this computer registered with the FOG server manually register it.

Now pxe boot the target computer, it should start to image right away, but instead of imaging it will drop you to a linux console on the target computer. There will be several screens of text you will need to clear with the enter key, but at the end you will be dropped to a linux command prompt.

How I want you to key in the following.

ip a s
lspci -k -nn | grep -i net
grep -i -e firm /var/log/syslog

get a clear picture of all of the values and post it here.

The first command will show us the network adapters
The second command will show us the hardware ID of the network adapters
The last command searches /var/syslog for any message that has firmware in the name.

After you are done with this, delete the capture/deploy task from the fog server.