Debos and last Image Update

[joergbrors]

Good morning,

I have a question regarding building customized images with debos from the debos_build repository located in GitLab. Last week, a new build failed on my Connect-SE device. It looks like that after upgrading the image from 6.6 → 6.12, the script /usr/sbin/revpi-factory-reset caused the system (at least the IP stack) to crash during the step where the system-specific overlay kernel modules are copied.

Has anyone experienced this kind of issue?

Working image: linux-image-revpi-v8 (6.6.84-rt52-revpi9-1+deb12+1)
Failing image: linux-image-revpi-v8 (6.12.56-revpi0-1+deb12+1)

[nicolaiB]

Hi,

do you have any error messages / logs so we can have a look?

Thanks.

[joergbrors]

Hi,
I currently don’t have a mini HDMI cable to connect to my Connect-SE. From the build process I’ve already created a ticket and attached the captured build logs.
Do you have the possibility to check this in your environment?
Otherwise, please let me know which additional logs you would need.

thanks

[nicolaiB]

I was able to reproduce the issue in my lab and pinned it down to the usb controller. With kernel 6.12 we switched to the xhci usb controller on CM4S modules, which performs much better than the designware dwc2 which was enabled so far. This does not affect devices, which already have choosen the correct overlay, but during factory reset the device runs initially on dwc2, so usb vanishes as soon as the target overlay is loaded. Luckily the fix is quite straightforward: Ensure that the xhci controller is always loaded on CM4S, so the overlay applies cleanly:

https://gitlab.com/revolutionpi/debos-b ... quests/146

With these changes, your build should work on Connect S/SE.

[joergbrors]

WoW! That’s very cool to read this.
Thank you very much for the quick support!
I will test the fix this evening and provide feedback afterwards.

[joergbrors]

Now it’s working again — thanks a lot!
Jörg