network driver not detecting

Issues related to hardware problems
Post Reply
drbonev
Posts: 7
Joined: 2019/11/04 10:23:19

network driver not detecting

Post by drbonev » 2020/01/27 18:14:21

Hi, I am having a similar problem with an Intel I350 on Centos 7 on a Lenovo. I can see the card in lspci.

Output from:
grep -i 8086 /lib/modules/3.10.0-1062.9.1.el7.x86_64/modules.* | grep -i 1521
is:
/lib/modules/3.10.0-1062.9.1.el7.x86_64/modules.alias:alias pci:v00008086d00001521sv*sd*bc*sc*i* igb
so the card is recognised and the igb seems to be there. The ONBOOT=yes is also set in the ifcfg file. Yet, when enabled via the GUI, the card is searching for connection but never connects. I also have a 10 GB onboard interface, which has identical config and works fine.

Does anyone have any suggestions?

[Split away from viewtopic.php?f=49&t=68381&p=308237#p308237 which is too old]

User avatar
TrevorH
Forum Moderator
Posts: 28069
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: network driver not detecting

Post by TrevorH » 2020/01/27 18:17:38

Post the output from dmesg | grep -i igb and check the output from ip link show for unused devices.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

drbonev
Posts: 7
Joined: 2019/11/04 10:23:19

Re: network driver not detecting

Post by drbonev » 2020/01/28 12:40:49

Many thanks Trevor, here is the output from dmesg | grep -i igb:
[ 1.477833] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
[ 1.477836] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 1.478284] igb 0000:02:00.0: irq 35 for MSI/MSI-X
[ 1.478325] igb 0000:02:00.0: irq 35 for MSI/MSI-X
[ 1.478333] igb 0000:02:00.0: irq 36 for MSI/MSI-X
[ 1.478340] igb 0000:02:00.0: irq 37 for MSI/MSI-X
[ 1.478346] igb 0000:02:00.0: irq 38 for MSI/MSI-X
[ 1.478352] igb 0000:02:00.0: irq 39 for MSI/MSI-X
[ 1.478358] igb 0000:02:00.0: irq 40 for MSI/MSI-X
[ 1.478364] igb 0000:02:00.0: irq 41 for MSI/MSI-X
[ 1.478370] igb 0000:02:00.0: irq 42 for MSI/MSI-X
[ 1.478376] igb 0000:02:00.0: irq 43 for MSI/MSI-X
[ 1.536291] igb 0000:02:00.0: added PHC on eth0
[ 1.536294] igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 1.536297] igb 0000:02:00.0: eth0: (PCIe:5.0Gb/s:Width x4) b4:96:91:1f:56:a0
[ 1.536614] igb 0000:02:00.0: eth0: PBA No: G93550-005
[ 1.536617] igb 0000:02:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[ 1.537033] igb 0000:02:00.1: irq 45 for MSI/MSI-X
[ 1.537087] igb 0000:02:00.1: irq 45 for MSI/MSI-X
[ 1.537092] igb 0000:02:00.1: irq 46 for MSI/MSI-X
[ 1.537098] igb 0000:02:00.1: irq 47 for MSI/MSI-X
[ 1.537103] igb 0000:02:00.1: irq 48 for MSI/MSI-X
[ 1.537109] igb 0000:02:00.1: irq 49 for MSI/MSI-X
[ 1.537115] igb 0000:02:00.1: irq 50 for MSI/MSI-X
[ 1.537120] igb 0000:02:00.1: irq 51 for MSI/MSI-X
[ 1.537126] igb 0000:02:00.1: irq 52 for MSI/MSI-X
[ 1.537132] igb 0000:02:00.1: irq 53 for MSI/MSI-X
[ 1.593779] igb 0000:02:00.1: added PHC on eth1
[ 1.593783] igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection
[ 1.593786] igb 0000:02:00.1: eth1: (PCIe:5.0Gb/s:Width x4) b4:96:91:1f:56:a1
[ 1.594102] igb 0000:02:00.1: eth1: PBA No: G93550-005
[ 1.594104] igb 0000:02:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)

and from ip link show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether b4:96:91:1f:56:a0 brd ff:ff:ff:ff:ff:ff
3: enp179s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether b4:96:91:1f:56:a1 brd ff:ff:ff:ff:ff:ff
4: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether f4:93:9f:ec:fb:e7 brd ff:ff:ff:ff:ff:ff
5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:37:d5:20 brd ff:ff:ff:ff:ff:ff
6: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:37:d5:20 brd ff:ff:ff:ff:ff:ff

drbonev
Posts: 7
Joined: 2019/11/04 10:23:19

Re: network driver not detecting

Post by drbonev » 2020/01/28 13:25:18

Actually, this was the output with the working interface connected. Here is the output with the cable connected to the card:

[ 1.477833] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
[ 1.477836] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 1.478284] igb 0000:02:00.0: irq 35 for MSI/MSI-X
[ 1.478325] igb 0000:02:00.0: irq 35 for MSI/MSI-X
[ 1.478333] igb 0000:02:00.0: irq 36 for MSI/MSI-X
[ 1.478340] igb 0000:02:00.0: irq 37 for MSI/MSI-X
[ 1.478346] igb 0000:02:00.0: irq 38 for MSI/MSI-X
[ 1.478352] igb 0000:02:00.0: irq 39 for MSI/MSI-X
[ 1.478358] igb 0000:02:00.0: irq 40 for MSI/MSI-X
[ 1.478364] igb 0000:02:00.0: irq 41 for MSI/MSI-X
[ 1.478370] igb 0000:02:00.0: irq 42 for MSI/MSI-X
[ 1.478376] igb 0000:02:00.0: irq 43 for MSI/MSI-X
[ 1.536291] igb 0000:02:00.0: added PHC on eth0
[ 1.536294] igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 1.536297] igb 0000:02:00.0: eth0: (PCIe:5.0Gb/s:Width x4) b4:96:91:1f:56:a0
[ 1.536614] igb 0000:02:00.0: eth0: PBA No: G93550-005
[ 1.536617] igb 0000:02:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[ 1.537033] igb 0000:02:00.1: irq 45 for MSI/MSI-X
[ 1.537087] igb 0000:02:00.1: irq 45 for MSI/MSI-X
[ 1.537092] igb 0000:02:00.1: irq 46 for MSI/MSI-X
[ 1.537098] igb 0000:02:00.1: irq 47 for MSI/MSI-X
[ 1.537103] igb 0000:02:00.1: irq 48 for MSI/MSI-X
[ 1.537109] igb 0000:02:00.1: irq 49 for MSI/MSI-X
[ 1.537115] igb 0000:02:00.1: irq 50 for MSI/MSI-X
[ 1.537120] igb 0000:02:00.1: irq 51 for MSI/MSI-X
[ 1.537126] igb 0000:02:00.1: irq 52 for MSI/MSI-X
[ 1.537132] igb 0000:02:00.1: irq 53 for MSI/MSI-X
[ 1.593779] igb 0000:02:00.1: added PHC on eth1
[ 1.593783] igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection
[ 1.593786] igb 0000:02:00.1: eth1: (PCIe:5.0Gb/s:Width x4) b4:96:91:1f:56:a1
[ 1.594102] igb 0000:02:00.1: eth1: PBA No: G93550-005
[ 1.594104] igb 0000:02:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[71533.242009] igb 0000:02:00.1 enp179s0f0: igb: enp179s0f0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether b4:96:91:1f:56:a0 brd ff:ff:ff:ff:ff:ff
3: enp179s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether b4:96:91:1f:56:a1 brd ff:ff:ff:ff:ff:ff
4: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether f4:93:9f:ec:fb:e7 brd ff:ff:ff:ff:ff:ff
5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:37:d5:20 brd ff:ff:ff:ff:ff:ff
6: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:37:d5:20 brd ff:ff:ff:ff:ff:ff

Many thansk for looking into this!

User avatar
TrevorH
Forum Moderator
Posts: 28069
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: network driver not detecting

Post by TrevorH » 2020/01/28 15:13:41

[71533.242009] igb 0000:02:00.1 enp179s0f0: igb: enp179s0f0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
100Mbps? Is that correct? If not then it's either a sign of a dodgy cable or switch port or ethernet port on the machine I suspect.

Also, if this happens to be a Dell machine, make sure that the options in the machine BIOS for SR-IOV match the ones in the bios setup for each card. There are SR-IOV settings in both places and they must agree with each other or weird stuff happens.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

drbonev
Posts: 7
Joined: 2019/11/04 10:23:19

Re: network driver not detecting

Post by drbonev » 2020/01/28 16:27:13

Yes, it's supposed to be a 100 Mbps card with two ports. The machine is Lenovo with Intel board and chipset. I suspect the card config on the system side is fine but the handshake with the network mis-communicates the speed. The GUI seems happy and on connection to the cable keeps trying to talk to the network reading "Connecting" for about a minute, then gives up and closes the port. I wonder if the hardware manages correctly packet speed and is able to negotiate 10 Mbps correcrtly. I also need to check if the LAN supports 100 Mbps.

Will have a look at the BIOS.

Thanks for looking into this!

drbonev
Posts: 7
Joined: 2019/11/04 10:23:19

Re: network driver not detecting

Post by drbonev » 2020/01/28 16:30:20

Cable is the same, just swapped between the 10 Mbps port and the card. You are probably right and the card may be faulty. The system must have been assembled by an ape because the screws that hold all PCI cards and blanking plates were inserted from the wrong end. The blanking plates (and PCI cards) were completely loose and I was lucky a blanking palte didn't drop on the motherboard with the power on...

User avatar
TrevorH
Forum Moderator
Posts: 28069
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: network driver not detecting

Post by TrevorH » 2020/01/28 16:58:14

Well I think it must be a 1Gbps card since all the cards that igb supports are 1Gbe. It might only be plugged into a port that negotiates 100Mbps from teh switch side...

You might want to look at if it's being told to use fixed parameters and not negotiate them with the switch - for example the log says 100Mbps Full Duplex, does the switch support that?
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

drbonev
Posts: 7
Joined: 2019/11/04 10:23:19

Re: network driver not detecting

Post by drbonev » 2020/01/28 17:08:19

It does look more like a hardware issue, will dig further. Many thanks for your help, again!

Post Reply

Return to “CentOS 7 - Hardware Support”