• Locked Locked
  • Replies 2 replies
  • Subscribers 136 subscribers
  • Views 6744 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Device driver API mismatch - LibEGL

Ariel Hernandez
Note: This was originally posted on 19th March 2013 at http://forums.arm.com

Hellor there!! How are you? This is my first post here!!
I have a BIG problem a few days ago! I have a ODROID-PC with a Exynos 4210 (Cortex A9 - Mali400) and I compiled Android ICS from AOSP repository and everything was fine ... or really not! Haha.. I don't have video signal and I think that the problem is with the OpenGL ES!
So ...  the Android logcat get this,

D/libEGL  ( 1252): loaded /system/lib/egl/libEGL_mali.so
D/libEGL  ( 1252): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL  ( 1252): loaded /system/lib/egl/libGLESv2_mali.so
E/        ( 1252): Device driver API mismatch
E/        ( 1252): Device driver API version: 9
E/        ( 1252): User space API version: 10
D/        ( 1252): mali: REVISION=Linux-r2p4-02rel0 BUILD_DATE=Mon May 14 20:33:23 KST 2012
W/libEGL  ( 1252): 0: eglInitialize(0x1) failed (EGL_BAD_ALLOC)
E/libEGL  ( 1252): initialize:290 error 3001 (EGL_NOT_INITIALIZED)
E/libEGL  ( 1252): validate_display:190 error 3001 (EGL_NOT_INITIALIZED)
E/libEGL  ( 1252): validate_display:190 error 3001 (EGL_NOT_INITIALIZED)
F/libc    ( 1252): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I/DEBUG   ( 1123): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   ( 1123): Build fingerprint: 'Android/odroidpc/odroidpc:4.0.4/IMM76L/eng.ahestevenz.20130312.171353:eng/test-keys'

If I have understood well .. the problem is: Device driver API mismatch, but I don't know how to resolve this!


If somebody has any idea why I'm getting this I would really appreciate your help!

Thanks in advance!

Ariel Hernández
Parents
  • Note: This was originally posted on 20th March 2013 at http://forums.arm.com

    Hi Ariel,

    It seems that the Kernel driver does not match the version of the userspace binaries that you are using (v of lib*_mali.so != v of mali.ko). Did you obtain the userspace binaries as part of a proprietary bundle? If so the userspace is fixed, but it should be possible to swap out the kernel side for the correct version, available from malideveloper.com.

    Thanks,
    Chris
Reply
  • Note: This was originally posted on 20th March 2013 at http://forums.arm.com

    Hi Ariel,

    It seems that the Kernel driver does not match the version of the userspace binaries that you are using (v of lib*_mali.so != v of mali.ko). Did you obtain the userspace binaries as part of a proprietary bundle? If so the userspace is fixed, but it should be possible to swap out the kernel side for the correct version, available from malideveloper.com.

    Thanks,
    Chris
Children
No data