On Sun, Feb 28, 2021, at 12:50 PM, Samuel Sieb wrote:
On 2/28/21 12:36 PM, Doug H. wrote:
On Sun, Feb 28, 2021, at 12:07 PM, Samuel Sieb wrote:
On 2/28/21 9:44 AM, Doug H. wrote:
On Sat, Feb 27, 2021, at 6:36 PM, Samuel Sieb wrote:
One thing to try if you can is to use a cross-over network cable.
I still think this would be your best option if you can find or make one.
For just $4.60 delivered: Amphenol MP-5XRJ45UNNB-003 Cat5e UTP Crossover Cable, RJ45,
I am willing, but do wonder why it worked for so long and still works when it does work.
There could be weird timing issues with the auto-negotiation. It's really hard to say. Just for curiosity, what happens if you disable the wake-on-lan option? Was that something you changed recently? Because it does seem possibly related to the transition from that, since you mentioned that it works after a full cold boot where the ethernet is completely off.
1. Turned off my rc.local line of `/sbin/ethtool -s enp5s0 wol g` 2. Powered off, did my "power drain" thing. 3. Booted, finding it working fine (as before). 4. Checked Wake on LAN and it was still on, hmmm... 5. Realized that it was being set by NetworkManager, the rc.local was only needed when I was using network *without* NetworkManager. 6. Set NetworkManager setting to off/default. Verified with `ethtool`. 7. Reboot. Still seeing the issue.
P.S. I found a Belkin cable for $3.99. I like that name better, so ordered it. Belkin 3-Foot CAT5e Crossover Molded Networking Cable (Yellow)
It seems worth the test and worth having such a cable.