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
Comments
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
or There's also another useful tool you can compile:
And type |
prabably some bug as i delete few letters from address, it works fine.... |
Thank you sooooooooo much for the help......
…On Fri, Mar 19, 2021 at 12:21 PM drakos ***@***.***> wrote:
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.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#97 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARMHY2YWKQYYVM74WY4NZLTTELX57ANCNFSM4ZOCPI6Q>
.
|
Actually, I should have mentioned to install deviceQuery first, since it gives you the exact CCAP version e.g. |
|
You must edit file named Makefile |
No need to edit the Makefile, you can pass it as a parameter when you run the |
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 |
Any suggestions please????????? |
I've seen that GeForce RTX 3090 (82x0 cores) problem before https://bitcointalk.org/index.php?topic=5112311.msg55773362#msg55773362 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. |
Somebody already changed codes for Kangaoo here : https://gitea.datahoarding.agency/ZenulAbidin/Kangaroo-256 |
i get these error after using these updated kangaroo-256 : https://gitea.datahoarding.agency/ZenulAbidin/Kangaroo-256 |
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:
This will temporarily enable core dumps until you reboot. Then compile Kangaroo again in debug mode ( |
8 GPU, cool. Need to brute-force passwords wallet.dat....no need to waste time on collisions. Write to me by mail. |
please send me your telegram id and will message you
…On Thu, Apr 1, 2021 at 5:42 AM Radar-7528 ***@***.***> wrote:
я получаю эту ошибку после использования этих обновленных kangaroo-256:
https://gitea.datahoarding.agency/ZenulAbidin/Kangaroo-256
[image: Ядро Kangaroo-256 выгружено без -g]
<https://user-images.githubusercontent.com/72907883/112721333-4a6caf80-8f29-11eb-8903-da7ad85c73d2.JPG>
я получаю эту ошибку после использования этих обновленных kangaroo-256:
https://gitea.datahoarding.agency/ZenulAbidin/Kangaroo-256
[image: Ядро Kangaroo-256 выгружено без -g]
<https://user-images.githubusercontent.com/72907883/112721333-4a6caf80-8f29-11eb-8903-da7ad85c73d2.JPG>
8 GPU, cool. Need to brute-force passwords wallet.dat....no need to waste
time on collisions. Write to me by mail.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#97 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARMHY25GKZNWWD4OKYP3WG3TGO25TANCNFSM4ZOCPI6Q>
.
|
|
please guide me if anybody has done it.....
The text was updated successfully, but these errors were encountered: