Skip to content
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

How to compile RTX 3090 with vanity search on ubuntu(VM)? #97

Closed
siupune opened this issue Mar 19, 2021 · 19 comments
Closed

How to compile RTX 3090 with vanity search on ubuntu(VM)? #97

siupune opened this issue Mar 19, 2021 · 19 comments

Comments

@siupune
Copy link

siupune commented Mar 19, 2021

please guide me if anybody has done it.....

@Jolly-Pirate
Copy link

First, install the CUDA toolkit https://developer.nvidia.com/cuda-downloads , the download and install instructions are given there, I recommend you do the "deb (local)" intallation, it's easier and less problematic than the "runfile (local) "method. Then do this too sudo apt -y install nvidia-cuda-toolkit, and reboot (you have to do that).
Check the nvcc version with nvcc --version and run nvidia-smi to check CUDA and the drivers are all good.
Clone the VanitySearch repo and build with:

git clone https://github.com/JeanLucPons/VanitySearch
cd VanitySearch
make gpu=1 CCAP=8.0 CUDA=/usr/local/cuda-11.2 CXXCUDA=/usr/bin/g++ all

or
make gpu=1 CCAP=8.6 CUDA=/usr/local/cuda-11.2 CXXCUDA=/usr/bin/g++ all
I'm not sure which CCAP version is the one for RTX 3090, and of course use the appropriate CUDA version you installed, e.g. CUDA=/usr/local/cuda-11.2, then you should have a VanitySearch binary that you can run with ./VanitySearch. You can copy it to your $HOME/bin folder so it will be accessible from any other folder, and you can run it directly by typing VanitySearch (no need for the ./

There's also another useful tool you can compile:

cd /usr/local/cuda-11.2/samples/1_Utilities/deviceQuery
sudo make
sudo cp deviceQuery /usr/bin/

And type deviceQuery for a detailed info about your GPU.

@siupune
Copy link
Author

siupune commented Mar 22, 2021

prabably some bug as i delete few letters from address, it works fine....

@siupune
Copy link
Author

siupune commented Mar 22, 2021 via email

@Jolly-Pirate
Copy link

Jolly-Pirate commented Mar 22, 2021

Thank you sooooooooo much for the help......

Actually, I should have mentioned to install deviceQuery first, since it gives you the exact CCAP version e.g. CUDA Capability Major/Minor version number: 7.5. From what I've read on forums and comments, it's 8.6 for the RTX 3090.

@siupune
Copy link
Author

siupune commented Mar 23, 2021

i checked kangaroo with ubuntu 20.04 with rtx 3090 and showed these
errors....
kangaroo error

@siupune
Copy link
Author

siupune commented Mar 23, 2021

First, install the CUDA toolkit https://developer.nvidia.com/cuda-downloads , the download and install instructions are given there, I recommend you do the "deb (local)" intallation, it's easier and less problematic than the "runfile (local) "method. Then do this too sudo apt -y install nvidia-cuda-toolkit, and reboot (you have to do that).
Check the nvcc version with nvcc --version and run nvidia-smi to check CUDA and the drivers are all good.
Clone the VanitySearch repo and build with:

git clone https://github.com/JeanLucPons/VanitySearch
cd VanitySearch
make gpu=1 CCAP=8.0 CUDA=/usr/local/cuda-11.2 CXXCUDA=/usr/bin/g++ all

or
make gpu=1 CCAP=8.6 CUDA=/usr/local/cuda-11.2 CXXCUDA=/usr/bin/g++ all
I'm not sure which CCAP version is the one for RTX 3090, and of course use the appropriate CUDA version you installed, e.g. CUDA=/usr/local/cuda-11.2, then you should have a VanitySearch binary that you can run with ./VanitySearch. You can copy it to your $HOME/bin folder so it will be accessible from any other folder, and you can run it directly by typing VanitySearch (no need for the ./

There's also another useful tool you can compile:

cd /usr/local/cuda-11.2/samples/1_Utilities/deviceQuery
sudo make
sudo cp deviceQuery /usr/bin/

And type deviceQuery for a detailed info about your GPU.

@siupune siupune closed this as completed Mar 23, 2021
@siupune siupune reopened this Mar 23, 2021
@Jolly-Pirate
Copy link

