Marvee Amasi
Marvee Amasi
PostsComments
DIIDevHeads IoT Integration Server
Created by Marvee Amasi on 6/3/2024 in #middleware-and-os
trying to enable CONFIG_AUTOFS4_FS in the kernel for my custom machine my_mach using Yocto Project
I'm trying to enable CONFIG_AUTOFS4_FS in the kernel for my custom machine my_mach using Yocto Project, but it's not reflected in the final image. Observe my set up: -Base layer: meta-xxx-yyy -Custom layer: meta-xxx-mylayer I took this steps to try trouble shoot -Added CONFIG_AUTOFS4_FS=y to a fragment file (frag.cfg) in 
meta-xxx-mylayer/recipes-kernel/linux/files/
meta-xxx-mylayer/recipes-kernel/linux/files/
-Included the fragment file in linux_git.bbappend using SRC_URI += "file://frag.cfg" -Set COMPATIBLE_MACHINE_my_mach = "my_mach" in linux_git.bbappend -Built the kernel using bitbake linux -c cleansstate -f; bitbake linux -c configure -f; etc. The build completes successfully. CONFIG_AUTOFS4_FS is not set in the final image 
/proc/config.gz
/proc/config.gz
. My custom layer meta-xxx-mylayer seems functional 
another recipe builds rootfs successfully
another recipe builds rootfs successfully
. frag.cfg is copied to a different directory than the main kernel source git. What could be causing CONFIG_AUTOFS4_FS to not be enabled despite the fragment file? Is the location difference between frag.cfg and the main source a potential issue? @Middleware & OS
7 replies