@Alex-Kushleyev Is there a way to run menuconfig and build the kernel successfully? I wonder if menuconfig might "deconflict" certain feature dependencies, if there are any? When I tried running menuconfig from apps_proc/src/kernel/*, the resulting build failed with errors about the source tree not being clean.

@Alex-Kushleyev in my case, 'lsmod' is empty after booting the kernel with SYSVIPC enabled...its as though none of the kernel modules are loading anymore.

@Alex-Kushleyev Thank you for the quick reply. Your advice successfully enabled SYSVIPC in my kernel. Sadly, SYSVIPC also broke eth0 on my system and I'm still attempting to troubleshoot that...

Hello. We are attempting to run our application on VOXL2. This application is linked against some pre-compiled libraries that we received from a third-party as their SDK. We have successfully run this application on x86_64 and on another arm64 platform, but on VOXL2 we receive the error message in the title "Fatal: ThreadLocker acquire: QSystemSemaphore::handle: unknown error 38"

In troubleshooting, I see that on VOXL2 the file /proc/sys/kernel/sem is not present. Could this be indicative that the kernel must be reconfigured for certain types of semaphore usage? I am able to download the MODAL.AI kernel build docker and build the default v1.8.02 kernel. But any time I try to make a change to the kernel config using menuconfig in one of the build_mount/lu.um.121/apps_proc/src/kernel/* directories, the rebuild fails (even if I clean first). So perhaps this is not the right way to reconfigure the build? I went down this road because it seemed that adding Qualcomm IPCC support (menuconfig, device drivers, SOC drivers, qualcomm IPCC) could potentially resolve the issue.

Any and all advice is welcome, including the proper way to reconfigure the kernel (via menuconfig or otherwise) or in troubleshooting this semaphore issue itself.