Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Dolpa
Novice
2,194 Views

NIC firmware update on ROMED8-2T failed?!

Jump to solution

Dear Folks,

I use an AsrockRack ROMED8-2T mobo with EPYC 7451 CPU and running Proxmox VE for virtualization.
This mobo has a dual Intel X550-T2 NIC onboard which has an old firmware from 2018.

The shipped NIC firmware is 1.93 80000AEE 05/25/2018.
The latest on official Intel site is 3.15 80001373 11/10/2020.

I mailed to AsrockRack support one month ago how can I update the firmware but the first question was why i want to update?
So I would like to use the SR-IOV function for KVM guest and bridge mode for LXC but this does not work at the same time with the old firmware, but will work with latest firmwares.

After a long exchange of letters with support stayed in to try the official update.
So I follow the Intel official method I used the UEFI tools.

https://downloadcenter.intel.com/download/28336/Non-Volatile-Memory-NVM-Update-Utility-for-Intel-Eth...

# nvmupdate64e -u -b -l -o update.xml -c nvmupdate.cfg
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.35.42.7
Copyright (C) 2013 - 2020 Intel Corporation.

Config file read.
Inventory
[00:098:00:00]: Intel(R) Ethernet Controller X550-T2
        Flash inventory started.
        Shadow RAM inventory started.
        Shadow RAM inventory finished.
        Flash inventory finished.
        OROM inventory started.
        OROM inventory finished.
[00:098:00:01]: Intel(R) Ethernet Controller X550-T2
        Device already inventoried.
Update
[00:098:00:00]: Intel(R) Ethernet Controller X550-T2
        Creating backup images in directory: D05099DB878F.
        Backup images created.
        Flash update started.
|======================[100%]======================|
        NVM verification started.
        Shadow RAM verification started.
|======================[100%]======================|
        Shadow RAM verification finished.
        Flash verification started.
|======================[100%]======================|
        Flash verification finished.
        NVM verification finished.
        Flash update successful.
Update security revisions
[00:098:00:00]: Intel(R) Ethernet Controller X550-T2
        Skipping update minimum security revisions.
Checking update availability for next tool run.
Post update inventory
[00:098:00:00]: Intel(R) Ethernet Controller X550-T2
        Flash inventory started.
        Flash inventory finished.
        OROM inventory started.
        OROM inventory finished.
[00:098:00:01]: Intel(R) Ethernet Controller X550-T2
        Device already inventoried.
Power Cycle is required to complete the update process.

 

The update.xml content is:

<?xml version="1.0" encoding="UTF-8"?>
<DeviceUpdate lang="en">
    <Instance vendor="8086" device="1563" subdevice="1563" subvendor="1849" bus="98" dev="0" func="0" PBA="000000-000" port_id="Port 1 of 2" display="Intel(R) Ethernet Controller X550-T2">
        <Module type="PXE" version="2.4.44" previous_version="2.4.32" display="">
            <Status result="Success" id="0">All operations completed successfully.</Status>
        </Module>
        <Module type="EFI" version="7.8.13" previous_version="7.0.19" display="">
            <Status result="Success" id="0">All operations completed successfully.</Status>
        </Module>
        <Module type="NVM" version="80001373" previous_version="80000AEE" display="">
            <Status result="Success" id="0">All operations completed successfully.</Status>
        </Module>
        <VPD>
            <VPDField type="String">Intel (r) Ethernet Controller X550</VPDField>
        </VPD>
        <MACAddresses>
            <MAC address="D05099DB878F">
            </MAC>
            <AltMAC address="D05099DB878F">
            </AltMAC>
        </MACAddresses>
    </Instance>
    <Instance vendor="8086" device="1563" subdevice="1563" subvendor="1849" bus="98" dev="0" func="1" PBA="000000-000" port_id="Port 2 of 2" display="Intel(R) Ethernet Controller X550-T2">
        <Module type="PXE" version="2.4.44" previous_version="2.4.32" display="">
            <Status result="Success" id="0">All operations completed successfully.</Status>
        </Module>
        <Module type="EFI" version="7.8.13" previous_version="7.0.19" display="">
            <Status result="Success" id="0">All operations completed successfully.</Status>
        </Module>
        <Module type="NVM" version="80001373" previous_version="80000AEE" display="">
            <Status result="Success" id="0">All operations completed successfully.</Status>
        </Module>
        <VPD>
            <VPDField type="String">Intel (r) Ethernet Controller X550</VPDField>
        </VPD>
        <MACAddresses>
            <MAC address="D05099DB8790">
            </MAC>
            <AltMAC address="D05099DB8790">
            </AltMAC>
        </MACAddresses>
    </Instance>
    <NextUpdateAvailable> 0 </NextUpdateAvailable>
    <RebootRequired> 0 </RebootRequired>
    <PowerCycleRequired> 1 </PowerCycleRequired>
</DeviceUpdate>

 

I did the power cycle and started the Proxmox. The NIC recognized and the linux kernel module loaded successful.

 

# ethtool -i enp98s0f0
driver: ixgbe
version: 5.1.0-k
firmware-version: 0x80001373, 1.2203.0
expansion-rom-version:
bus-info: 0000:62:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

# ethtool -i enp98s0f1
driver: ixgbe
version: 5.1.0-k
firmware-version: 0x80001373, 1.2203.0
expansion-rom-version:
bus-info: 0000:62:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

 

However the port0 working fine BUT the port1 has no link. Both worked before update.

Now only port0 has link, I double checked the cables and switch (NETGEAR GS110EMX).

# ethtool enp98s0f0
Settings for enp98s0f0:
    Supported ports: [ TP ]
    Supported link modes:   100baseT/Full
                            1000baseT/Full
                            10000baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes:  100baseT/Full
                            1000baseT/Full
                            10000baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Speed: 10000Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: Unknown
    Supports Wake-on: umbg
    Wake-on: g
    Current message level: 0x00000007 (7)
                   drv probe link
    Link detected: yes

# ethtool enp98s0f1
Settings for enp98s0f1:
    Supported ports: [ TP ]
    Supported link modes:   100baseT/Full
                            1000baseT/Full
                            10000baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes:  100baseT/Full
                            1000baseT/Full
                            10000baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Speed: Unknown!
    Duplex: Unknown! (255)
    Port: Twisted Pair
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: Unknown
    Supports Wake-on: umbg
    Wake-on: g
    Current message level: 0x00000007 (7)
                   drv probe link
    Link detected: no

 

I checked the firmware again and seems it's fine:

# nvmcheck64e /DEVICES
Intel(R) NVM Integrity Verification Tool
Nvmcheck version 1.35.57.00
QV SDK version 2.35.57.00
Copyright(C) 2012 - 2020 Intel Corporation.

NIC B/D/F     Ven-Dev   MAC          ENA Branding string
=== ========= ========= ============ === ======================================
1) 098/00/00 8086-1563 D05099DB878F YES Intel(R) Ethernet Controller X550-T2
2) 098/00/01 8086-1563 D05099DB8790 YES Intel(R) Ethernet Controller X550-T2

# nvmcheck64e /NIC=1 /VERIFY
Intel(R) NVM Integrity Verification Tool
Nvmcheck version 1.35.57.00
QV SDK version 2.35.57.00
Copyright(C) 2012 - 2020 Intel Corporation.

NVM module: Option ROM.
NVM Integrity verification PASSED.

NVM module: PHY Firmware.
NVM Integrity verification PASSED.

NVM module: EMP image.
NVM Integrity verification PASSED.

# nvmcheck64e /NIC=2 /VERIFY
Intel(R) NVM Integrity Verification Tool
Nvmcheck version 1.35.57.00
QV SDK version 2.35.57.00
Copyright(C) 2012 - 2020 Intel Corporation.

