bf26

Support could not answer all my questions, but they hinted at two things: r8169 is okay, as it supports the chips they use and they use it on newer versions as well. It's most likely an issue with the device tree, which appears to not contain an entry for the second PCIe controller. I'll play around a bit with this. Maybe, @krachlatte, you have an idea? 🙂

Hi everyone! I got a Radxa E25 network computer with two 2.5GBit ethernet ports. The first one is coming up, the second one, however, does not. After comparing to the Debian Bullseye image by Radxa, I figured they don't bring the second port up either but for a different reason. Finally, I found a release on Radxa's Github that brings up both ports. I'll give you the output of that one and the Armbian and the Radxa E25 Bullseye images marked accordingly. The three images are: "b1 (rsdk)", "radxa-e25_bullseye_cli_b1.output.img.xz", works, source: https://github.com/radxa-build/radxa-e25/releases Radxa E25 Bookworm: "radxa-e25-debian-bullseye-xfce4-arm64-20221028-0509-gpt.img.xz", does not work, source: https://wiki.radxa.com/Rock3/downloads Armbian 24 for E25, "Armbian_24.11.1_Radxa-e25_noble_current_6.6.62.img.xz", does not work, source: https://www.armbian.com/radxa-e25/ Number 1 (working) loads "r8125" for both ethernet ports. Number two (not working) loads "r8125" but fails to detect the second port. The third (Armbian, not working) loads "r8169", which does activate the first port but also fails to activate the second. I've checked the device trees of the three images and found a couple of differences. Under /pinctrl/ the device tree of the working "b1 (rsdk)" image has: eth0 { eth0-pins { rockchip,pins = <0x02 0x11 0x02 0x11a>; phandle = <0x231>; }; }; eth1 { eth1m1-pins { rockchip,pins = <0x04 0x0b 0x03 0x11a>; phandle = <0x233>; }; eth1m0-pins { rockchip,pins = <0x03 0x08 0x03 0x11a>; phandle = <0x232>; }; }; while Armbian has: eth0 { eth0-pins { rockchip,pins = <0x02 0x11 0x02 0xb1>; phandle = <0x183>; }; }; eth1 { eth1m1-pins { rockchip,pins = <0x04 0x0b 0x03 0xb1>; phandle = <0x185>; }; eth1m0-pins { rockchip,pins = <0x03 0x08 0x03 0xb1>; phandle = <0x184>; }; }; and Radxa's Debian Bookworm has: eth0 { eth0-pins { rockchip,pins = <0x02 0x11 0x02 0x101>; phandle = <0x1d9>; }; }; eth1 { eth1m1-pins { rockchip,pins = <0x04 0x0b 0x03 0x101>; phandle = <0x1db>; }; eth1m0-pins { rockchip,pins = <0x03 0x08 0x03 0x101>; phandle = <0x1da>; }; }; I am in touch with Radxa's support and will place any feedback from them here as well. Output of armbianmonitor for the Armbian image can be found here: https://paste.armbian.com/ekecujoqeb full-devicetree-armbian.dts full-devicetree-bookworm.dts full-devicetree-e25-b1.dts