twwn

I tried both. Only the Armbian vendor one was compiled by myself.

Yes, the vendor image was compiled by myself. I'm not that bothered by the orientation bug, but the inability to operate a hub given a single USB port badly curtails the use of the SBC. Unfortunately device tree issues are entirely out of my league. I've also edited my post to update the build script diffs. For one, I wasn't actually using ATF master, apparently it was just a cached v2.13. Armbian's build script (at least the rockchip64 part) actually breaks if you set ATFBRANCH='branch:master'. I'll try to get the minor fixes merged, but unfortunately BOOT_SCENARIO="binman-atf-mainline", while now working fine for current and edge, would break vendor as it needs to be set globally.

I’ve noticed two USB-C/USB3 issues with the Radxa Zero 3{E,W} when running Armbian (Edge & Current), which don’t occur on Radxa’s vendor builds (kernel 6.1). 1. Issues All branches (Vendor, Current, Edge) Depending on cable orientation, USB3 devices register inconsistently on either: Bus 001 → USB 2.0 (480M) Bus 002 → USB 3.0 (5000M) Reference: previous forum post Armbian dfb7c4f: Current (6.12) & Edge (6.16) My unpowered USB3 hub fails to work at all (it's fine on Radxa's builds & Vendor). On touch, the hub feels more electrically charged than on vendor builds. Plugging in a single device works, but it will still suffer from the cable “upside-down” speed bug. 2. Logs Vendor branch armbianmonitor -u: link Edge branch (same behavior as Current) armbianmonitor -u: link Tried with U-Boot master and ATF mainline → no improvement build script diffs: link U-Boot: 0c558bb ATF: still v2.13, cannot set branch:master (or 9ee2ff1 directly) as Armbian's build script will fail lsusb {-t} outputs: link Build command used: ./compile.sh build BOARD=radxa-zero3 BRANCH=edge RELEASE=trixie \ BUILD_DESKTOP=yes BUILD_MINIMAL=no \ DESKTOP_ENVIRONMENT=gnome \ DESKTOP_APPGROUPS_SELECTED="browsers desktop_tools" \ KERNEL_CONFIGURE=no 3. Notes My USB-PD passthrough adapter’s ethernet device does not appear on the OTG port (seems broken on both Armbian & Radxa vendor images). No relevant fixes appear left in the kernel repos: Linux mainline: rk356 linux-rockchip: rk356 4. Device Tree References Radxa U-Boot fork (2024.10, next-dev branch) rk3566.dtsi rk3568-u-boot.dtsi rk3566-radxa-zero3.dts u-boot-rockchip (merged into mainline) rockchip-u-boot.dtsi rk356x-u-boot.dtsi rk3566-radxa-zero-3w-u-boot.dtsi I think this is due to the DT overlays, but this is a new topic for me. Could somebody please help me or point towards the next steps?

Using Jun 26's Sid_vendor_server-kali, my Zero 3W is stuck in a loop. I can't "Create a loop password" as it'll instantly jump to the "armbian-security login:" prompt. If I login with the default root:1234, I'll briefly see the welcome screen, followed by a very brief "waiting for the system to finish booting", then it's back to 1. This occurs regardless of internet access (provided by a USB-C ethernet adapter, for which Armbian reports a valid LAN IP address).