Bitcoin Forum
December 06, 2016, 02:27:45 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 [46] 47 48 49 50 51 »
  Print  
Author Topic: Algorithmically placed FPGA miner: 255MH/s/chip, supports all known boards  (Read 109535 times)
kakobrekla
Hero Member
*****
Offline Offline

Activity: 714


Psi laju, karavani prolaze.


View Profile
November 30, 2012, 02:27:01 AM
 #901

I've started running the status_port option in an attempt to get quick statistics (and possibly kill the process early).

What am I looking at here?

Code:
modminer:/dev/ttyACM0  155 155 155   155 155 155     0  71  71    42  85 100



If I would guess the outputs order is same as via tml cli output hashrate/clockspeed/errors (ref: http://www.tricone-mining.com/tml.html ) but I dunno if your numbers makes sense.
Can you compare the two outputs?



1481034465
Hero Member
*
Offline Offline

Posts: 1481034465

View Profile Personal Message (Offline)

Ignore
1481034465
Reply with quote  #2

1481034465
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481034465
Hero Member
*
Offline Offline

Posts: 1481034465

View Profile Personal Message (Offline)

Ignore
1481034465
Reply with quote  #2

1481034465
Report to moderator
lukasbradley
Donator
Member
*
Offline Offline

Activity: 90


View Profile
November 30, 2012, 02:49:30 AM
 #902

Ugh.  It totally is the same telnet information.  I'm an idiot.
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
December 01, 2012, 10:10:46 AM
 #903

Ugh.  It totally is the same telnet information.  I'm an idiot.

Also: if you press "enter" it will cycle between showing you clock-rates, hash-rates, and error-rates.

Yeah, a lot of this stuff is seriously under-documented.

The printing press heralded the end of the Dark Ages and made the Enlightenment possible, but it took another three centuries before any country managed to put freedom of the press beyond the reach of legislators.  So it may take a while before cryptocurrencies are free of the AML-NSA-KYC surveillance plague.
mining4fun11
Member
**
Offline Offline

Activity: 110


View Profile
December 01, 2012, 02:46:30 PM
 #904

Has the issues with the modminer been corrected yet.
lukasbradley
Donator
Member
*
Offline Offline

Activity: 90


View Profile
December 01, 2012, 04:48:37 PM
 #905

Has the issues with the modminer been corrected yet.

Mine still dies after 20-60 minutes.

Tyrell, I'd be happy to open a port today and let you take a look remotely.
kakobrekla
Hero Member
*****
Offline Offline

Activity: 714


Psi laju, karavani prolaze.


View Profile
December 02, 2012, 12:09:52 AM
 #906

Has the issues with the modminer been corrected yet.

Get latest version (1.54) from here and give it a go. Follow the procedure if it fails.

eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
December 02, 2012, 12:15:03 AM
 #907

Has the issues with the modminer been corrected yet.

Mine still dies after 20-60 minutes.

The log file you sent me is from tml-1.52.  I fixed the minimum_accept_rate bug in 1.53.

The printing press heralded the end of the Dark Ages and made the Enlightenment possible, but it took another three centuries before any country managed to put freedom of the press beyond the reach of legislators.  So it may take a while before cryptocurrencies are free of the AML-NSA-KYC surveillance plague.
lukasbradley
Donator
Member
*
Offline Offline

Activity: 90


View Profile
December 02, 2012, 11:55:43 PM
 #908

Has the issues with the modminer been corrected yet.

Mine still dies after 20-60 minutes.

The log file you sent me is from tml-1.52.  I fixed the minimum_accept_rate bug in 1.53.

That works.  When the accept rate drops below, the process resets.

I was just noting that it is not stable long term.

I'll set it back up on that machine tomorrow, and give you shell access, along with a debugging port.
mining4fun11
Member
**
Offline Offline

Activity: 110


View Profile
December 03, 2012, 12:27:31 PM
 #909

Has the issues with the modminer been corrected yet.

Mine still dies after 20-60 minutes.

The log file you sent me is from tml-1.52.  I fixed the minimum_accept_rate bug in 1.53.

That works.  When the accept rate drops below, the process resets.

I was just noting that it is not stable long term.

I'll set it back up on that machine tomorrow, and give you shell access, along with a debugging port.

Does this work with just entering the new command line entry or does it need the script. 
kakobrekla
Hero Member
*****
Offline Offline

Activity: 714


Psi laju, karavani prolaze.


View Profile
December 03, 2012, 01:16:43 PM
 #910

Do you have the same issues as lukasbradley?

mining4fun11
Member
**
Offline Offline

Activity: 110


View Profile
December 03, 2012, 01:25:13 PM
 #911

Yes.  They start mining and shut off one at a time, some within 5 minutes of starting. 
kakobrekla
Hero Member
*****
Offline Offline

Activity: 714


Psi laju, karavani prolaze.


View Profile
December 03, 2012, 01:51:13 PM
 #912

Any success with http://www.tricone-mining.com/troubleshooting.html ?

mining4fun11
Member
**
Offline Offline

Activity: 110


View Profile
December 05, 2012, 01:27:12 PM
 #913


Same issues cutting out after running for a little bit.  Is anyone else still experiencing this problem on the modminer.
kakobrekla
Hero Member
*****
Offline Offline

Activity: 714


Psi laju, karavani prolaze.


View Profile
December 05, 2012, 01:33:13 PM
 #914


Same issues cutting out after running for a little bit.  Is anyone else still experiencing this problem on the modminer.


Please submit debugging log.

eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
December 05, 2012, 04:43:22 PM
 #915

Same issues cutting out after running for a little bit.  Is anyone else still experiencing this problem on the modminer.

Please submit debugging log.

Aren't you using -Dminimum_accept_rate=X?

The printing press heralded the end of the Dark Ages and made the Enlightenment possible, but it took another three centuries before any country managed to put freedom of the press beyond the reach of legislators.  So it may take a while before cryptocurrencies are free of the AML-NSA-KYC surveillance plague.
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
December 05, 2012, 04:44:30 PM
 #916

Heads up, I am going to be mostly offline until Monday.  Kakobrekla (and a few other people on the forum) have my phone number if there is any sort of dire crisis.

The printing press heralded the end of the Dark Ages and made the Enlightenment possible, but it took another three centuries before any country managed to put freedom of the press beyond the reach of legislators.  So it may take a while before cryptocurrencies are free of the AML-NSA-KYC surveillance plague.
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
December 12, 2012, 01:20:26 PM
 #917

TML 1.55 is released.


12.Dec.2012  Version 1.55
             Telnet monitor improvements
             Remove limits on HTTP submit thread pool size

The printing press heralded the end of the Dark Ages and made the Enlightenment possible, but it took another three centuries before any country managed to put freedom of the press beyond the reach of legislators.  So it may take a while before cryptocurrencies are free of the AML-NSA-KYC surveillance plague.
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
December 12, 2012, 01:22:10 PM
 #918

Yes.  They start mining and shut off one at a time, some within 5 minutes of starting.  

Please post a log, or we can't help you.

If it's too big, put it on pastebin and post a link.

Recently there have been at least three bug reports that turned out to be people running an outdated version of the TML, and the latest version had the fix for the problem.  If you post a log, at the very least we can look at the first line where it says what version it is.  You'd be surprised how many problems this solves.

Please don't post a question here and email us the log.  You can email a question and email the log, or you can post a question and post the log.  Please don't do one of each -- not only is it hard to correlate emails and forum posts (peoples' email addresses seem to bear no relation to their usernames), but if you post a problem and email the log, other users don't get to see the fix… even if it was "please use the latest version".

Thanks.

The printing press heralded the end of the Dark Ages and made the Enlightenment possible, but it took another three centuries before any country managed to put freedom of the press beyond the reach of legislators.  So it may take a while before cryptocurrencies are free of the AML-NSA-KYC surveillance plague.
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
December 15, 2012, 05:21:20 PM
 #919

Short summary: pool rejections may be caused by a memory leak.  Please be sure to use -Dminimum_accept_rate=X until I come up with a proper fix.  If you're using this option the bug will cost less than 0.01% of your hashpower.

I've found a small, slow memory leak in the TML host-side software.  It takes at least a week to fill up the JVM heap.  If you use the -Xmx=1G command line option to set the JVM heap to something huge like 1GB it will take almost a month.

What's peculiar about this is the failure mode: the TML gets stuck in a mode where it stops loading new work onto the chips, or at least waits way too long between loading jobs.  The bitstream is designed in such a way that it doesn't bother checking that it's run through the whole nonce-space -- it just loops around and starts again from the beginning.  So if you don't load new work before the nonce-space is exhausted, you get duplicate results.  Unfortunately I haven't been checking for these in software, so the duplicates get submitted to the pool.  This results in one of two things happening:

 1. If the work is more than a few minutes old, the pool reports "unknown-work" or similar.  Most pools only retain the outstanding jobs in RAM, and since this is limited they forget jobs after 90 seconds or so.  If you try to submit a nonce from a job older than this the pool will reject it even if it's valid (and even if it would have resulted in finding a block!).

 2. The job is left running on the ring for longer than (232)/(clock_rate/2) seconds, at which point it simply loops through the nonce-space again and starts reporting duplicates.  These are reported to the pool, which rejects them.

Since X-Reject-Reason headers aren't standardized, both (1), (2), and stales all count as "rejects".  You can see the pool-specific description string in the logfile, but in the statistics I don't separate them because, well, I can't (each pool uses a different text string for each case).

So the end result is that running out of memory manifests itself as what looks like a lot of stales.

I am working on a "proper" fix but I just want to emphasize that if you're using -Dminimum_accept_rate=X this bug has virtually no impact on you.  Potential hard-to-debug intermittent performance bugs like this are why I added the -Dminumum_accept_rate option.  You really ought to be using it.  I'm considering making it mandatory in the next release.

The printing press heralded the end of the Dark Ages and made the Enlightenment possible, but it took another three centuries before any country managed to put freedom of the press beyond the reach of legislators.  So it may take a while before cryptocurrencies are free of the AML-NSA-KYC surveillance plague.
lukasbradley
Donator
Member
*
Offline Offline

Activity: 90


View Profile
December 15, 2012, 05:37:40 PM
 #920

Short summary: pool rejections may be caused by a memory leak.  Please be sure to use -Dminimum_accept_rate=X until I come up with a proper fix.  If you're using this option the bug will cost less than 0.01% of your hashpower.

I'd like to make a suggestion: please add something to the effect of minimum_accept_timeframe, so that we can change the frequency that the accept rate is checked.  If I could force TML to check every minute (instead of every 10) that my rate is above 700, I think TML would be superior to BFG.

However, from my tests, the 10 minutes max that a miner may sit idle forces the average hashrate below that of other software.

In short, I would love to be able to have the miner decide to reset itself every minute if hashrate drops below 700.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 [46] 47 48 49 50 51 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!