A small, affordable computer with free resources to help people learn, make things, and have fun
https://forums.raspberrypi.com/
Code: Select all
[root@rpi ~]# rpm-ostree status
State: idle
Deployments:
●くろまる fedora-iot:fedora/stable/aarch64/iot
Version: 40.20240926.0 (2024年09月26日T15:46:00Z)
BaseCommit: 7a242e48bdf0d65d68b0d0d27df81628b6ea2a87d2a2c02121359fd9b0ee61fb
GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
LayeredPackages: bind-utils bluez ethtool htop systemd-container systemd-networkd tcpdumpCode: Select all
rpm-ostree upgradeCode: Select all
[root@rpi ~]# dig +short aaaa d2uk5hbyrobdzx.cloudfront.net
2600:9000:2261:4400:1a:9c17:e740:21
2600:9000:2261:fa00:1a:9c17:e740:21
2600:9000:2261:7c00:1a:9c17:e740:21
2600:9000:2261:b400:1a:9c17:e740:21
2600:9000:2261:4a00:1a:9c17:e740:21
2600:9000:2261:6a00:1a:9c17:e740:21
2600:9000:2261:2a00:1a:9c17:e740:21
2600:9000:2261:6600:1a:9c17:e740:21Code: Select all
curl -o /var/tmp/test https://d2uk5hbyrobdzx.cloudfront.net/objects/b6/a2e2f2833ddbcf117796ca4ac0fac6638efedb3c8536be70d4f63eabec3379.filezCode: Select all
[root@rpi ~]# cat /etc/systemd/network/20-end0.link
[Match]
MACAddress=dc:a6:32:4c:75:2c
[Link]
Advertise=10baset-full
Advertise=10baset-half
Advertise=100baset-full
Advertise=100baset-halfCode: Select all
[root@rpi ~]# ethtool --show-eee end0
EEE settings for end0:
EEE status: disabled
Tx LPI: disabled
Supported EEE link modes: 100baseT/Full
1000baseT/Full
Advertised EEE link modes: 100baseT/Full
1000baseT/Full
Link partner advertised EEE link modes: 100baseT/Full
1000baseT/Full'Fedora is RedHat/IBM', they set/are a standard for Linux. They likely find it more important that their Linux is driving and following the mainline kernel and multi-vendor standards then something from a tiny company that just did an IPO and uses proprietary firmware and boot-loader.
Good point. I ordered a new cable and tried it with a new cable. Same issue.First thing to try with all random ethernet problems is a different ethernet cable.
This feels like cookie-cutter advice which doesn't help here. I assume this is in reference to finding a fast mirror which is fundamentally not how Fedora IoT/RPM-Ostree works. It only has one mirrorgoogle for tweaks, there out there and sometimes help for the larger updates.
Code: Select all
[root@rpi ~]# curl https://ostree.fedoraproject.org/iot/mirrorlist
https://d2ju0wfl996cmc.cloudfront.net/Code: Select all
[root@rpi ~]# curl -o /dev/null https://d2uk5hbyrobdzx.cloudfront.net/objects/b6/a2e2f2833ddbcf117796ca4ac0fac6638efedb3c8536be70d4f63eabec3379.filez
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 131M 100 131M 0 0 10.3M 0 0:00:12 0:00:12 --:--:-- 10.5MFedora 40 (as seen in the original post by the output of rpm-ostree status).what fedora version are you running.
Not sure how this is related to my problem?i've seen ultramarine in imager, but haven't tried it. i watch videos so i need DRM for some, so i prefer a custom raspberry os lite install.
No, i only have a FRITZ!Box, but not sure what else a managed switch would tell me that the tcpdump wouldn't.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.
Raspberry Pi 4 is officially supported since Fedora 37. See here: https://fedoraproject.org/wiki/Changes/RaspberryPi4Fedora is not RPi specific AFAIR
How would a bootloader impact the Ethernet after boot? I'm also not sure about how to detect a firmware mismatch. My Firmware is fairly recent, i updated it via rpi-eeprom-update about 6 months ago to the latest stable back then. Also the fedora-arm-installer has a special flag to indicate the image is for a RPi4 which copies then some special boot files. Is this what you mean?so it might be the set of bootloader+firmware+kernel causes some internal mismatch.
It is not. Fedora 40 is the current stable release, being out for some time now. The timestamp just indicates the last time i ran a system wide update.Or wait until someone else also experiences the same problem with 'Version: 40.20240926.0 (2024年09月26日T15:46:00Z)' and reacts in this topic. It is very new version, so usually that means you need Fedora maintainers themselves.
I'm not sure i understand correctly. Do you mean the mainline linux kernel receives no support in here?On this RPI forum focus is on Debian+vendorkernel, not mainline and/or U-boot/EFI, where the problem might come from