may142012
Member
Offline
Activity: 301
Merit: 10
|
|
November 29, 2017, 03:38:43 AM |
|
Is everyone experiencing low hash rates monitored from the pool you are using? My miner's showing 14,837 MH/s, but on my pool, it is showing me incorrect hash rate like under 10,000 MH/s below my miner's hash rates.
|
|
|
|
|
|
The forum strives to allow free discussion of any ideas. All policies are built around this principle. This doesn't mean you can post garbage, though: posts should actually contain ideas, and these ideas should be argued reasonably.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
dalu1
Member
Offline
Activity: 83
Merit: 10
Performing it is a better way of learning things
|
|
November 29, 2017, 03:46:10 AM |
|
Is everyone experiencing low hash rates monitored from the pool you are using? My miner's showing 14,837 MH/s, but on my pool, it is showing me incorrect hash rate like under 10,000 MH/s below my miner's hash rates.
Pool monitor rate varies in a range around your miner's reported hashrate. Normally slightly lower, but not much.
|
|
|
|
dalu1
Member
Offline
Activity: 83
Merit: 10
Performing it is a better way of learning things
|
|
November 29, 2017, 05:21:31 AM |
|
Blissz,
I have suggestion, can you auto tune the hashrate some thing like when a chain error rate exceeds 5 (x) errors per minutes, decrease the hashrate by 1 (x/5) meg until it is stable starting from the configured hashrate.
|
|
|
|
may142012
Member
Offline
Activity: 301
Merit: 10
|
|
November 29, 2017, 06:23:48 AM |
|
Can you add an option to power off the miner, so you don't have to unplug the cable cord immediately.
|
|
|
|
|
blissz (OP)
|
|
November 29, 2017, 06:54:14 AM |
|
Blissz,
Your newest firmware 28/11 crashes right after 2 hours when it tries to switch from pool 3 to pool 0. I am flashing back to your 26/11 version.
Can you try to flash 28/11 again and disable the "automatic reboot on low hashrate detection / asic failure". Please pm the last ~100 lines of the kernel log after a few hours of hashing if you do.
|
|
|
|
fecell
Jr. Member
Offline
Activity: 133
Merit: 2
|
|
November 29, 2017, 07:09:41 AM |
|
Can you add an option to power off the miner, so you don't have to unplug the cable cord immediately.
it's impossible. hash blades powering directly from PSU. it can't be power off by control board.
|
|
|
|
DragosD1
Newbie
Offline
Activity: 89
Merit: 0
|
|
November 29, 2017, 07:20:35 AM |
|
LOL, i just set to the frequency to 425, my third chain and second chain are starting to give HWs, and the third chain shows some xxx
Do i have to reboot the miner after change something? [/quote]
Try to play with voltages. No need to reboot, restart miner is ok. That happens when you hit Save&Apply button
|
|
|
|
DragosD1
Newbie
Offline
Activity: 89
Merit: 0
|
|
November 29, 2017, 07:42:33 AM |
|
Blissz,
Your newest firmware 28/11 crashes right after 2 hours when it tries to switch from pool 3 to pool 0. I am flashing back to your 26/11 version.
Can you try to flash 28/11 again and disable the "automatic reboot on low hashrate detection / asic failure". Please pm the last ~100 lines of the kernel log after a few hours of hashing if you do. I did that. With option DISABLED, everything seems fine...prob when switching pools D3 falls under those 15732 Gh/s trigger. I saw abnormal restarts aswell this morning. We need to adjust restart "if" conditions a bit Nov 29 07:24:26 (none) local0.err cgminer[10724]: low hashrate detection trigger: 15732.000000 Gh/s Nov 29 07:24:26 (none) local0.notice cgminer[10724]: set voltage = 1198.763842 real:225 mv Nov 29 07:24:26 (none) local0.notice cgminer[10724]: set_PIC16F1704_voltage_new ok, voltage = 0xe1 Nov 29 07:24:27 (none) local0.notice cgminer[10724]: set_PIC16F1704_voltage_new ok, voltage = 0xd7 Nov 29 07:24:27 (none) local0.notice cgminer[10724]: set_PIC16F1704_voltage_new ok, voltage = 0xe1 Nov 29 07:24:27 (none) local0.err cgminer[10724]: cgminer time error total_secs = 1511940267.915820 last_total_secs = 1.000000 Nov 29 07:24:28 (none) local0.warn cgminer[10724]: Pool 0 stratum+tcp://hub.miningpoolhub.com:17007 alive, testing stability Nov 29 07:24:28 (none) local0.warn cgminer[10724]: Switching to pool 0 stratum+tcp://hub.miningpoolhub.com:17007 Nov 29 07:24:33 (none) local0.warn cgminer[10724]: API running in IP access mode on port 4028 (16) Nov 29 07:26:05 (none) local0.warn cgminer[10724]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9995 Nov 29 07:27:55 (none) local0.warn cgminer[10724]: Switching to pool 0 stratum+tcp://hub.miningpoolhub.com:17007
|
|
|
|
|
HavenZone
Jr. Member
Offline
Activity: 37
Merit: 1
|
|
November 29, 2017, 07:46:21 AM |
|
after the new update I went from 0 HW Errors for 26 hours to 8 HW Errors in the last 3 hours. Also it seems that it rebooted both miners on its own. Do I need to readjust the settings for the new cgminer?
|
|
|
|
DragosD1
Newbie
Offline
Activity: 89
Merit: 0
|
|
November 29, 2017, 07:47:55 AM |
|
after the new update I went from 0 HW Errors for 26 hours to 8 HW Errors in the last 3 hours. Also it seems that it rebooted both miners on its own. Do I need to readjust the settings for the new cgminer?
Probably. Some things have changed into firmware
|
|
|
|
blissz (OP)
|
|
November 29, 2017, 07:54:30 AM |
|
after the new update I went from 0 HW Errors for 26 hours to 8 HW Errors in the last 3 hours. Also it seems that it rebooted both miners on its own. Do I need to readjust the settings for the new cgminer?
This is not the firmware, unfortunately its the hashing boards which behave a very little bit different each reboot. My advice: don't bother those 8 HW errors as it's still very little or increase the voltage one step for that board.
|
|
|
|
HavenZone
Jr. Member
Offline
Activity: 37
Merit: 1
|
|
November 29, 2017, 08:00:54 AM |
|
after the new update I went from 0 HW Errors for 26 hours to 8 HW Errors in the last 3 hours. Also it seems that it rebooted both miners on its own. Do I need to readjust the settings for the new cgminer?
This is not the firmware, unfortunately its the hashing boards which behave a very little bit different each reboot. My advice: don't bother those 8 HW errors as it's still very little or increase the voltage one step for that board. I went back to the old firmware for now... I noticed that it was rebooting every couple of hours as well.
|
|
|
|
blissz (OP)
|
|
November 29, 2017, 08:15:24 AM |
|
after the new update I went from 0 HW Errors for 26 hours to 8 HW Errors in the last 3 hours. Also it seems that it rebooted both miners on its own. Do I need to readjust the settings for the new cgminer?
This is not the firmware, unfortunately its the hashing boards which behave a very little bit different each reboot. My advice: don't bother those 8 HW errors as it's still very little or increase the voltage one step for that board. I went back to the old firmware for now... I noticed that it was rebooting every couple of hours as well. Yes it seems a bit sensitive, I am now testing an update which only reboots after two consecutive failures. By the way there is no need to flash back, just disable the automatic reboot option for now.
|
|
|
|
martyshmoo
Newbie
Offline
Activity: 56
Merit: 0
|
|
November 29, 2017, 08:42:56 AM |
|
Blissz,
Your newest firmware 28/11 crashes right after 2 hours when it tries to switch from pool 3 to pool 0. I am flashing back to your 26/11 version.
Can you try to flash 28/11 again and disable the "automatic reboot on low hashrate detection / asic failure". Please pm the last ~100 lines of the kernel log after a few hours of hashing if you do. Hi, New member, been reading. One question for today: 28/11 today, YES or no? Should I do it, or await 29/11? BTW BLISSZ Lets have a Beer someday after we are all rich and can still hear eachother. THANK YOU! Marty PS as I see it I only have to disable the "automatic reboot on low hashrate detection / asic failure". to ensure a good quiet working machine, right? Thanks for your response in advance. Marty
|
|
|
|
|
martyshmoo
Newbie
Offline
Activity: 56
Merit: 0
|
|
November 29, 2017, 08:51:22 AM |
|
I am thinking wait. I am currently getting about 12 a day from one D3, running on Solar Power. I need to bring down the power consumption if I want to add another miner. and I think this is exactly what we all need. Blissz! Thanks again!!! Marty
|
|
|
|
cryptolavena
Newbie
Offline
Activity: 1
Merit: 0
|
|
November 29, 2017, 08:56:27 AM |
|
Hi all thanks god and blissz for this firmware.. yesterday i received the invoice from antminer about my fucking D3..
At the moment i spent 1500USD plus 70 for shipping cost and probably when D3 arrive, i have to pay also the custom fee
As You know there is a way to return of investment by using this new amazing firmware?
i really don't know if is good to check it out from the customs
with this firmware which is the ROI? (at the moment?)
you know if is possible (in the future) improve the hash power?
thankyou guy and THANKYOU blissz
|
|
|
|
jbmod
Newbie
Offline
Activity: 13
Merit: 0
|
|
November 29, 2017, 08:59:08 AM |
|
Hi @all,
as probably some of you have exchanged fans - what kind of model / type would you guys recommend? How many RPM fans are you using to get the D3 quiet? Mine are currently running at 2500-3000rpm with original fans. Any recommendations?
And thanks Blissz, for starting this and still working on an even better custom FW. :-)
|
|
|
|
|