-
Notifications
You must be signed in to change notification settings - Fork 9
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
pycuda issue with CUDA toolkit 12.0 #39
Comments
Hi, It works on cuda 10. I am already surprised that you manage to make it work with cuda 11. It's also not working using the last version of pycuda. I just used a commit of beginning of 2021 (when it was working) and it works for the docker. So basically the solution will be to downgrade your versions and drivers. If you want to use it without downgrading you drivers, you can use the docker either locally or your computer (see installation in the readme) or using galaxy. It has been installed on the european galaxy server. You can find it at this address: https://usegalaxy.eu/?tool_id=instagraal&version=0.1.6. Amaury |
Hi @ABignaud thanks a lot for the info, I believe I will resort to Docker, as I'm not a big fan of Galaxy (also I believe at this point without a payed account on Galaxy my machine would perform much better). With that said, the only thing concerning me about Docker is this:
which I'm not entirely sure how to manage, or whether I already have this requisite satisfied. Please, let me know since you could make it work on Docker. Thanks! P. S. Is there, by any chance, interest of having |
Hi, Nvidia-docker2 is just a "docker package" to allow to setup nvidia in a docker container. Once it's installed just pull the image and run it with the gpus option. it will run as the normal container. You just won't have the graphical plot during the scaffolding. For the PS question, actually there are no one in the lab with enough knowledge and time to do it. We are just maintaining it and providing docker or others stuff to be able to use with modern configuration. Thus, there are no plan to tune it for cuda 12. However if you want to do a pull request or if you know someone who want to do one, we will welcome it. Amaury |
Hi @ABignaud I got my I'm in contact with some people on the NVIDIA forum, maybe I will switch back to CUDA toolkit |
Hi, |
@ABignaud good to know! For now I'm just trying to get it to work; in fact, when I launch it from
I get this error message
Which seems to be addressed here #13 and here #20, but for some reason it still prompts me with this message. Maybe there is something wrong with my command? |
It seems that you don't have the permission access while you mount your folder in the docker repository. Can you try changing the permissions to all before running the docker: Also add a working directory in the docker run command to write the log file in a folder where you have the permission. docker run \
--gpus all \
--workdir $WORKDIR \
--mount "type=bind,src=$WORKDIR,dst=$WORKDIR" \
koszullab/instagraal |
Hi @ABignaud thanks a lot this solve the issue! If one day there will be the chance for someone to work on |
Hi there,
I've been using
instaGRAAL
for a while and recently happen to upgrade my GPU. I then installed the most recent version of NVIDIA Drivers, see belowand CUDA toolkit
Unfortunately, for some reason after pyramids build correctly and the tool starts loading them, I get prompted with the following error
which at first seemed to be related to
kernel.cu
but even after following the procedure in issue #18, the problem persists. So, at a first thought I believed something might have changed from CUDA toolkit 11 to 12 so that those lines in the kernel_sparse.cu and in the kernel_sparse_adapt.cu which should handle the changes in thev11
are no longer robust to the latest NVIDIA updates.Alternatively, it could be an issue with the most recent version of
pycuda
, the problem is that I tried to go back to last year's version2021.1
but I'm not allowed to, possibly because of the newer implementation of the NVIDIA Driver and toolkit.Please, let me know whether there is a solution to this, thanks!
The text was updated successfully, but these errors were encountered: