Bjorn_Blockchain
Sr. Member
 Offline
Activity: 449
Merit: 250
Belief in the immutable.
|
 |
December 06, 2017, 07:00:44 PM |
|
My visible hashrate on D3 screen is much better with fewer hw errors using this firmware. However, my shares/poolside hashrate is better with stock firmware. I've ran 48 hour tests on the same pool using the same workers.
The only variable is the firmware, I wonder why this is so, because it seems very promising but for us not worth a 20% drop in shares.
This was tested using Blizz firmware previous version I have not had time to test this very latest. Anyone have insight on what could cause this?
I have experienced a reduction with some pools (mainly Yiimp clones) 5%. Switching seems to adversely lower their PPS calculations, but not 20% No idea on the power usage, but I have kept this F\W as my D3's are running a lot cooler, no H\W errors ans no failed chains!! Despite latest bitmain f\w, I was experiencing failed chains (all) 0 hash and fans on full!! I was running 487freq (batch 1) Current settings; Freq: 450, ASIC: Lowest, Fans: Auto Stats: M/H: 16.8ghz H\W: Zero despite running for days Temp (PCB): 59 Temp (Chip): 70 Fan: 3,690 (auto) I can get the hash higher without H\W errors, but like how cool and stable the unit is running. 28 degrees ambient temps!!! Perhaps as more users run the F\W, fees could reduce, but 1.5% seems reasonable for an excellent enhancement. If you don't want the DEV fees, you can download the antminer toolkit from bitmain, to set the lower CHIP voltages, ect , but greater risk of getting it wrong and miss the key features, auto reboot on low hash, updated cgminer, better fan control, ability to set each board individually. Toolset can be a bit hard to get working with the D3's. Our team tested it on mpos pools only, I cannot stand yiimp as well, very few are setup to correctly handle an asic rig. I will retry using the newest fw version in hopes our 48 hour test was a fluke. I want this to work, the hw errors and heat reduction is worth it. I just cannot have a large share reduction. |
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
|
|
blissz (OP)
|
|
December 06, 2017, 07:48:23 PM |
|
As Nicehash is down, my miners lost in DevPools I think. They don't use 2nd pool or 3rd pool, which both are alive, last seen there 6 hours ago. Attached kernel log can say more... FfE1W]https[Suspicious link removed]FfE1Whttps://drive.google.com/open?id=1r7fd5skHXOkMY6qNxvBK8Cld-5NLqHvI....seems i cannot attach txt anymore, so.... Dec 6 08:44:21 (none) local0.warn cgminer[362]: Lost 9 shares due to stratum disconnect on pool 0 Dec 6 08:44:21 (none) local0.warn cgminer[362]: Pool 0 stratum share submission failure Dec 6 08:44:27 (none) local0.warn cgminer[362]: Pool 0 stratum+tcp://x11.eu.nicehash.com:3336 not responding! Dec 6 08:44:27 (none) local0.warn cgminer[362]: Switching to pool 1 stratum+tcp://hub.miningpoolhub.com:17007 Dec 6 08:58:13 (none) local0.warn cgminer[362]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9995 It worked perfectly normal as what I see from your log. It switched to your 1st pool after nicehash went down. Of course it switches to the dev pool every 2 hours (the last line). Blissz, check picture in the same post, last seen alive, last column on miner status... Fact is at the time of kernel save was not mining Nicehash(normally, down) but not MiningPool either, which was 2nd alive pool. Still, miner showing 18 k Gh....where?? I see the picture now and the LS time is strange... I will have a look at it edit: nevermind I checked your kernel log again: you're not on the latest version. This is a known bug on v1.01 (see the changelog). Please upgrade to v1.1 |
|
|
|
|
DragosD1
Newbie
Offline
Activity: 89
Merit: 0
|
|
December 06, 2017, 08:16:46 PM |
|
Lol, I probably wrong clicked on updating, damn. Sorry
|
|
|
|
|
|
funminer
|
|
December 06, 2017, 08:31:55 PM |
|
It´s maybe a power problem with the hashboards, when you run your miner at 120V reduce the frequency in adv. Settings, maybe to 500 or lower. when you have 240V try with 506. |
|
|
|
|
mkmfins
Newbie
Offline
Activity: 30
Merit: 0
|
|
December 06, 2017, 08:43:53 PM |
|
It´s maybe a power problem with the hashboards, when you run your miner at 120V reduce the frequency in adv. Settings, maybe to 500 or lower. when you have 240V try with 506. More is on 220v. |
|
|
|
|
|
cryptonitro
|
|
December 06, 2017, 09:12:07 PM |
|
As Nicehash is down, my miners lost in DevPools I think. They don't use 2nd pool or 3rd pool, which both are alive, last seen there 6 hours ago. Attached kernel log can say more... FfE1W]https[Suspicious link removed]FfE1Whttps://drive.google.com/open?id=1r7fd5skHXOkMY6qNxvBK8Cld-5NLqHvI....seems i cannot attach txt anymore, so.... Dec 6 08:44:21 (none) local0.warn cgminer[362]: Lost 9 shares due to stratum disconnect on pool 0 Dec 6 08:44:21 (none) local0.warn cgminer[362]: Pool 0 stratum share submission failure Dec 6 08:44:27 (none) local0.warn cgminer[362]: Pool 0 stratum+tcp://x11.eu.nicehash.com:3336 not responding! Dec 6 08:44:27 (none) local0.warn cgminer[362]: Switching to pool 1 stratum+tcp://hub.miningpoolhub.com:17007 Dec 6 08:58:13 (none) local0.warn cgminer[362]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9995 It worked perfectly normal as what I see from your log. It switched to your 1st pool after nicehash went down. Of course it switches to the dev pool every 2 hours (the last line). Blissz, check picture in the same post, last seen alive, last column on miner status... Fact is at the time of kernel save was not mining Nicehash(normally, down) but not MiningPool either, which was 2nd alive pool. Still, miner showing 18 k Gh....where?? I see the picture now and the LS time is strange... I will have a look at it edit: nevermind I checked your kernel log again: you're not on the latest version. This is a known bug on v1.01 (see the changelog). Please upgrade to v1.1 i'm in 1v1 , and i seem have this sort of issue to, dont come back auto to pool 0 , at least with prohasing in priority ... when i restart miner it connect again Switching to pool 0 stratum+tcp://prohashing.com:3333
Dec 6 19:50:06 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 0
Dec 6 19:50:41 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 0
Dec 6 19:50:48 (none) local0.warn cgminer[21504]: Lost 2 shares due to stratum disconnect on pool 0
Dec 6 19:50:49 (none) local0.warn cgminer[21504]: Pool 0 stratum+tcp://prohashing.com:3333 not responding!
Dec 6 19:50:49 (none) local0.warn cgminer[21504]: Switching to pool 1 stratum+tcp://X11.mine.zpool.ca:3533
Dec 6 19:50:55 (none) local0.warn cgminer[21504]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9995
Dec 6 19:52:47 (none) local0.warn cgminer[21504]: Switching to pool 1 stratum+tcp://X11.mine.zpool.ca:3533
Dec 6 20:11:03 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:15:45 (none) local0.warn cgminer[21504]: Pool 1 stratum+tcp://X11.mine.zpool.ca:3533 not responding!
Dec 6 20:15:45 (none) local0.warn cgminer[21504]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Dec 6 20:16:16 (none) local0.warn cgminer[21504]: Pool 1 stratum+tcp://X11.mine.zpool.ca:3533 alive, testing stability
Dec 6 20:16:31 (none) local0.warn cgminer[21504]: Pool 0 stratum+tcp://prohashing.com:3333 not responding!
Dec 6 20:16:31 (none) local0.warn cgminer[21504]: Switching to pool 1 stratum+tcp://X11.mine.zpool.ca:3533
Dec 6 20:17:13 (none) local0.warn cgminer[21504]: Lost 2 shares due to no stratum share response from pool 1
Dec 6 20:17:18 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:17:31 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:17:36 (none) local0.warn cgminer[21504]: Lost 2 shares due to no stratum share response from pool 1
Dec 6 20:17:38 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:17:46 (none) local0.warn cgminer[21504]: Lost 3 shares due to no stratum share response from pool 1
Dec 6 20:27:37 (none) local0.warn cgminer[21504]: Pool 1 stratum+tcp://X11.mine.zpool.ca:3533 not responding!
Dec 6 20:27:37 (none) local0.warn cgminer[21504]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Dec 6 20:28:09 (none) local0.warn cgminer[21504]: Pool 1 stratum+tcp://X11.mine.zpool.ca:3533 alive, testing stability
Dec 6 20:29:16 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:29:39 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:30:09 (none) local0.warn cgminer[21504]: Pool 1 stratum+tcp://X11.mine.zpool.ca:3533 stable for >120 seconds
Dec 6 20:30:09 (none) local0.warn cgminer[21504]: Switching to pool 1 stratum+tcp://X11.mine.zpool.ca:3533
Dec 6 20:56:23 (none) local0.warn cgminer[21504]: Pool 1 stratum+tcp://X11.mine.zpool.ca:3533 not responding!
Dec 6 20:56:23 (none) local0.warn cgminer[21504]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Dec 6 20:56:56 (none) local0.warn cgminer[21504]: Pool 1 stratum+tcp://X11.mine.zpool.ca:3533 alive, testing stability
Dec 6 20:57:33 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:57:38 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:57:51 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:57:56 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:58:23 (none) local0.warn cgminer[21504]: Lost 1 shares due to no stratum share response from pool 1
Dec 6 20:58:56 (none) local0.warn cgminer[21504]: Pool 1 stratum+tcp://X11.mine.zpool.ca:3533 stable for >120 seconds
Dec 6 20:58:56 (none) local0.warn cgminer[21504]: Switching to pool 1 stratum+tcp://X11.mine.zpool.ca:3533
[...]
|
The only project make me believe ... Holochain
|
|
|
|
blissz (OP)
|
|
December 06, 2017, 09:15:36 PM |
|
It;s prohashing related. I actually found what's the problem so it will be fixed in the next release
|
|
|
|
|
|
cryptonitro
|
|
December 06, 2017, 09:19:00 PM |
|
It;s prohashing related. I actually found what's the problem so it will be fixed in the next release
ok , fine  |
The only project make me believe ... Holochain
|
|
|
mkmfins
Newbie
Offline
Activity: 30
Merit: 0
|
|
December 06, 2017, 09:21:19 PM |
|
Can anyone help me with this error? This is mine D3_2, different from the above mistakes that I put. This is giving these errors on CHAIN_1 Does anyone have a solution or a hint to fix this? ERRO: https://i.imgur.com/CyQB8WG.png |
|
|
|
|
|
blissz (OP)
|
|
December 06, 2017, 09:49:43 PM |
|
Can anyone help me with this error? This is mine D3_2, different from the above mistakes that I put. This is giving these errors on CHAIN_1 Does anyone have a solution or a hint to fix this? ERRO: https://i.imgur.com/CyQB8WG.pngAhh it seems you flashed the custom firmware. Please set all chain frequencies to global and try again by setting the global frequency at 450 Mhz |
|
|
|
|
|
cryptcoin_de
|
|
December 06, 2017, 09:56:41 PM |
|
Can anyone help me with this error? This is mine D3_2, different from the above mistakes that I put. This is giving these errors on CHAIN_1 Does anyone have a solution or a hint to fix this? ERRO: https://i.imgur.com/CyQB8WG.pngDo you bought the two D3 as new from Bitmain or in used condition? Maybe ASICS are burned out, see the lot of HW errors, they will mostly never be come back. Use the tip from blissz - when this not helps you have a problem. S9 / L3+ have stable ASIC's but the ASIC's from D3 burning out very easy, simply a longer time chip temp above 75 or 80 degrees kill them and IMHO the frequenzy and voltage set from Bitmain on the 19 GH/s batch is to high for a long time 24/7 ASIC runtime. When i read the "overclock" posts here - simply do it and you will kill all your ASIC's after a week or so. This is good for decreasing the DASH difficulty...  |
|
|
|
|
DragosD1
Newbie
Offline
Activity: 89
Merit: 0
|
|
December 06, 2017, 10:33:32 PM |
|
Bad news guys! Nicehash is down because of "Bitcoin wallet stolen" ...bye bye 1900 usd  |
|
|
|
|
mkmfins
Newbie
Offline
Activity: 30
Merit: 0
|
|
December 06, 2017, 10:55:35 PM |
|
Can anyone help me with this error? This is mine D3_2, different from the above mistakes that I put. This is giving these errors on CHAIN_1 Does anyone have a solution or a hint to fix this? ERRO: https://i.imgur.com/CyQB8WG.pngDo you bought the two D3 as new from Bitmain or in used condition? Maybe ASICS are burned out, see the lot of HW errors, they will mostly never be come back. Use the tip from blissz - when this not helps you have a problem. S9 / L3+ have stable ASIC's but the ASIC's from D3 burning out very easy, simply a longer time chip temp above 75 or 80 degrees kill them and IMHO the frequenzy and voltage set from Bitmain on the 19 GH/s batch is to high for a long time 24/7 ASIC runtime. When i read the "overclock" posts here - simply do it and you will kill all your ASIC's after a week or so. This is good for decreasing the DASH difficulty... The two are brand new, in the same LOT. - One has this error in CHAIN 1 in 5 ASIC status. - The other one is in error in the 3 CHAINS. |
|
|
|
|
Bajula
Member
Offline
Activity: 166
Merit: 16
|
|
December 06, 2017, 11:19:22 PM |
|
It´s maybe a power problem with the hashboards, when you run your miner at 120V reduce the frequency in adv. Settings, maybe to 500 or lower. when you have 240V try with 506. has more to do with your psu than the (edit for INPUT voltage I mean) voltage you are running at.. pretty much 240v to psu vs 120v to psu comes down to how many amps the psu draws (how hot is the psu and the cord to wall going to get) psu to machine is 12v and whatever amps the settings draw, it doesn't give a flip at that point what the input voltage is. (240v is better for many reasons, but primarily (for miners) to ease the workload on your psu, and in the case of certain dual voltage psu's allow for more watts to be drawn (which also decreases the work load on your psu.) over half the problems I've encountered with people overclocking was about the psu and not so much the machines. - The other half was about improper cooling. (Either from manf end. or user derping) All that being said lowering settings is still probably the right choice. |
|
|
|
|
Bajula
Member
Offline
Activity: 166
Merit: 16
|
|
December 06, 2017, 11:28:15 PM |
|
Bad news guys! Nicehash is down because of "Bitcoin wallet stolen" ...bye bye 1900 usd oh man, that was my pay certain bills money. I didn't set aside from last paycheck for them either. |
|
|
|
|
mkmfins
Newbie
Offline
Activity: 30
Merit: 0
|
|
December 06, 2017, 11:30:22 PM |
|
It´s maybe a power problem with the hashboards, when you run your miner at 120V reduce the frequency in adv. Settings, maybe to 500 or lower. when you have 240V try with 506. has more to do with your psu than the (edit for INPUT voltage I mean) voltage you are running at.. pretty much 240v to psu vs 120v to psu comes down to how many amps the psu draws (how hot is the psu and the cord to wall going to get) psu to machine is 12v and whatever amps the settings draw, it doesn't give a flip at that point what the input voltage is. (240v is better for many reasons, but primarily (for miners) to ease the workload on your psu, and in the case of certain dual voltage psu's allow for more watts to be drawn (which also decreases the work load on your psu.) over half the problems I've encountered with people overclocking was about the psu and not so much the machines. - The other half was about improper cooling. (Either from manf end. or user derping) All that being said lowering settings is still probably the right choice. I think they are from the same machines, because the two I bought came with errors. 1 - It has an error in the 3 CHAINS, it is not active, it is active ... It takes 20 seconds with ASIC STATUS in "0" and ASICS is missing, and then everyone has the "X". 2 - You are in error only in CHAIN 1, taking only 5 ASIC STATUS. I do not know what else to do... |
|
|
|
|
Bajula
Member
Offline
Activity: 166
Merit: 16
|
|
December 07, 2017, 12:22:14 AM |
|
It´s maybe a power problem with the hashboards, when you run your miner at 120V reduce the frequency in adv. Settings, maybe to 500 or lower. when you have 240V try with 506. has more to do with your psu than the (edit for INPUT voltage I mean) voltage you are running at.. pretty much 240v to psu vs 120v to psu comes down to how many amps the psu draws (how hot is the psu and the cord to wall going to get) psu to machine is 12v and whatever amps the settings draw, it doesn't give a flip at that point what the input voltage is. (240v is better for many reasons, but primarily (for miners) to ease the workload on your psu, and in the case of certain dual voltage psu's allow for more watts to be drawn (which also decreases the work load on your psu.) over half the problems I've encountered with people overclocking was about the psu and not so much the machines. - The other half was about improper cooling. (Either from manf end. or user derping) All that being said lowering settings is still probably the right choice. I think they are from the same machines, because the two I bought came with errors. 1 - It has an error in the 3 CHAINS, it is not active, it is active ... It takes 20 seconds with ASIC STATUS in "0" and ASICS is missing, and then everyone has the "X". 2 - You are in error only in CHAIN 1, taking only 5 ASIC STATUS. I do not know what else to do... You were already informed what to try, lower the speed. --> do 400 freq - see if the boards come back up, if they do cool .. work your way up, if they don't then come back with what they did when you put it at 400. Does that make it clearer? |
|
|
|
|
mkmfins
Newbie
Offline
Activity: 30
Merit: 0
|
|
December 07, 2017, 12:47:48 AM |
|
It´s maybe a power problem with the hashboards, when you run your miner at 120V reduce the frequency in adv. Settings, maybe to 500 or lower. when you have 240V try with 506. has more to do with your psu than the (edit for INPUT voltage I mean) voltage you are running at.. pretty much 240v to psu vs 120v to psu comes down to how many amps the psu draws (how hot is the psu and the cord to wall going to get) psu to machine is 12v and whatever amps the settings draw, it doesn't give a flip at that point what the input voltage is. (240v is better for many reasons, but primarily (for miners) to ease the workload on your psu, and in the case of certain dual voltage psu's allow for more watts to be drawn (which also decreases the work load on your psu.) over half the problems I've encountered with people overclocking was about the psu and not so much the machines. - The other half was about improper cooling. (Either from manf end. or user derping) All that being said lowering settings is still probably the right choice. I think they are from the same machines, because the two I bought came with errors. 1 - It has an error in the 3 CHAINS, it is not active, it is active ... It takes 20 seconds with ASIC STATUS in "0" and ASICS is missing, and then everyone has the "X". 2 - You are in error only in CHAIN 1, taking only 5 ASIC STATUS. I do not know what else to do... You were already informed what to try, lower the speed. --> do 400 freq - see if the boards come back up, if they do cool .. work your way up, if they don't then come back with what they did when you put it at 400. Does that make it clearer? Currently I'm using settings like this. But still with the mistakes, I do not know what to do, maybe it was already bad this CHAIN 1. If they have recommendations for me to test and have a higher percentage. IMAGES: https://i.imgur.com/MSteVB4.pnghttps://i.imgur.com/T5tyPIT.png |
|
|
|
|
Bajula
Member
Offline
Activity: 166
Merit: 16
|
|
December 07, 2017, 01:36:47 AM |
|
It´s maybe a power problem with the hashboards, when you run your miner at 120V reduce the frequency in adv. Settings, maybe to 500 or lower. when you have 240V try with 506. has more to do with your psu than the (edit for INPUT voltage I mean) voltage you are running at.. pretty much 240v to psu vs 120v to psu comes down to how many amps the psu draws (how hot is the psu and the cord to wall going to get) psu to machine is 12v and whatever amps the settings draw, it doesn't give a flip at that point what the input voltage is. (240v is better for many reasons, but primarily (for miners) to ease the workload on your psu, and in the case of certain dual voltage psu's allow for more watts to be drawn (which also decreases the work load on your psu.) over half the problems I've encountered with people overclocking was about the psu and not so much the machines. - The other half was about improper cooling. (Either from manf end. or user derping) All that being said lowering settings is still probably the right choice. I think they are from the same machines, because the two I bought came with errors. 1 - It has an error in the 3 CHAINS, it is not active, it is active ... It takes 20 seconds with ASIC STATUS in "0" and ASICS is missing, and then everyone has the "X". 2 - You are in error only in CHAIN 1, taking only 5 ASIC STATUS. I do not know what else to do... You were already informed what to try, lower the speed. --> do 400 freq - see if the boards come back up, if they do cool .. work your way up, if they don't then come back with what they did when you put it at 400. Does that make it clearer? Currently I'm using settings like this. But still with the mistakes, I do not know what to do, maybe it was already bad this CHAIN 1. If they have recommendations for me to test and have a higher percentage. IMAGES: https://i.imgur.com/MSteVB4.pnghttps://i.imgur.com/T5tyPIT.pngso you have 7 voltage on chain one (has problems) 17 voltage on the other two.. do you see where I am going with this? Try making them all 10, the come back with what you get.. then SLOWLY up the freq til you get errors again, then take it down one. If you want to go down on the voltage again, cool, just go back to super low freq, and work it up little by little til you get errors. |
|
|
|
|
|
Poll
