Make sure to set the PI end to match. The 100Mbit/full auto-neg failure default is 10mbit/half and works badly with the other end running 100/full.
As someone also said you might want to try a 100Mbit crossover cable. The gig port would need to figure out correctly that it needs to have 2 pairs swapped and also apply the auto-neg process to the swapped pairs. It may be that forcing 100/full simplifies this process or it may be that a crossover cable with the correct pairs swapped removes the steps that don't happen right all of the time.
On Sat, Feb 27, 2021 at 8:55 PM Ed Greshko ed.greshko@greshko.com wrote:
On 28/02/2021 10:36, Samuel Sieb wrote:
So this confirms what I was suspecting. The 10M you see at first is the "default" state of the ethernet card where it's watching for the wake-on-lan signal. Once the kernel boots and initializes the card, the card tries to auto-negotiate. This seems to be failing due to some interaction between the pi's network device and this one.
If it is an issue of auto negotiation one could also try using nmcli to set
802-3-ethernet.auto-negotiate: to no and as well as the appropriate settings for
802-3-ethernet.speed: 802-3-ethernet.duplex:
in the connection settings.
Or use the appropriate GUI if more comfortable with that. :-)
-- People who believe they don't make mistakes have already made one. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure