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
I've found that neither 1.2.0 nor 1.3.0 can change the install path, and if they do, they get an error saying that the config file is not available.
Similar to #130 Same problem Is there a way to fix it?
Or maybe we can fix it later.
The text was updated successfully, but these errors were encountered:
@Garbo1229 will you able to provide some more details and error logs, so we can reproduce this error.
What is your windows OS version, NPU driver version, and confirm if you have all the prerequisites necessary for RyzenAI-SW installation as mentioned in https://ryzenai.docs.amd.com/en/latest/inst.html
@Garbo1229 will you able to provide some more details and error logs, so we can reproduce this error.
What is your windows OS version, NPU driver version, and confirm if you have all the prerequisites necessary for RyzenAI-SW installation as mentioned in https://ryzenai.docs.amd.com/en/latest/inst.html
If I try to install to D:\Program Files\RyzenAI\1.3.0\
Will get an error with the following log.
D:\ProgramData\anaconda3\Lib\argparse.py:2006: FutureWarning: `remote_definition` is deprecated and will be removed in 25.9. Use `conda env create --file=URL` instead.
action(self, namespace, argument_values, option_string)
EnvironmentFileNotFound: 'C:\Windows\Installer\SFXCA9F96D96CAA417B59DAD65FC164648D94\env.yaml' file not found
OS version: windows 11 24H2(26100.2454)
NPU driver version:1.3.0(1.2.0 will be the same)
If I hadn't changed it, I wouldn't have had this problem, and I'm sure I've prepared the environment well in advance.
I've found that neither 1.2.0 nor 1.3.0 can change the install path, and if they do, they get an error saying that the config file is not available.
Similar to #130 Same problem Is there a way to fix it?
Or maybe we can fix it later.
The text was updated successfully, but these errors were encountered: