I've been going around in circles all day with this and I'm no closer. Tried all sorts of suggested solutions I can find.
I'm trying to get an Intel PRO/1000 PT Quad Port adapter working in Linux on my Dell Precision. The system has an onboard Intel 82579LM which is working fine and is using the e1000e kernel module. As far as I can tell, the quad port has 82571EB controller and should work with the same e1000e kernel module. But, the four interfaces of the quad port are all showing as UNCLAIMED.
This is a fresh build system and I've tried Ubuntu Server 20.04 and Rocky/CentOS 8, all with the same result.
Here's some output samples to show what I'm seeing.
lshw -C network
*-network:0 UNCLAIMED
description: Ethernet controller
product: 82571EB PRO/1000 AT Quad Port Bypass Adapter
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:08:00.0
version: 06
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: latency=0
resources: memory:fb8a0000-fb8bffff memory:fb880000-fb89ffff ioport:b020(size=32) memory:fb860000-fb87ffff
*-network:1 UNCLAIMED
description: Ethernet controller
product: 82571EB PRO/1000 AT Quad Port Bypass Adapter
vendor: Intel Corporation
physical id: 0.1
bus info: pci@0000:08:00.1
version: 06
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: latency=0
resources: memory:fb840000-fb85ffff memory:fb820000-fb83ffff ioport:b000(size=32) memory:fb800000-fb81ffff
*-network:0 UNCLAIMED
description: Ethernet controller
product: 82571EB PRO/1000 AT Quad Port Bypass Adapter
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:09:00.0
version: 06
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: latency=0
resources: memory:fb7a0000-fb7bffff memory:fb780000-fb79ffff ioport:a020(size=32) memory:fb760000-fb77ffff
*-network:1 UNCLAIMED
description: Ethernet controller
product: 82571EB PRO/1000 AT Quad Port Bypass Adapter
vendor: Intel Corporation
physical id: 0.1
bus info: pci@0000:09:00.1
version: 06
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: latency=0
resources: memory:fb740000-fb75ffff memory:fb720000-fb73ffff ioport:a000(size=32) memory:fb700000-fb71ffff
*-network
description: Ethernet interface
product: 82579LM Gigabit Network Connection (Lewisville)
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eno1
version: 05
serial: 18:03:73:3a:c4:0c
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=4.18.0-348.el8.0.2.x86_64 duplex=full firmware=0.13-4 ip=192.168.192.104 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:50 memory:fbf00000-fbf1ffff memory:fbf29000-fbf29fff ioport:f040(size=32)
lspci | grep Ethernet
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 05)
08:00.0 Ethernet controller: Intel Corporation 82571EB PRO/1000 AT Quad Port Bypass Adapter (rev 06)
08:00.1 Ethernet controller: Intel Corporation 82571EB PRO/1000 AT Quad Port Bypass Adapter (rev 06)
09:00.0 Ethernet controller: Intel Corporation 82571EB PRO/1000 AT Quad Port Bypass Adapter (rev 06)
09:00.1 Ethernet controller: Intel Corporation 82571EB PRO/1000 AT Quad Port Bypass Adapter (rev 06)
[ 2.110651] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 2.194772] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[ 2.278708] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 18:03:73:3a:c4:0c
[ 2.278778] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 2.278891] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 7041FF-0FF
[ 2.280277] e1000e 0000:00:19.0 eno1: renamed from eth0
[ 10.647032] e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
I'm almost resigned to the fact that the card is just too old but I've read a lot of stuff that seems to indicate it should work with that driver so I'm hoping I'm just doing something fundamentally wrong.