| Summary: | Yocto does not update configuration with .cfg file | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Yocto Project Subprojects] Kernel | Reporter: | xerofoify | ||||||||
| Component: | kernel-configuration | Assignee: | Bruce Ashfield <bruce.ashfield> | ||||||||
| Status: | RESOLVED NOTABUG | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | Undecided | CC: | yp.kernel.watcher, yp.watcher | ||||||||
| Version: | unspecified | ||||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | x86 | ||||||||||
| OS: | Multiple | ||||||||||
| Whiteboard: | |||||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||||
| Verified: | Documentation change: | Don't know | |||||||||
| Attachments: |
|
||||||||||
This works just fine here. In fact, if it didn't work, none of the reference kernels would be building and booting at all, meta-virtualization, etc, wouldn't be able to modify configurations and any number of core elements would be broken. So unfortunately, yes. We'll need everything to reproduce this. Your machine, any local.conf settings, your layers, your kernel bbappend. Something that can just be added to a build and reproduce the issue. I tried 5 or 6 different layer combos and changed settings, and they all worked here. (Note: that if some other setting is selecting SMP, you can't turn it off in a fragment, so that's why we need the complete set of layers, machine, kernel recipe). (In reply to comment #1) > This works just fine here. In fact, if it didn't work, none of the reference > kernels would be building and booting at all, meta-virtualization, etc, > wouldn't be able to modify configurations and any number of core elements > would be broken. > > So unfortunately, yes. We'll need everything to reproduce this. Your > machine, any local.conf settings, your layers, your kernel bbappend. > Something that can just be added to a build and reproduce the issue. > > I tried 5 or 6 different layer combos and changed settings, and they all > worked here. > > (Note: that if some other setting is selecting SMP, you can't turn it off in > a fragment, so that's why we need the complete set of layers, machine, > kernel recipe). OK its running on qemu with this command: runqemu qemux86 qemuparams="-smp 2" It's just the default yocto-poky on Ubuntu 18.04. The only things were I added a layer with: bitbake-layers create-layer examples bitbake-layers add-layer examples For the bbappend and local.conf those are attached as well. Created attachment 4477 [details]
BBappend file for yocto kernel
Created attachment 4478 [details]
local.conf
Sorry the commands I ran were: bitbake-layers create-layer ypbook bitbake-layers add-layer ypbook cd ypbook/ mkdir -p recipes-kernel/linux mkdir -p recipes-kernel/linux/files cd recipes-kernel/ Those other commands were for another layer. I'll take this for a spin and see if I can reproduce the issue, or offer an explanation why things are working as expected. I'll be testing this on master, so if this is incorrect, update the bug with your branch details. Is that really the bbappend you are using ? If so, you have a typo and are not adding your fragment to the SRC_URI, you have "SRC_URL". I can confirm with that typo fixed, I can definitely override the SMP setting build2 [/home/bruc...0a3acff-r0]> grep CONFIG_SMP linux-qemux86-standard-build/.config # CONFIG_SMP is not set |
Created attachment 4476 [details] Kernel Configuration file I was trying to update my kernel compile and build with: bitbake -C fetch virtual/kernel to have no smp. It shows two cores when running in qemu when through I just updated my layer with the attached .cfg file as run with diffconfig after disabling smp in processor settings. This is is on the latest thud release branch. If you need my bbappend file let me know as it's not attached due it to being the standard example from the Yocto kernel development manual.