I have a dual 2.5Gbps Ethernet hat that uses the RTL8125 driver. I have tried installing the driver in several ways using apt and also just downloading the driver from Realtek. It seems to have the driver loaded but it never gets an IP address (stuck and "connecting"). Is there something still missing from the kernel that would allow this to work?
EDIT: Interesting fact, when I disable the interface on the ethernet hat I lose the display and it appears to reboot.
Is this the one from radxa? Because if so, we are in the same boat.
No, mine is an MCUZone dual ethernet 2.5 Gbps adapter. It's an 8125 based adapter, which I'm sure the Radaxa is as well. I've tried installed the driver manually with no luck. Something must be missing from the kernel to make this work.
Mine is finally working on the latest 24.04 release, but runs extremely hot though. After letting the barrel jack from the hat provide the power to the tachyon, the heat issues are gone. It's running perfectly now.
Did you need to load any drivers? I am powering my stack from the molex connector on my 4 slot sata card connected to a pc power supply so juice isn't the problem. The problem I have is that it doesn't get an IP from the DHCP server and when I assign a static IP it doesn't work. Did you reflash or just do updates?
I fully reflashed
That didn't seem to work for me. I think I have some sort of interrrupt conflict because if I have the wifi adapter enabled with the dual 2.5 gb hat, the Tachyon reboots, if I plug it into the nework and it never grabs an IP. It looks like the driver is loaded but that's where the fun ends. I have to resort to a usb 2.5 gb ethernet adapter that does work. Can you tell me if your hat is using the R8125 driver?
When the link comes up I'm getting this error. I blacklisted the R8169 driver and compiled the R8125 driver and it keeps failing to activate the connection:
Dec 29 15:15:18 tachyon-d974595f kernel: r8125: enP1p6s0: link up
Dec 29 15:15:18 tachyon-d974595f kernel: qsmmuv500-tbu 151f9000.anoc_1_pcie_tbu: ATOS generated a fault interrupt! PAR = 803, SID=0x1c80
Dec 29 15:15:18 tachyon-d974595f kernel: qsmmuv500-tbu 151f9000.anoc_1_pcie_tbu: ATOS generated a fault interrupt! PAR = 803, SID=0x1c80
Dec 29 15:15:18 tachyon-d974595f kernel: qsmmuv500-tbu 151f9000.anoc_1_pcie_tbu: ATOS generated a fault interrupt! PAR = 803, SID=0x1c80
Dec 29 15:15:18 tachyon-d974595f kernel: qsmmuv500-tbu 151f9000.anoc_1_pcie_tbu: ATOS generated a fault interrupt! PAR = 803, SID=0x1c80
Dec 29 15:15:18 tachyon-d974595f kernel: qsmmuv500-tbu 151f9000.anoc_1_pcie_tbu: ATOS generated a fault interrupt! PAR = 803, SID=0x1c80
Dec 29 15:15:18 tachyon-d974595f kernel: qsmmuv500-tbu 151f9000.anoc_1_pcie_tbu: ATOS generated a fault interrupt! PAR = 803, SID=0x1c80
Dec 29 15:15:18 tachyon-d974595f kernel: arm-smmu 15000000.iommu: Unhandled context fault: fsr=0x402, iova=0xfe310000, fsynr=0x3b0002, cbfrsynra=0x1c80, cb=6
Dec 29 15:15:18 tachyon-d974595f kernel: arm-smmu 15000000.iommu: FSR = 00000402 [TF ], SID=0x1c80
Dec 29 15:15:18 tachyon-d974595f kernel: arm-smmu 15000000.iommu: soft iova-to-phys=0x0000000000000000
Dec 29 15:15:18 tachyon-d974595f kernel: arm-smmu 15000000.iommu: SOFTWARE TABLE WALK FAILED! Looks like 15000000.iommu accessed an unmapped address!
Dec 29 15:15:18 tachyon-d974595f kernel: arm-smmu 15000000.iommu: hard iova-to-phys (ATOS) failed
I have this dual 2.5Gb hat:
With the given r8125 driver installed directly indeed.
Hmm..so your card has more than just the dual ethernet ports. I have a dual PCI slot hat and a Penta Sata Hat. I wonder if all that in combination is causing a problem somehow. Did you have to blacklist the R8169 driver?
I came across this in a Ubuntu forum regarding the R8125 based adapters:
"FWIW, the driver support for the chip is present in 6.12.36. 24.04 HWE kernel hasn't reached that version yet; I believe it sits at 6.8 at the moment."
So looks like I have to wait for the Particle version of the 6.12 kernel. I'm wondering how yours is working because I see other Ubuntu users reporting the same behavior I'm seeing: driver loads, card connects but doesn't get an IP. Even setting a static IP doesn't work.