I can try it but if you see the breakage return upon downgrading a single package, that's pretty good evidence that the package is breaking it. Plus, if I reproduce it that doesn't really help debug it beyond a "me too" confirmation.
Only two files changes between those versions:
$this->bbcode_second_pass_code('', 'git diff 76851155c..c617300d8 -- PKGBUILD config
diff --git a/core/linux-raspberrypi4/PKGBUILD b/core/linux-raspberrypi4/PKGBUILD
index d5ed1974d..2350a86d4 100644
--- a/core/linux-raspberrypi4/PKGBUILD
+++ b/core/linux-raspberrypi4/PKGBUILD
@@ -7,12 +7,12 @@
buildarch=12
pkgbase=linux-raspberrypi4
-_commit=24c8b0546a820222a1ebcfe606dfacb0e228c466
+_commit=046e2dccac6414e728d87188eb28f9e047d63884
_srcname=linux-${_commit}
_kernelname=${pkgbase#linux}
_desc="RPi 3/4/400"
-pkgver=5.10.63
-pkgrel=18
+pkgver=5.10.73
+pkgrel=3
pkgdesc='Linux'
url="http://www.kernel.org/"
arch=(armv7h aarch64)
@@ -30,15 +30,15 @@ source=("https://github.com/raspberrypi/linux/archive/${_commit}.tar.gz"
60-linux.hook
90-linux.hook
)
-md5sums=('725444e5327983af92983dd30cb02b0d'
+md5sums=('cb641ff2cac6fa1244b888c01ab8c2ec'
'31c02f4518d46deb5f0c2ad1f8b083cd'
'f66a7ea3feb708d398ef57e4da4815e9'
'86d4a35722b5410e3b29fc92dae15d4b'
'0a5f16bfec6ad982a2f6782724cca8ba'
'441ec084c47cddc53e592fb0cbce4edf')
-md5sums_armv7h=('8de6f2c9117439f4ef3c28db695e99ef'
+md5sums_armv7h=('b4b1e43f274564a18afdb2c73b568e25'
'9669d916a5929a2eedbd64477f83d99e')
-md5sums_aarch64=('7e706b74e472828c0eefd98f8e2d7008'
+md5sums_aarch64=('05b1db704734c0d18b98c06c2df9da70'
'9669d916a5929a2eedbd64477f83d99e')
# setup vars
diff --git a/core/linux-raspberrypi4/config b/core/linux-raspberrypi4/config
index 2b0f85f9f..4d65229d0 100644
--- a/core/linux-raspberrypi4/config
+++ b/core/linux-raspberrypi4/config
@@ -2566,7 +2566,7 @@ CONFIG_NET_VENDOR_RDC=y
CONFIG_NET_VENDOR_REALTEK=y
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
-# CONFIG_R8169 is not set
+CONFIG_R8169=m
CONFIG_NET_VENDOR_RENESAS=y
CONFIG_NET_VENDOR_ROCKER=y
CONFIG_NET_VENDOR_SAMSUNG=y
@@ -2651,7 +2651,7 @@ CONFIG_MICROCHIP_PHY=y
# CONFIG_NXP_TJA11XX_PHY is not set
CONFIG_AT803X_PHY=m
# CONFIG_QSEMI_PHY is not set
-# CONFIG_REALTEK_PHY is not set
+CONFIG_REALTEK_PHY=m
# CONFIG_RENESAS_PHY is not set
# CONFIG_ROCKCHIP_PHY is not set
CONFIG_SMSC_PHY=y
')
The change to the config, building a few modules, is not to blame. You should open a bug report against the RPiF kernel citing their last-known-good (the 24c8b0546a commit) and the new one breaking the functionality.
https://github.com/raspberrypi/linux/issues