I think that cgminer 4.0 tries to restarted fallen USB device (AntMinerU1) too fast (and it doesn't work): [2014-02-22 15:55:01] ANU 3: No valid hashes for over 53 secs, attempting to reset
[2014-02-22 15:55:01] ANU 3 attempted reset got err:(0) LIBUSB_SUCCESS
[2014-02-22 15:55:03] ANU 3: No valid hashes for over 53 secs, attempting to reset
[2014-02-22 15:55:03] ANU 3 attempted reset got err:(0) LIBUSB_SUCCESS
[2014-02-22 15:55:05] ANU 3: No valid hashes for over 53 secs, attempting to reset
[2014-02-22 15:55:05] ANU 3 attempted reset got err:(0) LIBUSB_SUCCESS
[2014-02-22 15:55:07] ANU 3: No valid hashes for over 53 secs, attempting to reset
[2014-02-22 15:55:08] ANU 3 attempted reset got err:(0) LIBUSB_SUCCESS
[2014-02-22 15:55:10] ANU 3: No valid hashes for over 53 secs, attempting to reset
[2014-02-22 15:55:10] ANU 3 attempted reset got err:(0) LIBUSB_SUCCESS
[2014-02-22 15:55:12] ANU 3: No valid hashes for over 53 secs, attempting to reset
[2014-02-22 15:55:12] ANU 3 attempted reset got err:(0) LIBUSB_SUCCESS
|
|
|
|
Is there an easy way to replug AntMiner U1 device in bfgminer? New cgminer introduced a menu to work with broken USB devices. From time to time, U1 device dies, it is not mining and it is not dead, like in this example, AMU 3 device was mining for some time at 2GHps but it is not mining for a while (or mining at low hashrate): 4 | 8.35/ 8.33/ 6.61Gh/s | A:3492 R:1+0(.03%) HW:0/none
--------------------------------------------------------------------------------
AMU 0: | 2.06/ 2.06/ 1.99Gh/s | A:1015 R:0+0(none) HW:0/none
AMU 1: | 2.07/ 2.06/ 2.01Gh/s | A:1084 R:1+0(.09%) HW:0/none
AMU 2: | 2.06/ 2.06/ 1.99Gh/s | A:1081 R:0+0(none) HW:0/none
AMU 3: | 2.10/ 2.14/ 0.62Gh/s | A: 314 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
I am not sure what is a problem but devices were running at 2GHps for several days but they make trouble today... ;-) I know, I can restart bfgminer, it will fix the problem. |
|
|
|
First of all, thanks a bunch for the Antminer U1 support.  3.12.3 running stable for two hours on my rpi. So far so good. Just a thought, would be nice to have 12.5 MHz increments, allowing more specific fine tuning with +/- 100 GHash/s steps. Guess it's not that difficult implementing those values into the freq. table? freq_hex freq_mhz ghash_s 0781 200.0 1.600 08 01 212.5 1.700 0881 225.0 1.800 09 01 237.5 1.900 0981 250.0 2.000 0A 01 262.5 2.100 0A81 275.0 2.200 etc. The documentation specifies only certain numbers, have you seen anywhere the values you mention? It's easy to hack the code if you wish to try them and report back  Below the freq. table there is some additional information how to 'build your own' freq. hex values. Played around with the formular and found these values. Can confirm the additional mentioned 0801, 0901 and 0A01 working fine with Bitmain's cgminer fork, at least on my Antminers. Would be a pleasure testing a modified version (on a rpi or Windows PC) and reporting back. That is COOL! It means that "HEX frequency" 0x1305 configures AntMinerU1 clock to run at 243.75 MHz and hash rate is about 1950 MHash/s! Tested with bfgminer that works with HEX frequency... AntMiner clock can be tuned in 0.12 MHz steps, hashrate increased by 25 MHash/s. |
|
|
|
Information from ASIC-README: --anu-freq <arg> Set AntminerU1 frequency in hex, range 150-500 (default: 200)
This is not correct. Your parameter Frequency is in MHz. Frequency in hex for 200 MHz is 0x0781 and AntMinerU1 has hash rate 1600 MHash/s at that frequency... Could be a table with frequencies added to the ASIC-README? |
|
|
|
A patch to support miner that report 'MHS 20s'... # git diff -p index.php
diff --git a/index.php b/index.php
index 2935bc7..4890627 100644
--- a/index.php
+++ b/index.php
@@ -217,7 +217,7 @@ for ($i=0; $i<$nr_rigs; $i++)
<td style="text-align:center"><?php echo $dev['Fan Percent']?>%</td>
<td style="text-align:center">
<?php
- $stats_second = isset ($dev['MHS 5s']) ? $dev['MHS 5s'] : (isset ($dev['MHS 2s']) ? $dev['MHS 2s'] : 0);
+ $stats_second = isset ($dev['MHS 20s']) ? $dev['MHS 20s'] : (isset ($dev['MHS 5s']) ? $dev['MHS 5s'] : (isset ($dev['MHS 2s']) ? $dev['MHS 2s'] : 0));
$stats_second_string = $r[$i]['coin']['COIN']['Hash Method'] == 'scrypt' ? $stats_second * 1000 . ' | ' . $dev['MHS av'] * 1000 : $stats_second . ' | ' . $dev['MHS av'];
$stats_ratio = 0;
if ($dev['MHS av'] > 0)
A patch to address that several small USB devices don't have FAN and temperature sensor. # git diff -p index.php
diff --git a/index.php b/index.php
index 2935bc7..5ca0d67 100644
--- a/index.php
+++ b/index.php
@@ -213,11 +213,11 @@ for ($i=0; $i<$nr_rigs; $i++)
?>
</td>
<td style="text-align:center"><?php echo $dev['Status'] == 'Alive' ? '<span class="ok">' . $dev['Status'] . '</span>' : '<span class="error">' . $dev['Status'] . '</span>' ?></td>
- <td style="text-align:center"><?php echo $dev['Temperature'] > ALERT_TEMP ? '<span class="error">' . round($dev['Temperature']) . '°C</span>' : round($dev['Temperature']) . '°C' ?></td>
- <td style="text-align:center"><?php echo $dev['Fan Percent']?>%</td>
+ <td style="text-align:center"><?php echo isset ($dev['Temperature']) ? ($dev['Temperature'] > ALERT_TEMP ? '<span class="error">' . round($dev['Temperature']) . '°C</span>' : round($dev['Temperature']) . '°C') : '-' ?></td>
+ <td style="text-align:center"><?php echo isset ($dev['Fan Percent']) ? $dev['Fan Percent'] . '%' : '-' ?></td>
<td style="text-align:center">
|
|
|
|
Sorry, i don't know how to use java API with cgminer. I am noob
cgminer$ ls -l API.class; java API coin localhost 4028
-rw-r--r-- 1 peon peon 3431 2013-05-27 16:56 API.class
Attempting to send 'coin' to 127.0.0.1:4028
Answer='STATUS=S,When=1391857634,Code=78,Msg=BFGMiner coin,Description=bfgminer 3.10.0|COIN,Hash Method=scrypt,Current Block Time=1391857600,Current Block Hash=fb246a37af09cb9c2cac0593375fd94752b81e72c591274b39870b1dc049b16d,LP=true,Network Difficulty=158.43854530|'
[STATUS] =>
(
[STATUS] => S
[When] => 1391857634
[Code] => 78
[Msg] => BFGMiner coin
[Description] => bfgminer 3.10.0
)
[COIN] =>
(
[0] => COIN
[Hash Method] => scrypt
[Current Block Time] => 1391857600
[Current Block Hash] => fb246a37af09cb9c2cac0593375fd94752b81e72c591274b39870b1dc049b16d
[LP] => true
[Network Difficulty] => 158.43854530
)
[/code] |
|
|
|
hello pooler, I have used your cpuminer for doge and ltc. I just started using it for maxcoin and It pops up and runs fine but I get a 0.00% and boo, tried running it like the following below.
This version of cpuminer cannot be used to mine maxcoin because that coin needs a miner with support for "keccak" algorithm. |
|
|
|
I can't change any of the variables like the pool.....sigh. I'm really beginning to hate Linux.
Delete Linux and install your lovely Windows on your BBB and be happy... ;-) |
|
|
|
|
Well, it is not a fix but workaround. It is working, blockchain was synchronized till block 190965.
|
|
|
|
Was this fix tested? When I check the code, I don't understand it... Is the function GetEmaNextWorkRequired right place for the fix?? |
|
|
|
|
I tried to compile TRC client for smartbook Toshiba AC100 that is based around Nvidia Tegra2 (32-bit ARM processor). I run Ubuntu 12.10 (armhf) at AC100.
TRC client passed the test, whole blockchain was downloaded, no issue at all.
I observe the problem at several x86 computers running different 32-bit versions of Ubuntu.
|
|
|
|
hm ... here my output.
root@bitcoin:~/.terracoin# grep 00000000000342fd6e38765cc6f8f56d60c49e3e9522a54d99f561d35800a293 *
debug.log:received block 00000000000342fd6e38765cc6f8f56d60c49e3e9522a54d99f561d35800a293 from 5.39.79.140:13333
debug.log:SetBestChain: new best=00000000000342fd6e38765cc6f8f56d60c49e3e9522a54d99f561d35800a293 height=137162 work=4137787908838877763 tx=272549 date=2013-05-30 11:54:41
root@bitcoin:~/.terracoin#
You don't have the problem described in this thread, your client accepted block 137162. Is your report from 32-bit Linux? What distribution is that? |
|
|
|
i'think it's work very fine. i was clone today from github ... and is run perfect. no problems ...
I updated source code from github to the latest version and after retest I am sure this bug WAS NOT FIXED... $ ./terracoind getinfo
{
"version" : 80000,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 137161,
"timeoffset" : 0,
"connections" : 10,
"proxy" : "",
"difficulty" : 19373.63213164,
"testnet" : false,
"keypoololdest" : 1370166643,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
This is in debug.log:
received block 00000000000342fd6e38765cc6f8f56d60c49e3e9522a54d99f561d35800a293 from 46.59.225.84:41156
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 46.59.225.84:41156 (0 -> 100) DISCONNECTING
|
|
|
|
Try again ... it works ... I wrote it  PWC solo & 5750 (about 80 kHash), Last Valid Work is 1751 seconds old just now and still growing. I already noticed that this value was higher than 2000 seconds. On the other side, faster card (7950) and different scrypt coin has lower values but I see 244 seconds timeout just now... These values are related to coin and GPU hashrate. |
|
|
|
... The best one to use there would be "Last Valid Work" ... that says 357835s ago or 99h 23m 55s ...
This can work when mining against pool but cannot be used for solo mining at higher diff; in that situation you can mine several days without block or share and Last valid work cannot be used. ... Nope. I really did say that coz it is correct ... I added "Last Valid Work" to cgminer coz it is the best way to determine something is wrong. It has nothing to do with shares or difficulty. It is the last time a valid hash was returned by the device. Tested and it doesn't work for solo mining. I calculated "timeout" from devs data, like devs.STATUS.When-devs.DEVS(x).Last Valid Work; I see that timeout can be high even for healthy card... |
|
|
|
|
What about API and blocks found by cgminer? It looks like noone is really interested in blocks, all effort is focused to shares reporting... The only API command "summary" reports blocks found. I can manually display blocks found for a pool. Could by API command "pools" extended to report blocks found for a pool?
|
|
|
|
Firstly, "When" - "Last Share Time" was 357929s ago ... so yeah that explains the rejects - it's spitting out crap 357929s = 99h 25m 29s Probably scrypt mining on too high settings? I don't comply about rejects. These are OK, it was mining against p2pool. Problem is that HASHRATE of this card was 0 for few days and API didn't indicate that card is SICK and AVG rate was not updated. Other problem is that cgminer had no data for few seconds, marked card SICK and never tried to restart mining. Two or three different issues. I am not sure what is the trigger of this situation, maybe that PC running p2pool was rebooted to apply security updates, so p2pool was offline for few minutes. The best one to use there would be "Last Valid Work" ... that says 357835s ago or 99h 23m 55s ...
This can work when mining against pool but cannot be used for solo mining at higher diff; in that situation you can mine several days without block or share and Last valid work cannot be used. The MH av will take a long time to get to 0 since it is the av since it started and it obviously did 'some' work. It says you did "Total MH": 156195.3567, so it would take a long time for that to average out to less than 10kH/s (more than 180 days)
The device isn't SICK when you did the API command it was "Status": "Alive"
Card was running ok for several days and in one moment card was marked as SICK, hashrate changed to 0, temperature and GPU engine frequency were set low; card was marked sick for several days and status was ALIVE all the time, otherwise monitoring script will highlight the problem. And this is why I thing there is a bug... Is it expected that SICK card is reported in API as DEAD? The notify command would say when it last has a problem and also how many times it was SICK.
I don't have "notify" report for sick card; next time... |
|
|
|
My GPU was SICK for several days and I missed that because monitoring script reading API port 4028 reported OK. Is there a way to detect SICK card through API? cgminer 3.2.2 reported: [2013-07-28 11:29:54] Stratum from pool 1 detected new block
[2013-07-28 11:29:55] Pool 1 stale share detected, discarding
[2013-07-28 11:29:56] Accepted 876fa488 Diff 4/2 GPU 0 pool 1
[2013-07-28 11:31:28] Stratum connection to pool 1 interrupted
[2013-07-28 11:31:28] Lost 517 shares due to stratum disconnect on pool 1
[2013-07-28 11:31:30] Pool 1 stratum share submission failure
[2013-07-28 11:32:00] Pool 1 communication resumed, submitting work
[2013-07-28 11:32:00] Rejected acc5c400 Diff 3/2 GPU 0 pool 1
[2013-07-28 11:32:32] GPU0: Idle for more than 60 seconds, declaring SICK!
[2013-07-28 11:32:32] GPU0: Attempting to restart
[2013-07-28 11:32:32] Thread 0 still exists, killing it off
[2013-07-28 11:32:32] Thread 0 restarted
"devs" report for SICK card: echo '{"command" : "devs"}' | nc localhost 4028 | tr -d '\0' | python -mjson.tool
{
"DEVS": [
{
"Accepted": 694192,
"Diff1 Work": 2380127,
"Difficulty Accepted": 1360131.0,
"Difficulty Rejected": 436120.0,
"Enabled": "Y",
"Fan Percent": 56,
"Fan Speed": -1,
"GPU": 0,
"GPU Activity": 0,
"GPU Clock": 157,
"GPU Voltage": 1.1,
"Hardware Errors": 0,
"Intensity": "18",
"Last Share Difficulty": 2.0,
"Last Share Pool": 1,
"Last Share Time": 1375003796,
"Last Valid Work": 1375003890,
"MHS 5s": 0.0,
"MHS av": 0.17,
"Memory Clock": 300,
"Powertune": 0,
"Rejected": 222954,
"Status": "Alive",
"Temperature": 40.0,
"Total MH": 156195.3567,
"Utility": 44.85
}
],
"STATUS": [
{
"Code": 9,
"Description": "cgminer 3.2.2",
"Msg": "1 GPU(s) - ",
"STATUS": "S",
"When": 1375361725
}
],
"id": 1
}
I am not sure but this could be a bug. I can try to detect SICK state from several parameters (MHS 5s, GPU Activity, Temperature) but is it correct way? If it is, what parameter should be used for detection? BTW, reported parameter "MHS av" is wrong, it was 0.00, because card was sick for several days... |
|
|
|
Hope this helps people. Requires Safari and I think Chrome has a version now, but took the original poster here's GreaseMonkey script concept to the next level. This will return just the header and your bitcoin address on the webpage. Just replace <enter your bitcoin address here> with your own address between the quotes.
Extension for Google Chrome: http://tampermonkey.net/Info about GreaseMonkey: http://en.wikipedia.org/wiki/Greasemonkey |
|
|
|
|
Show Posts
