I’ve been working on this since the first Blender 4.4.0 was released. Raytracing doesn’t work on any of the 4.4.x versions. It still works on Blender 4.3.x. so this is a 4.4.x problem. I’ve done so much over the last 8-10 weeks that there’s no way I can remember it all.
I even compiled the level-zero-raytracing-support and that made no difference.
Is Raytracing working for anyone using an Intel GPU?
I’m using this Blender model. Note it is 94MB.
Model Download: Blender 3.1 – Secret Deer
I ran Blender from a terminal to get more info and this is it…not much. It crashes completely while "loading render kernels (This may take a while the first time). After a few seconds, poof, it’s gone. I can’t find the file “drm_neo.cpp” that it says caused the error on line 1060, and the “/home/abuild/rpmbuild/BUILD/” directory never does exist.
~> /home/john/code/blender-4.4.3-linux-x64/blender
Read blend: "/home/john/Downloads/Blender Models/blender-3.1-splash/blender3.1-splash.blend"
Abort was called at 1060 line in file:
/home/abuild/rpmbuild/BUILD/intel-opencl-24.52.32224.5-build/compute-runtime-24.52.32224.5/shared/source/os_interface/linux/drm_neo.cpp
@jsmith64 Hi Using Blender Benchmark for 4.4.0 I see;
BLENDER: I0501 07:52:08.450107 655382 device.cpp:147] Device with id "ONEAPI_Intel(R) oneAPI Unified Runtime over Level-Zero_Intel(R) Arc(TM) A380 Graphics_0000:04:00.0" supports OpenImageDenoise.
BLENDER: oneAPI queue initialization error: got runtime exception "Hardware Raytracing is not available; please install "intel-level-zero-gpu-raytracing" to enable it or disable Embree on GPU."
So if you disable Embree in Blender, what happens?
Unckecking Embree on CPU causes it to crash with the same error.
If I uncheck the A750 too, it renders on the CPU.
Some simple models render but they’re not using the more advanced rendering methods. I made a 3D fan blade for an icon. It’s simple, with simple shading, and it renders with everything checked.
@jsmith64 I believe the issue is with intel-opencl… Might be worth a bug report?
I’ve looked into OpenCL and it works great with Darktable etc. I looked at the versions and version 25.13.33276.16 is the latest and the error shows we have intel-opencl-24.52.32224.5 on Tumbleweed (I checked too). I have assumed that maybe Blender needs a newer OpenCL but since it works on Darktable, maybe not.
I found a post from a guy who had a very similar error and the cause was “kernel was unable to load the GuC firmware” (last comment on that post).
That’s from 2022 but the error looks a lot like mine. Note, clinfo works fine for me, as does OpenCL in Darktable.
$ clinfo
Abort was called at 347 line in file:
/var/tmp/portage/dev-libs/intel-compute-runtime-22.43.24558/work/compute-runtime-22.43.24558/shared/source/os_interface/linux/drm_neo.cpp
zsh: IOT instruction clinfo
That led me to believe it may be a firmware/OpenCL mis-match.
I was trying to fix it, then just pin it down so I’d know where the bug report goes, Blender, Intel or Suse. Fixing it may be easier than pining it down at this point…with a little luck. 
But the experts who know this stuff might recognize it right away, too.
@jsmith64 I use ARC/Nvidia setups here, so cuda… Guc/Huc hardware encode/decode will be used automatically on newer Intel GPU’s including ARC so not relevant.