I am running OMV7 on my RPI 5 (using latest OS Lite (64 bit), installed and updated this morning on a fresh SD card so i didn't screw up my working setup...) and I wanted to add a 2.5G NIC to it. Before anyone asks, not I don't really need it....but as my PC has a 2.5G NIC natively and I happen to have a 2.5G switch I want my access to the NAS to be upto the same speed. I often move some big data sets around for work and it would be nice to speed up transfers.
I have a plugbale 2.5G USB Ethernet adaptor, as shown in the below link and i've followed the setup to get a full duplex connection. I tested the unit on my PC, worked first time, and also tested it on another RPI 5 running the desktop version of Raspberry PI OS and it also work. My trouble is when trying to run it the Lite version.
I also get the same issue when testing on my RPI 4 running NextcloudPi
https://www.jiribrejcha.net/2022/07/plu ... t-adapter/
List USB devices - It is recognised..
Shows up as eth1 with interfaces are listed...
Get the following error with ethtool, 'netlink error: Operation not permitted', which doesn't happen on my destop Pi.
There is obviously some difference between Lite and desktop OS', the question is what? and how do I activate the USB ethernet adaptor?
(i have tried all the above with the ethernet cable unplugged from the onboard port, just SSHing in so I can easily copy paste from the Pi)
I have a plugbale 2.5G USB Ethernet adaptor, as shown in the below link and i've followed the setup to get a full duplex connection. I tested the unit on my PC, worked first time, and also tested it on another RPI 5 running the desktop version of Raspberry PI OS and it also work. My trouble is when trying to run it the Lite version.
I also get the same issue when testing on my RPI 4 running NextcloudPi
https://www.jiribrejcha.net/2022/07/plu ... t-adapter/
List USB devices - It is recognised..
Code:
tomb@pi:~ $ lsusbBus 004 Device 002: ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LANBus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubBus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubBus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying ReceiverBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubCode:
tomb@pi:~ $ ifconfigeth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.110 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::da3a:ddff:febe:ae8 prefixlen 64 scopeid 0x20<link> inet6 fd1d:d4d7:e781:0:da3a:ddff:febe:ae8 prefixlen 64 scopeid 0x0<global> inet6 2a02:c7c:c1b3:bb00:da3a:ddff:febe:ae8 prefixlen 64 scopeid 0x0<global> ether d8:3a:dd:be:0a:e8 txqueuelen 1000 (Ethernet) RX packets 18586 bytes 1826063 (1.7 MiB) RX errors 0 dropped 4545 overruns 0 frame 0 TX packets 574 bytes 76473 (74.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 107eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::8eae:4cff:fedd:a631 prefixlen 64 scopeid 0x20<link> ether 8c:ae:4c:dd:a6:31 txqueuelen 1000 (Ethernet) RX packets 4938 bytes 554155 (541.1 KiB) RX errors 0 dropped 981 overruns 0 frame 0 TX packets 19 bytes 4151 (4.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 890 bytes 1128000 (1.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 890 bytes 1128000 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0tomb@pi:~ $ ip link show1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:002: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether d8:3a:dd:be:0a:e8 brd ff:ff:ff:ff:ff:ff4: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether d8:3a:dd:be:0a:e9 brd ff:ff:ff:ff:ff:ff5: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 8c:ae:4c:dd:a6:31 brd ff:ff:ff:ff:ff:ffCode:
tomb@pi:~ $ ethtool eth1Settings for eth1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full 2500baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 2500Mb/s Duplex: Full Auto-negotiation: on Port: MII PHYAD: 32 Transceiver: internalnetlink error: Operation not permitted Current message level: 0x00007fff (32767) drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol Link detected: yes(i have tried all the above with the ethernet cable unplugged from the onboard port, just SSHing in so I can easily copy paste from the Pi)
Statistics: Posted by TomB1984 — Wed Jan 24, 2024 3:39 pm — Replies 0 — Views 57