-
Notifications
You must be signed in to change notification settings - Fork 50
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
Comments
ROCm/rocminfo#42 (comment) may help |
Closes: ROCm#102 Signed-off-by: YiyangWu <xgreenlandforwyy@gmail.com>
Fixed as of 9f6614e. Please reopen if you disagree :) |
In case amdgpu is builtin Closes: ROCm#102 Signed-off-by: YiyangWu <xgreenlandforwyy@gmail.com>
In case amdgpu is builtin Closes: ROCm#102 Signed-off-by: YiyangWu <xgreenlandforwyy@gmail.com>
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: |
Thank you very much for the PR, @LtdJorge! I will go ahead and close the issue, as the PR will resolve it and will be merged through AMD's internal system. |
… as kernel built-in. Fixes ROCm/rocm_smi_lib#102 and is an updated version of ROCm/rocm_smi_lib#104 Change-Id: Icb3abe820bc67035b822358a1c04bd09a7c22b6b Signed-off-by: Galantsev, Dmitrii <dmitrii.galantsev@amd.com> Reviewed-by: Galantsev, Dmitrii <dmitrii.galantsev@amd.com>
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: