Stannieman

Ok I thought it could be some more generic layer on top, but if this is proven to be Rockchip specific then it must indeed be something else. Thanks for the reply!

This seems to affect the Odroid HC4 too, as no disks connected to the built in SATA ports show up anymore.

Ok that's all clear now, thanks a lot for the answers!

Ok so RE the builds: That means that if you want to build an image that corresponds to one of versions listed here (https://docs.armbian.com/Release_Changelog/) you pretty much need to build on release day. Otherwise it is possible that some commits for the next version are already merged in and will be part of the build, right? What kind of work is needed for specific version builds to work? I guess the build scripts need to also checkout that version from other repos and today it just takes the latest of everything? And RE the version file: What do you mean with "If you want the packages you have collected to be installed..."? Is that for the OFFLINE_WORK=yes option so that the current online version appears older than the local build?

Hi! I'm sorry if the answer to my question is already documented somewhere, but I couldn't find it. I am trying to figure out how to build a specific release. My understanding is that you checkout the desired tag of the armbian/build repo and just build it. However, when I do this with v24.2.1 the image that comes out is named 24.5.0-trunk. Changing the version in the VERSION file (by default set to 24.5.0-trunk) changes the name of the output image, but it is not clear to me if that affects other things than just this. So basically, now I am confused which scenario is correct: Is using the armbian/build tag the correct way to build a specific release and is the VERSION file just cosmetic? Is setting the version in the VERSION file the correct way and should any commit in armbian/build be able to generate the same image, provided the commit is new enough? A 3rd more correct way that I'm not aware of? Can anyone help me out here? Regards Stan