fliz
April 6, 2026, 8:10am
1
where do I look to see how the buildbot builds firmware for the firmware-selector.openwrt page?
when it builds the image for the eax17, the image is broken, but when I build myself using make it works fine.
I'd like to dig into this so I can submit a fix, but I don't know where to look.
followed the link in the lower right corner of https://firmware-selector.openwrt.org/ ?
efahl
April 6, 2026, 11:03pm
4
fliz:
buildbot builds firmware
Do you mean the CI that takes the main and package repos, producing the actual binaries, packages and package indexes, or do you mean the CI that creates the containerized imagebuilders that the ASU server uses to produce custom images for the Firmware Selector, LuCI Attended Sysupgrade and owut?
fliz
April 8, 2026, 7:34am
5
I figured out the issue and submitted a fix:
main ← Jascha-Sundaresan:fix-eax17-per-device-rootfs
opened 07:27AM - 08 Apr 26 UTC
…ootfs builds
When CONFIG_TARGET_PER_DEVICE_ROOTFS is enabled (as in buildbot… builds), the final per-device rootfs is assembled at root.squashfs+pkg=<hash> rather than root.squashfs. The gen_netgear_rootfs_node.sh script was always hashing root.squashfs (the base rootfs without device-specific packages), causing the size and hash in the FIT node to not match the actual rootfs written to the UBI volume, resulting in boot failure on buildbot-produced images.
Fix by using the per-device rootfs path when TARGET_PER_DEVICE_ROOTFS is set, consistent with how include/image.mk handles the same distinction elsewhere.
Fixes: 46ab9f3f1c ("filogic: add support for Netgear EAX17")