I've compiled it without any errors and applied the necessary patches too. I used cm12.0's boot.img so that I can get logcat (can't get logcat from cm12.1's boot.img). But whenever I try to boot cm12.1, it stucks at bootlogo and never goes ahead. I can get logs from adb but can't figure out, can you help me fix this problem while booting? Here's the logcat: https://paste.ee/p/A5GHK
I contacted a developer and he said that the problem is in this line:
Code:
[ 01-27 10:33:43.634 116: 116 E/HAL ]
load: module=/vendor/lib/hw/gralloc.mt6589.so
dlopen failed: library "libcorkscrew.so" not found
But I'm not sure on how to fix it, I applied a patch regarding libcorkscrew but then too can't fix that. Help me please. Thank you
Related
Anyone know anything about this line i keep seeing in my kernel boot up logs?
kgsl_ioctl_rb_issueibcmds| invalid cmd buffer ibaddr 000171b0 sizedwords 1
It seems that the boot process encounters this and starts re-processing from the htc-acoustic peice onwards, until the above is encountered. Stuck in a loop.
Any help is much appreciated. Thanks
Anyone know anything about this line i keep seeing in my kernel boot up logs? This is an ICS kernel for the mecha
kgsl_ioctl_rb_issueibcmds| invalid cmd buffer ibaddr 000171b0 sizedwords 1
It seems that the boot process encounters this and starts re-processing from the htc-acoustic peice onwards, until the above is encountered. Stuck in a loop.
Any help is much appreciated. Thanks
Please give me some hints. What I'm trying to accomplish is to port CM10 and 10.1 and kernel 3.4 to LG E400. E400 has CM9 but the kernel is old - 2.6. I'm using kernel 3.4 for LG L3 II which has the same hardware.
I've compiled CM 10 but when I boot it with 3.4 kernel, I have a blank screen. I looked at dmesg and logcat, but I didn't figure what went wrong. I tried to boot CM 10 with 2.6 kernel but I have the same issue. I even try to test the 3.4 kernel with CM9 and it's the same story.
Can you give me some tips, how to figure out what went wrong?
dmesg for CM 10 using kernel 3.4: http://pastebin.com/M4R5tixn
logcat for CM 10 using kernel 3.4: http://pastebin.com/qRKttGTY
dmesg for CM 9 using kernel 3.4: http://pastebin.com/nppGkKB0
Thanks.
Here are some logcats for CM 10, kernel 3.4:
a. with blobs extracted from phone running CM9: http://pastebin.com/NKeYgEBw
b. with some blobs from LG L5 and adreno drivers for JB 4.1 from qualcomm site: http://pastebin.com/6D4VQDRa
c. with software renderer: http://pastebin.com/rtfiZi5s
d. with some blobs from LG L5 and latest adreno drivers from qualcomm site: http://pastebin.com/bcC6KCwj
In b. it seems adreno libs are loaded, surfaceflinger is running, so why I can't see android boot logo? All I'm able to see is a white background.
Using software renderer I see nothing but a blank display too.
dmesg says: init: could not import file /system/etc/init.local.rc, might this be relevant? Init.rc and init.board.rc are from CM 9.
edit1:
Since it didn't boot after I flashed the rom, I used ramdisk from CM9 and kernel 3.4 packing that into a boot.img and using that to boot.
Maybe using the ramdisk from CM9 with CM10 is why I am having problems?
edit2:
It seems zygote is crashing and restarting. Probably because of faulty init.rc.
edit3:
I fixed zygote crashing, now I have this:
Code:
E/memalloc( 128): /dev/pmem: Failed to open pmem device: No such file or directory
E/memalloc( 128): /dev/pmem: failed to initialize pmem area
E/gralloc ( 128): gralloc failed err=No such file or directory
It's weird there's no /dev/pmem because I've compiled the kernel with CONFIG_ANDROID_PMEM=y.
edit 4:
in board-xxx.c there's this comment:
Code:
/*LGE_CHANGE_S[[email protected]]20121102:
*Migrating QCT patch to remove pmem and fmem support*/
Also, there's no other reference to pmem in the file. It seems LG removed support for pmem. How do I get around this? gralloc needs /dev/pmem and there's no /dev/pmem because LG patched the kernel...
Code:
E/memalloc( 130): /dev/pmem: Failed to open pmem device: No such file or directory
E/memalloc( 130): /dev/pmem: failed to initialize pmem area
E/gralloc ( 130): gralloc failed err=No such file or directory
W/GraphicBufferAllocator( 130): alloc(240, 320, 2, 00000b03, 0 ...) failed -2 (No such file or directory)
E/SurfaceFlinger( 130): GraphicBufferAlloc::createGraphicBuffer(w=240, h=320) failed (No such file or directory), handle=0x0
E/BufferQueue( 130): [<pid_249>] dequeueBuffer: SurfaceComposer::createGraphicBuffer failed
Should I try to patch board-xxx.c to use pmem or should I try to compile CM10 with ION support? If so, how do I enable ION support before compiling CM10? adreno drivers support ION?
It's enough to add TARGET_USES_ION := true to BoardConfigCommon.mk ?
I think hardware/qcom/display/* might use only pmem in CM10. For CM10.1 I had to replace hardware/qcom/display with the one in CM10 since I had tons of compile errors...
I really wish i knw watever u r saying above... i would lke to help. By d way thnx for such great work. I knw u ll solve out eventually.
Sent from my LG-E400 using xda app-developers app
Your kernel is the problem.
Hi,
I'm new on this forum, so I canno't post my thread on the right forum/thread. (10 posts needed for this)
So I'm asking here.
I have installed yesterday the ROM Enigma for Xperia U with the Kernel Nemesis 6.2.
All works well on the phone, except the logcat.
When I'm trying to check the log on the phone with Eclipse DDMS and Logcat plugins, I got this error :
Code:
Unable to open log device '/dev/log/main': No such file or directory
- I have activate the log in the Dev Menu on the phone and reboot the phone, don't work.
- I've check if an init.d script remove this file, but not.
- I've try to launch logcat by hand with adb shell, but no luck, same message.
And finally, I've tried to load kernel module logger.ko with insmod. But I got this message
Code:
[email protected]:/lib/modules # insmod logger.ko
insmod: can't insert 'logger.ko': invalid module format
[email protected]:/lib/modules # dmesg
[...]
<4>[ 1841.764984] logger: disagrees about version of symbol module_layout
If I try to insert the module from the directory /system/lib/module/, I got the same result.
So, someone know how to activate the logcat system on the phone ?
Thanks in advance,
Cheers.
Denia
Have you solved it?
Have you solved it?
Deniadan said:
Hi,
I'm new on this forum, so I canno't post my thread on the right forum/thread. (10 posts needed for this)
So I'm asking here.
I have installed yesterday the ROM Enigma for Xperia U with the Kernel Nemesis 6.2.
All works well on the phone, except the logcat.
When I'm trying to check the log on the phone with Eclipse DDMS and Logcat plugins, I got this error :
Code:
Unable to open log device '/dev/log/main': No such file or directory
- I have activate the log in the Dev Menu on the phone and reboot the phone, don't work.
- I've check if an init.d script remove this file, but not.
- I've try to launch logcat by hand with adb shell, but no luck, same message.
And finally, I've tried to load kernel module logger.ko with insmod. But I got this message
Code:
[email protected]:/lib/modules # insmod logger.ko
insmod: can't insert 'logger.ko': invalid module format
[email protected]:/lib/modules # dmesg
[...]
<4>[ 1841.764984] logger: disagrees about version of symbol module_layout
If I try to insert the module from the directory /system/lib/module/, I got the same result.
So, someone know how to activate the logcat system on the phone ?
Thanks in advance,
Cheers.
Denia
Click to expand...
Click to collapse
Hi everyone,
I have recently been trying to port Ubuntu Touch to our beloved surnia.
I'm using the phablet-5.1 tree with AOSP-5.1 device, vendor, kernel and other repositories.
I managed to finish the build with the kernel config adapted to work with Ubuntu. (using jamino's phablet-porting-scripts (on github) and patching some files about uid/gid errors). But this isn't the problem, the default defconfig causes the same problems.
I can confirm my kernel/e3 recovery both work and can mount partitions etc, but only when I'm using the
Code:
fastboot boot recovery.img
command AND my custom boot.img isn't flashed to the device.
When trying to boot the recovery directly from the phone I get a
Code:
Error: Failed to load kernel!
error message in the bootloader log.
If my boot.img is flashed to the phone, whatever file I try to load with
Code:
fastboot boot
, I get an error from my computer :
Code:
booting...
FAILED (remote failure)
but no error from the phone
I had to replace the prebuilt gcc toolchains in the android source tree with my system's ones, could it cause the problem?
I'm quite new to android development and all so please don't blame me if the fix is obvious.
Thanks in advance