That's at the OS level which is essentially CentOS and the Anaconda installer. We don't have any documented procedure to do that as far as I'm aware, but if you can find instructions for CentOS 8 the same type of procedure should apply.

Can you post exactly what you are seeing?

What is the exact NIC you are trying to use?

These are the Broadcom NICs on the compatibility list but they have received no in-house testing.

We would initially recommend Intel or Mellanox NICs as they have received the most testing in-house and are likely the path of least friction.

@oilaser said in Boot hang:

Hello,

Boot hangs at lo0: link state changed to up

current upgrade worked for a day and I rebooted today and this started happening.

Thank you.

Are you running pfSense or tnsr? If pfSense you posted in the wrong place.

Hi,

Yes this was the reason, issue is solved. For any how the resolve of the former Updates where working, now Proxy was Blocking...

Tx for Opening my eyes

Check on https://ark.intel.com/content/www/us/en/ark.html if your processor supports SSE4.2.

You may want to reboot after changing the driver to ensure the right driver is fully attached. I think it shouldn't matter since they were not active before, but I know a reboot is needed when changing from one driver to another.

It may just not run on that particular hardware, though I am not 100% certain on that. I don't recall mentions of it running on Broadcom, mostly I've seen Intel, Chelsio, and Mellanox if I remember right. You may want to ping your contact for the eval with more info about your NICs

I added that to the known issues list, since others are likely to hit it: https://docs.netgate.com/tnsr/en/latest/releases/release-notes-19.05.html#updates