For some reason when I try 'bitbake -c menuconfig virtual/kernel' it always fails.  It gets to the 'do_menuconfig()' step and fails with '256'.

Simply modifying the .config file as suggested below (and copying it to the recipe's folder as $OVEROTOP/ also causes it to fail when I 'bitbake virtual/kernel'.  It fails at do_compile() with an error 256.

I'll take a look at board-overo.c and see what that tells me.

On Tue, Nov 22, 2011 at 5:54 PM, Scott Ellis <> wrote:
The method I use is here

If you are editing the config manually, set the options this way


# CONFIG_LEDS_GPIO is not set

The Gumstix kernels are generic. The buttons and leds configured in the
default kernels don't even exist on most of their boards. Same with all
the LCD display setup and the second NIC configuration.  It's unlikely
you want any of that.

It's not hard to go through the board-overo.c file and understand what
it does.


On Tue, 2011-11-22 at 13:34 -0500, wrote:
> How do I modify the kernel config?  Is there a .config file somewhere
> that I just turn those two options to "=N"?
> Also, is this specific to one of the carrier boards (summit, tobi,
> etc) or it would also apply to a custom carrier board developed in
> house?

All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
gumstix-users mailing list