This should not be too difficult to pinpoint, as said test other cable, look in network switch/linkpartner settings, I hope you have managed switch where you can see various logs.
Fedora is not RPi specific AFAIR, so it might be the set of bootloader+firmware+kernel causes some internal mismatch. You could find and look into the PDF 'Updating the Pi firmware'. In there, there is also a download link to the kernel ZIP file. Put that on your Fedora installation, essentially config.txt determines what is booted. So then you have a stable RPi set of bootloader+firmware+kernel with Fedora userspace. Then see what happens.
Or wait until someone else also experiences the same problem with 'Version: 40.20240926.0 (2024-09-26T15:46:00Z)' and reacts in this topic. It is very new version, so usually that means you need Fedora maintainers themselves. I use/used Opensuse Tumbleweed, same story. On this RPI forum focus is on Debian+vendorkernel, not mainline and/or U-boot/EFI, where the problem might come from.
Fedora is not RPi specific AFAIR, so it might be the set of bootloader+firmware+kernel causes some internal mismatch. You could find and look into the PDF 'Updating the Pi firmware'. In there, there is also a download link to the kernel ZIP file. Put that on your Fedora installation, essentially config.txt determines what is booted. So then you have a stable RPi set of bootloader+firmware+kernel with Fedora userspace. Then see what happens.
Or wait until someone else also experiences the same problem with 'Version: 40.20240926.0 (2024-09-26T15:46:00Z)' and reacts in this topic. It is very new version, so usually that means you need Fedora maintainers themselves. I use/used Opensuse Tumbleweed, same story. On this RPI forum focus is on Debian+vendorkernel, not mainline and/or U-boot/EFI, where the problem might come from.
Statistics: Posted by redvli — Mon Sep 30, 2024 5:31 am