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

> On 15 Feb 2021, at 23:01, Peter Korsgaard <> wrote:
> I guess your problem is that the device (and/or whatever you have
> connected at the other end of the cable) is too slow to negotiate a
> link, so the DHCP client send the DHCP requests too soo and gives up
> before the link comes up.

This comment, together with Cristopher's comment on the possibility of a switch-related issue, made me wonder what could all be causing a slow link negotiation. So I decided I?d put up the Raspberry Pi right next to the router, as before it was indeed behind an extra switch *and* needed to go over a power line adapter. Then again, I could not imagine that this was the cause as I never ever experienced this particular problem before with any other similar device, so if it would be the switch, the router, or the power line adapter then surely I would?ve seen this problem before. Therefore, I decided on a whim that I first would try swapping the Pi?s network cable with that of some other device and it worked immediately!

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.

Thanks for the help.



  reply	other threads:[~2021-02-16 10:37 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 [this message]
2021-02-16 11:23     ` Peter Korsgaard
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.