PCI Interface LAN7430 IC with Jetson Nano is not detecting with PCI core driver on bootup


We are using Jetson Nano module CPU with our own custom carrier board. we have connected LAN7430 IC on PCI interface and as per out existing knowledge PCI core driver of Jetson nano should detect LAN7430 IC atleast.

LAN7430 IC should show in lspci but it is not showing. please see following output,
00:02.0 PCI bridge: NVIDIA Corporation Device 0faf (rev a1)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

We have not changes anything PCI related in device tree.

Please find below bootup log of dmesg related to pci,
2.895535] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[ 2.936493] tegra-pcie 1003000.pcie: PCI host bridge to bus 0000:00
[ 2.936498] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
[ 2.936502] pci_bus 0000:00: root bus resource [mem 0x13000000-0x1fffffff]
[ 2.936505] pci_bus 0000:00: root bus resource [mem 0x20000000-0x3fffffff pref]
[ 2.936508] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 2.936529] pci 0000:00:02.0: [10de:0faf] type 01 class 0x060400
[ 2.936586] pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 2.936725] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 2.936832] pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000
[ 2.936855] pci 0000:01:00.0: reg 0x10: [io 0x0000-0x00ff]
[ 2.936884] pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x00000fff 64bit]
[ 2.936903] pci 0000:01:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit]
[ 2.937038] pci 0000:01:00.0: supports D1 D2
[ 2.937041] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 2.946835] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 2.946860] pci 0000:00:02.0: BAR 14: assigned [mem 0x13000000-0x130fffff]
[ 2.946863] pci 0000:00:02.0: BAR 13: assigned [io 0x1000-0x1fff]
[ 2.946869] pci 0000:01:00.0: BAR 4: assigned [mem 0x13000000-0x13003fff 64bit]
[ 2.946885] pci 0000:01:00.0: BAR 2: assigned [mem 0x13004000-0x13004fff 64bit]
[ 2.946900] pci 0000:01:00.0: BAR 0: assigned [io 0x1000-0x10ff]
[ 2.946907] pci 0000:00:02.0: PCI bridge to [bus 01]
[ 2.946910] pci 0000:00:02.0: bridge window [io 0x1000-0x1fff]
[ 2.946915] pci 0000:00:02.0: bridge window [mem 0x13000000-0x130fffff]
[ 2.947155] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
[ 2.947158] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[ 2.947163] pcie_pme 0000:00:02.0:pcie001: service driver pcie_pme loaded
[ 2.947236] aer 0000:00:02.0:pcie002: service driver aer loaded
[ 2.947406] r8168 0000:01:00.0: enabling device (0000 → 0003)
[ 2.947422] r8168 Gigabit Ethernet driver 8.045.08-NAPI loaded
[ 2.962188] r8168 0000:01:00.0 (unnamed net_device) (uninitialized): Invalid ethernet address 00:00:00:00:00:00, trying device tree node
[ 2.962251] r8168 0000:01:00.0 (unnamed net_device) (uninitialized): Found valid ethernet address 48:b0:2d:3d:56:24 from device tree
[ 2.962679] r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
[ 2.962718] r8168 Copyright (C) 2017 Realtek NIC software team nicfae@realtek.com
This program comes with ABSOLUTELY NO WARRANTY; for details, please see http://www.gnu.org/licenses/.
This is free software, and you are welcome to redistribute it under certain conditions; see http://www.gnu.org/licenses/.

Please confirm, should LAN7430 detect in lspci automatically using PCI core driver ? we did not install LAN7430 IC driver it board.

Thanks in advance.


Welcome to the NVIDIA Developer forums. I am going to move your topic over to the Jetson Nano category for better visibility.

Tom K


Please reply on this topic. I am stuck here since long time.

Mukesh Prajapati

Sorry for the late response, have you managed to get issue resolved or still need the support? Thanks

Yes, this issue has been resolved.
PCI core driver should detect LAN7430 in lspci automatically on boot up.

In our case there were an issue with hardware with communication line.


Good, thanks for the update!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.