hell_slayer
|
|
July 22, 2018, 04:24:51 PM |
|
Is there any way to decrease mining intensity ?...
Is there any way to get people to read a thread instead of asking the same question that's, literally, been asked 100 times and answered by dev on the exact same page the newest ask is on? FFS, it's not like you even had to dig through every page (but rather just 12 posts back). yeap , my bad ... sometimes I'm too lazy Seems like modification of mining intensity not working on current version of miner , I hope EWBF will fix it in next versions
|
|
|
|
swisstrader
|
|
July 23, 2018, 01:01:57 PM |
|
v0.4 is unstable and disconnects the GPUs, I switched back to v0.3 and works fine again.
|
|
|
|
000jocker000
Newbie
Offline
Activity: 1
Merit: 0
|
|
July 23, 2018, 01:30:13 PM |
|
v0.4 works rather good +5% sol\s increase
|
|
|
|
longphiphi
Newbie
Offline
Activity: 13
Merit: 0
|
|
July 23, 2018, 02:26:41 PM |
|
I'm too . I can't decrease intensity . i=0 Is there any way to decrease mining intensity ?...
Is there any way to get people to read a thread instead of asking the same question that's, literally, been asked 100 times and answered by dev on the exact same page the newest ask is on? FFS, it's not like you even had to dig through every page (but rather just 12 posts back). yeap , my bad ... sometimes I'm too lazy Seems like modification of mining intensity not working on current version of miner , I hope EWBF will fix it in next versions
|
|
|
|
cryptdough5
Newbie
Offline
Activity: 2
Merit: 0
|
|
July 23, 2018, 04:26:35 PM |
|
Why is it not possible to mine this with AMD cards? Might be a stupid question but I'd like to understand how that works?
Because it's like trying to put Chevy parts in a Ford; they just aren't made the same and it takes special items to be able to fit both. Oh ok do you mind explaining how so? Is this something that could eventually be mined with AMD cards?
|
|
|
|
ComputerGenie
|
|
July 23, 2018, 04:50:30 PM |
|
Why is it not possible to mine this with AMD cards? Might be a stupid question but I'd like to understand how that works?
Because it's like trying to put Chevy parts in a Ford; they just aren't made the same and it takes special items to be able to fit both. Oh ok do you mind explaining how so? Is this something that could eventually be mined with AMD cards? No. Yes.
|
If you have to ask "why?", you wouldn`t understand my answer. Always be on the look out, because you never know when you'll be stalked by hit-men that eat nothing but cream cheese....
|
|
|
pinpins
|
|
July 23, 2018, 08:21:15 PM Last edit: July 24, 2018, 10:36:21 AM by pinpins |
|
Hi devs
nvm, I got answer in PM
pinpin
|
|
|
|
mytiburon
Newbie
Offline
Activity: 31
Merit: 0
|
|
July 23, 2018, 09:32:07 PM |
|
V0.4 is SLOWER by 5% ASUS 1080ti. Back to V0.3
|
|
|
|
topteam
Newbie
Offline
Activity: 157
Merit: 0
|
|
July 24, 2018, 10:50:36 AM Last edit: July 24, 2018, 11:24:43 AM by topteam |
|
v0.4 crash, back to the v0.3 (ubuntu, cuda 9.2, splitters) no real time log write to the syslog, can you fix it? Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU1 Accepted share 46ms [A:10, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU0 Accepted share 46ms [A:6, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 62C GPU1: 52C GPU2: 60C GPU3: 58C GPU4: 60C GPU5: 51C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 37 Sol/s GPU1: 37 Sol/s GPU2: 37 Sol/s GPU3: 39 Sol/s GPU4: 38 Sol/s GPU5: 38 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 226 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU2 Accepted share 49ms [A:4, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU1 Accepted share 45ms [A:11, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU0 Accepted share 46ms [A:7, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Detected new work: 8138 Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU2 Accepted share 45ms [A:5, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU0 Accepted share 45ms [A:8, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 62C GPU1: 52C GPU2: 61C GPU3: 58C GPU4: 61C GPU5: 51C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 39 Sol/s GPU1: 39 Sol/s GPU2: 40 Sol/s GPU3: 37 Sol/s GPU4: 37 Sol/s GPU5: 38 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 230 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 62C GPU1: 52C GPU2: 61C GPU3: 58C GPU4: 62C GPU5: 51C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 37 Sol/s GPU1: 37 Sol/s GPU2: 37 Sol/s GPU3: 38 Sol/s GPU4: 37 Sol/s GPU5: 37 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 223 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Detected new work: 8139 Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU5 Accepted share 46ms [A:4, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 62C GPU1: 52C GPU2: 61C GPU3: 59C GPU4: 61C GPU5: 51C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 37 Sol/s GPU1: 36 Sol/s GPU2: 36 Sol/s GPU3: 38 Sol/s GPU4: 37 Sol/s GPU5: 36 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 220 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 62C GPU1: 52C GPU2: 61C GPU3: 59C GPU4: 62C GPU5: 51C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 38 Sol/s GPU1: 37 Sol/s GPU2: 38 Sol/s GPU3: 39 Sol/s GPU4: 37 Sol/s GPU5: 38 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 227 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU4 Accepted share 45ms [A:3, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Target: 000fe5451d97c28a... Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Detected new work: 813a Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU0 Accepted share 48ms [A:9, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 62C GPU1: 52C GPU2: 62C GPU3: 59C GPU4: 62C GPU5: 51C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 37 Sol/s GPU1: 38 Sol/s GPU2: 38 Sol/s GPU3: 39 Sol/s GPU4: 35 Sol/s GPU5: 38 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 225 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU2 Accepted share 45ms [A:6, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU5 Accepted share 45ms [A:5, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 62C GPU1: 52C GPU2: 61C GPU3: 59C GPU4: 62C GPU5: 51C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 38 Sol/s GPU1: 39 Sol/s GPU2: 36 Sol/s GPU3: 35 Sol/s GPU4: 36 Sol/s GPU5: 37 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 221 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Detected new work: 813b Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 62C GPU1: 53C GPU2: 62C GPU3: 59C GPU4: 62C GPU5: 52C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 37 Sol/s GPU1: 39 Sol/s GPU2: 36 Sol/s GPU3: 38 Sol/s GPU4: 38 Sol/s GPU5: 38 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 226 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU3 Accepted share 46ms [A:6, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU2 Accepted share 45ms [A:7, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Detected new work: 813c Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 62C GPU1: 52C GPU2: 62C GPU3: 59C GPU4: 62C GPU5: 52C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 37 Sol/s GPU1: 40 Sol/s GPU2: 37 Sol/s GPU3: 40 Sol/s GPU4: 36 Sol/s GPU5: 37 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 227 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU4 Accepted share 45ms [A:4, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 63C GPU1: 52C GPU2: 62C GPU3: 60C GPU4: 62C GPU5: 52C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 38 Sol/s GPU1: 38 Sol/s GPU2: 37 Sol/s GPU3: 38 Sol/s GPU4: 37 Sol/s GPU5: 38 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 226 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU3 Accepted share 45ms [A:7, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Detected new work: 813d Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 63C GPU1: 53C GPU2: 62C GPU3: 60C GPU4: 63C GPU5: 52C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 38 Sol/s GPU1: 38 Sol/s GPU2: 38 Sol/s GPU3: 38 Sol/s GPU4: 39 Sol/s GPU5: 37 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 228 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU1 Accepted share 46ms [A:12, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU4 Accepted share 47ms [A:5, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 63C GPU1: 53C GPU2: 62C GPU3: 60C GPU4: 63C GPU5: 52C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 37 Sol/s GPU1: 38 Sol/s GPU2: 36 Sol/s GPU3: 36 Sol/s GPU4: 37 Sol/s GPU5: 37 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 221 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU0 Accepted share 46ms [A:10, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU4 Accepted share 45ms [A:6, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Detected new work: 813e Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU1 Accepted share 45ms [A:13, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 63C GPU1: 53C GPU2: 62C GPU3: 60C GPU4: 63C GPU5: 52C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 37 Sol/s GPU1: 37 Sol/s GPU2: 36 Sol/s GPU3: 37 Sol/s GPU4: 36 Sol/s GPU5: 39 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 222 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Detected new work: 813f Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 63C GPU1: 53C GPU2: 62C GPU3: 60C GPU4: 63C GPU5: 52C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 37 Sol/s GPU1: 38 Sol/s GPU2: 38 Sol/s GPU3: 38 Sol/s GPU4: 38 Sol/s GPU5: 36 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 225 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU4 Accepted share 46ms [A:7, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Target: 000e73561ae70df2... Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: Detected new work: 8140 Jul 24 13:41:51 rig1 miner.sh[1567]: Temp: GPU0: 63C GPU1: 53C GPU2: 62C GPU3: 60C GPU4: 63C GPU5: 52C Jul 24 13:41:51 rig1 miner.sh[1567]: GPU0: 35 Sol/s GPU1: 37 Sol/s GPU2: 39 Sol/s GPU3: 38 Sol/s GPU4: 37 Sol/s GPU5: 38 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: Total speed: 224 Sol/s Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU4 Accepted share 49ms [A:8, R:0] Jul 24 13:41:51 rig1 miner.sh[1567]: INFO: GPU2 Accepted share 46ms [A:8, R:0]
|
|
|
|
meinerneiner
Newbie
Offline
Activity: 11
Merit: 0
|
|
July 24, 2018, 01:31:24 PM |
|
Sanity check needed here guys - I've been running 0.3 and now 0.4 with success but have always used the miner files labelled "...cuda8" - it occurs to me that maybe thats not the right, most efficient miner to use - I am running Win10 on all machines, latest patches, etc and using modern Nvidia GPU's like the 1080, 1070 with latest Nvidia driver.
Can ewbf or someone clarify and maybe update the first post to include a pointer on which file to use under which Windows circumstance.
|
|
|
|
Vokas123
Newbie
Offline
Activity: 73
Merit: 0
|
|
July 24, 2018, 01:40:00 PM |
|
Cuda is related to Nvidia drivers that you have. Older display drivers use cuda 7.5, 8,.. etc and recent drivers use 9+ (most recent driver use cuda 9.2). You can run miner for cuda 8 although you have cuda 9 (but not vice versa). What is best for you, you'll have to test. Sometimes versions for older cuda work better and faster than versions for newer cuda.
|
|
|
|
meinerneiner
Newbie
Offline
Activity: 11
Merit: 0
|
|
July 24, 2018, 06:34:06 PM |
|
Cuda is related to Nvidia drivers that you have. Older display drivers use cuda 7.5, 8,.. etc and recent drivers use 9+ (most recent driver use cuda 9.2). You can run miner for cuda 8 although you have cuda 9 (but not vice versa). What is best for you, you'll have to test. Sometimes versions for older cuda work better and faster than versions for newer cuda.
Interesting, thank you. I think I should at least try using the miner for newer cuda, it seems that it would be more appropriate, at least in theory. Thanks a ton, any other feedback welcome of course.
|
|
|
|
skuma
Newbie
Offline
Activity: 1
Merit: 0
|
|
July 25, 2018, 01:44:11 AM |
|
I have this problem all time:
04.07.2018 13:45:52 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable" 04.07.2018 13:45:52 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable" 04.07.2018 13:45:53 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable" 04.07.2018 13:45:53 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable" 04.07.2018 13:45:53 CUDA: Device: 5 Thread exited with message: "all CUDA-capable devices are busy or unavailable" 04.07.2018 13:45:53 WARNING: Looks like GPU0 are stopped. Restarting... 04.07.2018 13:45:53 INFO: GPU0 are restarted. 04.07.2018 13:45:53 WARNING: Looks like GPU1 are stopped. Restarting... 04.07.2018 13:45:53 INFO: GPU1 are restarted. 04.07.2018 13:45:54 WARNING: Looks like GPU2 are stopped. Restarting... 04.07.2018 13:45:54 INFO: GPU2 are restarted. 04.07.2018 13:45:54 WARNING: Looks like GPU3 are stopped. Restarting... 04.07.2018 13:45:54 INFO: GPU3 are restarted. 04.07.2018 13:45:54 WARNING: Looks like GPU4 are stopped. Restarting... 04.07.2018 13:45:54 INFO: GPU4 are restarted. 04.07.2018 13:45:54 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable" 04.07.2018 13:45:54 WARNING: Looks like GPU5 are stopped. Restarting... 04.07.2018 13:45:54 INFO: GPU5 are restarted.
I have 6x 1070 ti, the OC is ok i think, 65 TDP, 180 core, 550 memory, windows 10. Thanks for helps.
Not enough info: pool? size of virtual memory? v0.2 or v.03 miner? bat file settings? suprnova.cc 20000 virtual v0.3 miner --algo 144_5 --pers BgoldPoW --server btg.suprnova.cc --port 8866 --user user.user --pass x --pec --log 2 pause I have tried to remove all the OC and it works stable for more than 15 hours, so I guess it was too much OC, but I do not think I had much OC. I also have this problem since July 2018 I have this problem with 0.3 & 0.4 version - my cards didn't overclocked - when I see that problem my cards work normally (I can adjust the fan) - I close tool and run again, it's normal - someone said to increase "virtual memory" (but someone said It's still not work) My info suprnova.cc 67000 virtual v0.4 miner -U --algo 144_5 --pers BgoldPoW --server btg.suprnova.cc --user user.user --pass x --port 8866 --i=22 --api How can I fix this problem ?
|
|
|
|
minefarmbuy
Full Member
Offline
Activity: 1022
Merit: 221
We are not retail.
|
|
July 25, 2018, 05:20:48 AM |
|
So far cuda 8 of the latest version (0.4) has been fine for my 1070 ti's. haven't fine tuned clocks yet but cards are stable so far with 100 pwr / +150 core /+500-600 Mem.
odd thing is I cant create a batch file to run off of in winX. I have to modify the miner.cfg file and run the miner.exe directly to connect to suprnova.cc at least. Nothing else has worked.
I'll update final clocks as they come, but sure others have beat me to some good numbers.
|
|
|
|
shashilx
Newbie
Offline
Activity: 7
Merit: 0
|
|
July 25, 2018, 08:54:09 AM |
|
can't understand what algo I need to put to mine ZEC. Also can't understand why sols per sec is so small.
|
|
|
|
twente-mining
Member
Offline
Activity: 176
Merit: 10
|
|
July 25, 2018, 09:43:43 AM |
|
So far cuda 8 of the latest version (0.4) has been fine for my 1070 ti's. haven't fine tuned clocks yet but cards are stable so far with 100 pwr / +150 core /+500-600 Mem.
odd thing is I cant create a batch file to run off of in winX. I have to modify the miner.cfg file and run the miner.exe directly to connect to suprnova.cc at least. Nothing else has worked.
I'll update final clocks as they come, but sure others have beat me to some good numbers.
Use batfile : miner --algo 144_5 --server btg.suprnova.cc --port 8866 --user username.rigname --pass x --pers BgoldPoW I have a few 1070ti of my own, my settings are 65 power / +125 core / + 550 mem ... Getting around 38 Sols, on low power and low temps...
|
▄▄▄▄▄▄▄▄▄▄▄▄
|
|
|
unc0nnected
Newbie
Offline
Activity: 21
Merit: 0
|
|
July 25, 2018, 11:52:21 AM |
|
Running .4 and using Zhash for the new BTG Fork and am getting a ton of rejected shares. I've tried with and without afterburner running so the OC isn't causing this GPU0: 603 Sol/s GPU1: 385 Sol/s GPU2: 705 Sol/s Total speed: 1693 Sol/s INFO 07:51:15: GPU0 Rejected share 203ms [A:0, R:38] INFO 07:51:16: GPU0 Rejected share 250ms [A:0, R:39] INFO 07:51:18: GPU1 Rejected share 187ms [A:0, R:17] INFO 07:51:24: GPU2 Rejected share 206ms [A:0, R:39] INFO 07:51:26: GPU2 Rejected share 187ms [A:0, R:40] INFO 07:51:26: GPU1 Rejected share 189ms [A:0, R:18] INFO 07:51:29: GPU1 Rejected share 203ms [A:0, R:19] INFO 07:51:31: GPU1 Rejected share 191ms [A:0, R:20] INFO 07:51:34: GPU2 DevFee Accepted share INFO 07:51:36: GPU2 DevFee Accepted share
|
|
|
|
cashtrader$$$
Newbie
Offline
Activity: 28
Merit: 0
|
|
July 25, 2018, 01:27:57 PM |
|
Can the EWBF miner not include other algos? Such as neoscrypt, keccak, x16r, etc.
|
|
|
|
ComputerGenie
|
|
July 25, 2018, 01:37:13 PM |
|
Can the EWBF miner not include other algos? Such as neoscrypt, keccak, x16r, etc.
It could, but then it wouldn't be EWBF's Cuda Equihash Miner.
|
If you have to ask "why?", you wouldn`t understand my answer. Always be on the look out, because you never know when you'll be stalked by hit-men that eat nothing but cream cheese....
|
|
|
DGBfanster
Member
Offline
Activity: 122
Merit: 10
|
|
July 25, 2018, 01:53:19 PM |
|
WARNING: Looks like GPU0 are stopped. Restarting...
Is there a way to make the miner auto close and reopen when this happens? This error is very random and has nothing to do with overclocking.
|
|
|
|
|