HowTo UP second eth on network card

mashrum · 2020-03-11 06:14:04

Embedded 2 port Intel I211
Default kernel module - igb
The first eth created and works fine
The second eth detected on PCI but interface is not created in system, and IP can't be added
cable is connected - yes

I can't understand how the first interface was created and how to add second one

/usr/lib/systemd/network/ - all by default
/usr/lib/udev/rules.d/75-net-description.rules - by default
/usr/lib/udev/rules.d/80-net-setup-link.rules - by default

ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 4c:02:89:11:d2:3c brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.6/24 brd 192.168.100.255 scope global dynamic noprefixroute enp1s0
       valid_lft 85877sec preferred_lft 75077sec
    inet6 fe80::b359:cdc0:db93:da55/64 scope link 
       valid_lft forever preferred_lft forever

01:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
	Subsystem: Intel Corporation I211 Gigabit Network Connection
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at 90500000 (32-bit, non-prefetchable) [size=128K]
	I/O ports at 2000 [size=32]
	Memory at 90520000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
	Capabilities: [70] MSI-X: Enable+ Count=5 Masked-
	Capabilities: [a0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 4c-02-89-ff-ff-11-d2-3c
	Capabilities: [1a0] Transaction Processing Hints
	Kernel driver in use: igb
	Kernel modules: igb

02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
	Subsystem: Intel Corporation I211 Gigabit Network Connection
	Flags: fast devsel, IRQ 17
	Memory at 90400000 (32-bit, non-prefetchable) [size=128K]
	I/O ports at 1000 [size=32]
	Memory at 90420000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
	Capabilities: [70] MSI-X: Enable- Count=5 Masked-
	Capabilities: [a0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 4c-02-89-ff-ff-11-d2-3d
	Capabilities: [1a0] Transaction Processing Hints
	Kernel modules: igb

# lsmod | grep igb
igb                   253952  0
i2c_algo_bit           16384  2 igb,i915
dca                    16384  1 igb

# networkctl
IDX LINK   TYPE     OPERATIONAL SETUP    
  1 lo     loopback carrier     unmanaged
  2 enp1s0 ether    routable    unmanaged

# ip addr add 192.168.2.101/24 dev enp2s0 
Cannot find device "enp2s0"

Lone_Wolf · 2020-03-11 11:20:48

The lspci output shows 2 network interfaces that both use igb , which is good and indicates kernel sees both interfaces.

post full dmesg and/or journalctl -b

mashrum · 2020-03-11 14:56:40

# dmesg | grep igb
[    8.304943] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
[    8.304947] igb: Copyright (c) 2007-2014 Intel Corporation.
[    8.386796] igb 0000:01:00.0: added PHC on eth0
[    8.386800] igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection
[    8.386804] igb 0000:01:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 4c:02:89:11:d2:3c
[    8.386808] igb 0000:01:00.0: eth0: PBA No: FFFFFF-0FF
[    8.386812] igb 0000:01:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
[    8.387816] igb: probe of 0000:02:00.0 failed with error -2
[    8.424274] igb 0000:01:00.0 enp1s0: renamed from eth0
[   12.056768] igb 0000:01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

# dmesg | grep 01:00
[    0.629866] pci 0000:01:00.0: [8086:1539] type 00 class 0x020000
[    0.629907] pci 0000:01:00.0: reg 0x10: [mem 0x90500000-0x9051ffff]
[    0.629937] pci 0000:01:00.0: reg 0x18: [io  0x2000-0x201f]
[    0.629953] pci 0000:01:00.0: reg 0x1c: [mem 0x90520000-0x90523fff]
[    0.630107] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[    8.386796] igb 0000:01:00.0: added PHC on eth0
[    8.386800] igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection
[    8.386804] igb 0000:01:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 4c:02:89:11:d2:3c
[    8.386808] igb 0000:01:00.0: eth0: PBA No: FFFFFF-0FF
[    8.386812] igb 0000:01:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
[    8.424274] igb 0000:01:00.0 enp1s0: renamed from eth0
[   12.056768] igb 0000:01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

# dmesg | grep 02:00
[    0.630480] pci 0000:02:00.0: [8086:1539] type 00 class 0x020000
[    0.630520] pci 0000:02:00.0: reg 0x10: [mem 0x90400000-0x9041ffff]
[    0.630549] pci 0000:02:00.0: reg 0x18: [io  0x1000-0x101f]
[    0.630565] pci 0000:02:00.0: reg 0x1c: [mem 0x90420000-0x90423fff]
[    0.630718] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[    8.387816] igb: probe of 0000:02:00.0 failed with error -2

Last edited by mashrum (2020-03-11 15:23:17)

seth · 2020-03-11 16:51:31

Smells like a firmware error, but could also be a failure to power up the device or…

Lone_Wolf wrote:

post full dmesg and/or journalctl -b

The context might be relevant/shed light on this and the actual error long before the actual failure.
Random excerpts or filters are rarely meaningful.

mashrum · 2020-03-12 06:39:25

journalctl -b

https://www.dropbox.com/s/ogo9s04kvhzj8c4/journal.log

seth · 2020-03-12 07:09:52

мар 12 09:05:11 fobot-01 kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Any idea what happened? It's not really likely to be the cause, but you should fix that and re-install the kernel (and regenerate the initramfs) to be sure.
Is there maybe a parallel windows installation? (Which would be more likely to cause trouble if it's hibernating)

мар 12 09:05:10 fobot-01 kernel: Command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img root=PARTUUID=e86510da-cf79-49ad-816e-1e15f5783f8e rw console=ttyS0,115200 console=tty0

Do you have physical access to the system (to blacklist and load igb by hand delayed)?
Also in this case you should re-plug (and maybe swap, use a different slot) the ethernet cards to rule out HW errors since the probe really fails straight away.

Lastly: pass "igb.debug=16" to the kernel.

mashrum · 2020-03-12 10:28:05

i't embedded device
no pci slot, no cards, no video - one board solution
can't add or remove lan
access over ttyS0

only one OS installed, one kernel

sda1
i'm too lazy for correct shutdown sometimes - no reset or power button, ssh closed... just disconnected from power
fsck is clear for /dev/sda1

igb.debug=16
will do today later

Last edited by mashrum (2020-03-12 10:32:35)

seth · 2020-03-12 13:25:40

You could also try to (remove an) rescan the PCI bus after the boot.

# echo 1 > /sys/bus/pci/devices/0000:02:00.0/remove
# echo 1 > /sys/bus/pci/rescan

Arch Linux

#1 2020-03-11 06:14:04

HowTo UP second eth on network card

#2 2020-03-11 11:20:48

Re: HowTo UP second eth on network card

#3 2020-03-11 14:56:40

Re: HowTo UP second eth on network card

#4 2020-03-11 16:51:31

Re: HowTo UP second eth on network card

#5 2020-03-12 06:39:25

Re: HowTo UP second eth on network card

#6 2020-03-12 07:09:52

Re: HowTo UP second eth on network card

#7 2020-03-12 10:28:05

Re: HowTo UP second eth on network card

#8 2020-03-12 13:25:40

Re: HowTo UP second eth on network card

Board footer