neko
neko copied to clipboard
Intel ARC GPU support
I run neko with my Intel iGPU for a while now, with no issues. I recently got my hands on a Intel ARC A380 GPU.
I gave it a try with neko, tho neko instantly fails when trying to spin it up. I use an up-to-date kernel (6.8) on the underlying host for the Intel ARC to be working.
The error message is probably saying that the neko container is missing a gstreamer plugin (no element "vaapih264enc"
) or somehow other related to gstreamer-vaapi
.
I don't know if that is actually the issue. I will be happy to assist in any way, if there are questions or help needed/further information required.
can you teach me how to use with intel igpu? i have a intel 1260p but failed to run neko with gpu acceleration
- You need to use Ubuntu 24.04. (at least a 24.04 container) or similarly new container distro.
- You need vah264lpenc (gst-bad, va / separate from the legacy vaapi plugin) - It should be to first check if vah264enc (older Intel GPUs, AMD GPUs) plugin exists then if it doesn't, switch to vah264lpenc from within the code internally.
Reference: https://github.com/selkies-project/selkies-gstreamer/blob/8476d8fc44dbc90103f7d615ca719858526b2bc7/src/selkies_gstreamer/gstwebrtc_app.py#L401
I do use Ubuntu 24.04 already. The rest is on neko's side on the code base or in the docker container as i understand it.
The host and the container should both be Ubuntu 24.04. The above message is for @m1k1o.
We are currently on debian bullseye / ubuntu 20.04 for nvidia. As 24.04 is available only since couple of days, I think we could upgrade. But even the upgrade to bookworm was not successful as we saw high CPU usage spikes. Let's see if that happens with the latest version.
Is there anything i can do or test to help out bring this a little further?
I have an Arc and the driver support is very bad.
https://github.com/intel/media-driver/issues/1800
I only used my Arc for transcoding in Emby, worked fine so far there. I dont know how support with gstreamer looks. But thats why i ask if there is anything specific i can test.
It's a vapostproc issue. Encoding seems to work fine.