-
Notifications
You must be signed in to change notification settings - Fork 86
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 trying to upgrade xrt #1618
Comments
I'm not sure if this is your problem, but I found I had to explicitly remove and reinstall the xrt plugin when upgrading. |
I did remove the old xrt. The only thing I am not sure of is that I compiled a new Linux kernel based on the old one. Does it mean I am required to reinstall the operating system? |
That shouldn't be necessary. Are you sure there were no errors when compiling/installing the xrt_plugin module? The fact that it can't find the firmware is very suspicious. |
I found the problem and I guess it is a BUG that is required to be fixed. In the tutorial (https://github.com/Xilinx/mlir-aie/blob/main/docs/buildHostLin.md), it asks us to switch to an specific commit with:
In this commit, when running the:
I found However, I found that this URL is not working anymore. Therefore, there will be 404 error. However, an empty file will be generated so everything will run smoothly and no other errors will show up. To solve this, I have to manually change the info.json to the new URL: https://gitlab.freedesktop.org/drm/firmware/-/raw/amd-ipu-staging/amdnpu/1502_00/npu.sbin.1.4.2.323 Now, it works. I believe either the mlir-aie repository or the xdna-driver repository has to change and has this problem fixed. |
I was trying to use the new xdna-driver. Therefore, I followed the installation of xdna driver for linux. However, in the end, the NPU device is not found when running
xbutil examine
. The output is shown below:I checked the dmesg. I found the amdxdna driver failed to load:
I also checked the PCI information:
May I ask how to solve this?
The text was updated successfully, but these errors were encountered: