Re: [android-building] panda board sgx libs mismatch

[Jean-Baptiste Queru]

You need an exact match between the kernel and the user-space graphics
libraries. Those match in the master branch, but nowhere else.

JBQ

On Fri, Jul 27, 2012 at 3:05 AM, yogi <speak...@gmail.com> wrote:
> Hi,
>
> We are porting kernel version 3.0.8 + Android ICS filesystem on to Omap4
> (panda board) we were able to get the kernel and filesystem up.
>
> But after the kernel boots it continuously displays incompatible SGX libs
>
> Logs for reference
>
> [ 67.132659] PVR_K: (FAIL) SGXInit: Incompatible driver DDK revision
> (785978)/device DDK revision (550175).
>
> [ 67.143829] PVR_K:(Error): PVRSRVFinaliseSystem: Failed
> PVRSRVDevInitCompatCheck call (device index: 0) [456,
> drivers/gpu/pvr/pvrsrv.c]
>
> [ 67.157318] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.
> Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
>
> [ 67.210266] android_work: sent uevent USB_STATE=CONNECTED
>
> [ 67.217620] android_usb gadget: high speed config #1: android
>
> [ 67.224426] android_work: sent uevent USB_STATE=CONFIGURED
>
> [ 68.187347] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.
> Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
>
> [ 68.204742] init: untracked pid 86 exited
>
> [ 68.971649] init: untracked pid 82 exited
>
> [ 68.986999] init: untracked pid 88 exited
>
> [ 72.097076] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.
> Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
>
> [ 72.718597] init: untracked pid 117 exited
>
> [ 72.724609] init: untracked pid 118 exited
>
> [ 76.834167] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.
> Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
>
> [ 77.449340] init: untracked pid 135 exited
>
> [ 77.454101] init: untracked pid 136 exited
>
> [ 81.571258] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.
> Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]
>
> Let me know
> 1) Are we using the right FS
> 2) Does the libs downloaded from the url
> "https://developers.google.com/android/nexus/drivers#panda" works for panda
> board
>
> Provide me few pointers to suggest where it is going wrong
>
> Regards
> Yogesh
>
>
>
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en



--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[Jean-Baptiste Queru]

Use the master branch, it's the only one that works on PandaBoard.

JBQ

On Wednesday, December 12, 2012, rams <ramesh...@gmail.com> wrote:
> Hi,
> I have the same prob like sgx mismatch.
>
> I have downloaded the android-4.0.4_r2.1 source code and built the code. To flash on the board  I followed steps from device/ti/panda/README file.
> I have copied vendor specific libraries and got the following error.
>
> PVR: SysFinalise: Version string: SGX revision = 1.2.0
> [    5.069854] PVR_K: (FAIL) SGXInit: Incompatible driver DDK revision (279068)/device DDK revision (550175).
>     5.069854] PVR_K:(Error): PVRSRVFinaliseSystem: Failed PVRSRVDevInitCompatCheck call (device index: 0) [451, drivers/gpu/pvr/pvrsrv.c]
> [    5.093811] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.  Driver unusable. [4795, drivers/gpu/pvr/bridged_pvr_bridge.c]
> [    5.811157] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.  Driver unusable. [4795, drivers/gpu/pvr/bridged_pvr_bridge.c]
> [    5.831268] init: untracked pid 71 exited
>
> can anyone help me in solving the issue?
>
> rgds,
> rams
>
> On Tuesday, July 31, 2012 1:42:23 PM UTC+5:30, hagenp wrote:

>>
>> On Friday, 27 July 2012 12:05:27 UTC+2, yogi wrote:
>>>
>>> We are porting kernel version 3.0.8 + Android ICS filesystem on to Omap4 (panda board) we were able to get the kernel and filesystem up.
>>
>>  
>>>

>>> [   67.132659] PVR_K: (FAIL) SGXInit: Incompatible driver DDK revision (785978)/device DDK revision (550175).

>>
>>  
>>>
>>> Provide me few pointers to suggest where it is going wrong
>>

>> As you know, you can download three different graphics library packages for PandaBoard:
>>
>> PandaBoard binaries for Android 4.0.1 (ITL41D)
>>  -> contains build 1.8@279068
>>
>> PandaBoard binaries for Android 4.0.3 (IML74K)
>>  -> contains build 1.8@550175
>>
>> PandaBoard binaries for Android 4.0.4 (IMM76I to IMM76L)
>>  -> contains build 1.8@785978
>>
>> You can look up the build version of the imgtec libraries (from the top-level android build directory) with
>>  $ strings vendor/imgtec/panda/proprietary/libGLESv2*.so | grep "build"
>> [Thanks to Zoltan who posted this on 2012-jan-6 in android-building > "4.0.3-based master on PandaBoard".]
>>
>>
>> Looks like you extracted the 4.0.3 package, but the Linux kernel wants the 4.0.4 variant of the libraries.
>>
>> NB: Matching SGX build versions are still no guarantee to get graphics output on Panda. 
>>
>> Good luck!

[Jean-Baptiste Queru]

You can't. Only the master branch is supported, and it's currently
based on JB-MR1.

JBQ

On Thu, Dec 13, 2012 at 9:35 PM, rams <ramesh...@gmail.com> wrote:
> Thanks JBQ for the reply.
>
> But I want to run ICS on Panda board.
> If I'm not wrong the current master branch has JB.
>
> Then,How can I run ICS on Panda baord frm the master branch?
>
> rgds,
> Rams
>
>
> On Thursday, December 13, 2012 9:39:35 PM UTC+5:30, Jean-Baptiste Queru

[Jean-Baptiste Queru]

That's not going to work (any more), as the matching graphics
libraries aren't available any more.

JBQ

On Mon, Dec 17, 2012 at 5:13 AM, rams <ramesh...@gmail.com> wrote:
> Ok JBQ.
>
> I came across one "ics-plus-aosp" branch in repo. Shall I try my luck with
> this version to port ICS on panda.
>
> Any suggestion pls help ?I want to port ICS on PANDA.
>
> rgds,
> rams
>
>
> On Friday, December 14, 2012 10:34:46 PM UTC+5:30, Jean-Baptiste Queru

[Jean-Baptiste Queru]

Because it makes my life easier ;-)

Slightly longer explanation: ICS is very old and doesn't build on
modern versions of Ubuntu or MacOS. It's so far behind the current
master that there's no hope that changes made there would apply to the
current state. And, because there's no good versioning for the
PandaBoard libraries, there was no way to know which libraries would
work on which branch.

JBQ

On Tue, Dec 18, 2012 at 6:05 AM, hagenp <hagen....@gmail.com> wrote:
> On Monday, 17 December 2012 17:48:15 UTC+1, Jean-Baptiste Queru wrote:
>>
>> That's [=ics-plus-aosp is] not going to work (any more), as the matching

>> graphics
>> libraries aren't available any more.
>
>

> And why is that?
>
> The individual archives are only slightly larger than one one megabyte each,
> so I find it hard to believe Google ran out of server space for them ...
>
> (Sorry for the persistence, I just want to understand what's happening
> here.)

[Jean-Baptiste Queru]

I still have all the versions of the PandaBoard libraries that had
been published on the Google side. The original filenames were
meaningless, but in theory it should be possible to rename them by
creation date and re-publish them, though there won't be any good way
to match them to individual builds.

Would that help?

JBQ

On Thu, Dec 20, 2012 at 1:23 AM, hagenp <hagen....@gmail.com> wrote:
> Thanks for the explanation, Jean-Baptiste.
>
> Is there a PandaBoard build option that gives us (and our customers and
> FAEs) a chance to repeat an older build without the high risk of unavailable
> proprietary blobs?
> For our support and demos we can probably live without graphics
> acceleration.
> With manifest snapshots we can also live with branches not working for
> PandaBoard builds.
> But we can not live with builds being non-reproducible due to missing
> components.
>
> The current PandaBoard "build state" means we might have to go back to the
> "stone age" of rolling out Android build trees compressed on DVD. Maybe with
> an additional DVD with a VM for the build environment. Not good.
>
> As Linaro, too, relies on these binaries available from e.g. Google, if they
> are gone, there is not even a way to re-create an older Linaro ICS or JB
> build. Should I approach Linaro and ask them if they can store a local
> copy? And/or Imagine Technologies? Texas Instruments?
>
> What would you suggest, JBQ?

[Jean-Baptiste Queru]

The problem with using build numbers is that they confused people. As
an example, "IMM76" didn't mean "use those binaries with build IMM76",
but rather, "use those binaries with the master branch at an
indeterminate time after build IMM76 was released". Each time someone
tries to use those binaries with build IMM76, they're wasting time.

My experience is that the SGX build numbers aren't reliable enough:
binaries with non-matching numbers don't work, but that doesn't imply
that binaries with matching numbers always do.

I'll look into re-publishing the old binaries under appropriate names.

JBQ

On Fri, Dec 21, 2012 at 4:01 PM, hagenp <hagen....@gmail.com> wrote:

> On Fri, Dec 21, 2012 at 4:57 PM, Jean-Baptiste Queru wrote:
>>
>> I still have all the versions of the PandaBoard libraries that had
>> been published on the Google side. The original filenames were
>> meaningless, but in theory it should be possible to rename them by
>> creation date and re-publish them, though there won't be any good way
>> to match them to individual builds.
>

> Maybe not to the individual builds, but here is an idea:
>
> As far as I remember, the original file name contained the Android build
> name (e.g., IMM76). IMHO this should be kept.
>
> Additionally, the internal SGX DDK revision number would be helpful: then
> someone, who sees a mismatch message between kernel wrapper and library
> builds (in their logcat output), could quickly find and download the proper
> version.
>
>
>>
>> Would that help?
>
>
> Yes, this would help a lot. Then we can give people a snapshot manifest and
> a link to the correct graphic binary blob, and they will have a chance to
> sync and build themselves a working PandaBoard version again.
>
> Many thanks!
> Hagen

[Jean-Baptiste Queru]

I've re-published the previous versions of the pandaboard binaries,
tagged by date (instead of version numbers that didn't mean anything).
That should give you more flexibility in exploring what happens when
using older kernels.

JBQ

[sudharsanam narasimhan]

Hi Dhyan,

Thanks it works

Regards,

Sudharsanam.N

On Friday, 27 July 2012 15:35:27 UTC+5:30, yogi wrote:

Hi,

We are porting kernel version 3.0.8 + Android ICS filesystem on to Omap4 (panda board) we were able to get the kernel and filesystem up.

But after the kernel boots it continuously displays incompatible SGX libs

Logs for reference

[   67.132659] PVR_K: (FAIL) SGXInit: Incompatible driver DDK revision (785978)/device DDK revision (550175).

[   67.143829] PVR_K:(Error): PVRSRVFinaliseSystem: Failed PVRSRVDevInitCompatCheck call (device index: 0) [456, drivers/gpu/pvr/pvrsrv.c]

[   67.157318] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.  Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]

[   67.210266] android_work: sent uevent USB_STATE=CONNECTED

[   67.217620] android_usb gadget: high speed config #1: android

[   67.224426] android_work: sent uevent USB_STATE=CONFIGURED

[   68.187347] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.  Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]

[   68.204742] init: untracked pid 86 exited

[   68.971649] init: untracked pid 82 exited

[   68.986999] init: untracked pid 88 exited

[   72.097076] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.  Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]

[   72.718597] init: untracked pid 117 exited

[   72.724609] init: untracked pid 118 exited

[   76.834167] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.  Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]

[   77.449340] init: untracked pid 135 exited

[   77.454101] init: untracked pid 136 exited

[   81.571258] PVR_K:(Error): BridgedDispatchKM: Initialisation failed.  Driver unusable. [4812, drivers/gpu/pvr/bridged_pvr_bridge.c]

Let me know
1) Are we using the right FS
2) Does the libs downloaded from the url "https://developers.google.com/android/nexus/drivers#panda" works for panda board

Provide me few pointers to suggest where it is going wrong

Regards
Yogesh

[sudharsanam narasimhan]

Hi Dhyan,

I have a quick question.

ICS-plus-aosp branch comes with prebuilt kernel version 3.0.8.

I wanted to replace this kernel with one of my newly build kernel version 3.0.31 and to boot Panda board. I followed the steps mentioned it shows the same pvr driver mismatch error.

Do you have any idea how to solve this issue??

{{{

[57019.603271] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not comp]

[57019.773498] init: untracked pid 9844 exited

[57019.866119] init: untracked pid 9819 exited

[57019.871490] init: untracked pid 9822 exited

[57024.594299] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not comp]

[57024.684051] init: untracked pid 9842 exited

[57024.909820] init: untracked pid 9853 exited

[57032.375427] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not comp

}}}

Thanks and Regards,

Sudharsanam.N

On Thursday, 16 May 2013 14:45:29 UTC+5:30, Dhyan wrote:

Hi Sudarsan,

You can use ics-plus-aosp branch, It wil work fine ,Please follow below steps

#mkdir ics-plus-aosp
#cd ics-plus-aosp
#repo init -u https://android.googlesource.com/platform/manifest
#repo init -u https://android.googlesource.com/platform/manifest -b ics-plus-aosp
# repo sync
# wget -p -nd https://dl.google.com/dl/android/aosp/imgtec-panda-20120430-67545da7.tgz
# tar -xzvf imgtec-panda-20120430-67545da7.tgz
# ./extract-imgtec-panda.sh
# source build/envsetup.sh
#lunch full_panda-userdebug
# make

With no SD card inserted, plug USB first, then the power cord,#   and load fastboot over USB:
# device/ti/panda/usbboot device/ti/panda/bootloader.bin
# source build/envsetup.sh
#lunch full_panda-userdebug
# make fastboot
# fastboot oem format
# fastboot erase cache
# fastboot flash userdata
# fastboot flashall

Regards
Dhyan

[Jean-Baptiste Queru]

You need to use the exact same kernel-side GPU code as in the official kernel, so that the user-side GPU libraries continue to work.

JBQ

--

--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
 

---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jean-Marc GRIMAUD]

Hello,

I would like to do the same exercise with android JB 4,1

I tried the same instruction than bellow, but with branch android-4.1.2_r1.

(I use exactly the same imgtec patch).

But it does not work, I have errors like:

 init: untracked pid 22381 exited

Does anybody could tell me if there is a specific branch on JB4.1 that can work on pandaboard ?

If not, would it be possible to know if I can start from this branch ( android-4.1.2_r1), then only retrieve a few modules from master branch to make it working ? If yes, which one ?

Thanks a lot !!

[barun...@gmail.com]

Hi Dhyan,

I want to build the JBMR2 for panda board, can you please let me know the procedure please, Thank you in advance.

On Thursday, May 16, 2013 2:45:29 PM UTC+5:30, Dhyan wrote:

Hi Sudarsan,

You can use ics-plus-aosp branch, It wil work fine ,Please follow below steps

#mkdir ics-plus-aosp
#cd ics-plus-aosp
#repo init -u https://android.googlesource.com/platform/manifest
#repo init -u https://android.googlesource.com/platform/manifest -b ics-plus-aosp
# repo sync
# wget -p -nd https://dl.google.com/dl/android/aosp/imgtec-panda-20120430-67545da7.tgz
# tar -xzvf imgtec-panda-20120430-67545da7.tgz
# ./extract-imgtec-panda.sh
# source build/envsetup.sh
#lunch full_panda-userdebug
# make

With no SD card inserted, plug USB first, then the power cord,#   and load fastboot over USB:
# device/ti/panda/usbboot device/ti/panda/bootloader.bin

# source build/envsetup.sh
#lunch full_panda-userdebug