Ethernet Products
Intel® Ethernet products and technologies
4088 Discussions

nvmupdate64e gives Access error

Marco_Canini
Beginner
862 Views

Hello.

 

I have an Intel E810-2CQDA2 Dual-Port 100GbE installed on a Ubuntu 20.04 system with Linux 5.15.0-48-generic.

 

$ ethtool -i enp2s0

driver: ice
version: 5.15.0-48-generic
firmware-version: 3.20 0x8000d846 1.3146.0
expansion-rom-version:
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes

 

When I run the nvmupdate64e (v4.01) tool, I get an Access error message and I cannot proceed to update the firmware.

 

Num Description Ver.(hex) DevId S:B Status
=== ================================== ============ ===== ====== ==============
01) Intel(R) Ethernet Network Adapter N/A(N/A) 1592 00:002 Access error
E810-2C-Q2

 

I'm using E810_NVMUpdatePackage_v4_01_Linux.tar.gz obtained from https://downloadmirror.intel.com/742508/Release_27.6.1.zip

 

The card is not an OEM unit. 

 

Thanks for the assistance!

Labels (1)
0 Kudos
14 Replies
Marco_Canini
Beginner
846 Views

A photo of the NIC:

IMG_20220928_174403.jpgIMG_20220928_174327.jpg

Crisselle_Intel
Moderator
841 Views

Hello Marco_Canini,


Thank you for posting in Intel Ethernet Communities. 


Please share the following information that would help in checking your request. 

1. Is this newly purchased adapter?

2. For how long is the E810-2CQDA2 working fine?

3. Do you encounter any issue on the E810-2CQDA2 aside from the Firmware update issue?

4. Can you share if you already tried installing the latest ice driver version 1.9.11 from link below then try updating the Firmware again to version 4.01?

Intel® Network Adapter Driver for E810 Series Devices under Linux*

https://www.intel.com/content/www/us/en/download/19630/intel-network-adapter-driver-for-e810-series-...


Looking forward to your reply. 


We will follow up after 3 business days in case we don't hear from you.


Best regards,

Crisselle C.

Intel® Customer Support


Marco_Canini
Beginner
837 Views

Hello Crisselle,

 

1. Yes, this is a newly purchased NIC.

2. The NIC appears to be working fine but the OS reports a single Ethernet port even though the NIC is dual port.

3. Same as 2.

4. I have not tried to install the latest driver. I will do that.

Crisselle_Intel
Moderator
821 Views

Hello Marco_Canini,


Thank you for the swift response. 


While we are waiting for you to test the latest driver, can you also share the exact brand and model of the motherboard where the E810-2CQDA2 was installed?


Awaiting to your reply. 


Should there be no response from you, we will follow up after 3 business days.


Best regards,

Crisselle C.

Intel® Customer Support


Marco_Canini
Beginner
786 Views

Hello Criselle.

 

After updating the ice drivers as you suggested, I was able to perform the firmware update.

 

On the upside, I now have more information from the driver about the NIC.

On the downside, I am still unsure why, despite this is a dual-port NIC, only one port comes up

 

The driver's log shows some message about the PCIe bandwidth being limited:

[73934.572029] ice: Intel(R) Ethernet Connection E800 Series Linux Driver - version 1.9.11
[73934.572033] ice: Copyright (C) 2018-2021, Intel Corporation.
[73935.037183] ice 0000:02:00.0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.30.0
[73935.122978] ice 0000:02:00.0: PTP init successful
[73935.485947] ice 0000:02:00.0: DCB is enabled in the hardware, max number of TCs supported on this port are 8
[73935.485949] ice 0000:02:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[73935.486056] ice 0000:02:00.0: Commit DCB Configuration to the hardware
[73935.488225] ice 0000:02:00.0: 126.024 Gb/s available PCIe bandwidth, limited by 16.0 GT/s PCIe x8 link at 0000:00:03.1 (capable of 252.048 Gb/s with 16.0 GT/s PCIe x16 link)

 