Jolly-Pirate commented Mar 23, 2021

i checked kangaroo with ubuntu 20.04 with rtx 3090 and showed these
errors....
kangaroo error

Kangaroo uses the old ccap make switch, so change CCAP=8.6 to ccap=86. You can determine that by looking at the Makefile, and it's also in the README of Kangaroo.

@ZielarPL
Copy link

You must edit file named Makefile
Go to the lines 62 and 65 and change "$(ccap)" to "86"

@Jolly-Pirate
Copy link

You must edit file named Makefile
Go to the lines 62 and 65 and change "$(ccap)" to "86"

No need to edit the Makefile, you can pass it as a parameter when you run the make command. Besides, it can be tedious to edit everytime if you have multiple and different GPUs.

@ZielarPL
Copy link

When i try compile few weeks ago - set CCAP=86 give that same error what when use 8.6 so i write checked solution to solve that problem

@siupune
Copy link
Author

siupune commented Mar 24, 2021

its not setting full cuda cores( 82x 0)
image

@siupune
Copy link
Author

siupune commented Mar 26, 2021

Any suggestions please?????????

@Jolly-Pirate
Copy link

Jolly-Pirate commented Mar 26, 2021

I've seen that GeForce RTX 3090 (82x0 cores) problem before https://bitcointalk.org/index.php?topic=5112311.msg55773362#msg55773362
Not sure if it was resolved. Can you try downgrading to CUDA 11.1 and recompile it? You can get it here https://developer.nvidia.com/cuda-toolkit-archive

Also, in later responses on the forum https://bitcointalk.org/index.php?topic=5112311.msg56537112#msg56537112, it seems many are having problems with RTX 30xx. Clearly the code of VanitySearch and Kangaroo need proper updating/optimization for those cards.

@siupune
Copy link
Author

siupune commented Mar 27, 2021

Somebody already changed codes for Kangaoo here : https://gitea.datahoarding.agency/ZenulAbidin/Kangaroo-256
just change last line in GPUEngine.cu 86 , 128 not 64. thats all but i came across Segmentation broken(core dumped)

@siupune
Copy link
Author

siupune commented Mar 27, 2021

i get these error after using these updated kangaroo-256 : https://gitea.datahoarding.agency/ZenulAbidin/Kangaroo-256

Kangaroo-256 core dumped witout -g

@ZenulAbidin
Copy link

ZenulAbidin commented Mar 29, 2021

Somebody already changed codes for Kangaoo here : https://gitea.datahoarding.agency/ZenulAbidin/Kangaroo-256
just change last line in GPUEngine.cu 86 , 128 not 64. thats all but i came across Segmentation broken(core dumped)

Fork author here.

If modification to 128 SMs doesn't work then just leave it at the default 64, some A100 cards have less than 128 SMs: https://www.guru3d.com/news-story/nvidia-tesla-a100-with-ga100-ampere-gpu-spotted.html

Now for further debugging I need you to upload a core dump for me.

Run this command as root:

echo "/tmp/cores/core.%e.%p.%h.%t" > /proc/sys/kernel/core_pattern

This will temporarily enable core dumps until you reboot.

Then compile Kangaroo again in debug mode (make gpu=1 debug=1) and run the program again and then look for a file called "/tmp/cores/core.something.something.something.something". Upload it so that I can inspect it locally.

@siupune siupune closed this as completed Mar 31, 2021
@Radar-7528
Copy link

я получаю эту ошибку после использования этих обновленных kangaroo-256: https://gitea.datahoarding.agency/ZenulAbidin/Kangaroo-256

Ядро Kangaroo-256 выгружено без -g

я получаю эту ошибку после использования этих обновленных kangaroo-256: https://gitea.datahoarding.agency/ZenulAbidin/Kangaroo-256

Ядро Kangaroo-256 выгружено без -g

8 GPU, cool. Need to brute-force passwords wallet.dat....no need to waste time on collisions. Write to me by mail.

@siupune
Copy link
Author

siupune commented Apr 3, 2021 via email

@Radar-7528
Copy link

please send me your telegram id and will message you
ok. https://t.me/G_Rodary

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

No branches or pull requests

5 participants