RPi5 with LinuxCNC Image and Waveshare PCIe TO Gigabit ETH Board

Hello together,
I am trying to prepare my first LinuxCNC installation. I took the latest RPi 5 Image from LinuxCNC and copied it on an SD-card.
So far everything worked fine. LinuxCNC starts and a connection via SSH is working.
For the Raspberry Pi I would like to use a case with an additional ethernet port from Waveshare.

According to their FAQ ( Waveshare FAQ ) I enabled PCIe, but there is still no extra ethernet port listed in ifconfig.

To see if the hardware is working I took a stock image of Linux Bookworm and did the same there. After reboot I can see ETH1 listed in ifconfig.

Does anyone have an idea how to get this working?

Best regards
Benjamin

OK the Linuxcnc image is Debian with a custom kernel.
The kernel has been configured for the Realtek 8169.
First things:should list the hardware and the driver that is loadedwill list all interfaces whether configured or notwill list any messages related to ethernet devices.
Just thinking aloud, it could be a firmware issue. The Realtek devices can be a bit of a PITA and usually, dont do this yet, a dkms package to suit needs to be installed otherwise latency can be an issue.
Just to let you know I'm connected to my RPi5 in the garage via wifi, the RPi5 is in the Waveshare metal case and surrounded by metal shelving
Once you have all this info please post to forum. Maybe be an idea to redirect the output of each command to a separate file, saves clogging up the forum and makes it easier to read and use grep.
I wouldn't recommend running a cnc machine via a remote connection....just saying.

Hello,thank you for your answer. Here are the outputs

cnc@linuxcnc1:~$ lspci -v
0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 38
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: 80000000-800fffff =1M% [32-bit]
        Prefetchable memory behind bridge: [disabled] [64-bit]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

0000:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
        Flags: fast devsel, IRQ 38
        Memory at 1b80004000 (64-bit, non-prefetchable)
=4K%        Memory at 1b80000000 (64-bit, non-prefetchable)
=16K%        Capabilities: <access denied>
        Kernel driver in use: r8169
        Kernel modules: r8169

0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 39
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: 00000000-005fffff =6M% [32-bit]
        Prefetchable memory behind bridge: [disabled] [64-bit]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

0001:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge
        Flags: bus master, fast devsel, latency 0, IRQ 39
        Memory at 1f00410000 (32-bit, non-prefetchable)
=16K%        Memory at 1f00000000 (32-bit, non-prefetchable) [virtual]
=4M%        Memory at 1f00400000 (32-bit, non-prefetchable)
=64K%        Capabilities: <access denied>
        Kernel driver in use: rp1

cnc@linuxcnc1:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 2c:cf:67:3a:15:bb brd ff:ff:ff:ff:ff:ff
    altname end0
    inet 192.168.0.153/24 brd 192.168.0.255 scope global dynamic eth0
       valid_lft 825164sec preferred_lft 825164sec
    inet6 fdce:a2be:2d61:0:2ecf:67ff:fe3a:15bb/64 scope global dynamic mngtmpaddr
       valid_lft 7188sec preferred_lft 3588sec
    inet6 2003:e4:9741:1e00:2ecf:67ff:fe3a:15bb/64 scope global dynamic mngtmpaddr
       valid_lft 7188sec preferred_lft 1313sec
    inet6 fe80::2ecf:67ff:fe3a:15bb/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether aa:57:f1:85:a9:88 brd ff:ff:ff:ff:ff:ff
    altname enp1s0
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 2c:cf:67:3a:15:bc brd ff:ff:ff:ff:ff:ff

For there is no output on console.


 

I'm assuming this is the output when running the Linuxcnc image.

Ethernet device has been detected and the driver loaded.

Your NIC is there, just waiting to be configured, most likely it will be enp1s0. It's very rare interfaces identify as eth0 eth1 etc anymore without any kernel options being given. Has been this way for a few years now.

forum.linuxcnc.org/38-general-linuxcnc-q...l-images-only#325007 is a thread that indexes topics in the main RPi5/4 thread. Plenty there on configuring interfaces installing Gnome Network manager and the sort.

Unsure as to why dmesg isn't giving any output.

Using dmesg gives information if I unplug and plug the network cable on eth0 and eth1:

cnc@linuxcnc1:~$ sudo dmesg | grep eth
[51259.808328] r8169 0000:01:00.0 eth1: Link is Down
[51334.956935] macb 1f00100000.ethernet eth0: Link is Down
[51336.323225] r8169 0000:01:00.0 eth1: Link is Up - 100Mbps/Full - flow control rx/tx
[51431.494868] r8169 0000:01:00.0 eth1: Link is Down
[51433.262584] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control tx

If I connect the port to a network switch it is getting an IP from the router, but it is not possible to ping to that ip. I will try to read some more about how to get that working.

Have you configured the waveshare NIC to get an address via dhcpd ?
Have you done anything to configure that interface ?

No, up to now I did not configure anything. I installed the Gnome network manager and plugged the network cable to the ethernet port. I got an information from my router that it assigned a new IP to that ethernet port, so I tried to ping on that IP.
As I wrote, I will take my time and try to read and understand how to configure the new NIC in Linux. I have worked with Linux several times in the past, but I am more a noob than an expert in Linux.

If the second NIC is for ethercat or a Mesa Card, I would use the on board Broadcom NIC for it and the Realtek card for internet connectivity.
The DKMS driver should exist for the Pi on Debian. You may have to edit /etc/apt/sources.list to add non-free to the Deb stanzas so it can find DKMS.
Worst you can do is break it again...
sudo apt update
sudo apt install linux-headers r8168-dkms

Headers are already installed, and because of the kernel coming from the RPi GitHub repo, there are no Debian packages to suit the installed kernel.
will inform you of the info, including addresses, of all your network adapters.

If you could try that as well as the output of the ping command to that IP would be helpful. "It doesn't work" or some other statement along those lines without any additional information makes it very difficult and time consuming to help.

I've already mentioned that Realtek NICs can cause latency issues and the dkms package may need installing.
I kind of the OP skipped over that part or just ignored it. Anyways I think the issue at hand is to get the interface up and running and cross the Realtek driver later.
As it was the OP was claiming the Linuxcnc image was not recognising the interface and after digging that was found not to be the case.
To tell the truth the wifi adaptor of the RPi5 is quite good, even within the confines of a metal case, and is more than enough for transferring files via samba, nfs or sftp (which is my preferred method). Ssh sessions are a non issue as well.
Given the choice of Nvme or a second NIC, Nvme will win, if a second wired network interface is needed a usb3 one will be fine, probably better if you can find one that isn't Realtek based.