Ethernet does not come up after reboot after latest update

Accelerated Computing DGX Spark / GB10 User Forum DGX Spark / GB10
,
1

Dear All,

I’ve done software update on my NVIDIA DGX Spark and after the restart the ethernet interface didn’t come up.

After a lot of confusion I’ve done a full shutdown + unplug + start and voila ethernet is back.

But sudo reboot brings the computer up without ethernet device i.e. what I see is

$ sudo lshw -class network -short

[sudo] password for david:

H/W path Device Class Description

========================================================

/0/100/0 enp1s0f0np0 network MT2910 Family [ConnectX-7]

/0/100/0.1 enp1s0f1np1 network MT2910 Family [ConnectX-7]

/0/101/0 enP2p1s0f0np0 network MT2910 Family [ConnectX-7]

/0/101/0.1 enP2p1s0f1np1 network MT2910 Family [ConnectX-7]

/0/104/0 wlP9s9 network MEDIATEK Corp.

$

In other words the ethernet adapter HW is missing: I need to also have /0/103/0 enP7s7 network Realtek Semiconductor Co., Ltd. in the list above.

A full shutdown + unplug + start fixes things.

But that’s a bit annoying as I often use the box remotely and wouldn’t want to be in a situation that it doesn’t come up after reboot.

Has anyone seen this? Fixed this? Some kind of BIOS (or whatever it’s called) setting?

Cheers!

2

FWIW – ran the update on both my units yesterday. One came back up and the other didn’t. Had to physically pull power cord and it finally came back.

4

There was some discussion in the forum earlier about having to blacklist a particular kernel module to ensure the correct one was selected. I wonder if finding that forum post could help?

5
6

Okay, my post is basically duplicate of above and the solution is on the other thread: Realtek r8127 Ethernet NIC disappears on every reboot, only recovers with full power cycle - #3 by czankel

I’ll check tomorrow when I am physically next to the box so I dare mess about with kernel command line and grub and reboot.

7

Just a final update that the solution proposed on the other thread worked, I’ve just tested.

It needed one final cold restart (to reset the Realtek hw after the wrong driver messed it up), but now a normal reboot leaves the box in a good state.