So I am using Docker to build ARM64 applications natively on the Axon system.
To save space I am storing the cache in an SD card, a SanDisk Extreme 64GB U3 A2 microXC V30.
The system was working fine for a while, then it started to crash after some time whenever Docker.service started .
I thought it was due to high RAM usage, so I avoided using the browser while running the Docker.
The crashes become frequent. Now the system is not working at all .
The white light stays still, It’s not blinking.
I also tried to reflash the image, but that approch also not working , alas i am getting a segmentation error .
1 > I used the same method mentioned in the document
2 > I was using rockay9 image and using latest kernel
3 > i am not touching anything related to boot partition or uboot
Yes, basically you can not access the whole system, including the U-Boot console, but if Axon is booted properly, you can access it using Type-C to USB, but I don’t think it will be useful for you.
1> 6.1 ubuntu24.04 axon image
2 > i wast building blender and moonray form arm64 , using both normal build and buildx container build.
For testing I suggest to
Blender : use make ninja deps , this will build dependency from source takes time and space so
Moonray: Don’t support arm64 fully as build on x64 intersinc , was working. FOR testing build the dependency first .
GitHub source have a method on how to build it inside container
3 > During the middle of running the build process
Hey, I’m trying to reproduce your Blender + Moonray builds inside the RockyLinux 9 ARM64 Docker container.
But I’m running into dependency issues (JPEG, Vulkan, shaderc, SPIRV-Tools, Git LFS, etc.).
Can you tell me exactly how you built Blender inside the RockyLinux:9 image?
Did you install all the dependencies directly inside the container manually,
or
Did you use a Dockerfile with pre-installed packages (e.g., Vulkan, shaderc, SPIR-V tools, glslang, devtoolset)?
Also:
Did you disable any optional Blender features during CMake?
(like Vulkan, OpenColorIO, Embree, OSL, etc.) OR you set any environment variables such as GIT_LFS_SKIP_SMUDGE=1 when cloning?