Hello,
with yocto scarthgap the interface is named end0, how to use the old name eth0.
How congfigure yocto to get this ?.
Thank you.
Regards
Flavio
Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
I’d be glad to help! Could you let me know which OS and version you are using? You can use the tdx-info command to get detailed information about your setup - please check this link for more details.
The interface naming behavior can vary between different Toradex platforms and OS versions, so knowing your specific hardware and software configuration will help me provide the most accurate guidance for configuring your Yocto build to use the eth0 naming convention.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
Hello ToradexAI
root@colibri-imx8x-14791379:~# tdx-info
Software summary
Bootloader: U-Boot
Kernel version: 6.6.101-7.4.0-devel #1 SMP PREEMPT Thu Sep 25 07:49:28 UTC 2025
Kernel command line: root=PARTUUID=076c4a2a-02 ro rootwait
Distro name: NAME=“TDX Wayland with XWayland”
Distro version: VERSION_ID=7.4.0-devel-20251106113704-build.0
Distro variant: -
Hostname: colibri-imx8x-14791379
Hardware info
HW model: Toradex Colibri iMX8QXP on Colibri Evaluation Board V3
Toradex version: 0050 V1.0D
Serial number: 14791379
Processor arch: aarch64
Thank you for providing the system information! I can see you’re running BSP 7.4.0-devel on a Colibri iMX8QXP.
Interface Naming in Yocto BSP
The interface naming convention has changed in newer kernel versions. According to the Toradex documentation, for BSP systems, Ethernet interfaces are named eth<x> where <x> represents the number of the interface(1). However, you’re experiencing the newer predictable network interface naming where the interface is named end0.
Solutions to Use eth0 Naming
Option 1: Kernel Command Line Parameter
You can disable the predictable network interface naming by adding a kernel parameter. In U-Boot, you can set this using the tdxargs variable(2):
setenv tdxargs "net.ifnames=0 biosdevname=0"
saveenv
This will force the system to use the traditional eth0 naming convention(2).
Option 2: Yocto Build Configuration
If you’re building your own Yocto image, you can modify the kernel command line by setting the APPEND variable in your Yocto configuration(2). Add this to your local.conf or image recipe:
APPEND += "net.ifnames=0 biosdevname=0"
Network Configuration Considerations
Once you have the eth0 interface name, you can configure it using the network management tools available in the BSP. The Toradex BSP reference images provide two utilities for network configuration: connman and systemd-networkd(1).
For systemd-networkd configuration with eth0, you would create a file named wired.network under /etc/systemd/network/(1):
[Match]
Name=eth0
[Network]
DHCP=ipv4
This configuration will work once the interface is renamed back to eth0 using one of the methods above.
Best regards, Toradex AI Assistant.
Did you like my answer?
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.