Open bennr01 opened 3 weeks ago
I've investigated this a bit more and think I may have found a possible fix. Modifying this line by changing it to CONFIG_BINFMT_MISC=y
fixes this specific issue with binfmt. Following the change, x86/x64 binaries can be seamlessly executed as the automated invocation of box86 and box64 works properly.
However:
Starting of proc-sys-fs-binfmt_misc.automount unsupported
. This does not seem to have any negative effect on the system as far as I can tell, but I am going to investigate this a bit more. Perhaps this is related to the missing autofs4
module.Update:
I've tested another build with CONFIG_AUTOFS4_FS=y
and CONFIG_AUTOFS_FS=y
. Using these parameters, no failure, unsupported or not found message appear during boot and in dmesg. Everything seems to work fine.
Describe the bug
The
proc-sys-fs-binfmt_misc.mount
service fails to start during boot, causing binfmt integration to not work correctly.How to reproduce
On a fresh installation of ROCKNIX using
ROCKNIX-RK3399.aarch64-20241029.img
on a SD card (leaving the other SD card slot empty), booting the device shows a message that the service fails to start during boot, After boot,sudo systemctl status proc-sys-fs-binfmt_misc.mount
confirms that the service failed due to a missing file or directory. Attempting to run any x86/x64 file also shows that the automatic invocation of box86/box64 fails, further confirming that the service is not running correctly.Information
Log file
sudo systemctl status proc-sys-fs-binfmt_misc.mount
ls /proc/sys/fs/
Relevant
dmesg
sectionssudo systemctl restart proc-sys-fs-binfmt_misc.mount (fails, followed by journalctl -xe)
mount
Context
This is my first install of ROCKNIX. No changes have been made to the system. I've tried re-downloading and re-flashing the SD card. I do not know if this is bug was recently added with the new release or if it has been around for a while.