Hi,
We have developed a custom carrier that uses I225-IT for jp6.2. it’s not work. when I executed the command “lsmod | grep igc“, I don’t get any information. But it’s ok for jp5.2.
Hi,
We have developed a custom carrier that uses I225-IT for jp6.2. it’s not work. when I executed the command “lsmod | grep igc“, I don’t get any information. But it’s ok for jp5.2.
FOR JP62
nvidia@nvidia-desktop:~$ lspci
0001:00:00.0 PCI bridge: NVIDIA Corporation Device 229e (rev a1)
0001:01:00.0 Ethernet controller: Intel Corporation Ethernet Controller (2) I225-IT (rev 03)
0005:00:00.0 PCI bridge: NVIDIA Corporation Device 229a (rev a1)
0005:01:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03)
nvidia@nvidia-desktop:~$ lsmod | grep igc
nvidia@nvidia-desktop:~$
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that you are experiencing issues with the Intel I225-IT Ethernet controller on your custom carrier board, specifically with the Jetson AGX Orin module.
The lsmod | grep igc command is used to check if the igc driver is loaded, which is responsible for the Intel I225-IT Ethernet controller. Since you don’t see any information, it suggests that the driver is not loaded or not functioning correctly.
Comparing your setup to the provided context, I notice that the Jetson AGX Orin reference carrier board (P3737-0000) is mentioned, but it does not specifically mention the Intel I225-IT Ethernet controller. However, it does mention that the Jetson AGX Orin Dev-Kit Module (P3701-0000) and Jetson AGX Orin 32GB-DRAM (P3701-0004) modules are compatible with the reference carrier board.
To troubleshoot the issue, I would recommend checking the following:
modprobe igc command to see if it makes any difference.If none of these troubleshooting steps resolve the issue, it may be helpful to provide more information about your custom carrier board design, kernel configuration, and device tree configuration to further assist with debugging.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Please enable vendor driver from kernel manually.
Looks like PCIe already detected device.