I am not against adding support for Arc GPUs. Now that there is also support for Nvidia the code architecture allows for it. However I do not have any access to Arc hardware to test on, so any potential implementation would be based solely off documentation and test reports from users.

I've actually looked into Arc support previously, and at the time there seemed to be no way to do any configuration under Linux. Could you be more specific about fully configurable with the oneAPI feature under Blender LTS software? What settings does it expose, is there any documentation about it or example scripts? I haven't found anything that's clearly applicable to Arc with a quick search, but I also haven't looked at intel's documentation in detail.

It's also worth noting that for now the popularity and overall viability of Intel dGPUs is still quite low, and it's uncertain if they will exist beyond Alchemyst and maybe Battlemage. Because of this I don't want to spend too much effort on this if support for it ends up being too problematic or doesn't fit well into LACT. But again, I'm not opposed to it if it's reasonable to implement.

That's ok, understandable.

Now, ARC cards are simply fully supported via oneAPI in Blender 4.2 LTS once you install all the necessary dependencies (I can speak for openSUSE which is the distro I use) even though the ray tracing isn't great but at least with no strange artifacts or crashes. I'm confident that things will improve soon and Intel ARC will gain respect.

Keep up the great work, LACT is a very interesting and promising utility ;)

I did some more searching and there doesn't seem to be any way to do things like clocks configuration or custom power limits on Linux with Arc. The closest thing is xpumanager, which only works for Intel data center GPUs and not Arc.

UPDATE: after digging through kernel code, it appears that it is actually possible to configure intel graphics on Linux. However, it needs the xe kernel driver to be used. Starting with Battlemage it is the default, all previous platforms use i915 instead, but it is possible to force the xe driver to be used on graphics starting with Rocket Lake (including Alchemyst).

I got the driver working on a laptop iGPU, and it does expose frequency controls, and I'll try to see what I can get working. However I cannot do full testing as I do not have access to any Intel dGPU (Battlemage or Alchemyst).

Hi Ilya,
this is great news! Looks promising and I think from a quiet long time that the i915 is the key factor to have decent readings through useful stuff like nvtop terminal and, by consequence, all the apps like yours. Thank you also for have changed the title, it makes more sense also because the ARC line is advancing despite the poor distribution in Europe. Let's hope Intel will improve.

If you have a decent desktop machine with a mobo that support the resize bar I can give you an ASRock Challenger A380 6GB GDDR6 for testing. It requires one additional power connector (8 pin) and it has been used for just 8 months on my Asus Prime B550-M CSM then I switched to something more capable and well balanced like the Sparkle A580 8Gb GDDR6.
I'm glad to help as I could for the right cause, let me know, hit me a message in private.

Cheers,
C.

Thanks for the offer, this would be very helpful. Do you have a private contact channel where we could arrange this?

Yes, send me message at [email protected]

I have received an A380 thanks to @Citizen839X.
After taking a look at the exposed options with the default i915 driver, here's the status of various functionality:

• Stats monitoring mostly works, with a major exception of temperature. Frequency, voltage and fan speed are reported. Power draw is not reported directly, but is possible to calculate.
• Frequency controls work, but only for downclocking. It is not possible to set a max clockspeed above the default.
• Power limit settings are exposed, but completely ignored by the hardware.
• There is no fan control.

I will check the xe driver later, but from what I've seen in the kernel code it's doesn't seem to provide anything extra, rather just exposes the same settings in a different way.

So unfortunately there is still a lot of things missing compared to AMD or Nvidia. But hopefully even this limited functionality will be useful for some people.

I have received an A380 thanks to @Citizen839X. After taking a look at the exposed options with the default i915 driver, here's the status of various functionality:

* Stats monitoring mostly works, with a major exception of temperature. Frequency, voltage and fan speed are reported. Power draw is not reported directly, but is possible to calculate.

* Frequency controls work, but only for downclocking. It is not possible to set a max clockspeed above the default.

* Power limit settings are exposed, but completely ignored by the hardware.

* There is no fan control.

I will check the xe driver later, but from what I've seen in the kernel code it's doesn't seem to provide anything extra, rather just exposes the same settings in a different way.

So unfortunately there is still a lot of things missing compared to AMD or Nvidia. But hopefully even this limited functionality will be useful for some people.

You're welcome Ilya.

So, the statistics reported in LACT should be all figured with "0" value or N/A do you confirm?
I've also noticed that the GPU usage is 0% but if I open something like Mission Center (flatpak version in my case, installed as system) it gives me real time readings and also the video encode/decode percent value is available, obviously at 0% while I'm not doing that operations.

Oh wait, could my 0% GPU usage value in LACT be possible due to a permission denial (os error 13) ?

Cheers,
C.

That list is just what's possible to implement at all with what the driver provides - many of those things aren't working in LACT yet, I'm working on it in #439.