-
Notifications
You must be signed in to change notification settings - Fork 341
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
Default AMI Fails to detect Nvidia driver on AWS g6e #1480
Comments
This issue could be literally anything related to GPU drivers. Please run a non-GPU workload like I currently can't be of much help, but with these hints you should be able to find out what's happening. |
@OLSecret @0x2b3bfa0 is it possible to mention AMI Id which I have in AWS .. private or public one ? Because I am getting a 11.4 cuda version with T4 GPU while launching a g4dn.xlarge instance. Where as in manual method I am getting 12.4 with T4 GPU |
e.g. `--cloud-image=ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20221206`
if that's what you want
…On Fri, 29 Nov 2024 at 09:17, Ajith ***@***.***> wrote:
This is the file I used
https://github.com/ajithvcoder/emlo4-session-10-ajithvcoder/blob/main/.github%2Fworkflows%2Fec2-pipeline-end-to-end.yml
—
Reply to this email directly, view it on GitHub
<#1480 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACW4FW4DOUOPBFLGXFGBIID2DAPKJAVCNFSM6AAAAABQG4K3B6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBXGI4TMOBUHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Getting:
from setup like:
The text was updated successfully, but these errors were encountered: