Arch Linux

summers

Member

Registered: 2016-01-27

Posts: 33

[Solved] Whats the time scale on enabling the intel xe drm ...

Hi,

Notice that the new intel graphics drm drive Xe, that will replace i915 eventually, has landed in the kernel:

https://github.com/torvalds/linux/tree/ … gpu/drm/xe

Is there a plan to enable it in arch, and do we have a timescale?

David.

P.S. the i915 driver doesn't seem to be working all that well on my i7-12650 cpu ...

Last edited by summers (2024-01-16 13:33:19)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,164

Re: [Solved] Whats the time scale on enabling the intel xe drm ...

That's an in development branch, the soonest you can expect that is on the 6.8 kernel. When it gets officially pulled into stable it will get enabled as all things.

Since you are actually asking for something different, can you elaborate on "doesn't seem to be working all that well"? What doesn't? General advice if xf86-video-intel is installed remove it.

FWIW if you want help with your actual problem, make a new thread and describe your issues. If you want to test whether the xe driver would fix things right now, you'd have to opt for linux-git and build the driver and activate it and build mesa-git an d activate it and... https://www.phoronix.com/review/intel-xe-benchmark

It's going to be quite a few months until this is built up enough and all the support pieces in place that would enable this -- and nothing of this has anything to do with Arch per se.

Last edited by V1del (2024-01-16 09:57:23)

summers

Member

Registered: 2016-01-27

Posts: 33

Re: [Solved] Whats the time scale on enabling the intel xe drm ...

when I say "doesn't work all that well" when I do "mpv --hwdec=auto" I get a string of errors:

[ffmpeg] AVHWDeviceContext: cu->cuInit(0) failed -> CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected
[ffmpeg/video] h264: Device does not support the VK_KHR_video_decode_queue extension!
[ffmpeg/video] h264: Failed setup for format vulkan: hwaccel initialisation returned error.
[ffmpeg] AVHWDeviceContext: Failed to initialise VAAPI connection: -1 (unknown libva error).
[ffmpeg] AVHWDeviceContext: cu->cuInit(0) failed -> CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected
[ffmpeg/video] h264_v4l2m2m: Could not find a valid device
[ffmpeg/video] h264_v4l2m2m: can't configure decoder

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,164

Re: [Solved] Whats the time scale on enabling the intel xe drm ...

Which has on it's own no direct relation to the kernel module: https://wiki.archlinux.org/title/Hardwa … tion#Intel -- if that is setup, one thing that's indeed not explicitly mentioned there but potentially relevant, for tigerlake you might also need https://archlinux.org/packages/extra/x8 … intel-gpu/

summers

Member

Registered: 2016-01-27

Posts: 33

Re: [Solved] Whats the time scale on enabling the intel xe drm ...

Yes it a new Alder Lake box, I'm slowly installing things on. Currently using the i915 module, haven't  yet chased down what mesa module is being used. "vulkan-intel" is installed. and seems to be working; and yes slowly digging though what I've missed installing ...

summers

Member

Registered: 2016-01-27

Posts: 33

Re: [Solved] Whats the time scale on enabling the intel xe drm ...

Ah "intel-media-driver" was needed for va api which gives access to hardware acceleration! And that seems to have stop some issues with "mpv" glitching!

Last edited by summers (2024-01-16 13:07:50)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,164

Re: [Solved] Whats the time scale on enabling the intel xe drm ...

You fell into the classical XY Problem trap: https://xyproblem.info/ -- you thought you needed the xe drm module, but this is a weird question to ask since i915 is still maintained and still gets all the new developments done to it anyway, which is why I asked for clarification on your actual issue.

If you consider my answer to your original question satisfactory, please mark as [SOLVED] and make new threads for any current problems you are running into -- and remember -- start with the problem description instead of thinking about a potential solution that might be too far fetched