cgladue
Member
 Offline
Activity: 97
Merit: 10
|
 |
June 14, 2014, 03:02:18 PM |
|
To the dev: what is being done to fix the crashing/hanging of the computer when switching from X11/x13 back to scrypt-n ?
this is a huge issue
Pretty much just don't use it for that, right now. If you are living in an area where you can mine scrypt-n without it being unbearably hot, then I would just do so for a few hours a day with another mining program right now, since it's been the dominant profitable algorithm on nicehash now for 3 days straight. You're not missing anything with these shitty rental rates and profitability right now amongst x11/x13. yea thats what im doing right now, but at any time it can go the other way... my power is free so i dont care about heat or ower at the moment i just have my rigs mining scrypt/scrypt-n at the moment ... id just like to a) make sure the devs know its a reproduceable problem and b) that it needs to be corrected soon i have a workaround at the moment but sometime it will become more of a headache |
|
|
|
|
|
|
|
|
|
|
Every time a block is mined, a certain amount of BTC (called the
subsidy) is created out of thin air and given to the miner. The
subsidy halves every four years and will reach 0 in about 130 years.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
platinum4
|
|
June 14, 2014, 03:11:51 PM |
|
yea thats what im doing right now, but at any time it can go the other way... my power is free so i dont care about heat or ower at the moment i just have my rigs mining scrypt/scrypt-n at the moment ... id just like to a) make sure the devs know its a reproduceable problem and b) that it needs to be corrected soon i have a workaround at the moment but sometime it will become more of a headache
They know -- https://github.com/sgminer-dev/sgminer/issues/246TL;DR - "But back to the point, I spent some time looking at what could be causing this weird bug with scrypt kernels, but I have no idea at all yet :/" |
|
|
|
|
cgladue
Member
Offline
Activity: 97
Merit: 10
|
|
June 14, 2014, 03:44:08 PM |
|
yea thats what im doing right now, but at any time it can go the other way... my power is free so i dont care about heat or ower at the moment i just have my rigs mining scrypt/scrypt-n at the moment ... id just like to a) make sure the devs know its a reproduceable problem and b) that it needs to be corrected soon i have a workaround at the moment but sometime it will become more of a headache
They know -- https://github.com/sgminer-dev/sgminer/issues/246TL;DR - "But back to the point, I spent some time looking at what could be causing this weird bug with scrypt kernels, but I have no idea at all yet :/" thats not the error i get, i never get -4 enqueueing error mine just go DEAD, and the pc freezes but only when switching algos and only when X11/X13 to Scrypt-N scrypt to scrypt-n is fine x11-to x13 is fine scrypt n by itself fine its weird |
|
|
|
|
kenshirothefist (OP)
|
|
June 14, 2014, 04:05:28 PM
Last edit: June 15, 2014, 09:35:52 AM by kenshirothefist |
|
Yep, it's undoubtedly broke. I'm going to stick to 1 algorithm since it seems Scrypt and N-Scrypt are neck-to-neck right now.
Yup i'm with you. Ill go back to standard mining until NiceHash Guys start posting what they are doing to address these issues Hi. Much as we'd like to, we (NiceHash) can't do much to address various sgminer_v5 issues. NiceHash auto-switching service is running very stable, however, there are still some issues, need to be addressed regarding the sgminer_v5 itself. As I mentioned in the first post, we've sponsored the development of new sgminer, but haven't been involved in the development itself. sgminer_v5 is still in beta and mrbrdo, the lead developer of the sgminer kernel switching functionality obviously underestimated the difficulty of the kernel switching implementation. sgminer v5 with kernel switching has been tested in our labs and is working fine with basic (no overclocking or special tuning) GPU configuration (also, many users are successfully using this functionality on our service for quite some time now). However, AMD GPU world is extremely diverse and there are many combinations and configurations of various GPU+OS+drivers+overclocking+tuning that obviously raises issues and instability with kernel switching functionality as reported by the community and beta testers. I'm sure that mrbrdo and other sgminer developers will address all these issues and will have a stable working solution for various GPU+OS+drivers+overclocking+tuning combination in the near future. The community involvement is very important with reports on issues and help with testing - it has been like this from the early development of cgminer (I'm sure some of you remembers issues when fist Bitcoin ASICs arrived, etc.) and all later forks and versions. Therefore I ask you for help with reporting issues to https://github.com/sgminer-dev/sgminer/issues. The most useful reports are the one with 100% repeatable scenario and with the debug log files "sgminer ... -D 2>>sgminer.log" attached to issue reports. One of the currently most problematic issue is the one with pool-gpu-engine and pool-gpu-memclock not being evaluated correctly when switching algorithms ( https://github.com/sgminer-dev/sgminer/issues/265). This might cause freezes, lower hashrate, died GPU's, etc. Therefore I ask you to test the auto-switching functionality without setting different engine and mem clock per pool/algo - use the same engine and mem speed for all algos and use explicit low-high specification to disable engine/mem throttling. And start by using default/stock engine/settings! Also, make sure you specify low enough thread-concurrency for scrypt-N - test with various low enough settings if you're getting "-4 enqueueing error" and make sure you're using at least "worksize" : "256" for scrypt-N if you're seeing issues with scrypt-N (for now, worksize can't be configured in a per-pool fashion). Last, but not least, make sure you're using the latest version from https://nicehash.com/software/#sgminer. Here is an example of 100% working configuration for a rig with 5x Radeon R9 290 on Linux where switching between all algorithms with all combinations works 100% correct without any GPU issues and with decent hashrate scrypt: 840 khs scryptN: 420 khs X11: 3.15 Mhs X13: 2.25 Mhs keccak: 390 Mhs {
"pools" : [
{
"name" : "NiceHash_Scrypt_AS",
"url" : "stratum+tcp://stratum.nicehash.com:4333",
"user" : "BTC_addr",
"pass" : "d=1024",
"pool-algorithm" : "zuikkis",
"pool-nfactor" : "10",
"pool-thread-concurrency" : "20481",
"pool-gpu-engine" : "947-947",
"pool-gpu-memclock" : "1250-1250",
"pool-gpu-threads" : "1"
},
{
"name" : "NiceHash_Scrypt-N_AS",
"url" : "stratum+tcp://stratum.nicehash.com:4335",
"user" : "BTC_addr",
"pass" : "d=512",
"pool-algorithm" : "zuikkis",
"pool-nfactor" : "11",
"pool-thread-concurrency" : "20481",
"pool-gpu-engine" : "947-947",
"pool-gpu-memclock" : "1250-1250",
"pool-gpu-threads" : "1"
},
{
"name" : "NiceHash_X11_AS",
"url" : "stratum+tcp://stratum.nicehash.com:4336",
"user" : "BTC_addr",
"pass" : "d=0.08",
"pool-algorithm" : "darkcoin-mod",
"pool-nfactor" : "10",
"pool-thread-concurrency" : "20481",
"pool-gpu-engine" : "947-947",
"pool-gpu-memclock" : "1250-1250",
"pool-gpu-threads" : "2"
},
{
"name" : "NiceHash_X13_AS",
"url" : "stratum+tcp://stratum.nicehash.com:4337",
"user" : "BTC_addr",
"pass" : "d=0.08",
"pool-algorithm" : "marucoin-mod",
"pool-nfactor" : "10",
"pool-thread-concurrency" : "20481",
"pool-gpu-engine" : "947-947",
"pool-gpu-memclock" : "1250-1250",
"pool-gpu-threads" : "2"
},
{
"name" : "NiceHash_Keccak_AS",
"url" : "stratum+tcp://stratum.nicehash.com:4338",
"user" : "BTC_addr",
"pass" : "d=1024",
"pool-algorithm" : "maxcoin",
"pool-nfactor" : "10",
"pool-thread-concurrency" : "8960",
"pool-gpu-engine" : "947-947",
"pool-gpu-memclock" : "1250-1250",
"pool-gpu-threads" : "1"
}
],
"xintensity" : "300",
"vectors" : "1",
"kernel" : "ckolivas",
"lookup-gap" : "2",
"worksize" : "256",
"shaders" : "2560",
"thread-concurrency" : "20481",
"gpu-threads" : "1",
"gpu-engine" : "947-947",
"gpu-memclock" : "1250-1250",
"gpu-fan" : "0-95",
"gpu-powertune" : "20",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"auto-fan" : true,
"auto-gpu" : true,
"log" : "5",
"log-dateformat" : "1",
"failover-only" : true,
"failover-switch-delay" : "30",
"no-pool-disable" : true,
"scrypt" : true,
"queue" : "1",
"scan-time" : "7",
"expiry" : "28"
}
Regarding the dilemma on weather to use or not to use multi-switching functionality: well, as you've observed in the last few weeks there are truly big fluctuations in profitability for various algorithms and it looks like it's going to be this way in the near future as well. First there has only been Bitcoin - almost no work for miner - run and forget, then came Litecoin - more tuning for Scrypt needed; then came X-altcoins - lots of work for miner to keep up with different coin profitability - solved by multipools; and now there are X-algorithms - lots of work for miner to keep up with different algorithm profitability - to be solved by multi-algo-auto-switching. Said that - if you like to constantly watch algorithm profitability, then you can switch miners manually, but if you just want to run your miners and let them get best profit four you - well then you'll have to go with multi-algo-auto-switching. We're not quite there yet, but will be soon. |
|
|
|
|
|
lbr
|
|
June 14, 2014, 05:09:59 PM |
|
Any bounty for bug free multi-algo miner?
|
|
|
|
|
platinum4
|
|
June 14, 2014, 06:40:45 PM |
|
thats not the error i get, i never get -4 enqueueing error
mine just go DEAD, and the pc freezes but only when switching algos and only when X11/X13 to Scrypt-N scrypt to scrypt-n is fine x11-to x13 is fine scrypt n by itself fine
its weird
Interesting, I've been the one encountering DEAD cards and mrbrdo thinks it's just my particular configuration. It's not like I could stress enough that something is inherently wrong with the miner and I experience the SICK -> DEAD issue too. But they simply won't extend the timer, or address it. |
|
|
|
|
|
platinum4
|
|
June 14, 2014, 06:43:00 PM |
|
Also, the overheat issue is back whenever you encounter this crash too. If you soft-restart your rig, the next time you boot up the miner, all the temps are on overheat and it ratchets your fans up to 100%.
Something's being overlooked.
|
|
|
|
|
|
coda
|
|
June 14, 2014, 08:07:58 PM |
|
guys,
how do you enable the auto algo switching mode ?
if i launch the miner it goes to the first server in the list
(i've got 2: on X13 and one X11 on trade my bit)
it's not choosen on the profitability but in the order in the .conf
|
BTC:18oLLFcxwwzfQt4F2YF7QzKyFeksq3dqsQ
|
|
|
|
bullus
|
|
June 14, 2014, 08:22:18 PM |
|
guys,
how do you enable the auto algo switching mode ?
if i launch the miner it goes to the first server in the list
(i've got 2: on X13 and one X11 on trade my bit)
it's not choosen on the profitability but in the order in the .conf
Which port did u used? U have to use the multiport X11 MultiPort 4440 X13 MultiPort 5550 |
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
Adz
Newbie
Offline
Activity: 24
Merit: 0
|
|
June 14, 2014, 08:28:12 PM |
|
guys,
how do you enable the auto algo switching mode ?
if i launch the miner it goes to the first server in the list
(i've got 2: on X13 and one X11 on trade my bit)
it's not choosen on the profitability but in the order in the .conf
Ports need to be 4xxx for switching |
|
|
|
|
|
coda
|
|
June 14, 2014, 08:31:37 PM |
|
guys,
how do you enable the auto algo switching mode ?
if i launch the miner it goes to the first server in the list
(i've got 2: on X13 and one X11 on trade my bit)
it's not choosen on the profitability but in the order in the .conf
Which port did u used? U have to use the multiport X11 MultiPort 4440 X13 MultiPort 5550 yes i did when i start the miner without no .bin it says it's creating marucoin-modTahitigw128l8big4.bin and then after i can see 2 bin, one like this one and another ckolivasTahitigw1128l8lg2tc8192nf10.bin ... but no darkcoin-mod .bin |
BTC:18oLLFcxwwzfQt4F2YF7QzKyFeksq3dqsQ
|
|
|
|
coda
|
|
June 14, 2014, 08:37:12 PM |
|
here's my conf
{
"pools" : [
{
"name" : "trademybit x13",
"url" : "stratum+tcp://east01.us.trademybit.com:5550",
"user" : "XXX",
"pass" : "1234",
"pool-nfactor" : "10",
"pool-algorithm" : "marucoin-mod"
},
{
"name" : "trademybit x11",
"url" : "stratum+tcp://east01.us.trademybit.com:4440",
"user" : "XXX",
"pass" : "1234",
"pool-nfactor" : "10",
"pool-algorithm" : "darkcoin-mod"
}
],
"failover-only" : true,
"failover-switch-delay" : "30",
"intensity" : "18",
"vectors" : "1",
"worksize" : "128",
"lookup-gap" : "2",
"thread-concurrency" : "8192",
"gpu-threads" : "2",
"gpu-engine" : "1030",
"gpu-memclock" : "1250",
"gpu-powertune" : "20",
"temp-cutoff" : "90",
"temp-overheat" : "85",
"auto-fan" : true,
"temp-hysteresis" : "3",
"show-coindiff" : true,
"kernel-path" : "/usr/local/bin"
}
|
BTC:18oLLFcxwwzfQt4F2YF7QzKyFeksq3dqsQ
|
|
|
|
platinum4
|
|
June 14, 2014, 08:40:32 PM |
|
guys,
how do you enable the auto algo switching mode ?
if i launch the miner it goes to the first server in the list
(i've got 2: on X13 and one X11 on trade my bit)
it's not choosen on the profitability but in the order in the .conf
Which port did u used? U have to use the multiport X11 MultiPort 4440 X13 MultiPort 5550 This is partially correct, for the algo-switch ports they are x11 are :4010, for x13 they are :4011 |
|
|
|
|
|
coda
|
|
June 14, 2014, 08:44:04 PM |
|
guys,
how do you enable the auto algo switching mode ?
if i launch the miner it goes to the first server in the list
(i've got 2: on X13 and one X11 on trade my bit)
it's not choosen on the profitability but in the order in the .conf
Which port did u used? U have to use the multiport X11 MultiPort 4440 X13 MultiPort 5550 This is partially correct, for the algo-switch ports they are x11 are :4010, for x13 they are :4011 thanks i'll try it i've read this a few pages ago on one miner's conf, but i thought theses infos were obsolete and other people seems using 4440 and 5550 also, in the getting started infos of the pool it says 4440 and 5550 ...? where did you get this info ? |
BTC:18oLLFcxwwzfQt4F2YF7QzKyFeksq3dqsQ
|
|
|
|
bullus
|
|
June 14, 2014, 08:48:59 PM
Last edit: June 14, 2014, 09:05:29 PM by bullus |
|
guys,
how do you enable the auto algo switching mode ?
if i launch the miner it goes to the first server in the list
(i've got 2: on X13 and one X11 on trade my bit)
it's not choosen on the profitability but in the order in the .conf
Which port did u used? U have to use the multiport X11 MultiPort 4440 X13 MultiPort 5550 This is partially correct, for the algo-switch ports they are x11 are :4010, for x13 they are :4011 yes u are right, the faq isn't updated yet and I also use 4010 and 4011  My other rig is stable for alomost 2 days and is switching nice between x11/x13 sgminer 4.2.1 - Started: [2014-06-13 05:29:39] - [1 day 17:18:40]
--------------------------------------------------------------------------------
(5s):1.572M (avg):1.432Mh/s | A:0 R:0 HW:0 WU:0.020/m
ST: 2 SS: 0 NB: 9034 LW: 377 GF: 0 RF: 0
Connected to am02 x13 multi (stratum) diff 0.005 as user xxxx
Block: 2b92b0d9... Diff:57 Started: [22:48:14] Best share: 0.283
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 56.0C 2774RPM | 1.436M/1.445Mh/s | R: 0.0% HW:0 WU:0.021/m I:18
--------------------------------------------------------------------------------
[22:43:07] am02 x11 multi stable for 30 seconds
[22:43:07] Switching to am01 x11 multi
[22:43:20] Stratum connection to am01 x11 multi interrupted
[22:43:21] am02 x11 multi not responding!
[22:43:21] Switching to am02 x13 multi
[22:43:31] Initialising kernel marucoin-modold.cl with bitalign, unpatched BFI, nfactor 10, n 1
024
[22:43:31] Initialising kernel marucoin-modold.cl with bitalign, unpatched BFI, nfactor 10, n 1
024
[22:43:32] Accepted 2f27e145 Diff 0.021/0.005 GPU 0 at am02 x13 multi
[22:43:41] Accepted 0feec71f Diff 0.063/0.005 GPU 0 at am02 x13 multi
[22:43:42] Accepted 0387f2bc Diff 0.283/0.005 GPU 0 at am02 x13 multi
[22:43:55] Accepted 6b8c388a Diff 0.009/0.005 GPU 0 at am02 x13 multi
[22:44:39] Accepted 97403a13 Diff 0.007/0.005 GPU 0 at am02 x13 multi
[22:44:55] Accepted 5b047272 Diff 0.011/0.005 GPU 0 at am02 x13 multi
[22:45:08] Accepted b17a84c4 Diff 0.006/0.005 GPU 0 at am02 x13 multi
[22:45:22] Accepted 3a215c1f Diff 0.017/0.005 GPU 0 at am02 x13 multi
[22:46:15] Accepted 890bae5e Diff 0.007/0.005 GPU 0 at am02 x13 multi
[22:46:29] Accepted 35dda8de Diff 0.019/0.005 GPU 0 at am02 x13 multi
[22:46:35] Accepted 956dc3bb Diff 0.007/0.005 GPU 0 at am02 x13 multi
[22:47:04] Accepted 662095be Diff 0.010/0.005 GPU 0 at am02 x13 multi
[22:47:04] Accepted 3070a6b8 Diff 0.021/0.005 GPU 0 at am02 x13 multi
[22:47:06] Accepted c0967602 Diff 0.005/0.005 GPU 0 at am02 x13 multi
[22:47:10] Accepted 8832e442 Diff 0.007/0.005 GPU 0 at am02 x13 multi
[22:47:12] Accepted 4f15e377 Diff 0.013/0.005 GPU 0 at am02 x13 multi
[22:47:18] Accepted 54e6ecbe Diff 0.012/0.005 GPU 0 at am02 x13 multi
[22:48:00] Accepted 39886b27 Diff 0.017/0.005 GPU 0 at am02 x13 multi
[22:48:04] Accepted 5bfc8fa5 Diff 0.011/0.005 GPU 0 at am02 x13 multi
[22:48:16] Accepted 22e75d10 Diff 0.029/0.005 GPU 0 at am02 x13 multi
But the Accepted shares are not calculated . Also when checking pool info ,it's showing 0 info , it's not calculated continue and resets it when switching |
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
|
coda
|
|
June 14, 2014, 09:00:12 PM |
|
this seems to work fine ...
i started mining on the x11 algo, but my first server in the list is x13
thanks for the trick, i was starting to getting mad on my keyboard
|
BTC:18oLLFcxwwzfQt4F2YF7QzKyFeksq3dqsQ
|
|
|
|
bullus
|
|
June 14, 2014, 09:04:30 PM |
|
this seems to work fine ...
i started mining on the x11 algo, but my first server in the list is x13
thanks for the trick, i was starting to getting mad on my keyboard
My config with 6970 {
"pools" : [
{
"name" : "am02 x11 multi",
"url" : "stratum+tcp://am02.eu.trademybit.com:4010",
"user" : "x",
"pass" : "x",
"algorithm":"darkcoin-mod"
},
{
"name" : "am02 x13 multi",
"url" : "stratum+tcp://am02.eu.trademybit.com:4011",
"user" : "x",
"pass" : "x",
"algorithm":"marucoin-modold"
},
{
"name" : "am02 x11",
"url" : "stratum+tcp://am02.eu.trademybit.com:4440",
"user" : "x",
"pass" : "x",
"algorithm" : "darkcoin-mod"
},
{
"name" : "am02 x13 ",
"url" : "stratum+tcp://am02.eu.trademybit.com:5550",
"user" : "x",
"pass" : "x",
"algorithm" : "marucoin-modold"
},
{
"name" : "am01 x11",
"url" : "stratum+tcp://am01.eu.trademybit.com:4440",
"user" : "x",
"pass" : "x",
"algorithm" : "darkcoin-mod"
},
{
"name" : "am01 x13",
"url" : "stratum+tcp://am01.eu.trademybit.com:5550",
"user" : "x",
"pass" : "x",
"algorithm" : "marucoin-modold"
}
],
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "10",
"failover-only" : true,
"kernel-path" : "D:\\sgminer_v5_0_10062014",
"extranonce-subscribe" : true,
"log" : "5",
"queue" : "1",
"scan-time" : "7",
"shares" : "0",
"failover-switch-delay" : "30",
"gpu-threads" : "2",
"gpu-dyninterval" : "7",
"gpu-engine" : "0",
"gpu-fan" : "65",
"gpu-platform" : "0",
"gpu-memclock" : "0",
"gpu-memdiff" : "0",
"gpu-powertune" : "8",
"gpu-vddc" : "0",
"intensity" : "18",
"temp-target" : "75",
"temp-overheat" : "85",
"temp-cutoff" : "95",
"temp-hysteresis" : "3",
"vectors" : "1",
"worksize" : "64",
"lookup-gap" : "0",
"shaders" : "1536",
"thread-concurrency" : "8000",
"no-pool-disable" : true
} |
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
|
platinum4
|
|
June 14, 2014, 09:39:20 PM |
|
My other rig is stable for alomost 2 days and is switching nice between x11/x13 sgminer 4.2.1 - Started: [2014-06-13 05:29:39] - [1 day 17:18:40]
--------------------------------------------------------------------------------
(5s):1.572M (avg):1.432Mh/s | A:0 R:0 HW:0 WU:0.020/m
ST: 2 SS: 0 NB: 9034 LW: 377 GF: 0 RF: 0
Connected to am02 x13 multi (stratum) diff 0.005 as user xxxx
Block: 2b92b0d9... Diff:57 Started: [22:48:14] Best share: 0.283
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 56.0C 2774RPM | 1.436M/1.445Mh/s | R: 0.0% HW:0 WU:0.021/m I:18
--------------------------------------------------------------------------------
[22:43:07] am02 x11 multi stable for 30 seconds
[22:43:07] Switching to am01 x11 multi
[22:43:20] Stratum connection to am01 x11 multi interrupted
[22:43:21] am02 x11 multi not responding!
[22:43:21] Switching to am02 x13 multi
[22:43:31] Initialising kernel marucoin-modold.cl with bitalign, unpatched BFI, nfactor 10, n 1
024
[22:43:31] Initialising kernel marucoin-modold.cl with bitalign, unpatched BFI, nfactor 10, n 1
024
[22:43:32] Accepted 2f27e145 Diff 0.021/0.005 GPU 0 at am02 x13 multi
[22:43:41] Accepted 0feec71f Diff 0.063/0.005 GPU 0 at am02 x13 multi
[22:43:42] Accepted 0387f2bc Diff 0.283/0.005 GPU 0 at am02 x13 multi
[22:43:55] Accepted 6b8c388a Diff 0.009/0.005 GPU 0 at am02 x13 multi
[22:44:39] Accepted 97403a13 Diff 0.007/0.005 GPU 0 at am02 x13 multi
[22:44:55] Accepted 5b047272 Diff 0.011/0.005 GPU 0 at am02 x13 multi
[22:45:08] Accepted b17a84c4 Diff 0.006/0.005 GPU 0 at am02 x13 multi
[22:45:22] Accepted 3a215c1f Diff 0.017/0.005 GPU 0 at am02 x13 multi
[22:46:15] Accepted 890bae5e Diff 0.007/0.005 GPU 0 at am02 x13 multi
[22:46:29] Accepted 35dda8de Diff 0.019/0.005 GPU 0 at am02 x13 multi
[22:46:35] Accepted 956dc3bb Diff 0.007/0.005 GPU 0 at am02 x13 multi
[22:47:04] Accepted 662095be Diff 0.010/0.005 GPU 0 at am02 x13 multi
[22:47:04] Accepted 3070a6b8 Diff 0.021/0.005 GPU 0 at am02 x13 multi
[22:47:06] Accepted c0967602 Diff 0.005/0.005 GPU 0 at am02 x13 multi
[22:47:10] Accepted 8832e442 Diff 0.007/0.005 GPU 0 at am02 x13 multi
[22:47:12] Accepted 4f15e377 Diff 0.013/0.005 GPU 0 at am02 x13 multi
[22:47:18] Accepted 54e6ecbe Diff 0.012/0.005 GPU 0 at am02 x13 multi
[22:48:00] Accepted 39886b27 Diff 0.017/0.005 GPU 0 at am02 x13 multi
[22:48:04] Accepted 5bfc8fa5 Diff 0.011/0.005 GPU 0 at am02 x13 multi
[22:48:16] Accepted 22e75d10 Diff 0.029/0.005 GPU 0 at am02 x13 multi
But the Accepted shares are not calculated . Also when checking pool info ,it's showing 0 info , it's not calculated continue and resets it when switching I've already opened an issue about this, the same thing was happening with the uptime counter from issue 229. It seems everytime a new algo's bin is initialized, it wipes the stats of the GPUs and also up top it appears as well too. It'd be nice to keep running totals for each algo, as it flips, and after it flips. |
|
|
|
|
cgladue
Member
Offline
Activity: 97
Merit: 10
|
|
June 15, 2014, 01:21:16 AM |
|
thats not the error i get, i never get -4 enqueueing error
mine just go DEAD, and the pc freezes but only when switching algos and only when X11/X13 to Scrypt-N scrypt to scrypt-n is fine x11-to x13 is fine scrypt n by itself fine
its weird
Interesting, I've been the one encountering DEAD cards and mrbrdo thinks it's just my particular configuration. It's not like I could stress enough that something is inherently wrong with the miner and I experience the SICK -> DEAD issue too. But they simply won't extend the timer, or address it. exactly! mine go SICK then DEAD too, but only 2 of my 4 most of the time ... or my video driver stops responding also sometimes... |
|
|
|
|
platinum4
|
|
June 15, 2014, 01:55:08 AM |
|
thats not the error i get, i never get -4 enqueueing error
mine just go DEAD, and the pc freezes but only when switching algos and only when X11/X13 to Scrypt-N scrypt to scrypt-n is fine x11-to x13 is fine scrypt n by itself fine
its weird
Interesting, I've been the one encountering DEAD cards and mrbrdo thinks it's just my particular configuration. It's not like I could stress enough that something is inherently wrong with the miner and I experience the SICK -> DEAD issue too. But they simply won't extend the timer, or address it. exactly! mine go SICK then DEAD too, but only 2 of my 4 most of the time ... or my video driver stops responding also sometimes... I have a theory, as I've been watching this miner now for about 3 weeks straight. When the miner flips algos and initializes a new bin file, I noticed the last card/device of the mining rig always gets sick or dead, never any others. Is your environment variables GPU_SYNC_OBJECTS 1? I am going to experiment with dropping this environment variable and seeing if it has any benefit on how shares and work are being distributed amongst the cards of the rig. Report back ok. |
|
|
|
|
|
