ok so I just woke up… and I suppose your probably near bedtime now… I have 980ti and I will get them up and running. was going to wait wil my new board comes in. maybe i can rip apart an existing amd/windows rig now and get them going today. that will take me some time though as I have to put the heatsink back on the 980ti
quick question. . can you mine with GPU and CPU at the same time? if I am buying another CPU, can I get a good CPU so it can mine at the same time? and for a socket 1150 board, what would be the besat CPU for mining? E3 or i7?
and for system Ram, does that make any difference when mining with GPU? do I need a certain amount of system ram? 4G is ok? or is 8G or 16G better? if I choose to CPU and GPU mine on the same rig, then system ram will make a difference and I should have at least 8G , 16 G being better?
Thanks for your advice, I will help you out with testing 980ti, though compliling things from scratch sometimes gives me problems… i think i have only compiled from scratch twice with success. I will try to compile the miner now on my laptop with 780m… I might also be able to try other mobile cards.
If your OS doesn’t have any timing command, then maybe you can just print the time before and after running “equi1 -n 1000 -r 100” to work out the Sol/s …
in the worst case, use your stopwatch
ok, so if i install ubuntu and use that, it should post the sol/s
ubuntu 16 is ok or should I use 14? or i can use the latest version of mint? cause honestly hate that ubuntu desktop.
eitherway your interested in the total solutions number that I got at the bottom, or you need the sol/s?
does that output for 780m help you is what I mean?
you can compute Sol/s with e.g.
$ bc -l
bc 1.06.95
Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty’.
188/23.712
7.92847503373819163292
ok but i dont get those numbers because time is missing?
ill try on linux mint with the 980ti later today, should I do that?
otherwise im doing everything right? is that correct? thanks
Btw, you may want to include the latest commits that fix the XFULL definition (accidentally changed after experiment), and save lots of memory.
Also note that the major reason for my own blake implementation is to make the blake2b_compress calls eager rather than lazy, which is needed to get an actual midstate for headers longer than 128 bytes…
Currently I am working on integrating this solver into standalone miner.
Will try to integrate XFULL changes after completing cuda & standalone changes.
Sarath, This looks fantastic! … Cannot wait to try them both, the Cuda and the new improved CPU jobbie, pity i’ve got to work now
Thanks a Million !!!
Put your BTC addr here for some tips !!!