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.
Unfortunately the cross over cable has not solved the issue. It works just the same as a straight cable in this situation. The NIC does say that it supports auto detection, which does seem to be working and not the core of this issue.
It would have been helpful to see what the output of ethtool is when it's working, but when it's not working, try the following:
ethtool -s enp5s0 mdix on
Give it a few seconds, see if it comes on. If not, then try:
ethtool -s enp5s0 mdix off
I did try this. Those commands do execute without giving an error but it does not then turn on any lights.
Yes, now that I see your ethtool output, neither device supports setting this. I'm somewhat surprised that it doesn't give an error, but maybe by design it doesn't error on unsupported functions.
An interesting note is that while testing with the cross over cable I ended up with it hardly working at all. The fix was `ethtool -s enp5s0 mdix on`. So it does seem that these commands were doing something after all.
I did find a 1 Gig switch that has a low power draw, so I can either use that to fully fix the issue or I can use my "bounce it from the Pi side" icon after each reboot.