Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error initialising vaapi on Gnome Wayland #7

Open
darren-steven opened this issue Nov 16, 2018 · 8 comments
Open

Error initialising vaapi on Gnome Wayland #7

darren-steven opened this issue Nov 16, 2018 · 8 comments
Labels
Intel Wayland Known issue

Comments

@darren-steven
Copy link

I know this issue might be broader than just this app, but I think vaapi is working on other apps under wayland (vlc for example)

chromium-vaapi-70.0.3538.77-1.fc29.x86_64.rpm from rpmfusion koji
Hardware Intel Skylake

$ chromium-vaapi
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
[22955:22955:1116/104946.418564:ERROR:vaapi_wrapper.cc(328)] vaInitialize failed: unknown libva error

  • Defaults to software decoder in youtube

Works fine in Gnome X11 session (I see GPU decoder selected in chrome://media-internals for youtube)

vaainfo reports same info on wayland and X11

$ vainfo
libva info: VA-API version 1.3.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_3
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.3 (libva 2.3.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 2.2.0
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD

@qnixsynapse
Copy link
Owner

qnixsynapse commented Nov 16, 2018

Hello.
Chromium runs through XWayland unlike vlc.
See link

I'm trying my best to compile chromium with wayland ozone but the build is still failing(complaining of a missing vaapi drm file). Unless any of this is solved, chromium on intel wayland won't able to decode in hardware.

Update:
Try Launching Chromium with --use-gl=egl

@qnixsynapse qnixsynapse added the Intel Wayland Known issue label Nov 16, 2018
@megamaddu
Copy link

That flag doesn't make a difference for me

@qnixsynapse
Copy link
Owner

qnixsynapse commented Nov 25, 2018

@spicydonuts hmm. Anyway that PR is closed now. The only thing left to do is enabling ozone on chromium.

@rathann
Copy link

rathann commented Dec 3, 2018

@spicydonuts hmm. Anyway that PR is closed now. The only thing left to do is enabling ozone on chromium.

It is closed, but not merged due to submitter inactivity: intel/intel-vaapi-driver#369 (comment) . It needs to be resubmitted.

@qnixsynapse
Copy link
Owner

@rathann Yes. Also there is a bug report @ Bugzilla. It's been there since Fedora 26

@ghost
Copy link

ghost commented May 5, 2019

Hello.
Chromium runs through XWayland unlike vlc.
See link

I'm trying my best to compile chromium with wayland ozone but the build is still failing(complaining of a missing vaapi drm file). Unless any of this is solved, chromium on intel wayland won't able to decode in hardware.

Update:
Try Launching Chromium with --use-gl=egl

are there still problems with Ozone wayland?

@mthomos
Copy link

mthomos commented Sep 23, 2019

Any update on this issue ?

@qnixsynapse
Copy link
Owner

@mthomos I am providing chromium-ozone binaries for Fedora in copr. These come with vaapi disabled.

For intel vaapi driver there is still need for someone to add support for DRI3.

You can try building your own version of libva-intel-driver using these patches(for now):
1 and 2

@qnixsynapse qnixsynapse pinned this issue Oct 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Intel Wayland Known issue
Projects
None yet
Development

No branches or pull requests

5 participants