All of
 help / color / mirror / Atom feed
From: Peter Korsgaard <>
Subject: [Buildroot] Handling delays in network interface visibility in Raspberry Pi 3
Date: Tue, 16 Feb 2021 12:23:59 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Ivo Grondman's message of "Tue, 16 Feb 2021 11:37:26 +0100")

>>>>> "Ivo" == Ivo Grondman <> writes:


 > Turned out I was using an old cable only capable of 100BASE-TX
 > (i.e. it only had 2 wire pairs). Replacing it with a cable with all 4
 > wire pairs in it did the trick, even when still behind the switch and
 > the power line adapter. Never had problems with that cable before
 > (didn?t care about the speed difference), but apparently in this case
 > it was the culprit of slow link negotiation.

Ok, good to hear that you solved it!

Bye, Peter Korsgaard

  reply	other threads:[~2021-02-16 11:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 16:34 [Buildroot] Handling delays in network interface visibility in Raspberry Pi 3 Ivo Grondman
2021-02-15 18:26 ` Nicolas Cavallari
2021-02-15 22:01 ` Peter Korsgaard
2021-02-16 10:37   ` Ivo Grondman
2021-02-16 11:23     ` Peter Korsgaard [this message]
2021-02-15 23:33 ` Christopher McCrory
2021-02-16 20:30   ` Peter Seiderer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.