From: "Dave Tucker" <theaethereal@gmail.com>
To: meta-ti@lists.yoctoproject.org
Subject: Beaglebone Black Ethernet Failures
Date: Wed, 10 Mar 2021 05:27:22 -0800 [thread overview]
Message-ID: <u0TL.1615382842912667990.O2ud@lists.yoctoproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
I have been using a Beaglebone Black for a project for years. I recently upgraded from Dunfell to Gatesgarth and again began experiencing a problem with the ethernet interface failing to come online 10% of the time, a problem which can only be fixed by a power cycle (not a reboot). This is a well known problem documented by this thread ( https://groups.google.com/g/beagleboard/c/9mctrG26Mc8 ) going back over 7 years. It's a hardware problem, but it does have a software fix. But that fix must have been left out of recent meta-bbb builds. I believe previous fixes have been something like this patch ( https://github.com/RobertCNelson/bb-kernel/blob/607ae2e36477357a4bb222f285fd7460d5230ab9/patches/net/0009-cpsw-search-for-phy.patch ). That old patch targets the 3.15 kernel and I believe Gatesgarth is using 5.10. Should I expect that patch to work unmodified on 5.10? I don't know low level kernel mechanics well enough to understand what it's really doing. If that patch won't work, does anyone know how I could proceed to get ethernet working on the Beaglebone Black with current versions of Yocto?
Dave
[-- Attachment #2: Type: text/html, Size: 1320 bytes --]
next reply other threads:[~2021-03-10 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 13:27 Dave Tucker [this message]
2021-03-10 16:23 ` [meta-ti] Beaglebone Black Ethernet Failures Nishanth Menon
2021-03-11 22:18 ` Dave Tucker
2021-03-11 22:19 ` Dave Tucker
2021-03-11 22:37 ` [meta-ti] " Nishanth Menon
2021-03-12 0:57 ` Robert Nelson
2021-03-12 14:11 ` Dave Tucker
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u0TL.1615382842912667990.O2ud@lists.yoctoproject.org \
--to=theaethereal@gmail.com \
--cc=meta-ti@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.