TorizonCore 6.1 cannot render anymore 3D content on Verdin iMX8M-Mini

Hi @jeremias.tx
thanks to your email I discovered two interesting things:

  1. not all the bookworm-based containers have been already released. I hope for the booworm chromium soon

  2. The page to download binaries has some problmes with the links: today you can see it sould point to build 210, but if you link on the Verdin iMX8M Mini, the link points to build 202.
    This explains why I think I downloaded build 209 (yesterday), but I got the files for build 202 (which has weston-vivante:2).
    Some of the links point to the right build 210, some to 209, some others to 202.
    On the other side, it seems that the links for TorizonCore (without Evaluation Containers) point to build 210 for all the devices.

Can you verify, please?
And can you share a roadmap for the release of chromium:3 container (bookworm-based)?

Thanks

Not all of our nightly builds succeed. So when we do build 210 for example maybe some devices fail to build or have other issues, in these cases those builds are not published. When that happens the links just point to the latest successful build for those modules.

And can you share a roadmap for the release of chromium:3 container (bookworm-based)?

I do not have any definite roadmap or timeline I can share at the moment. All I can say is that the bookworm chromium container is in progress and is one of the last containers that need to be updated to bookworm.

Best Regards,
Jeremias

2 Likes

Hi @jeremias.tx ,
after a deeper investigation I have some other doubts on what happens to the download links.
As I wrote, yesterday the link for iMX8M-Mini pointed to build 202, and you gave a possible explanation.

But today, the same link points to build 26 of last August.
I cannot see the reason, actually.

Moreover, the link on the left part of the page 6.2.0-devel-20230315+build.210.container opens a page with toradex artifacts, and it seems that the build 210 is there, so it didn’t fail.
Do you mean it has other issues?

That is odd, perhaps there’s something wrong with the automation that is publishing these links to our developer site. Let me check with the responsible team and see if they know what’s going on with this.

Best Regards,
Jeremias

I confirm that there is a mess with the links.
Now the link for iMX8M-Plus points to “File not found”

I informed our team about this and they’re still looking into it.

Best Regards,
Jeremias

Hi @vix !

Could you please check again the download links on your side?

Best regards,

Now they’re ok.
Did you found what happened?

Hi @vix !

I am not part of the team that deals with it.

I just checked and the links worked for me :slight_smile:

Thanks for your confirmation.

Best regards,

Do you have updates on the release of the bookworm containers?

Hi @vix !

Toradex’s main website has a news section: Novidades sobre computação embarcada. Maybe you want to subscribe there :slight_smile:

You can see from this news that Bookworm is (kind of) already available, but the documentation was not yet updated: TorizonCore 6.2.0 Quarterly Release

You can see in Docker Hub, e.g. for the Debian container: Docker

If you really want, you can try it, but I think it makes sense to wait for the documentation to be updated because it is possible that the documentation for Bullseye is not totally compatible with Bookworm.

Best regards,

Thank you @henrique.tx

I see that the news has been published today.
Great news!

In a few days I expect to download TorizonCore with Evaluation Containers binaries where the containers are bookworm-based.
The last Nightly has bullseye-based containers (weston-vivante, chromium, portainer-ce).

The last Nightly has bullseye-based containers (weston-vivante, chromium, portainer-ce).

Just to clarify, the bookworm versions of the Chromium and Cog containers are still not available as stated in the 6.2.0 release news.

Just to clarify, the bookworm versions of the Chromium and Cog containers are still not available as stated in the 6.2.0 release news.

Thank you.
I’ve been confused by this commit that bumped conmtainer tags to bookworm (CT_TAG_CHROMIUM and CT_TAG_COG too).
But I canot easy understand which meta-toradex-torizon commit is used in the several TorizonCore builds (Quarterly, Monthly, Nightly).

Hi @vix !

This bumping that you are referring to was done as a test for Toradex R&D to check for problems. It was done on purpose. Now it was rolled back, as you can see here: container-tags.sh: rollback browsers to bullseye · toradex/meta-toradex-torizon@cd85120 · GitHub