NVM module: Option ROM.
NVM Integrity verification PASSED.

NVM module: PHY Firmware.
NVM Integrity verification PASSED.

NVM module: EMP image.
NVM Integrity verification PASSED.

 

Intel diagnostic tool port0 and port1:

linkonport1.jpgnolinkonport2.jpg

I made a backup from the old firmware, but the update tool said "Rollback blocked". So I can't rollback to the old version.

rollbacks.jpg

I tried firmware update on Windows10 too but same story.

Any idea? How I can revive the link? I know this is a 3rd party issue but AsrockRack said only solution is RMA and they will flash back the old firmware but I would like to avoid it because this is a long procedure for me and my system is a massive watercooling build very hard to dissassemble.

Best Regards,

Dolpa

 

1 Solution
CrisselleF_C_Intel
Moderator
213 Views

Hello All,


How are you all doing? I hope this message finds you well!


Please accept our sincerest apologies for the delay on this matter. Kindly see below information for the update from our Engineering team.


We believe the issue is that Debug Mode is enabled which results in the single port failure following the update.


Debug Mode is entered when the signal to X550 between the Flash's SCLK pin is pulled up when the X550 powers on (like a boot strapping configuration).


This mode is for engineering and debug work only and is not supported in normal operation or basically in manufacturing.


We surmise that ASROCK is shipping the motherboards in this configuration.


The Debug Mode tells the Firmware onboard the X550 it is ok to make certain writes to the NVM it might normally. This would explain the behavior we see evidence of, and it also correlates to the isolation to this one manufacturer.


It is highly recommended to request RMA to your boards and share the aforementioned information with the OEM, ASROCK.

https://asrock.com/support/index.asp


Thank you for your utmost cooperation while we are checking your concerns. We will now proceed closing this request on our end. Your time and cooperation throughout the process is highly appreciated. Just feel free to post a new question if you may have any other inquiry in the future as this thread will no longer be monitored.


Best regards,

Crisselle C.

Intel® Customer Support


View solution in original post

44 Replies
CrisselleF_C_Intel
Moderator
1,275 Views

Hello Dolpa,


Thank you for posting in Intel Ethernet Communities. 


As the Intel(R) Ethernet Controller X550-T2 is embedded on an ASRock system, please be informed that we have a limited support on this and we might push you back to your manufacturer for further assistance. However, we will still try to check this issue with our engineers and request for their inputs for possible resolution. 


We will get back to you as soon as we heard from them but no later than 2-3 business days.


Hoping for your kind patience.


Best regards,

Crisselle C

Intel® Customer Support


Dolpa
Novice
1,263 Views

Dear Crisselle,

Thank You for the quick answer.

As I wrote I know it would be Asrock's job to deal with it, but they said the only solution is RMA and they will flash back the good firmware. Because of pandemic I working at home and this server has a very busy daily work. I would like to avoid the RMA, I think its a software/firmware problem not a hardware issue and may I fix it with your engineer help.

As an additional info, I made a new kernel modul for Proxmox VE, and tried it but unsuccessful.

There is the console outputs:

# dmesg | grep ixgbe
[    3.526558] ixgbe: loading out-of-tree module taints kernel.
[    3.527277] ixgbe: loading out-of-tree module taints kernel.
[    3.582592] ixgbe 0000:62:00.0 0000:62:00.0 (uninitialized): ixgbe_check_options: FCoE Offload feature enabled
[    4.170518] ixgbe 0000:62:00.0: Multiqueue Enabled: Rx Queue count = 24, Tx Queue count = 24 XDP Queue count = 0
[    4.255287] ixgbe 0000:62:00.0: 31.504 Gb/s available PCIe bandwidth (8 GT/s x4 link)
[    4.305993] ixgbe 0000:62:00.0 eth0: MAC: 4, PHY: 3, PBA No: 000000-000
[    4.309235] ixgbe 0000:62:00.0: d0:50:99:db:87:8f
[    4.312403] ixgbe 0000:62:00.0 eth0: Enabled Features: RxQ: 24 TxQ: 24 FdirHash vxlan_rx
[    4.321977] ixgbe 0000:62:00.0 eth0: Intel(R) 10 Gigabit Network Connection
[    4.336721] ixgbe 0000:62:00.1 0000:62:00.1 (uninitialized): ixgbe_check_options: FCoE Offload feature enabled
[    4.838376] ixgbe 0000:62:00.1: Multiqueue Enabled: Rx Queue count = 24, Tx Queue count = 24 XDP Queue count = 0
[    4.922960] ixgbe 0000:62:00.1: 31.504 Gb/s available PCIe bandwidth (8 GT/s x4 link)
[    4.973997] ixgbe 0000:62:00.1 eth1: MAC: 4, PHY: 3, PBA No: 000000-000
[    4.977507] ixgbe 0000:62:00.1: d0:50:99:db:87:90
[    4.980921] ixgbe 0000:62:00.1 eth1: Enabled Features: RxQ: 24 TxQ: 24 FdirHash vxlan_rx
[    4.989993] ixgbe 0000:62:00.1 eth1: Intel(R) 10 Gigabit Network Connection
[    4.994438] ixgbe 0000:62:00.0 enp98s0f0: renamed from eth0
[    5.038225] ixgbe 0000:62:00.1 enp98s0f1: renamed from eth1
[   17.462340] ixgbe 0000:62:00.0: registered PHC device on enp98s0f0
[   17.663919] ixgbe 0000:62:00.1: registered PHC device on enp98s0f1
[   22.690084] ixgbe 0000:62:00.0 enp98s0f0: NIC Link is Up 10 Gbps, Flow Control: None
# ethtool -i enp98s0f0
driver: ixgbe
version: 5.9.4
firmware-version: 0x80001373, 1.2877.0
expansion-rom-version:
bus-info: 0000:62:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

# ethtool enp98s0f0
Settings for enp98s0f0:
        Supported ports: [ TP ]
        Supported link modes:   100baseT/Full
                                1000baseT/Full
                                10000baseT/Full
                                2500baseT/Full
                                5000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  100baseT/Full
                                1000baseT/Full
                                10000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 10000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: umbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes

 

# ethtool -i enp98s0f1
driver: ixgbe
version: 5.9.4
firmware-version: 0x80001373, 1.2877.0
expansion-rom-version:
bus-info: 0000:62:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

# ethtool enp98s0f1
Settings for enp98s0f1:
        Supported ports: [ TP ]
        Supported link modes:   100baseT/Full
                                1000baseT/Full
                                10000baseT/Full
                                2500baseT/Full
                                5000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  100baseT/Full
                                1000baseT/Full
                                10000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: umbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: no
