I'm trying to setup a system with two I210 controllers. The 2nd one operates in Flash-less mode
and I have problems to get it working.
I have successfully programmed the INVM using the eeupdate64e tool with:
eeupdate64e /nic=2 /invmupdate /file=I210_Invm_Copper_NoAPM_v0.6.txt
It now reports:
Using: Intel (R) PRO Network Connections SDK v2.25.20
EEUPDATE v5.25.20.03
Copyright (C) 1995 - 2015 Intel Corporation
Intel (R) Confidential and not for general distribution.
Driverless Mode
Warning: No Adapter Selected
NIC Bus Dev Fun Vendor-Device Branding string
=== === === === ============= =================================================
1 1 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
2 3 00 00 8086-157B Intel(R) I210 Gigabit Network Connection
The 2nd NIC is the one without flash.
However, when I try to program the MAC address, it fails:
eeupdate64e /nic=2 /mac=001395160935
NIC Bus Dev Fun Vendor-Device Branding string
=== === === === ============= =================================================
1 1 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
2 3 00 00 8086-157B Intel(R) I210 Gigabit Network Connection
2: Updating Mac Address to 001395160935...Failed!
Further more when I load the driver "igb" in linux, it reports an
invalid checksum on the 2nd NIC:
Intel(R) Gigabit Ethernet Network Driver - version 5.3.2
Copyright (c) 2007-2015 Intel Corporation.
igb 0000:01:00.0: irq 76 for MSI/MSI-X
igb 0000:01:00.0: irq 77 for MSI/MSI-X
igb 0000:01:00.0: added PHC on eth0
igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection
igb 0000:01:00.0: eth0: (PCIe:2.5GT/s:Width x1)
igb 0000:01:00.0 eth0: MAC: 00:13:95:16:09:34
igb 0000:01:00.0: eth0: PBA No: 000300-000
igb 0000:01:00.0: LRO is disabled
igb 0000:01:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
igb 0000:03:00.0: irq 78 for MSI/MSI-X
igb 0000:03:00.0: irq 79 for MSI/MSI-X
igb 0000:03:00.0: The NVM Checksum Is Not Valid
igb: probe of 0000:03:00.0 failed with error -5
Basically I have two questions now:
1. Why does the MAC address programming fail?
2. Why does the driver complain about the checksum? As far as I know there isn't
a checksum in the internal memory.
Regards,
Felix