The message above seems to reference a wrong PCI ID (00:03.1) though.

The NIC's PCI ID is 02:00.0 and I've the following info about it.

It mentions a downgrade of the PCI width from x16 to x8.

LnkSta: Speed 16GT/s (ok), Width x8 (downgraded)

$ lspci -vv -s 02:00.0
02:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for QSFP (rev 02)
        Subsystem: Intel Corporation Ethernet Network Adapter E810-2C-Q2
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 55
        IOMMU group: 72
        Region 0: Memory at 280b2000000 (64-bit, prefetchable) [size=32M]
        Region 3: Memory at 280b1000000 (64-bit, prefetchable) [size=64K]
        Expansion ROM at f9300000 [disabled] [size=1M]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
                Address: 0000000000000000  Data: 0000
                Masking: 00000000  Pending: 00000000
        Capabilities: [70] MSI-X: Enable+ Count=2048 Masked-
                Vector table: BAR=3 offset=00000000
                PBA: BAR=3 offset=00008000
        Capabilities: [a0] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
                DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq-
                        RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop- FLReset-
                        MaxPayload 512 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 16GT/s, Width x16, ASPM not supported
                        ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
                LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 16GT/s (ok), Width x8 (downgraded)
                        TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Range AB, TimeoutDis+ NROPrPrP- LTR-
                         10BitTagComp+ 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix+, MaxEETLPPrefixes 1
                         EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
                         FRS- TPHComp- ExtTPHComp-
                         AtomicOpsCap: 32bit- 64bit- 128bitCAS-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
                         AtomicOpsCtl: ReqEn-
                LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
                LnkCtl2: Target Link Speed: 16GT/s, EnterCompliance- SpeedDis-
                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+ EqualizationPhase1+
                         EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
                         Retimer- 2Retimers- CrosslinkRes: unsupported
        Capabilities: [e0] Vital Product Data
                Product Name: Intel(R) Ethernet Network Adapter E810-2CQDA2
                Read-only fields:
                        [V1] Vendor specific: Intel(R) Ethernet Network Adapter E810-2CQDA2
                        [PN] Part number: K87758-009
                        [SN] Serial number: 40A6B79EE9F8
                        [V2] Vendor specific: 2722
                        [RV] Reserved: checksum good, 0 byte(s) reserved
                End
        Capabilities: [100 v2] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO+ CmpltAbrt- UnxCmplt+ RxOF+ MalfTLP+ ECRC+ UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
                AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn+ ECRCChkCap+ ECRCChkEn+
                        MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
                HeaderLog: 00000000 00000000 00000000 00000000
        Capabilities: [148 v1] Alternative Routing-ID Interpretation (ARI)
                ARICap: MFVC- ACS-, Next Function: 0
                ARICtl: MFVC- ACS-, Function Group: 0
        Capabilities: [150 v1] Device Serial Number 40-a6-b7-ff-ff-9e-e9-f8
        Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV)
                IOVCap: Migration-, Interrupt Message Number: 000
                IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy+
                IOVSta: Migration-
                Initial VFs: 256, Total VFs: 256, Number of VFs: 0, Function Dependency Link: 00
                VF offset: 8, stride: 1, Device ID: 1889
                Supported Page Size: 00000553, System Page Size: 00000001
                Region 0: Memory at 00000280b4000000 (64-bit, prefetchable)
                Region 3: Memory at 00000280b1010000 (64-bit, prefetchable)
                VF Migration: offset: 00000000, BIR: 0
        Capabilities: [1a0 v1] Transaction Processing Hints
                Device specific mode supported
                No steering table available
        Capabilities: [1b0 v1] Access Control Services
                ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
                ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
        Capabilities: [1d0 v1] Secondary PCI Express
                LnkCtl3: LnkEquIntrruptEn- PerformEqu-
                LaneErrStat: 0
        Capabilities: [200 v1] Data Link Feature <?>
        Capabilities: [210 v1] Physical Layer 16.0 GT/s <?>
        Capabilities: [250 v1] Lane Margining at the Receiver <?>
        Kernel driver in use: ice
        Kernel modules: ice

 

 

 

Marco_Canini
Beginner
779 Views

With regard to this question:

> While we are waiting for you to test the latest driver, can you also share the exact brand and model of the motherboard where the E810-2CQDA2 was installed?

 

The NIC is installed on an ASUS ESC N4A-E11. The server board is ASUS KMPN-U16 Server Board. The NIC is installed in the PCIe Gen4 expansion slot.

Crisselle_Intel
Moderator
761 Views

Hello Marco_Canini, 


Thank you for the reply. 


We are glad to hear that the Firmware update was successful. To further check the issue wherein OS reports a single Ethernet port even though the NIC is dual port, please check and share the following information. 


1. Have you tried installing the E810-2CQDA2 on another PCIe slot or different motherboard?

2. Please check the compatibility of the card with the board's manufacturer. 

3. When you say only one port comes up, does this mean that any of the two ports only work? Or only the port 1 is working?


Looking forward to your reply. 


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


Best regards,

Crisselle C.

Intel® Customer Support 


Marco_Canini
Beginner
740 Views

Hello Criselle.

 

1. We tried at a different PCIe slot but in that case the OS does not even recognize the presence of the card.

2. We are contacting their support.

3. I mean that at the level of the OS, there exists only one interface that we can configure and use. The driver's log refers to it as port 0. On the NIC, the is the port that is farthest from the PCI connector. In the photo below, it is the port with the DAC cable plugged (the black cable). This port works. We can bring up the link and the port appears to work. But the other port is not visible from the OS.

309216863_926394608335953_7864037198146334389_n.jpg

Crisselle_Intel
Moderator
737 Views

Hello Marco_Canini, 


Appreciate your swift reply. 


Please try checking below link as this might help resolving the issue. 


Only One Port of the Intel® Ethernet Network Adapter E810-2CQDA2 Is Working on a Dell PowerEdge R740

https://www.intel.com/content/www/us/en/support/articles/000090670/ethernet-products/800-series-netw...


Resolution:

It is important to review the bifurcation settings in BIOS to ensure the card is working with PCIe x16 bifurcation enabled. There have been reports from customers that were able to solve this issue by enabling the bifurcation setting in the system BIOS.


Please contact the system/platform manufacturer for detailed instructions on how to perform the necessary adjustments.


Here is the list of System Manufacturer

https://www.intel.in/content/www/in/en/support/contact-intel.html?tab=system-manufacturers


Direct link for ASUS Support

https://www.asus.com/us/support/


Feel free to let us know if you have questions or clarifications. 


Awaiting to your reply. 


We will follow up after 3 business days in case we don't hear from you. 


Best regards,

Crisselle C.

Intel® Customer Support 


Crisselle_Intel
Moderator
686 Views

Hello Marco_Canini, 


Good day!


This is just a follow up to check if you read our reply. If yes, please confirm and advise if you are able to check the link we shared. 


We would also highly appreciate if you can share some update regarding this matter. 


Hoping to hear from you soon. 


Should there be no reply from you, we will follow up after 3 business days.


Best regards,

Crisselle C.

Intel® Customer Support


Marco_Canini
Beginner
596 Views

Thanks.

 

Currently checking with ASUS regarding PCI bifurcation.

Mike_Intel
Moderator
580 Views

Hello Marco_Canini, 


Thank you for the update. Since you are now talking to Asus, is it okay if we can close this case?


If you have questions, please let us know. In case we do not hear from you, we will make a follow up after 3 workings days. Thank you.


Best regards,

Michael L.

Intel® Customer Support


Marco_Canini
Beginner
572 Views

Hi Michael,

 

yes, we can close it. Thank you.

Crisselle_Intel
Moderator
496 Views

Hello Marco_Canini, 


Thank you for the confirmation.


Please be informed that we will now close this request. 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.


May you have an amazing week and stay safe!


Best regards,

Crisselle C.

Intel Customer Support


Reply