# modinfo ixgbe
filename:       /lib/modules/5.4.78-2-pve/updates/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
version:        5.9.4
license:        GPL
description:    Intel(R) 10GbE PCI Express Linux Network Driver
author:         Intel Corporation, <linux.nics@intel.com>
srcversion:     AA8061C6A752528BD6CFE19
alias:          pci:v00008086d000015E5sv*sd*bc*sc*i*
alias:          pci:v00008086d000015E4sv*sd*bc*sc*i*
alias:          pci:v00008086d000015CEsv*sd*bc*sc*i*
alias:          pci:v00008086d000015CCsv*sd*bc*sc*i*
alias:          pci:v00008086d000015CAsv*sd*bc*sc*i*
alias:          pci:v00008086d000015C8sv*sd*bc*sc*i*
alias:          pci:v00008086d000015C7sv*sd*bc*sc*i*
alias:          pci:v00008086d000015C6sv*sd*bc*sc*i*
alias:          pci:v00008086d000015C4sv*sd*bc*sc*i*
alias:          pci:v00008086d000015C3sv*sd*bc*sc*i*
alias:          pci:v00008086d000015C2sv*sd*bc*sc*i*
alias:          pci:v00008086d000015AEsv*sd*bc*sc*i*
alias:          pci:v00008086d000015ADsv*sd*bc*sc*i*
alias:          pci:v00008086d000015ACsv*sd*bc*sc*i*
alias:          pci:v00008086d000015ABsv*sd*bc*sc*i*
alias:          pci:v00008086d000015B0sv*sd*bc*sc*i*
alias:          pci:v00008086d000015AAsv*sd*bc*sc*i*
alias:          pci:v00008086d000015D1sv*sd*bc*sc*i*
alias:          pci:v00008086d00001563sv*sd*bc*sc*i*
alias:          pci:v00008086d00001560sv*sd*bc*sc*i*
alias:          pci:v00008086d00001558sv*sd*bc*sc*i*
alias:          pci:v00008086d0000154Asv*sd*bc*sc*i*
alias:          pci:v00008086d00001557sv*sd*bc*sc*i*
alias:          pci:v00008086d0000154Dsv*sd*bc*sc*i*
alias:          pci:v00008086d00001528sv*sd*bc*sc*i*
alias:          pci:v00008086d000010F8sv*sd*bc*sc*i*
alias:          pci:v00008086d0000151Csv*sd*bc*sc*i*
alias:          pci:v00008086d00001529sv*sd*bc*sc*i*
alias:          pci:v00008086d0000152Asv*sd*bc*sc*i*
alias:          pci:v00008086d000010F9sv*sd*bc*sc*i*
alias:          pci:v00008086d00001514sv*sd*bc*sc*i*
alias:          pci:v00008086d00001507sv*sd*bc*sc*i*
alias:          pci:v00008086d000010FBsv*sd*bc*sc*i*
alias:          pci:v00008086d00001517sv*sd*bc*sc*i*
alias:          pci:v00008086d000010FCsv*sd*bc*sc*i*
alias:          pci:v00008086d000010F7sv*sd*bc*sc*i*
alias:          pci:v00008086d00001508sv*sd*bc*sc*i*
alias:          pci:v00008086d000010DBsv*sd*bc*sc*i*
alias:          pci:v00008086d000010F4sv*sd*bc*sc*i*
alias:          pci:v00008086d000010E1sv*sd*bc*sc*i*
alias:          pci:v00008086d000010F1sv*sd*bc*sc*i*
alias:          pci:v00008086d000010ECsv*sd*bc*sc*i*
alias:          pci:v00008086d000010DDsv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Bsv*sd*bc*sc*i*
alias:          pci:v00008086d000010C8sv*sd*bc*sc*i*
alias:          pci:v00008086d000010C7sv*sd*bc*sc*i*
alias:          pci:v00008086d000010C6sv*sd*bc*sc*i*
alias:          pci:v00008086d000010B6sv*sd*bc*sc*i*
depends:        dca
retpoline:      Y
name:           ixgbe
vermagic:       5.4.78-2-pve SMP mod_unload modversions
parm:           IntMode:Change Interrupt Mode (0=Legacy, 1=MSI, 2=MSI-X), default 2 (array of int)
parm:           InterruptType:Change Interrupt Mode (0=Legacy, 1=MSI, 2=MSI-X), default IntMode (deprecated) (array of int)
parm:           MQ:Disable or enable Multiple Queues, default 1 (array of int)
parm:           DCA:Disable or enable Direct Cache Access, 0=disabled, 1=descriptor only, 2=descriptor and data (array of int)
parm:           RSS:Number of Receive-Side Scaling Descriptor Queues, default 0=number of cpus (array of int)
parm:           VMDQ:Number of Virtual Machine Device Queues: 0/1 = disable (1 queue) 2-16 enable (default=8) (array of int)
parm:           max_vfs:Number of Virtual Functions: 0 = disable (default), 1-63 = enable this many VFs (array of int)
parm:           VEPA:VEPA Bridge Mode: 0 = VEB (default), 1 = VEPA (array of int)
parm:           InterruptThrottleRate:Maximum interrupts per second, per vector, (0,1,956-488281), default 1 (array of int)
parm:           LLIPort:Low Latency Interrupt TCP Port (0-65535) (array of int)
parm:           LLIPush:Low Latency Interrupt on TCP Push flag (0,1) (array of int)
parm:           LLISize:Low Latency Interrupt on Packet Size (0-1500) (array of int)
parm:           LLIEType:Low Latency Interrupt Ethernet Protocol Type (array of int)
parm:           LLIVLANP:Low Latency Interrupt on VLAN priority threshold (array of int)
parm:           FdirPballoc:Flow Director packet buffer allocation level:
                        1 = 8k hash filters or 2k perfect filters
                        2 = 16k hash filters or 4k perfect filters
                        3 = 32k hash filters or 8k perfect filters (array of int)
