I noticed that in some of our devices not all network interfaces are shown in Balena OS.
When booting a standard ubuntu on the machine these interfaces do show and ubuntu is using the e1000e driver for it.
In Balena OS the interface doesn’t appear. Is the e1000e driver not part of the standard kernel?
Hi
Can you share some more details?
- what device are you using?
- what version of the balenaOS do you see this in? Also, what version of ubuntu are you using where you see more network interfaces?
- logs from both ubuntu and balenaOS for
ifconfigwould also help
Of course,
- We’re running Balena Generic x86_64 as we’re running on an industrial PC (AMR Computer ABOX-5210｜AGV Computer｜SINTRONES).
- OS is balenaOS 2.58.6+rev1 and the ubuntu version is standard 18.04 server edition.
- Logs for ifconfig below
Balena OS:
balena0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 10.114.101.1 netmask 255.255.255.0 broadcast 10.114.101.255
ether 02:42:64:bd:91:cc txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-1a53868ad6f5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
inet6 fe80::42:c8ff:fe4a:96ae prefixlen 64 scopeid 0x20<link>
ether 02:42:c8:4a:96:ae txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 172 bytes 13866 (13.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
can0: flags=193<UP,RUNNING,NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 1041 bytes 8328 (8.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 31719 bytes 252968 (252.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
can1: flags=193<UP,RUNNING,NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6752 bytes 54040 (54.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device base 0x101
enp1s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:38 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1900000-b197ffff
enp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.1.8 netmask 255.255.255.0 broadcast 0.0.0.0
ether d0:4c:c1:04:fd:39 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1800000-b187ffff
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.20.153 netmask 255.255.255.0 broadcast 192.168.20.255
inet6 fe80::326f:9f87:fcc1:cba1 prefixlen 64 scopeid 0x20<link>
ether d0:4c:c1:04:fd:31 txqueuelen 1000 (Ethernet)
RX packets 17990 bytes 25390950 (25.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3353 bytes 374694 (374.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1700000-b177ffff
enp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.14.1 netmask 255.255.255.0 broadcast 0.0.0.0
ether d0:4c:c1:04:fd:32 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1600000-b167ffff
enp5s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:33 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1500000-b157ffff
enp6s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:34 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1400000-b147ffff
enp7s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:35 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1300000-b137ffff
enp8s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:37 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1200000-b127ffff
enp9s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:36 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1100000-b117ffff
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 335928 bytes 63002248 (63.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 335928 bytes 63002248 (63.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
resin-dns: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.114.102.1 netmask 255.255.255.0 broadcast 0.0.0.0
inet6 fe80::b0e8:daff:fe74:8759 prefixlen 64 scopeid 0x20<link>
ether b2:e8:da:74:87:59 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 160 bytes 12444 (12.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
resin-vpn: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.240.36.139 netmask 255.255.255.255 destination 52.4.252.97
inet6 fe80::fc99:e9a:dfce:36c4 prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 273 bytes 23538 (23.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 375 bytes 62953 (62.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
supervisor0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 10.114.104.1 netmask 255.255.255.128 broadcast 10.114.104.127
ether 02:42:8b:d2:98:5d txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth564ffad: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::2c38:5bff:fecd:73ed prefixlen 64 scopeid 0x20<link>
ether 2e:38:5b:cd:73:ed txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 200 bytes 17906 (17.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Ubuntu OS:
can0: flags=193<UP,RUNNING,NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 1633673 bytes 13069384 (13.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1060009 bytes 8598117 (8.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
can1: flags=193<UP,RUNNING,NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 225925 bytes 1812496 (1.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device base 0x101
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.20.150 netmask 255.255.255.0 broadcast 192.168.20.255
inet6 fe80::d24c:c1ff:fe04:fd30 prefixlen 64 scopeid 0x20<link>
ether d0:4c:c1:04:fd:30 txqueuelen 1000 (Ethernet)
RX packets 798171 bytes 58270452 (58.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 789928 bytes 111041927 (111.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xb1a00000-b1a20000
enp1s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:38 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1900000-b197ffff
enp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:39 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1800000-b187ffff
enp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:31 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1700000-b177ffff
enp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:32 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1600000-b167ffff
enp5s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:33 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1500000-b157ffff
enp6s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:34 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1400000-b147ffff
enp7s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:35 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1300000-b137ffff
enp8s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:37 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1200000-b127ffff
enp9s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d0:4c:c1:04:fd:36 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xb1100000-b117ffff
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 61012877 bytes 13162322271 (13.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 61012877 bytes 13162322271 (13.1 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
To add to that.
When I do an lspci -v on both systems, this is the result:
Balena OS:
00:1f.6 Ethernet controller: Intel Corporation Device 0d4c
Subsystem: Intel Corporation Device 0000
Flags: fast devsel, IRQ 11
Memory at b1a00000 (32-bit, non-prefetchable) [disabled] [size=128K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at b1900000 (32-bit, non-prefetchable) [size=512K]
I/O ports at b000 [size=32]
Memory at b1980000 (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 d0-4c-c1-ff-ff-04-fd-38
Capabilities: [1a0] Transaction Processing Hints
Kernel driver in use: igb
Kernel modules: igb
Ubuntu OS:
00:1f.6 Ethernet controller: Intel Corporation Device 0d4c
Subsystem: Intel Corporation Device 0000
Flags: bus master, fast devsel, latency 0, IRQ 133
Memory at b1a00000 (32-bit, non-prefetchable) [size=128K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: e1000e
Kernel modules: e1000e
01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at b1900000 (32-bit, non-prefetchable) [size=512K]
I/O ports at b000 [size=32]
Memory at b1980000 (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 d0-4c-c1-ff-ff-04-fd-38
Capabilities: [1a0] Transaction Processing Hints
Kernel driver in use: igb
Kernel modules: igb
Which is why I assumed issues with the e1000e driver in Balena.
Hi @MCFurry42,
I could be mistaken, but I believe that the e1000e driver is part of the meta-intel yocto BSP. Your machine might be possibly be using other intel devices we possibly don’t have built into our generic x86_64 image?
A crazy idea that might work (if you are willing to try) is using the Intel NUC as device type, to see if these drivers will work for that machine. I don’t believe there should be any consequences doing this as a test, but it’s worth a shot!
Are you installing on this device via balenaCloud, or from a general balenaOS image?
Thanks for your response. I might try running the Intel NUC release on that machine somewhere in the coming days, I will report back the result!
I’m always installing via general balenaOS image via usb-drive.
Hi, the E1000E driver should be built-in in both the “Generic x86_64” and “Intel NUC” device types. You can check whether that’s the case by accessing the hostOS shell and doing:
zcat /proc/config.gz | grep -i e1000e
If you are completely sure that’s the driver you need, maybe the firmware files are missing. Do you have an output from dmesg on a failing machine?
These are the results for the zcat and dmesg commands both executed on the machine that’s missing an interface. FIle attached since it’s too big for a post 
ABox_dmesg_log.txt (76.1 KB)
Hi, thanks for that information. I checked and support for Comet Lake and that specific network card was not added until the kernel version v5.5 (see e1000e: Add support for Comet Lake · torvalds/linux@914ee9c · GitHub).
BalenaOS v2.58 is still on v5.2, you will need to update to the latest version to support this chipset (the kernel was updated to 5.8 on v2.66, and the latest versions are already in 5.10)
Ahh thanks for confirmation, that sounds logical.
Let me test with the latest OS version asap and I’ll report back!
Thanks, let us know how that goes.
So the latest Balena OS 2.83.1+rev8 is indeed showing the extra network interface! Thx for the help!