I have been using a Beaglebone Black for a project for years.&nbsp; 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).&nbsp; This is a well known problem documented by <a title="Beaglebone Black Ethernet Phy Not Detected on Boot" href="https://groups.google.com/g/beagleboard/c/9mctrG26Mc8" target="_blank" rel="noopener">this thread</a> going back over 7 years.&nbsp; It's a hardware problem, but it does have a software fix.&nbsp; But that fix must have been left out of recent meta-bbb builds.&nbsp; I believe previous fixes have been something like <a href="https://github.com/RobertCNelson/bb-kernel/blob/607ae2e36477357a4bb222f285fd7460d5230ab9/patches/net/0009-cpsw-search-for-phy.patch" target="_blank" rel="noopener">this patch</a>.&nbsp; That old patch targets the 3.15 kernel and I believe Gatesgarth is using 5.10.&nbsp; Should I expect that patch to work unmodified on 5.10?&nbsp; I don't know low level kernel mechanics well enough to understand what it's really doing.&nbsp; 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?<br /><br />Dave