parm:           AtrSampleRate:Software ATR Tx packet sample rate (array of int)
parm:           FCoE:Disable or enable FCoE Offload, default 1 (array of int)
parm:           MDD:Malicious Driver Detection: (0,1), default 1 = on (array of int)
parm:           LRO:Large Receive Offload (0,1), default 0 = off (array of int)
parm:           allow_unsupported_sfp:Allow unsupported and untested SFP+ modules on 82599 based adapters, default 0 = Disable (array of int)
parm:           dmac_watchdog:DMA coalescing watchdog in microseconds (0,41-10000), default 0 = off (array of int)
parm:           vxlan_rx:VXLAN receive checksum offload (0,1), default 1 = Enable (array of int)

 

Best Reagrds,

Dolpa

CrisselleF_C_Intel
Moderator
1,252 Views

Hello Dolpa,


Thank you for the additional information provided. 


Rest assured that we will forward this to our engineers and get back to you as soon as we heard from them.


Feel free to let us know if there is additional questions and clarifications.


Best regards,

Crisselle C

Intel® Customer Support


CrisselleF_C_Intel
Moderator
1,226 Views

Hello Dolpa,


Good day!


Please be informed that we are still checking your request with our engineers. We will send an update as soon as we heard from them but no later than 2-4 business days.


Hoping for your kind patience.


Best regards,

Crisselle C

Intel® Customer Support


Dolpa
Novice
1,222 Views

Hello Crisselle,

 

Thank you for working on this issue.

Have a nice day!

 

Best regards,

Dolpa

 

CrisselleF_C_Intel
Moderator
1,159 Views

Hello Dolpa,


Apologies for the delay on this matter.


We'd like to inform you that we are still actively working on this issue with our higher level Engineers. Rest assured that we are doing our best to sort this out as soon as possible. We will get back to you for another update within 2-4 business days.


Thank you for your kind patience.


Best regards,

Crisselle C

Intel® Customer Support


Dolpa
Novice
1,156 Views

Hello Crisselle,

 

Thank you, I'm waiting.

 

Best regards,

Dolpa

CrisselleF_C_Intel
Moderator
1,139 Views

Hello Dolpa,


How are you doing? 


This is just an update to let you know that this request is still under investigation. We will get back to you as soon as we heard an update from our engineers but no later than 2-4 business days.


May you have an amazing weekend ahead!


Best regards,

Crisselle C

Intel® Customer Support


Dolpa
Novice
1,133 Views

Hello Crisselle,

 

I'm looking forward to the result.

 

Best regards,

Dolpa

CrisselleF_C_Intel
Moderator
1,109 Views

Hello Dolpa,


I hope you are going good!


We sincerely apologize for the delay on this matter as we are thoroughly checking on this. Please give us more time to look into this. Rest assured that we will update you as soon as there is any findings but not later than 4 business days.


Thank you for your kind understanding.


Best regards,

Crisselle C

