Hi,
On 5 May 2015 at 11:49, Rodrigo Santos rodriisantos@gmail.com wrote:
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.
Why didn't you capture the log from serial console instead?
Anyway you might not able to use adb with Android USB gadget driver as such with 3.14 kernel. If you can't live without adb then either use adb over ethernet https://wiki.linaro.org/Platform/Android/SetupAdbOverTcp Or adb over USB functionfs gadget https://plus.google.com/111524780435806926688/posts/AaEccFjKNHE
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.
Looks like those symbols are not exported in 3.14. You have to export those variables for your module to be able to find them.
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.
Add "androidboot.hardware=omap4pandaboard" in your bootargs to fix this problem.
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.
- 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.
Yes those properties are meant for Qemu because Qemu doesn't have hardware graphics support either. But you can use those properties for a generic build/platform as well.
BTW: I have libGLES_android.so in /system/lib/egl
So now that you have libGLES_android. You have to set these 2 properties "ro.kernel.qemu" and "ro.kernel.qemu.gles" to fallback to software rendering at runtime. Unpack uInitrd and add the following two lines in init.omap4pandaboard.rc (under "on boot" section) and then repackage it.
setprop ro.kernel.qemu 1 setprop ro.kernel.qemu.gles 0
Instructions to unpack and repack initrd/uInitrd is available here https://wiki.linaro.org/MichaelHope/Sandbox/DebuggingOnInitrd
Also depending on your Android rootfs version, make sure that your /system/lib/egl/egl.cfg only has "0 0 android" entry.
Regards, Amit Pundir
Regards, Rodrigo Santos
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