Hi Anuj, Thank you for the quick response with positive information. It makes me feel warm about our community.
1- "This doesn't look like complete error log. A complete log would have helped." Do you mean a complete run log from chromium? I will submit a full running log when I run chromium soon. 2- Regarding the suggestion in https://github.com/intel/media-driver/issues/1498 I reviewed that suggestion during my self-research for a solution. It suggests using chromium r107 and adding --disable-features=UseChromeOSDirectVideoDecoder However, I do not know which chromium recipe version for that r107. For the flag UseChromOSDirectVideoDecoder, I already have that. Thank you, Huy On Wed, Jun 7, 2023 at 8:49 AM Mittal, Anuj <[email protected]> wrote: > On Wed, 2023-06-07 at 08:24 +0700, HuyK wrote: > > Hi all, > > > > I am working on Intel J4125 platform with these meta layers: > > - poky: master branch > > - meta-intel: master branch > > - meta-browser: master branch > > > > 1/ I build chromium by chromium-ozone-wayland_111.0.5563.147.bb > > recipe with adding "use-vaapi" and "proprietary-codecs" to > > PACKAGECONFI in chromium-gn.inc > > That chromium did not call intel VAAPI functions, but I see it > > loads iHD_drv_video.so at runtime. > > > > 2/ Then I research to find this link about applying patches to > > support VAAPI in > > chromium https://aur.archlinux.org/packages/chromium-wayland-vaapi > > + 0001-ozone-wayland-add-VA-API-support.patch > > + vaapi-add-av1-support.patch > > + use-oauth2-client-switches-as-default.patch > > This chromium loads iHD_drv_video.so and calls Intel VAAPI APIs; > > however, chromium reports these errors when I open to play an H264 > > video so that HW Acceleration is not working > > > > [13436:13436:0606/150528.263552:ERROR:vaapi_wrapper.cc(2399)] > > vaCreateSurfaces (import mode) failed, VA error: resource allocation > > failed > > [13436:13436:0606/150528.263789:ERROR:vaapi_picture_native_pixmap_ozo > > ne.cc(73)] Failed creating VASurface for NativePixmap > > [13436:13436:0606/150528.264843:ERROR:vaapi_wrapper.cc(2399)] > > vaCreateSurfaces (import mode) failed, VA error: resource allocation > > failed > > [13436:13436:0606/150528.265073:ERROR:vaapi_picture_native_pixmap_ozo > > ne.cc(73)] Failed creating VASurface for NativePixmap > > [13436:13436:0606/150528.265294:VERBOSE1:vaapi_video_decode_accelerat > > or.cc(142)] NotifyError(): Notifying of error 4 > > This doesn't look like complete error log. A complete log would have > helped. > > > > > So far, I could not find a solution to fix chromium errors and I am > > new to chromium, intel vaapi, libva debugging. > > > > Please support how to debug the errors there or guidance on how to > > officially build chromium with intel VAAPI support in Yocto? > > This doesn't seem to be Yocto related. This looks very similar so > please try the suggestions here: > > https://github.com/intel/media-driver/issues/1498 > > Thanks, > > Anuj >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60194): https://lists.yoctoproject.org/g/yocto/message/60194 Mute This Topic: https://lists.yoctoproject.org/mt/99376559/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
