-
Notifications
You must be signed in to change notification settings - Fork 40
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
0 devices found after installation #14
Comments
Please look into dmesg log to see if driver loads properly. |
Thanks for the quick response, I can only see the following relevant line I presume this is due to the module being unsigned - Is the only way to fix this is to recompile the kernel with the following flags?
|
No, this is harmless. Anything else? |
Yeah, that's what I figured as well, no other mentions of either XOCL, XCLMGMT or AMDXDNA. Is there a way to check if the device is being recognized on the system at all - independent of driver installation? I'd like to rule out a hardware / motherboard firmware issue. I'm aware that on Windows the NPU/IPU would should up on device manager even without the driver being installed - but I'm unaware if that level of visibility is supported by the installed linux kernel. ROCm isn't required to be installed for this driver to work correct? |
On a system with NPU device, on Linux, you can run: "lspci -vd 1022:1502" and you should see the device as shown below: c3:00.1 Signal processing controller: Advanced Micro Devices, Inc. [AMD] Device 1502 |
Interesting, I don't get any output after running that command, would you expect this to work on an older kernel I.E. could an incorrect installation of the 6.7 kernel cause this or is this strictly a firmware issue on the PC vendors part - I'm assuming kernel version wouldn't impact this but I want to be sure before notifying the PC vendor. |
Not all vendors have activated the NPU via firmware, please check with your vendor. |
Yes, most likely the NPU device is not enabled in your BIOS and I have seen this issue before. Please talk to your vendor. |
I see, thanks a lot for the help. Feel free to mark this issue as closed - if I'm able to resolve this by some setting in the bios / firmware update later on I'll add a comment for future reference. |
All of our minisforum boxes worked out of the box ( since early last year) - I can try and get the bios version for you. |
That would be greatly appreciated, thanks! Our bios version is 1.09 which I believe is the latest, so unless something broke in the update last November not sure what else it could be. |
Quick update, it was in fact a bios setting everything works now - perhaps the default setting for enabling the IPU was disabled in the latest update (ours came preloaded with 1.09) ? Not entirely sure though. Regardless thanks for your help! Feel free to close |
For future reference, once you enter the BIOS, the IPU setting should be enabled by navigating to Advanced -> CPU Configuration on this PC. |
After installing Linux Kernel 6.7, XRT, and this driver on a fresh install of ubuntu 22.04 I'm seeing 0 devices found when running "xbutil examine", the provided code sample is also seg faulting when attempting to load device(0).
This is being executed on a minisforum PC with a 7940HS (UM790 Pro), any pointers with further debugging tips or solutions would be appreciated.
The text was updated successfully, but these errors were encountered: