How to enable eth1 in jetson nano

Hi. All:
1: In JetPack4.4_R32.4.3, Jetson NANO SOM with custom board
2: Custom board connected with SOM pcie1 as follow:

3: lspci -vvv

00:02.0 PCI bridge: NVIDIA Corporation Device 0faf (rev a1) (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 83
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 00001000-00001fff
        Memory behind bridge: fff00000-000fffff
        Prefetchable memory behind bridge: 0000000020000000-00000000200fffff
        Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
        BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
                PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
        Capabilities: <access denied>
        Kernel driver in use: pcieport

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 19)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 407
        Region 0: I/O ports at 1000 [size=256]
        Region 2: Memory at 20004000 (64-bit, prefetchable) [size=4K]
        Region 4: Memory at 20000000 (64-bit, prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: r8168

4: but eth1 didn’t show in ifconfig. what should I do to enable eth1

Thank you very much!
Best regards!!

I don’t know why it didn’t show up, but I’d start by looking at the most verbose output of lspci. What do you get from this?
sudo lspci -vvv -s 01:00.0

Right now it looks like it is loading a driver, so it probably should exist, but there might be errors. You might also provide a full boot log via serial console since what goes on during boot likely has a clue. See:
https://www.jetsonhacks.com/2019/04/19/jetson-nano-serial-console/

1 Like

Finally, it works after change the hardware . Thanks.