-
Notifications
You must be signed in to change notification settings - Fork 60
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
An issue may solve the situation to use this library on Chrome/Chromium. #274
Comments
Unfortunately I don't think this will work. While it may appear to be initialising the correct device, Chrome doesn't know we're using a different device to the one it's using. When we go to export the DMA-BUF, Chrome will attempt to import it into the EGL/Vulkan context on the Intel card which will fail. |
We have solution to make sure the Chrome using NVIDIA Vulcan, and when I did it, NVIDIA GPU Utilization is float (means the NVIDIA GPU were used). But the video engine still keeps frozen 0% |
This is currently affecting Chrome with Nvidia and it's been active for a while. Depending on what flags you run I also got this now which I haven't seen before: |
Yep, so I think there may be a solution to use NVIDIA card. but I have turned to Windows so that I can't test anymore |
Ok, so the previous error is gone but there's another one now, with the latest chromium release I have:
|
To remove the Nvidia skipping, You need --enable-features=VaapiOnNvidiaGpus |
how have you removed the following error ?
|
Have any tests been conducted with the latest patch? I haven't achieved any success yet. |
Can this driver be used on top of chromium. |
Environment:
CPU: Intel Core i7 13700H
GPU (In about system): Mesa Intel(R) Graphics (On-Demand)
GPU1: Intel Alderlake_p (Gen12) (RPL-P) [Intel Iris Xe Graphics]
GPU2: NVIDIA GeForce RTX 4060 Laptop 8GB
Desktop: Debian Testing + KDE + X11
Run Chrome with the command:
And I modified the function so that the library could run on multi-GPU mode:
And there is an error from Chrome:
Console log output:
And I think it can be used for Chrome/Chromium if we fixed the error?
The text was updated successfully, but these errors were encountered: