LE13 RK356X build issues using docker (podman)

    Hello,

    I'm trying to build LE13 with the aic8800 wifi driver, following the great work by Yasai-san (cf. https://github.com/ShigeakiAsai/L…er-and-firmware ) however, the build is failing.

    I've build the Trixie image and am now trying to build with the following command:

    podman run --rm --log-driver none --userns=keep-id:uid=1000,gid=1000 -v `pwd`:/build:z -w /build -it -e PROJECT=Rockchip -e DEVICE=RK356X -e ARCH=arm libreelec scripts/image image

    This is on a Fedora 43 host. --userns is needed to as this is rootless podman, and the :z in -v `pwd`:/build:z ensures SELinux labels are relabelled accordingly to allow processes in the container to access and use the files.

    The build fails at step 95/315: build Mako:host:

    Looking further in the logs doesn't give anything immediately useful.

    build.LibreELEC-RK356X.arm-13.0-devel/build/glibc-2.43/.armv8.2a-libreelec-linux-gnueabihf/config.log shows:

    Am i missing something obvious?

    I was able to build a release image ready to write to a micro SD card (using make image instead of ./scripts/image image), write it and then start from it. And on first run, it prompted me to connect to wireless networks and did so successfully, so that's very nice.

    However, when coming back to the device a few hours later, it had forgotten the wifi password as it was asking for it again. The device was no longer reachable on the network either. Is this a known issue? is there a place to track this bug?

    Quote from axel

    When coming back to the device a few hours later, it had forgotten the wifi password as it was asking for it again. The device was no longer reachable on the network either. Is this a known issue? is there a place to track this bug?

    It's not a general issue that we see with other WiFi drivers that we choose to include in LE images. Any issues with the aic8800 driver that we choose not to include in LE images are not something we're interested in taking bug-reports on. The Khadas driver repo would be a more appropriate place to log tickets.

    NB: ConnMan stores WiFi credentials in a profile reference that contains the MAC address of the NIC interface so check the MAC address doesn't rotate/change after boot or on each boot. If it does, ConnMan will correctly see a 'new' connection and will reprompt for the passphrase again.

    Thanks chewitt , as i've said elsewhere i understand and agree with the policy of not supporting issues with that drivers that can't be included in LE.

    I'll check the MAC address, could be that. I've see this happen on my rock4 se too, where LE "forgets" the wifi, so thought it might be linked to a more general bug. Let's see what's going of first.