Hello team -
I have a new laptop and it’s running the most current Manjaro Gnome. Most everything is working well but I’m experiencing trouble with wired Ethernet. Wifi works fine.
Symptom is that booting the system 1st-thing in the morning Ethernet has trouble. I get an address right away but ping to non-LAN sites (Yahoo, for example) just stalls. Same, of course, for any browser or email.
After 5-10 minutes all is good.
After establishing working Ethernet LAN connection I can shutdown, restart and everything is thing. Switching back and forth between WiFI and Ethernet then works fine.
Below is the output from uname -a
galago% uname -a
Linux galago 5.13.19-2-MANJARO #1 SMP PREEMPT Sun Sep 19 21:31:53 UTC 2021 x86_64 GNU/Linux
After establishing working Ethernet LAN connection I can shutdown, restart and everything is OK. Switching back and forth between WiFI and Ethernet then works fine.*
well, it’s a mystery. I’ve updated the kernel to 5.15. No change.
Not sure what the effect of HOSTNAME might be in this case but /etc/hostname shows “galago” and that’s what shows on the cable router when I look up IP lease info.
I don’t have any power saving configuration that I know of. That is, nothing I specifically.
I think I have a clue… This machine (System76 Galago) is very new to me and have owned it only a few days I recall most of what was installed, including the system76 driver. In the install notes there was a mention of some other network issues. I uninstalled it and the issue is resolved.
I’ll reach out to them (and maybe the AUR maintainers) for clarity on how best to install their drive on Manjaro
Turn off all your other network connections, including WiFi and after you successfully connected via Ethernet, try to locate problem.
ping your (router) and (external well-performed site or your provider’s network gateway) with not less than 500-1000 network packets.
While ping, use IPs only not host names. For external IP you can use 8.8.8.8 or 8.8.4.4 or your hosts.
To get local IP to ping use your local router’s gateway: get it in networkctl status.
If you see more than 0.2-0.3% for LAN and more than 1-1.5% for external host packets lost, than most probably you have physical connection problems (in your or provider’s infrastructure range, or provider’s software issue), but not your software-originated issue.