Intel® Customer Support


Dolpa
Novice
1,106 Views

Hello Crisselle,

 

Oh, I didn’t think this is such a complicated case.

 

Best regards,

Dolpa

CrisselleF_C_Intel
Moderator
1,023 Views

Hello Dolpa,


I hope you are doing great.


Please be informed that this request is still escalated to our engineers. We are currently waiting for an update from them and we will get back to you as soon as there is any. We hope you don't mind giving us more time with the investigation.


Hoping for your patience.


Best regards,

Crisselle C

Intel® Customer Support


Dolpa
Novice
1,017 Views

Hello Crisselle,

 

Thank You. I'm waiting for the result.

 

Best regards,

Dolpa

CrisselleF_C_Intel
Moderator
985 Views

Hello Dolpa,


How are you doing?


We'd like to inform you that we are still actively working on this issue with our higher level Engineers. We apologize as this is taking too long but rest assured that we are doing our best to sort this out as soon as possible. We will keep you posted and get back to you within 2-4 business days.


Thank you for your kind understanding.


Best regards,

Crisselle C

Intel® Customer Support


Dolpa
Novice
976 Views

Hello Crisselle,

 

Thank You for the hard working. I'm waiting for the result.

 

Best regards,

Dolpa

CrisselleF_C_Intel
Moderator
909 Views

Hello Dolpa,


Thank you for the patience on this matter.


Please see and provide below information from our engineers. 


80000AEE to 8001373 update increases the Security Revision of the NVM and the tool will block the "downgrade" to the original NVM. With this, we regret to inform you that we may not be able to downgrade it anymore. However, we will try to check as to why the port behavior changes after upgrade.

1.) Our engineering team would like to confirm if this is the exact model of your motherboard. 

Asrock Rack ROMED8-2T https://www.asrockrack.com/general/productdetail.asp?Model=ROMED8-2T

2.) Please send us the NVM file or Dump of the Flash before and after the update(if there is any).


Looking forward to your reply.


Should there be no response from you, I’ll make sure to reach out via phone after 3 business days.


Best regards,

Crisselle C

Intel® Customer Support


Dolpa
Novice
906 Views

Hello Crisselle,

 

Thank You for the response.

1. Yes I have the Asrock Rack ROMED8-2T motherboard.

2. I attached the before and after NVM bins zip file.

A before.bin is the backed up 80000AEE  and the after.bin is the 8001373.

Best regards,

Dolpa

CrisselleF_C_Intel
Moderator
904 Views

Hello Dolpa,


Appreciate your swift response.


Please allow us to forward your response to our engineers. We will get back to you as soon as there is any findings but no later than 2-4 business days.


Hoping for your kind patience. 


Best regards,

Crisselle C

Intel® Customer Support


Frieder
Novice
889 Views

Hi,

I have a similar issue with 3 Mainboards of the type  Asrock Rack X570D4U-2L2T with Intel X550-AT2 onboard.

After the update to the current firmware version of the Intel X550-AT2 (needed due to the virtualization features of the new firmware), only ONE of both Ethernet-Interface is getting a link.

The other interface is dead.

Firmware downgrade is not possible.  (as already described in this thread)

The issue a appears after the first complete powerloss of the system.  Shutting down / rebooting the system via the IPMI-Interface of the Mainboard is not enough to make the issue of the firmware update visible. 

 

Is there already a solution for this issue?

 

Thanks & BR

Frieder

Dolpa
Novice
921 Views

Hello Frieder,

 

As you read in this thread there is no solution yet, engineers working on. They try to investigate the differences of the two firmwares.

The big mistake was that AsrockRack did not rewrite the firmware version number to another different one, but left the original intel version number and thus the official firmware update recognized it as an updatable NIC.

This is a very bad thing because everyone who try to update the firmware will make a half brick from the 2 onboard NIC. And there is no AsrockRack NIC firmware update packages.

Best Regards,

Dolpa

Reply