On 30 April 2015 at 17:04, Rodrigo Santos rosantos@student.dei.uc.pt wrote:
Hello,
I am working on a Pandaboard ES and I can boot Android with the following release: http://releases.linaro.org/14.02/android/panda
However, I need some components from a newer version of the kernel. I found a version[1] which has everything that I need. However, I cannot boot it properly just by using the uImage that I generated from that kernel. You can see the log here: https://gist.github.com/rlvrs/846aec4730a28674557d As it is possible to see, the problem occurs on the init process.
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.
There could be a number of things which might have gone wrong in your setup. To start with, I'm pretty sure the boot process has failed to start SurfaceFlinger service. It has a strict dependency on hardware graphics binaries which only work with 3.2 kernel of Pandaboard.
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.
Let us know if you run into any issues while trying out software rendering.
Regards, Amit Pundir
I am using the same ramdisk from the working release. If it is that the problem, can you tell me a way to generate a compatible ramdisk image (rootfs).
[1] https://git.linaro.org/?p=kernel/linux-linaro-stable.git%3Ba=log%3Bh=refs/he...
Thanks in advance, Rodrigo Santos
linaro-android mailing list linaro-android@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-android