Scarthgap SPDX conflict

[Bull101]

We are currently updating our Jetson OS based on meta-tegra branch scarthgap-l4t-R35.x to scarthgap. We have switched from the linux-tegra kernel to the yocto-kernel and out of tree nvidia kernel module. When successfully build and run our OS with scarthgap-l4t-R35.x.

When run the build pipeline it appears that it failed at do_rootfs phase with the following error:

 ERROR: core-image-mtd-1.0.0-r0 do_rootfs: Unable to find package with name 'kernel-module-snd-soc-tegra186-asrc-6.6.92-yocto-standard' in SPDX file [OUR_YOCTO_DIR]/build/tmp-glibc/deploy/spdx/by-hash/my_machine/sstate:nvidia-kernel-oot:my_machine-linux:36.4.3:r0:my_machine:12:/nv-kernel-module-snd-soc-tegra186-asrc-6.6.92-yocto-standard.spdx.json

ERROR: Logfile of failure stored in: [OUR_YOCTO_DIR]build/tmp-glibc/work/my_machine-linux/core-image-mtd/1.0.0/temp/log.do_rootfs.9500

ERROR: Task ([OUR_YOCTO_DIR]Dependencies/meta-mtd/recipes-core/images/core-image-mtd_1.0.0.bb:do_rootfs) failed with exit code '1'

ERROR: core-image-mtd-1.0.0-r0 do_populate_sdk: Unable to find package with name 'kernel-module-snd-soc-tegra186-asrc-6.6.92-yocto-standard' in SPDX file [OUR_YOCTO_DIR]build/tmp-glibc/deploy/spdx/by-hash/orin_mtd_my_machine/sstate:nvidia-kernel-oot:my_machine-linux:36.4.3:r0:orin_mtd_my_machine:12:/nv-kernel-module-snd-soc-tegra186-asrc-6.6.92-yocto-standard.spdx.json

ERROR: Logfile of failure stored in: [OUR_YOCTO_DIR]build/tmp-glibc/work/my_machine-linux/core-image-mtd/1.0.0/temp/log.do_populate_sdk.9504

ERROR: Task ([OUR_YOCTO_DIR]Dependencies/meta-mtd/recipes-core/images/core-image-mtd_1.0.0.bb:do_populate_sdk) failed with exit code '1' 

The file nv-kernel-module-snd-soc-tegra186-asrc-6.6.92-yocto-standard.spdx.json is present in the build directory.

After digging a bit I've starting to suspect the addition of the "nv-" prefix in all the nvidia kernel modules without any certainty.

Does anyone already had this issue ?

[madisongh]

The nv-kernel-module-* packages should all be set to PROVIDE the equivalent kernel-module-* package name. I don't know the OE SPDX support well enough to know if it handles alternate providers in all cases. I've not seen this error crop up in any of my builds, though.

[Bull101]

Thank's for the answer. The issue was due to "kernel-modules" being installed in the image. This generates the conflict.

[asterix]

I can second this issue. We do get an SPDX error for OOT modules. Specifically I get one for "spi-tegra210-quad". Happy to supply a full error if needed.

[madisongh]

It would help to have some more info on how to reproduce the error. Adding kernel-modules to my image, and using the linux-yocto kernel instead of the stock NVIDIA kernel (which I'm guessing at based on what logs there were in the OP) still didn't trigger it for me in my builds.

[asterix]

Sorry about the delay on this. For example, with linux-yocto on scarthgap and

CORE_IMAGE_EXTRA_INSTALL += " kernel-modules"

you'll see

ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: Unable to find package with name 'kernel-module-spi-tegra210-quad-6.6.111-yocto-standard' in SPDX file /scarthgap/build/tmp/deploy/spdx/SPDX-1.1/by-hash/p3768_0000_p3767_0001/sstate:nvidia-kernel-oot:p3768_0000_p3767_0001-poky-linux:36.4.4:r0:p3768_0000_p3767_0001:12:/nv-kernel-module-spi-tegra210-quad-6.6.111-yocto-standard.spdx.json
ERROR: Logfile of failure stored in: /scarthgap/build/tmp/work/p3768_0000_p3767_0001-poky-linux/core-image-full-cmdline/1.0/temp/log.do_rootfs.213811
ERROR: Task (/scarthgap/poky/meta/recipes-extended/images/core-image-full-cmdline.bb:do_rootfs) failed with exit code '1'

and you can see the nv- prefixes in there

grep kernel-module-spi-tegra210-quad-6.6.111-yocto-standard /scarthgap/build/tmp/deploy/spdx/SPDX-1.1/by-hash/p3768_0000_p3767_0001/sstate\:nvidia-kernel-oot:p3768_0000_p3767_0001-poky-linux:36.4.4:r0:p3768_0000_p3767_0001:12:/nv-kernel-module-spi-tegra210-quad-6.6.111-yocto-standard.spdx.json

{"SPDXID": "SPDXRef-DOCUMENT", "creationInfo": {"comment": "This document was created by analyzing packages created during the build.", "created": "2026-04-03T21:02:50Z", "creators": ["Tool: OpenEmbedded Core create-spdx.bbclass", "Organization: OpenEmbedded ()", "Person: N/A ()"], "licenseListVersion": "3.14"}, "dataLicense": "CC0-1.0", "documentNamespace": "http://spdx.org/spdxdocs/nv-kernel-module-spi-tegra210-quad-6.6.111-yocto-standard-1cbf2f68-ae5e-539a-997a-c4e5b3f50ba7", "externalDocumentRefs": [{"checksum": {"algorithm": "SHA1", "checksumValue": "0bd1b01b46833d2f84572c0bf3b11f548a3f80a2"}, "externalDocumentId": "DocumentRef-recipe-nvidia-kernel-oot", "spdxDocument": "http://spdx.org/spdxdocs/recipe-nvidia-kernel-oot-33e3ae44-a347-5137-8580-c5770d172fb7"}], "files": [{"SPDXID": "SPDXRef-PackagedFile-nv-kernel-module-spi-tegra210-quad-6.6.111-yocto-standard-1", "checksums": [{"algorithm": "SHA1", "checksumValue": "9cd52a85de15af08de8178b0fd603e2c8f52b5a8"}, {"algorithm": "SHA256", "checksumValue": "fb9bdc90486f00d8b66c5e632616d803405995d15081fd217914b55599688a90"}], "copyrightText": "NOASSERTION", "fileName": "usr/lib/modules/6.6.111-yocto-standard/updates/drivers/spi/spi-tegra210-quad.ko", "fileTypes": ["BINARY"], "licenseConcluded": "NOASSERTION", "licenseInfoInFiles": ["NOASSERTION"]}], "name": "nv-kernel-module-spi-tegra210-quad-6.6.111-yocto-standard", "packages": [{"SPDXID": "SPDXRef-Package-nv-kernel-module-spi-tegra210-quad-6.6.111-yocto-standard", "copyrightText": "NOASSERTION", "downloadLocation":
...

[madisongh]

I tried it again to be sure, but as I said before, I do not get that error even when adding kernel-modules to my builds. I use our tegra-demo-distro setup for those, so perhaps there is something else in your layer setup or build configuration that is triggering the problem?