menuconfig not working

[MegaArman]

What happened?

Can't build armbian with a custom kernel.

In menuconfig if I go to load a .config file, does it actually read this file when exiting menuconfig and compiling?

For example, I deselected module loading and networking but I still see a lot being compiled like this

How to reproduce?

run compile.sh with no options,
when menuconfig comes up:

load -> full path to existing .config

confirm in the menu that it is using your .config

exit from menuconfig (compiling the kernel starts automatically)

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

ubuntu 22 LTS

Are you building on Windows WSL2?

• Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Jira ticket: AR-2123

[MegaArman]

This time I replaced the config/kernel/linux-meson64-current.config (chosen for the board I'm on - Le Potato) with my existing .config file and it actually seems to load it and is compiling as expected.

This looks to be a temporary workaround

EDIT: got error https://paste.armbian.com/okayaxijuw

[MegaArman]

trying to just use menuconfig to deselect some options then exit results in those options being ignored as well

[lanefu]

./compile BOARD=<boardname> BRANCH=current kernel-configure

[MegaArman]

Is this actually fixed or is that work around the only option for the time being? I'm unable to test this week .

Just to be clear, I'm talking about the kernel ncurses menu like this

^ when loading a config file there it gets ignored upon exiting and automatically starts compiling. This is particularly problematic because you may not realize a driver you didn't want was built until late in the build process (for example)

[EvilOlaf]

KERNEL_CONFIGURE is deprecated. Maybe it got broken in the meantime.
Also you are not supposed to do edits except from userpatches directory unless you plan to do patching.

The correct/modern/more developer friendly way to do it is

1. use kernel-config to modify the kernel configuration as needed.
2. Once done copy the config from output/ directory to userpatches/.
3. Use kernel build argument to use this config to create a kernel package or do not use an argument at all to build a full image.

Full example for an Orangepi One:

./compile.sh BOARD=orangepione BRANCH=current kernel-config
# Now configure and simply save as `.config
cp output/config/linux-sunxi-current.config userpatches/
./compile.sh BOARD=orangepione BRANCH=current kernel

Since you have a config already you can skip this part and directly copy the file to userpatches.,

[EvilOlaf]

@MegaArman I made a mistake with the path in userpatches which I corrected above. tl;dr: The config simply needs to be copied to userpatches. No sub-folders.