-
Notifications
You must be signed in to change notification settings - Fork 49
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
driverInitialized check not valid #102
Labels
Comments
ROCm/rocminfo#42 (comment) may help |
littlewu2508
added a commit
to littlewu2508/rocm_smi_lib
that referenced
this issue
Apr 2, 2022
Closes: ROCm#102 Signed-off-by: YiyangWu <[email protected]>
Fixed as of 9f6614e. Please reopen if you disagree :) |
littlewu2508
added a commit
to littlewu2508/rocm_smi_lib
that referenced
this issue
Jan 1, 2024
In case amdgpu is builtin Closes: ROCm#102 Signed-off-by: YiyangWu <[email protected]>
littlewu2508
added a commit
to littlewu2508/rocm_smi_lib
that referenced
this issue
Jan 1, 2024
In case amdgpu is builtin Closes: ROCm#102 Signed-off-by: YiyangWu <[email protected]>
Hi @dmitrii-galantsev could you check #189 out? It's based on @littlewu2508's #104 and simplifies the code a bit by not spawning a shell, as @keryell mentioned in that PR. I patched my rocm-smi with this: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This check is not valid since one can have the GPU module baked into the kernel. In that case,
lsmod
//proc/modules
won't report it.The text was updated successfully, but these errors were encountered: