10390 2016-10-06 21:34:58 +0000 Network interface eth0 not showing up on intel-core2-32 2018-01-24 04:41:46 +0000 1 1 11 Runtime General Runtime General Runtime unspecified MinnowBoard Max Multiple RESOLVED FIXED Undecided major --- 1 alejandro.hernandez alejandro.hernandez isaac.park --- New (Never tested) No (bug/feature does not impact docs) oldest_to_newest 67019 0 alejandro.hernandez 2016-10-06 21:34:58 +0000 When using MACHINE=intel-core-32 core-image-minimal on a Minnowboard MAX, the network interface eth0 is not showing up after boot: root@intel-core2-32:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1 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: sit0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1 link/sit 0.0.0.0 brd 0.0.0.0 After doing a dmesg I don't see anything related. 67020 1 alejandro.hernandez 2016-10-06 21:35:40 +0000 This problem is also happening on genericx86 and genericx86-64 platforms 67021 2 alejandro.hernandez 2016-10-06 21:38:34 +0000 This DOES NOT happen on intel-corei7-64 using core-image-minimal, nor does it happen on the other platforms when using core-image-sato-sdk. Which implies this is caused by a the driver being modularized on all platforms but corei7. 67022 3 alejandro.hernandez 2016-10-06 21:40:12 +0000 I can confirm that the config being used is: CONFIG_R8169=m I recompiled the kernel with the driver included and the interface is showing up correctly now: root@intel-core2-32:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1 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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:13:20:fe:33:28 brd ff:ff:ff:ff:ff:ff inet6 fe80::213:20ff:fefe:3328/64 scope link valid_lft forever preferred_lft forever 3: sit0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1 link/sit 0.0.0.0 brd 0.0.0.0 I will send a patch to yocto-kernel-cache. 67181 4 alejandro.hernandez 2016-10-12 16:56:00 +0000 Fixed here: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b872e2b2c78c17647b32aab616c767ec7901b119 79170 5 isaac.park 2018-01-20 09:34:21 +0000 Dear, Alejandro Hernandez I purchase the MinnowMax Board (Quad-Core). And I'm faced with same problem. I checked the ethernet model name. It is an intel I210 Gigabit. And I wanna build with the CONFIG_IGB feature. For test, how can I add that feature? Thanks. 79200 6 isaac.park 2018-01-24 04:41:46 +0000 Hello, I found the way to add custom kernel config. http://www.yoctoproject.org/docs/1.6.1/dev-manual/dev-manual.html#configuring-the-kernel 5.6.2. Creating Configuration Fragments And I added the "CONFIG_IGB", then it works well. After minnow booting, I can see the "eth0" device. Refer to below page. https://minnowboard.org/compare-boards/ Notes 7. The currently available Turbot B dual-core board has an Intel i211 ethernet controller. The original release of Turbot dual-core (Turbot A) had a Realtek ethernet controller—see BOM in GitHub. The Minnow board's network interface has been changed to Intel I210 series. Could you update this change? I'm waiting for you. Thanks.