Lazyweb, anyone know good tricks for discovering the kernel .config used on a device (old dev board) where /proc/config.gz was omitted and source was probably published but it's not clear where the relevant version is?
Conversation
Replying to
It's possible that CONFIG_IKCONFIG=y is enabled without CONFIG_IKCONFIG_PROC=y in which case you could use github.com/torvalds/linux. I don't really see a way of accurately figuring it out from the kernel itself, although if they have a standard toolchain you could compare builds.
2
2
Replying to
You should check /proc/version since scripts/setlocalversion sets the version based on git describe. It might have a commit hash to help with finding the correct version of the sources and hopefully the kernel configuration. I'm used to a defconfig in sources but it isn't always.
1
It also has the compiler version and you can potentially figure out the toolchain and build environment they used from that. I always try to reproduce the build and compare it because I don't want to be missing anything like a switch set in the environment rather than defconfig.
1
One issue that I encountered recently is that the 32-bit ARM vdso wasn't being built because of a weird bug in the standard build system requiring an extra variable to be set in some build environments, which is not supposed to be necessary. I think it's still buggy upstream too.
Replying to
I think my issue is that it's just not accepting the kernel command line from u-boot, but I'm not sure what options are affecting this. CONFIG_ATAGS was missing and I added it but still no output. Any ideas?
1
Looks like that's long-deprecated stuff and u-boot is supposed to be patching the command line into the DTB. Not sure why that's not getting seen or if that's even the problem now.. :(
1
Show replies