On Fri, Oct 6, 2023 at 7:07 PM Donovan Sydow <[email protected]> wrote:

> You can always change that gel to “en” or even “nic”, or likely check all
> of your dmesg output without grep to see if you can see your Ethernet
> driver loading. If that doesn’t help you may want to run lsmod to see if
> there are any drivers loaded for your NIC, and perhaps run modprobe with
> the specific driver module name for your network interface.
>
> Cheers,
> Donovan
>
> On Oct 6, 2023, at 6:35 PM, Tsai, Matt <[email protected]> wrote:
>
> 
>
> Hi Donovan,
>
>
>
> Thank you for your quick response.
>
>
>
> There is no customization of the original Yocto recipes related to
> Ethernet, except for adding PHY driver (maxlinear) and some MDIO
> configuration. System V init is used.
>
>
>
> The output of dmesg | grep eth0 is empty.
>
> Try grep Ethernet and also “ip addr show”.
Likely you need a kernel module for the “maxlinear” PHY. Google search for
the part number/family and “kernel driver” should point you in a direction.
If the device has good mainline support, you might need to turn on some
CONFIG_*. If it relies on an external out-of-tree driver, things get a
little more complicated.

Unlike most Linux distros which build everything into their kernel, Yocto
Project starts minimal because embedded systems have limited resources. For
this reason, there is likely a “kernel-module-*” that either has not been
built (.config didn’t enable it) or it wasn’t installed in your image.


>
> Does this mean the kernel menuconfig of PHY is not correct?
>
>
>
>
>
> Thank you.
>
>
>
> *From:* Donovan Sydow <[email protected]>
> *Sent:* Friday, October 6, 2023 6:09 PM
> *To:* Tsai, Matt <[email protected]>
> *Cc:* [email protected]
> *Subject:* Re: [meta-intel] x6000E Yocto build Ethernet questions
>
>
>
> *CAUTION:* This email originated from outside of Thermo Fisher
> Scientific. If you believe it to be suspicious, report using the Report
> Phish button in Outlook or send to [email protected].
>
>
>
> Most modern linux systems have udev rules that create a consistent name
> mechanism for each hardware interface, so eth# is rarely used anymore. This
> of course depends on how highly customized you made your yocto based OS. I
> would suggest running dmesg and searching for "eth", or the more modern
> "en". On my Atom board you can see my dmesg output and it is using a
> realtek 8169 for the PHY:
>
>
>
> dmesg | grep eth
> [    3.178558] r8169 0000:02:00.0 eth0: RTL8168h/8111h at
> 0xffffaee5401dd000, 00:07:32:95:7a:1e, XID 14100800 IRQ 121
> [    3.188701] r8169 0000:02:00.0 eth0: jumbo features [frames: 9200
> bytes, tx checksumming: ko]
> [    3.212560] r8169 0000:03:00.0 eth1: RTL8168h/8111h at
> 0xffffaee5401e5000, 00:07:32:95:7a:1f, XID 14100800 IRQ 122
> [    3.222703] r8169 0000:03:00.0 eth1: jumbo features [frames: 9200
> bytes, tx checksumming: ko]
> [    4.654901] r8169 0000:03:00.0 eno1: renamed from eth1
> [    4.664799] r8169 0000:02:00.0 enp2s0: renamed from eth0
>
>
>
> I hope that helps you find your correct interface name. If you don't know
> what PHY you have I would suggest consulting your board manufacturer
>
>
>
> On Fri, Oct 6, 2023 at 5:57 PM Matt <[email protected]> wrote:
>
> Hi all,
> We are working on a customized Linux system using Yocto on Intel x6000E
> CPU (6413 Elkhart Lake). The Yocto branch used is kirkstone; the Yocto
> machine used is intel-corei7-64; kernel version is 5.15.94.
> The Linux seems to start without issues. However, there is no network
> device eth0.This is the "ifup" output:
> $ ifup eth0
> ip: can't find device 'eth0'
> ip: SIOCGIFFLAGS: No such device
> ip: can't find device 'eth0'
>
> I believe an external PHY driver is added to the Linux kernel using
> menuconfig. So I suspect the cause of no network device eth0 may be the
> proper Ethernet driver not included.
>
> Questions:
> 1. What is the correct Ethernet driver to include for the x6413? If the
> Ethernet driver is not the cause, what else need to be done to get the
> Ethernet device (eth0) up?
> 2. Is meta-ptcm required to get Ethernet working on x6413?
>
> Any pointers are appreciated!
>
> Thank you for your help!
>
>
>
>
> --
>
> [image: iunu.com]
> <https://urldefense.com/v3/__https:/iunu.com__;!!HLrAl2XzZ3iCLg!GOCZVbUi-Dh9NTOoMS8cducA43FM02pH6RLvHEGuB-uEDCGmqDCy4XBAwdygva2fkQwa4YNBfkpS3s2bPhE$>
>
> *Donovan Sydow*
>
> Field Engineering Director
>
> Phone: 206.229.8740
>
> *iunu.com*
> <https://urldefense.com/v3/__http:/www.iunu.com/__;!!HLrAl2XzZ3iCLg!GOCZVbUi-Dh9NTOoMS8cducA43FM02pH6RLvHEGuB-uEDCGmqDCy4XBAwdygva2fkQwa4YNBfkpS9VvNITI$>
>
>
>
>
> 
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8117): 
https://lists.yoctoproject.org/g/meta-intel/message/8117
Mute This Topic: https://lists.yoctoproject.org/mt/101810015/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-intel/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to