Unsolved

1 Rookie

 • 

1 Message

 • 

4 Points

93

June 18th, 2026 12:33

Networking no longer possible after failed firmware update.

I have a poweredge R260 server that i updated the firmware on from iDRAC. However this update failed and now the ethernet ports on the back of the machine seem to be inoperable. The link lights on the ethernet port work fine and show green but then when i check in the OS the interface never appears. Checking the tg3 output from modprobe i get the following:

[    0.155534] pci 0000:06:00.0: [14e4:165f] type 00 class 0x020000 PCIe Endpoint
[    0.155597] pci 0000:06:00.0: BAR 0 [mem 0x4000250000-0x400025ffff 64bit pref]
[    0.155602] pci 0000:06:00.0: BAR 2 [mem 0x4000240000-0x400024ffff 64bit pref]
[    0.155606] pci 0000:06:00.0: BAR 4 [mem 0x4000230000-0x400023ffff 64bit pref]
[    0.155735] pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
[    0.155832] pci 0000:06:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:00:1c.6 (capable of 8.000 Gb/s with 5.0 GT/s PCIe x2 link)
[    0.156333] pci 0000:06:00.1: [14e4:165f] type 00 class 0x020000 PCIe Endpoint
[    0.156396] pci 0000:06:00.1: BAR 0 [mem 0x4000220000-0x400022ffff 64bit pref]
[    0.156401] pci 0000:06:00.1: BAR 2 [mem 0x4000210000-0x400021ffff 64bit pref]
[    0.156406] pci 0000:06:00.1: BAR 4 [mem 0x4000200000-0x400020ffff 64bit pref]
[    0.156534] pci 0000:06:00.1: PME# supported from D0 D3hot D3cold
[    0.200623] pci 0000:06:00.0: Adding to iommu group 12
[    0.200630] pci 0000:06:00.1: Adding to iommu group 12
[    0.832257] tg3 0000:06:00.0: Could not obtain valid ethernet address, aborting
[    0.832655] tg3 0000:06:00.0: probe with driver tg3 failed with error -22
[    0.865201] tg3 0000:06:00.1: Could not obtain valid ethernet address, aborting
[    0.865480] tg3 0000:06:00.1: probe with driver tg3 failed with error -2

I cant seem to update the firmware again as the network interface has disappeared from iDRAC and any of the dell update packages i try give me the following error:

Collecting inventory...
..
Running validation...

This Update Package is not compatible with your system configuration.

The PCI bus can see the NIC but the dell system refuses to acknowledge that it exists and, therefore, refuses any update i try to apply.

Does anyone know how i can rectify this issue?  

Community Manager

 • 

9.7K Posts

 • 

43.2K Points

July 7th, 2026 16:35

Hi.

Thank you for the detailed information and log output. This is very helpful in understanding the issue.

The key error in your tg3 driver output, "Could not obtain valid ethernet address, aborting," strongly indicates that the failed firmware update has corrupted the NIC's non-volatile memory where the MAC addresses and other configuration data are stored. The PCI bus can still enumerate the hardware because the device is physically present and functional at the electrical level, but the driver cannot initialize it because it cannot read a valid MAC address from the NIC's EEPROM or flash region. This is unfortunately a known consequence of an interrupted or failed NIC firmware flash.

There are a few things you can try before contacting support. First, try accessing the Lifecycle Controller by pressing F10 during boot and attempt a firmware update from there using the Platform Update or Firmware Update option. The Lifecycle Controller operates independently from the OS and iDRAC inventory and may be able to push the firmware to the device even though iDRAC no longer recognizes it. You can use a USB drive loaded with the firmware binary or point it to the Dell support site directly if you have network access through a separate interface.

Second, you could try downloading the Dell Platform Specific Bootable ISO for the R260 from the Dell support site using another machine, writing it to a USB drive, and booting from it. This bootable image performs its own hardware discovery and may be able to identify and reflash the NIC even in its current state.

Third, as a temporary workaround to regain network access in the OS while you work on resolving the firmware issue, you may be able to manually assign a MAC address to the interface in Linux. You would need to identify the interface names assigned to the PCI addresses using a command like "ls -la /sys/class/net/" to find which interfaces correspond to 0000:06:00.0 and 0000:06:00.1, and then use the "ip link set" command to assign a locally administered MAC address. However, please note that this is only a temporary workaround and does not fix the underlying firmware corruption.

If none of these approaches allow you to reflash the NIC firmware successfully, this situation will very likely require Dell ProSupport involvement. A support engineer may need to use specialized tools such as the Broadcom NIC configuration utility or BNXTMT to reprogram the NIC's EEPROM and restore the MAC addresses and firmware. If your server is under warranty or a ProSupport contract, please open a case with your Service Tag so that a technician can assist with the recovery. If the NIC flash memory is unrecoverable, a motherboard replacement may ultimately be necessary since the BCM5720 is an onboard LOM on the R260.

 

 

 

 

Let us know if there is anything else we can assist you with.

Thanks,

Josh

Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

#Iwork4Dell

No Events found!

Top