There are at least two ways (and, being honest, I just learned about them :smile: ).

You can check toradex-manifest.git - Repo manifest for Toradex Embedded Linux TorizonCore and BSP layer setup for Yocto Project/Openembedded for tags in Toradex’s manifest file. You will find there Quarterlies and probably Monthlies.

Also, you can get the layers’ commits from an image itself: you just need to check the /etc/build content. E.g.:

$ cat /etc/build      
-----------------------
Build Configuration:  |
-----------------------
DISTRO = torizon
DISTRO_VERSION = 6.3.0-devel-20230504145727+build.0
-----------------------
Layer Revisions:      |
-----------------------
meta-toradex-torizon = tor-2903:3f03c352e7d12987eb47edb4ae7a09cae6b3f506 -- modified
meta-toradex-distro = HEAD:fda3e56a06f7d3cef7f73b174bb68c4f1074c26e 
meta-toradex-bsp-common = HEAD:1c5d0d1d763366eabbacaeb40fb2813e9488f7c3 
meta-oe           = HEAD:82c75b466e55d7dca7a2364986ecb704cf63d141 
meta-networking   = HEAD:82c75b466e55d7dca7a2364986ecb704cf63d141 
meta-filesystems  = HEAD:82c75b466e55d7dca7a2364986ecb704cf63d141 
meta-python       = HEAD:82c75b466e55d7dca7a2364986ecb704cf63d141 
meta-perl         = HEAD:82c75b466e55d7dca7a2364986ecb704cf63d141 
meta-virtualization = HEAD:a7413c5d7568ce91b809ed11f84305b1afb468bb 
meta-updater      = HEAD:ffbbc2b9f46a60bd2d51be53079252f8e6304a8b 
meta-toradex-nxp  = HEAD:8f9e36d0af54b568a2eada60860605f4899daaa4 
meta-freescale    = HEAD:d9f77788e1902a7d999958575a955e701c1c1b61 
meta-freescale-3rdparty = HEAD:f6fa0fd8783ce69d07feaad0b7ca6759b5a4d5d6 
meta-yocto-bsp    = HEAD:b662ed3d7a40d7c96f67b8a2337fd1eaa3f179a9 
meta-poky         = HEAD:b662ed3d7a40d7c96f67b8a2337fd1eaa3f179a9 
meta-security     = HEAD:cc20e2af2ae1c74e306f6c039c4963457c4cbd0f 
meta-toradex-ti   = HEAD:82e19264109288ddd80a673d83079a96d20d6dce 
meta-arm-toolchain = HEAD:904f8e82c2772986fad500af4f72f5211a7ff831 
meta-arm          = HEAD:904f8e82c2772986fad500af4f72f5211a7ff831 
meta-ti-bsp       = HEAD:2a5a0339d5bd28d6f6aedaf02a6aaa9b73a248e4 
meta-ti-extras    = HEAD:2a5a0339d5bd28d6f6aedaf02a6aaa9b73a248e4 
meta              = HEAD:6b50713cd51002584915f46eb366b8667db210ea

Best regards,

1 Like

Hi @vix !

Do you have any updates regarding this thread?

Was this solved?

Best regards,

Hi @henrique.tx

not yet;
based on what I see in the past (i.e., issues mixing bullseye and bookworm containers), I prefer wating for Chromium:3 bookworm before trying again.

Hi @vix !

Did you have time to test the Chromium Bookworm version?

https://hub.docker.com/r/torizon/chromium/tags

Best regards,

Hi @vix !

Did you have time to test the new Chromium Bookworm Container?

Best regards,

Hi @henrique.tx
yes I tried.
Basically the Chromium Bookworm Container works for a simple web page.
But the behavior with 3D content is not ok.
It seems that Vulkan is not enabled (or something like that), but I need some more time to investigate.
I let you know.