Linux/PROCESSOR-SDK-AM335X: KMOD Recipe Not Populating to Rootfs

matt minga

Tool/software: Linux

I have a project configured to build the core-image-minimal out of the argo distribution. I realized that this latest version had moved to systemD, I need systemV due to some legacy requirements by my customer. In flipping over to ARAGO_SYSVINIT=1 in my local.conf the kmod recipe does not seem to be populating to the rootfs. Thoughts? Why would switching to systemV create an issue like this?

over 6 years ago

0 Kemal R. Shakir over 6 years ago

TI__Guru 55345 points

Hello Matt,

Please, see the DEPENDS = "kmod intltool-native gperf-native acl readline libcap libcgroup util-linux" line in <tisdk>/sources/oe-core/meta/recipes-core/systemd/systemd_<version>.bb recipe. This means that the systemd depends and indirectly includes these listed packages to the rootfs.

Best regards,
Kemal

0 Kemal R. Shakir over 6 years ago in reply to Kemal R. Shakir

TI__Guru 55345 points

Hello Matt,

Please, close this thread by clicking on "This resolved my issue" button.

Best regards,
Kemal

0 matt minga over 6 years ago in reply to Kemal R. Shakir

Intellectual 715 points

Thank you for your help.

I wound up including module-init-tools to get kmod back into the image. I also wound up including libltdl, usbutils, and pciutils in order to get this new image comparable to the old image.

0 Kemal R. Shakir over 6 years ago in reply to matt minga

TI__Guru 55345 points

Yes. You can include these packages by adding them to the <tisdk>/build/conf/local.conf file with IMAGE_INSTALL.

Processors

Processors forum

Linux/PROCESSOR-SDK-AM335X: KMOD Recipe Not Populating to Rootfs