hi nvidia:
if I change
/etc/systemd/network/10-jetson-onboard-ethernet.link
from
[Match]
Path=platform-6800000.ethernet
[Link]
Name=eno1
to
[Match]
Path=platform-6800000.ethernet
[Link]
Name=mgbe0
system can not boot complete
eno1-to-mgbe0-cannot-boot.txt (107.1 KB)
*** Please note that this reply is generated by LLM automatically ***
The issue you’re experiencing is related to changing the network interface name from eno1 to mgbe0 in the 10-jetson-onboard-ethernet.link file. This file is used by systemd to manage network interfaces.
When you change the MatchPath from platform/6800000/ethernet@link/eno1 to platform/6800000/ethernet@link/mgbe0, the system is unable to boot completely.
This is likely due to the fact that the mgbe0 interface is not properly configured or recognized by the system. The eno1 interface is a standard interface name used by many Linux distributions, including those based on systemd.
To resolve this issue, you can try the following:
- Revert the changes you made to the
10-jetson-onboard-ethernet.link file and change the MatchPath back to platform/6800000/ethernet@link/eno1.
- If you still want to use the
mgbe0 interface, you’ll need to ensure that it’s properly configured and recognized by the system. You can try adding a new .link file specifically for the mgbe0 interface, with the correct MatchPath and other settings.
- You can also try checking the system logs to see if there are any error messages related to the network interface or boot process. This can help you identify the root cause of the issue.
In terms of comparing the two interfaces, eno1 and mgbe0 are both Ethernet interfaces, but they may have different configurations or settings. The eno1 interface is a standard interface name used by many Linux distributions, while the mgbe0 interface may be a custom or specific interface name used by the Jetson AGX Orin board.
Here’s a comparison of the two interfaces:
eno1:
- Standard interface name used by many Linux distributions
- May be configured to use DHCP or a static IP address
- May have other settings or configurations specific to the system or distribution
mgbe0:
- Custom or specific interface name used by the Jetson AGX Orin board
- May have different configurations or settings than the
eno1 interface
- May require specific settings or configurations to function properly
In summary, the issue you’re experiencing is likely due to the fact that the mgbe0 interface is not properly configured or recognized by the system. You can try reverting the changes you made to the 10-jetson-onboard-ethernet.link file or adding a new .link file specifically for the mgbe0 interface.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Is this issue reproducible on NV devkit?
no, only on our custom board
我用中文再確認一次
這裡要問的是
- 你嘗試複製過了, 但NV devkit真的沒辦法複製出一樣的問題
- 你沒有NV devkit所以沒辦法測試
請問你是1還是2?
你這個問題的複製方式有點太過簡單了, 說實話不太像是custom board/devkit差別而影響的東西
devkit硬件和我们板子不一样,所有开发板上不会有这个问题, 我们已经解决了。
our board hardware is diff with devkit, cause this issue,. we have fix it
Thanks
你英文內容寫說你已經fix it是說問題已經解決嗎?
如果是的話請分享一下最後問題是發生在何處?
和网络没有关系也和这个文件没有关系。是其他问题和我修改这个文件时耦合在一起了。
1 Like