Neue Hardware und schlechter Latency Test

More
05 Aug 2023 13:51 #277005 by tommylight
3: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
Means nothing is connected to it, but the configuration is OK.
No carrier so the interface is down.
The following user(s) said Thank You: WKS-3D

Please Log in or Create an account to join the conversation.

More
05 Aug 2023 14:22 #277007 by WKS-3D
Yes, that's correct. The mesa card is not connected 
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
05 Aug 2023 20:56 #277054 by rodw
Great! so next step, type
sudo apt install ethtool
ethtool -i enps04
And share the results. This will report the ethernet driver in use to confirm its an Intel device.
also connect the mesa card and type
ping 10.10.10.10

If you get a reply you should be good to go.

Please Log in or Create an account to join the conversation.

More
06 Aug 2023 09:22 #277100 by WKS-3D

Great! so next step, type
sudo apt install ethtool
ethtool -i enps04And share the results. This will report the ethernet driver in use to confirm its an Intel device.
also connect the mesa card and type
ping 10.10.10.10

If you get a reply you should be good to go.
 


I had already posted thgis on page 4, but ok, here again :)
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.691 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.306 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.354 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.287 ms
64 bytes from 10.10.10.10: icmp_seq=5 ttl=64 time=0.364 ms
64 bytes from 10.10.10.10: icmp_seq=6 ttl=64 time=0.214 ms
64 bytes from 10.10.10.10: icmp_seq=7 ttl=64 time=0.357 ms
64 bytes from 10.10.10.10: icmp_seq=8 ttl=64 time=0.351 ms
64 bytes from 10.10.10.10: icmp_seq=9 ttl=64 time=0.361 ms
64 bytes from 10.10.10.10: icmp_seq=10 ttl=64 time=0.359 ms
64 bytes from 10.10.10.10: icmp_seq=11 ttl=64 time=0.360 ms
64 bytes from 10.10.10.10: icmp_seq=12 ttl=64 time=0.360 ms
64 bytes from 10.10.10.10: icmp_seq=13 ttl=64 time=0.359 ms
64 bytes from 10.10.10.10: icmp_seq=14 ttl=64 time=0.299 ms
64 bytes from 10.10.10.10: icmp_seq=15 ttl=64 time=0.359 ms
64 bytes from 10.10.10.10: icmp_seq=16 ttl=64 time=0.364 ms
64 bytes from 10.10.10.10: icmp_seq=17 ttl=64 time=0.358 ms
64 bytes from 10.10.10.10: icmp_seq=18 ttl=64 time=0.338 ms
64 bytes from 10.10.10.10: icmp_seq=19 ttl=64 time=0.363 ms
64 bytes from 10.10.10.10: icmp_seq=20 ttl=64 time=0.387 ms
^C
--- 10.10.10.10 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19525ms
rtt min/avg/max/mdev = 0.214/0.359/0.691/0.084 ms
driver: e1000e
version: 6.1.0-10-rt-amd64
firmware-version: 1.8-0
expansion-rom-version:
bus-info: 0000:04:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes


 

Please Log in or Create an account to join the conversation.

More
06 Aug 2023 12:37 #277105 by rodw
Perfect. It's hard to understand your config from a distance so thanks for going along with me.
The following user(s) said Thank You: WKS-3D

Please Log in or Create an account to join the conversation.

Time to create page: 0.139 seconds
Powered by Kunena Forum