You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
linuxmint 22, AMD 8700G processor, git source from 2024-11-03.
After some minor script/cmake adjustments, XRT and xdna .DEB file build and install fine (using gdebi).
However, it doesn't work. After reboot, "sudo journalctl -b | grep xdna" shows:
System Configuration
OS Name : Linux
Release : 6.8.0-47-generic
Machine : x86_64
CPU Cores : 16
Memory : 61867 MB
Distribution : Linux Mint 22
GLIBC : 2.39
Model : X600-ITX
BIOS Vendor : American Megatrends International, LLC.
BIOS Version : 8.01
XRT
Version : 2.19.0
Branch : HEAD
Hash : 090e3faccd90abd21e59a4edbf7ed9d9c1016d0b
Hash Date : 2024-11-04 13:08:10
xocl : unknown, unknown
xclmgmt : unknown, unknown
WARNING: xclmgmt version is unknown. Is xclmgmt driver loaded? Or is MSD/MPD running?
amdxdna : 2.19.0_20241104, 330cbcf822b280ddce5c81036fc2ee6d55e9a313
Device(s) Present
0 devices found
I presume that xrt-smi cannot work properly unless the xdna errors in journalctl have disappeared.
Is a later kernel version needed? Or what could be wrong?
Thanks, Mat
The text was updated successfully, but these errors were encountered:
Problem solved. I was using kernel 6.8, after upgrading to kernel 6.11 (using the "mainline" utility), doing a clean, build and install from both xrt and amdxdna , the xrt-smi command now reports a device present, and no more errors in the journal. Thank you for the assistance.
linuxmint 22, AMD 8700G processor, git source from 2024-11-03.
After some minor script/cmake adjustments, XRT and xdna .DEB file build and install fine (using gdebi).
However, it doesn't work. After reboot, "sudo journalctl -b | grep xdna" shows:
and "/opt/xilinx/xrt/bin/xrt-smi examine" shows:
I presume that xrt-smi cannot work properly unless the xdna errors in journalctl have disappeared.
Is a later kernel version needed? Or what could be wrong?
Thanks, Mat
The text was updated successfully, but these errors were encountered: