Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Question]: Which version of AMF to use on Amazon EC2 instance #526

Open
kode54 opened this issue Jan 17, 2025 · 3 comments
Open

[Question]: Which version of AMF to use on Amazon EC2 instance #526

kode54 opened this issue Jan 17, 2025 · 3 comments
Labels

Comments

@kode54
Copy link

kode54 commented Jan 17, 2025

Which older version of AMF should be paired with VCN firmware version 1.10? Or is it possible to upgrade the AMDGPU firmware which is loaded on an EC2 instance with GPU hardware?

@MikhailAMD
Copy link
Collaborator

AMF runtime SO and some other related SOs should match VCN FW and should be installed all-together with driver package. I assume they are already installed on EC2. I am not sure what can be upgraded on EC2 but if so, it should be whole driver package.
AMF SDK doesn't have binaries, only header files and is fully backward compatible. You can use the latest SDK version but check for errors if your application would try to enable newer features.

@kode54
Copy link
Author

kode54 commented Jan 18, 2025

The problem is, I am installing AMF library into a Docker image. I don't know any other way to do this, other than requiring the user to install their own AMF locally, then mount a path to the Docker container so it can access the host's copy of the AMF library.

@kode54
Copy link
Author

kode54 commented Jan 19, 2025

Considering the problems, I guess it's better and more flexible to allow the user to mount their own /opt/amdgpu-pro from the host and supply their own compatible version. Latest works on Arch, but apparently not Ubuntu or Amazon Linux images.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants