Build failure

[MrVan]

HI

This repo contains proprietary code?
My command: moulin prod-devel-rcar-virtio.yaml --MACHINE salvator-xs-m3-2x4g --ENABLE_DOMU yes --ENABLE_MM yes

[4/10] git clone
FAILED: yocto/proprietary /home/Freenix/work/sw-stash/xen/xentroops/meta-xt-prod-devel-rcar/.stamps/yocto--yocto-proprietary--ssh---git@gitpct.epam.com-epmd--aepr-img--proprietary--clone
GIT_SSH_COMMAND='ssh -o BatchMode=yes' GIT_TERMINAL_PROMPT=0 git clone -q ssh://[email protected]/epmd-aepr/img-proprietary yocto/proprietary && touch yocto/proprietary '/home/Freenix/work/sw-stash/xen/xentroops/meta-xt-prod-devel-rcar/.stamps/yocto--yocto-proprietary--ssh---git@gitpct.epam.com-epmd--aepr-img--proprietary--clone'
kex_exchange_identification: read: Connection timed out

Thanks,
Peng.

[lorc]

Hi @MrVan,

Yes, this repo contains proprietary code. Currently our build works only with GPU acceleration enabled. Problem is that we can't share the source code for the GPU driver. Moreover, we even can't share the prebuilt binaries. You can try asking Renesas to provide you prebuilt GPU driver binaries with virtualization support if you want, but this might take some time.

Or you can wait a bit, because right now @rshym is working on build with graphics disabled. I believe he will update you with estimations.

I'll leave this PR open if you don't mind, so we can track the progress.

[rshym]

Hi @MrVan,

We are working on the issue that you met. We already have not merged solution, that isolates proprietary graphic drivers.
Now we are working on the integration of Renesas' Gen4 into meta-xt-prod-devel, without any proprietary drivers.
After that we will integrate support for a 'console-only' solution for Gen3.
Only after that product will be available for the open-source community.
For now, the estimation is 1-1.5 months.

[MrVan]

Thanks for updating me the information. Ruslan Shymkevych ***@***.***> 于2024年1月5日周五 17:53写道：

…

Hi @MrVan <https://github.com/MrVan>, We are working on the issue that you met. We already have not merged solution, that isolates proprietary graphic drivers. Now we are working on the integration of Renesas' Gen4 into meta-xt-prod-devel, without any proprietary drivers. After that we will integrate support for a 'console-only' solution for Gen3. Only after that product will be available for the open-source community. For now, the estimation is 1-1.5 months. — Reply to this email directly, view it on GitHub <#110 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAIY2BBX257EHIWVDS6ZSDYM7ERHAVCNFSM6AAAAABBIXILA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZYGQYDAOJRGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

--

[heisaTeo]

hi, is the issue somehow resolved? or any workaround?
I ran into similar issue with the command: moulin prod-devel-rcar.yaml --MACHINE h3ulcb-4x2g --ENABLE_DOMU yes --ENABLE_MM yes --GRAPHICS binaries --ENABLE_ANDROID yes

[rshym]

@heisaTeo
This issue is not resolved yet because we are considering running the product without proprietary GFX drivers as a low-priority task. The corresponding PR, #127, is still "work in progress."

But considering that you are trying to build with the --ENABLE_ANDROID yes option, the PR mentioned can't help you. Android can't be built without proprietary graphics, and it is impossible to build the product with Android as a guest without 3D graphics.
To obtain proprietary graphics, you need to contact Renesas and get approval. Only then will you be able to build the product with Android as a guest.

[heisaTeo]

@rshym many thanks for the info!
for the Renesas proprietary 3D graphics driver, I need the Android version of it, right?

[rshym]

@heisaTeo
Right. You need prebuilt graphic binaries for the Android and with the support of virtualization,
Then you should use the few steps mentioned in the https://github.com/xen-troops/meta-xt-prod-devel-rcar?tab=readme-ov-file#building-with-prebuilts-android-graphics

[arminn]

@heisaTeo we have 2 different androids managed by different yaml files. The one you are tried ( prod-devel-rcar.yaml) will definitely need separate proprietary graphics for Android. But other, prod-devel-rcar-virtio.yaml - requires proprietary graphics only in DomD , but not in Android. That package could be downloaded from renesas site.

[heisaTeo]

@rshym thanks, I will contact Renesas for getting the drivers

@arminn thanks for the hint, that is the way I am trying out now till I get answers from Renesas. In this case (prod-devel-rcar-virtio.yaml), which distribution of the driver do I need? the "Evaluation Software Package for Linux for Yocto"? is there a specific recommendation for version?

[arminn]

@heisaTeo

I suppose you are building for Starterkit or Starterkit+KFp:

Download evaluation version of proprietary graphics and multimedia drivers from Renesas:

https://www.renesas.com/us/en/application/automotive/r-car-h3-m3-h2-m2-e2-documents-software

Download two files:

R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20220121.zip

R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20220121.zip

Use GSX_KM_H3.tar.bz2 form R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20220121.zip

Use INF_r8a77951_linux_gsx_binaries_gles.tar.bz2 from R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20220121.zip

Rename it to r8a77951_linux_gsx_binaries_gles.tar.bz2.

Place these two files like described in: https://github.com/xen-troops/meta-xt-prod-devel-rcar?tab=readme-ov-file#building-with-prebuilt-graphics-for-domddomu

[heisaTeo]

@arminn thanks a lot for the details
I am building for Starter kit Premier

[arminn]

@heisaTeo you might need to update docker image(please rebuild it from the master or v0.2.1 tag) , since we found one regression in case of Android build.