-
Notifications
You must be signed in to change notification settings - Fork 232
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
GPU not detected #698
Comments
could you provide more details about the setup? What device, what linux kernel, what driver version, where taken from? |
@JablonskiMateusz this is on Aurora - I'm waiting on confirmation on what info I can post publicly |
PVC support is not yet in upstream kernel, so you would need to use Backport DKMS kernel driver supports only specific kernel versions. Does |
@pvelesko do you build driver packages on your own or you take packages from our github? |
Aurora is a PVC system and normally runs the intel engineering releases.
I build them myself with As for the driver version (runtime driver i.e. NEO?) I use the latest tag and have been trying for months now. |
You may take a look at exactly how I build it: https://github.com/pvelesko/intel-compute-runtime-build |
At least one problem in that is not building everything with the same compiler version. LLVM changes its API between versions, so all components in the compute stack need to be build with the same compiler version, including opencl-clang, llvm-spirv and SPIRV tools. In my case, I get LLVM, opencl-clang and llvm-spirv stuff from the distro:
And build gmmlib, SPIRV-Headers, SPIRV-Tools, vc-intrinsics, intel-graphics-compiler, level-zero and compute-runtime myself. IGC is built with (When using packages from Ubuntu, main issue is getting suitable |
Can you elaborate on what I am building with different compiler versions? I compile clang-14 with LLVM-SPIRV and opencl-clang prior to building intel-compute-runtime stack. I can't use pre-built packages since I don't have sudo on this system. Also, I have verified that the build system works on at least 2 different non-PVC systems. |
Ok, so issue is not with build, but actual PVC support, either in the kernel, or in the user-space driver. Kernel driver Does Or if you do not have access to run User-space driver You could add I just tested following setup with Ubuntu LLVM 14 packages:
(On top of SLES SP15 "5.14.21-150400.24.92-default" kernel, but I'm not sure where its And at least
( [1] CMake configure output:
Build tests output:
|
Could you run |
Trying to run the public runtime on PVC - from my understanding this should be supported but devices fail to initialize.
Is there a debug procedure for this?
The text was updated successfully, but these errors were encountered: