- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Description:
While attempting to flash CAM firmware on an Intel E810 NIC using the devlink interface on a system running Linux kernel version 5.10.0, the firmware update process does not complete as expected. The devlink tool fails to initiate the flashing of the firmware file CAM1_Whitestone2_v_4_20.bin. According to Intel document #630155_CVL_EXTERNAL_E810 Feature Summary, kernel versions 5.10 and later should fully support NVM (Non-Volatile Memory) updates through the devlink interface, but this issue is still observed.
Updating with NVM Update Tool is also failing
To avoid damage to your device do not stop the update or reboot or power off the system during update. Intel Ethernet controller E810-C for SRP, DevID, 1593, 00:067, Update not available.
===========================================================================
Thank you for sharing the information. Since the Intel® Ethernet Controller E810-CAM1 is
integrated into the system, we recommend posting your query in the Embedded Connectivity forum for further information regarding the query.
Please follow the link below for Embedded Connectivity.
https://community.intel.com/t5/Embedded-Connectivity/bd-p/embedded-networking-connectivity
2 days ago 14:52
===========================================================================
Thank you for contacting Intel Support. We appreciate you sharing the detailed information. We kindly request you to check the link below for complete information regarding the Devlink user guidelines to update a device's NVM.
We recommend that you use the NVM Update tool.
See Intel® Ethernet NVM Update Tool for more information on this tool.
If you have any questions or doubts, Please reach out to us, We are happy to help you!
We appreciate your understanding!
===========================
Card details:
43:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)
DeviceName: E810 CAM1 Port1
Subsystem: Mitac Device 0014
Physical Slot: 2
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: 32 bytes
Interrupt: pin A routed to IRQ 16
NUMA node: 0
IOMMU group: 22
Region 0: Memory at 202ffa000000 (64-bit, prefetchable) [size=32M]
Region 3: Memory at 202ffe030000 (64-bit, prefetchable) [size=64K]
Expansion ROM at be200000 [disabled] [size=1M]
Capabilities: <access denied>
Kernel driver in use: ice
Kernel modules: ice
43:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)
DeviceName: E810 CAM1 Port2
Subsystem: Mitac Device 0014
Physical Slot: 2
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: 32 bytes
Interrupt: pin A routed to IRQ 16
NUMA node: 0
IOMMU group: 23
Region 0: Memory at 202ff8000000 (64-bit, prefetchable) [size=32M]
Region 3: Memory at 202ffe020000 (64-bit, prefetchable) [size=64K]
Expansion ROM at be100000 [disabled] [size=1M]
Capabilities: <access denied>
Kernel driver in use: ice
Kernel modules: ice
43:00.2 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)
DeviceName: E810 CAM1 Port3
Subsystem: Mitac Device 0014
Physical Slot: 2
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: 32 bytes
Interrupt: pin A routed to IRQ 16
NUMA node: 0
IOMMU group: 24
Region 0: Memory at 202ff6000000 (64-bit, prefetchable) [size=32M]
Region 3: Memory at 202ffe010000 (64-bit, prefetchable) [size=64K]
Expansion ROM at be000000 [disabled] [size=1M]
Capabilities: <access denied>
Kernel driver in use: ice
Kernel modules: ice
===========================================================
[ognb@WS03-A3370001 ~]$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 64
On-line CPU(s) list: 0-63
Thread(s) per core: 2
Core(s) per socket: 32
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 143
Model name: Intel(R) Xeon(R) Gold 6433N
Stepping: 8
CPU MHz: 1400.000
CPU max MHz: 3600.0000
CPU min MHz: 800.0000
BogoMIPS: 2800.00
Virtualization: VT-x
L1d cache: 48K
L1i cache: 32K
L2 cache: 2048K
L3 cache: 61440K
NUMA node0 CPU(s): 0-63
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cat_l2 cdp_l3 invpcid_single cdp_l2 ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect avx_vnni avx512_bf16 wbnoinvd dtherm ida arat pln pts hwp hwp_act_window hwp_pkg_req hfi avx512vbmi umip pku ospke waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid bus_lock_detect cldemote movdiri movdir64b enqcmd fsrm md_clear serialize tsxldtrk pconfig arch_lbr avx512_fp16 flush_l1d arch_capabilities
===========================================================================
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Phai,
Greetings for the day!
Thank you for posting in the Intel Community. We sincerely apologize for the delay in our response. We have received your concern and would like to assure you that assisting you is our top priority.
Could you kindly let us know if the issue has been resolved, or if you require further assistance from us? Your prompt response will greatly help us in diagnosing and resolving the issue as quickly as possible.
We appreciate your patience and understanding, and we look forward to hearing from you soon.
Regards
Jerome
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Phani,
Greetings for the day!
This is to follow up on the issue you reported with us.
Could you kindly let us know if the issue has been resolved, or if you require further assistance from us? Your prompt response will greatly help us in diagnosing and resolving the issue as quickly as possible.
We appreciate your patience and understanding, and we look forward to hearing from you soon.
Regards
Jerome
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Phani,
Greetings for the day!
This is a final follow up on the issue you reported with us.
Could you kindly let us know if the issue has been resolved, or if you require further assistance from us? Your prompt response will greatly help us in diagnosing and resolving the issue as quickly as possible.
We appreciate your patience and understanding, and we look forward to hearing from you soon.
Regards
Jerome
Intel Customer Support Technician
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page