My motherboard is Supermicro X11SPW-CTF. There is dual LAN with 10GBase-T with Intel® X722 + X557 on board. I have tried flash original network interfaces firmware version 3.45 to newer 3.50 using nvmupdatew64e utility. And I have power lost during update. Both interfaces doesn't work now. Is it possible to restore workability of the network interfaces? Here is log of my recovery tries:
-------------------------------------
D:\nvmupdatew64e.exe -i -o inv_xml.txt -l inv.txt
D:\type inv.txt
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.32.20.30
Copyright (C) 2013 - 2018 Intel Corporation.
nvmupdatew64e.exe -i -o inv_xml.txt -l inv.txt
Inventory
[00:025:00:00]: Intel(R) Ethernet Connection X722 for 10GBASE-T
Flash inventory started.
Shadow RAM inventory started.
Error: LAN MAC address cannot be read.
Shadow RAM inventory finished.
Flash inventory failed.
[00:025:00:00]: Intel(R) Ethernet Connection X722 for 10GBASE-T
DEVICE IS IN RECOVERY MODE!
Vendor : 8086
Device : 37CC
Subvendor : 8086
Subdevice : 35CF
Revision : 8
LAN MAC : 000000000000
Alt MAC : 000000000000
SAN MAC : 000000000000
ETrackId : 00000000
NVM Version : n/a(n/a)
PBA : n/a
VPD status : Not set
VPD size : 0
NVM update : No config file entry
checksum : Invalid
OROM update : No config file entry
CIVD : 0.0.0
D:\type inv_xml.txt
<?xml version="1.0" encoding="UTF-8"?>
<DeviceInventory lang="en">
<Instance vendor="8086" device="37CC" subdevice="35CF" subvendor="8086" bus="25" dev="0" func="0" PBA="n/a" port_id="Port 1 of 1" display="Intel(R) Ethernet Connection X722 for 10GBASE-T">
<Module type="NVM" recovery="1" version="00000000">
</Module>
</Instance>
</DeviceInventory>
-----------------------------------
D:\nvmupdatew64e.exe -l update.txt
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.32.20.30
Copyright (C) 2013 - 2018 Intel Corporation.
WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.
Inventory in progress. Please wait [**-.......]
Num Description Ver.(hex) DevId S:B Status
=== ================================== ============ ===== ====== ==============
01) Intel(R) Ethernet Connection X722 n/a(n/a) 37CC 00:025 RECOVERY
for 10GBASE-T available
Options: Adapter Index List (comma-separated), [A]ll, e[X]it
Enter selection:A
Update in progress. This operation may take several minutes.
[*-........]
Num Description Ver.(hex) DevId S:B Status
=== ================================== ============ ===== ====== ==============
01) Intel(R) Ethernet Connection X722 n/a(n/a) 37CC 00:025 RECOVERY
for 10GBASE-T failed
Tool execution completed with the following status: Cannot restore manufacturing data.
Press any key to exit.
D:\type update.txt
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.32.20.30
Copyright (C) 2013 - 2018 Intel Corporation.
nvmupdatew64e.exe -l update.txt
Config file read.
Inventory
[00:025:00:00]: Intel(R) Ethernet Connection X722 for 10GBASE-T
Flash inventory started.
Shadow RAM inventory started.
Error: LAN MAC address cannot be read.
Shadow RAM inventory finished.
Flash inventory failed.
Update
[00:025:00:00]: Intel(R) Ethernet Connection X722 for 10GBASE-T
Flash update started.
Error: Flash update failed.
---------------------------------
D:\type 000000000000\.rollback.cfg
;File generated automatically by NVMUpdate tool
CONFIG VERSION: 1.13.0
BEGIN DEVICE
DEVICENAME: Intel(R) Ethernet Connection X722 for 10GBASE-T
VENDOR: 8086
DEVICE: 37CC
SUBVENDOR: 8086
SUBDEVICE: 35CF
NVM IMAGE: 000000000000\000000000314.bin
IMAGE DOWNGRADE: TRUE
BEGIN PHY: ID=1540242
IMAGE: 000000000000\000000000314_phy0.bin
DOWNGRADE: TRUE
END PHY
END DEVICE
D:\nvmupdatew64e.exe -r -m 000000000000 -l rollback.txt
D:\type rollback.txt
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.32.20.30
Copyright (C) 2013 - 2018 Intel Corporation.
nvmupdatew64e.exe -r -m 000000000000 -l rollback.txt
Warning: Device with MAC address 000000000000 not found.
-------------------------------------
Please help!
Thanks in advance,
Anton.
Link Copied
Hi Michael.
Thank You for the answer. Supermicro support sent me special tool for recovering. And it's ok now.
Best regards,
Anton.
For more complete information about compiler optimizations, see our Optimization Notice.