Hello !

First of all, I want to thank you for your response.

That error log did not help. For future reference, if you ever run
into "init: untracked pid XXXX exited" then always share "logcat -d"
output.

I would like to insert that, but I got no output from the logcat. Actually,
adb detects no devices while booting.
Meanwhile, I changed the .config to be more faithful with respect to
the .config of the linaro release. I compiled some modules, but it looks like
it does not recognize their symbols.

https://gist.github.com/rlvrs/26383f27ce6b5242046f

Another thing that concerns me is the line 69:
fs_mgr: Cannot open file /fstab.genericomap4(flatteneddevicetre
I do not have that file. Instead, I have "fstab.omap4pandaboard". However,
I cannot see where is it getting that file name.

If you don't care about hardware graphics acceleration then you can
fall back to software graphics binaries but for that you need to build
your own set of rootfs images if I'm not wrong.
1) Just do a quick check and see if you can find libGLES_android.so in
/system/lib/egl of your Pandaboard rootfs. If you can't then there is
no way out and you have to build libGLES_android package.
2) Once you have libGLES_android.so then set "ro.kernel.qemu" and
"ro.kernel.qemu.gles" properties to let SurfaceFlinger fallback to
software rendering at runtime.

I just want to boot that kernel, but I want that on the pandaboard. I am no
expert on this subject, but it sounds that "ro.kernel.qemu" and
"ro.kernel.qemu.gles" properties are meant for QEMU. In that case, I
do not understand what you mean. So, if you can explain this better
it would be great.

BTW: I have libGLES_android.so in /system/lib/egl

Regards,
Rodrigo Santos