Bitcoin Forum
December 05, 2016, 06:53:14 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 109512 times)
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
September 21, 2012, 03:57:06 PM
 #761

With all the delays, don't you think making this project open source would have given you more "revenue"?

I haven't enabled commissions yet, so my total revenues so far are a whopping 0.0 BTC.


Look at the CM1 bitstream - a 300 BTC bounty was paid out and could have been yours.

This is not the only thing I have going on right now.  And the other things I have going on amount to a lot more than 300 BTC.

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.
1480963994
Hero Member
*
Offline Offline

Posts: 1480963994

View Profile Personal Message (Offline)

Ignore
1480963994
Reply with quote  #2

1480963994
Report to moderator
1480963994
Hero Member
*
Offline Offline

Posts: 1480963994

View Profile Personal Message (Offline)

Ignore
1480963994
Reply with quote  #2

1480963994
Report to moderator
1480963994
Hero Member
*
Offline Offline

Posts: 1480963994

View Profile Personal Message (Offline)

Ignore
1480963994
Reply with quote  #2

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

Posts: 1480963994

View Profile Personal Message (Offline)

Ignore
1480963994
Reply with quote  #2

1480963994
Report to moderator
1480963994
Hero Member
*
Offline Offline

Posts: 1480963994

View Profile Personal Message (Offline)

Ignore
1480963994
Reply with quote  #2

1480963994
Report to moderator
1480963994
Hero Member
*
Offline Offline

Posts: 1480963994

View Profile Personal Message (Offline)

Ignore
1480963994
Reply with quote  #2

1480963994
Report to moderator
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
September 21, 2012, 03:58:01 PM
 #762

the 'tml-leibniz.bit' bit stream file, has the 10x size of a standard bitstream file and it is an 'Ascii' file and not binary like a standard bit file.

I am so, so sorry -- you're right, I uploaded the wrong file.

I have re-uploaded tml-1.11.jar, please try again.  The md5 for the new version is

  3ae38972bbd2c82e3f08e22bc545e771

  adea3df2fb12578b542a4e8b58784a68

  a88413d574f8ced1608b4c6add54769f

(sorry, a bunch of tiny changes I'd had queued up)

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
September 21, 2012, 04:00:00 PM
 #763

Hey eldentyrell, please link up with cablepair so the MMQ can get the benefit of your bitstream.

I've responded to all emails…. FWIW I have a hard time remembering the connection between peoples' email addresses, real names, and businesses.  Is cablepair one of the people on the x6500 email thread with TheSeven and the MODMINER people?  Or is he with a different outfit?

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.
BR0KK
Hero Member
*****
Offline Offline

Activity: 742



View Profile
September 21, 2012, 10:06:46 PM
 #764

He is the one behind btcfpga.

He sells the mod miner quad

Smiley

purelithium
Hero Member
*****
Offline Offline

Activity: 504



View Profile
September 22, 2012, 12:58:03 PM
 #765

Cablepair is Tom, he's with Modminer.

Like my post? 1H7bfRYh7F89mfmFgsRCdn4awDaUHQmYqY
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
September 22, 2012, 05:52:51 PM
 #766

Loading in the Device works, but now i got this error:

"DCM did not report ready for programming"

That happens in ...miner.DCM.setClockFrequency(DCM.java:151)

Could you please post the complete command line you're using, with all arguments, and the complete log that's printed out?  It's hard to tell what's going on just from this one lone line.  However, I will tell you that this is the error message you get if the clock input to the chip isn't running, so you might want to double check that.

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.
AxelMi
Jr. Member
*
Offline Offline

Activity: 43


View Profile
September 23, 2012, 09:26:19 PM
 #767

Today i have time to test again.

You have to change the Device Identifier Code.
Cause My Spartan 6 have: Device IDCODE= 0x4401d093. That is the latest Revision that Xilinx delivers.

http://www.xilinx.com/support/documentation/user_guides/ug380.pdf page 80, the First 4 Bits Are Revision Codes.

My complete Commandline is:
java -Dbitstream=leibniz -Dclock_pin=csg484.W11 -Dclock_pin_freq=6.666 -jar tml.jar urjtag:flyswatter http://HelloWorld:-1@my.pool.bitcoin:8332

And this is the complete output:

_________________________________________________________________________
Tricone Mining Logic, host software v1.11

   IF YOU EXPERIENCE HIGH ERROR RATES: try running just one ring at a
   time (e.g. use 'ztex:0:0.0' on command line instead of 'ztex:0'). 
   If each ring works error free on its own, but you get errors when 
   running all three, it means your power supply is sagging.         

             adding work source gigaforge.com
             starting long poll thread
[flyswatter     ] found new board urjtag:flyswatter
[urjtag:flyswatter:0] found new chip
[urjtag:flyswatter:0] programming FPGA with bitstream leibniz
             USERCODE before bitstream upload: 0xcafebabe
             USERCODE after bitstream upload: 0xcafebabe
[urjtag:flyswatter:0]   done programming FPGA
[urjtag:flyswatter:0] magic number check ok 
[urjtag:flyswatter:0] chip is running bitstream version 0x50547e78, built 8d8h54m32s ago
[urjtag:flyswatter:0] chip has 3 rings       
[urjtag:flyswatter:0] assuming input clock frequency of 6 Mhz
[urjtag:flyswatter:0] asserting global reset
[urjtag:flyswatter:0.0] disabling DCM bypass mux
[urjtag:flyswatter:0.0] opening signcryption channel
[urjtag:flyswatter:0.0] setting clock to 149 Mhz, mult=45 div=2
H:0 X:0 E:0 T:10s   |  H:0 E:0 A:0 R:0 T:10s java.io.IOException: DCM did not report ready for programming
   at com.triconemining.miner.DCM.setClockFrequency(DCM.java:151)
   at com.triconemining.miner.DCM.setClockFrequency(DCM.java:62)
   at com.triconemining.miner.RingWrapper.setClockFrequency(RingWrapper.java:393)
   at com.triconemining.miner.ChipWrapper.enableRing(ChipWrapper.java:268)
   at com.triconemining.miner.ChipWrapper.enableRing(ChipWrapper.java:184)
   at com.triconemining.miner.BoardWrapper.run_(BoardWrapper.java:101)
   at com.triconemining.miner.BoardWrapper.run(BoardWrapper.java:73)
   at java.lang.Thread.run(Thread.java:722)


My Clock is generated from a Frequency Generator. I also tried with 5, 10 and 20 Mhz. always the same result.
cablepair
Hero Member
*****
Offline Offline

Activity: 854


https://btc-republic.com/index.php?ref=cablepair


View Profile WWW
September 24, 2012, 12:47:54 AM
 #768

Elden,


Please review this at your earliest convenience.

https://bitcointalk.org/index.php?topic=112303

Thank you for all you do Smiley

Tom
BTCFPGA.com

eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
September 26, 2012, 08:37:52 PM
 #769

FYI I will have limited/unreliable internet and email access until Tuesday 02-Oct.

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.
RicRock
Sr. Member
****
Offline Offline

Activity: 288



View Profile
October 04, 2012, 11:54:03 AM
 #770

Hello,

I've been happily running on my x6500 until 10 min or so ago.

Now I'm getting:

[x6500:AH01ABH9:0.0]   new cipher state = 0x4a1ab2152fd629d276cd6299
             restarting blocked threads for com.triconemining.signcryption.SCClient$Connection@20d9896e
               finished restarting blocked threads for com.triconemining.signcryption.SCClient$Connection@20d9896e
             opening signcryption connection to limp.tricone-mining.com/23.23.249.133:7778
listener thread for limp.tricone-mining.com/184.82.49.28:7778 exiting due to java.io.IOException: please update your TML to the latest version.

I'm running tml.1.11 from the website and do not see a newer version... anyone else having this problem?

Plazzman
Member
**
Offline Offline

Activity: 85



View Profile
October 04, 2012, 02:48:38 PM
 #771

Hello,

  I'm running 2 mod miners and mine died about the same time.
I don't have remote access to them yet and I'm not in front of them so I have know Idea what the error is yet.
Just weird that mine died at roughly the same time as yours.


 
cablepair
Hero Member
*****
Offline Offline

Activity: 854


https://btc-republic.com/index.php?ref=cablepair


View Profile WWW
October 04, 2012, 06:29:28 PM
 #772

Elden blocked a huge group of miners from using his system because he claims we need a "TML Update"

His mining software says that you need to upgrade to the latest version of TML and it effectively knocked everyone's rigs offline (overnight for most of us I might ad) without any prior notice either on the forum or on his tricone-miners subscription news letter.

So since a lot of people have lost some significant mining time due to this complete act of irresponsibility

my team has done a full analysis of this update and here are their findings:

No Bugfixes found / changes appear to be insignificant

Actual Changes from TML 1.11 to 1.12:
* a bit of whitespace here and there
* changed the default bitstream name from kreisel to leibniz
* fixed a misspelled parameter name in the usage info screen
* changed a couple of copyright headers
* bumped the version number to 1.12

Current Known TML Bugs:
* MakeFile Bug -- still unfixed
* Clocking Bug -- still unfixed
* Bitstream Upload Bug -- still unfixed


I am sorry elden but if you want people to feel secure using a centralized proprietary system like this you really need to do things in a way to increase our confidence and surprising us in the middle of the night by inexplicably taking down our mining rigs for no apparent reason is not a good way to do that.



Borzoi
Jr. Member
*
Offline Offline

Activity: 54



View Profile
October 04, 2012, 07:20:42 PM
 #773

Actual Changes from TML 1.11 to 1.12:
* a bit of whitespace here and there
* changed the default bitstream name from kreisel to leibniz
* fixed a misspelled parameter name in the usage info screen
* changed a couple of copyright headers
* bumped the version number to 1.12

Looks if code changed to avoid send of shares below difficulty.  May be because of load on TML servers.  It would be excuse for not allowing connections from older client.

Bitstreams significantly differ, but could be result of compilation of minor change.  Appears some midstate java code calls simplified.  Could be reason for larger bitstream, to move into fpga.  Midstate changes relate to signcryption and could be server affecting as well.

I am guessing based on simple analysis of available source code and eyeball + tools of bitstreams.

MS EECS MIT, PhD Math Stanford, L2 dropout American University Washington College of Law.
Forgive my English.  It is functional with good vocabulary but not so good grammar.  I give BNF for my English so not to offend you. Smiley
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
October 04, 2012, 10:41:29 PM
 #774

Wow - if that above is true - damn stay away from this
Proprietary FTL ...

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
TheSeven
Hero Member
*****
Offline Offline

Activity: 504


FPGA Mining LLC


View Profile WWW
October 04, 2012, 11:25:48 PM
 #775

Actual Changes from TML 1.11 to 1.12:
* a bit of whitespace here and there
* changed the default bitstream name from kreisel to leibniz
* fixed a misspelled parameter name in the usage info screen
* changed a couple of copyright headers
* bumped the version number to 1.12

Looks if code changed to avoid send of shares below difficulty.  May be because of load on TML servers.  It would be excuse for not allowing connections from older client.

Bitstreams significantly differ, but could be result of compilation of minor change.  Appears some midstate java code calls simplified.  Could be reason for larger bitstream, to move into fpga.  Midstate changes relate to signcryption and could be server affecting as well.

I am guessing based on simple analysis of available source code and eyeball + tools of bitstreams.

Indeed, besides pushing a new bitstream he also implemented difficulty >1 support, wow!
But why on earth does this warrant a breaking protocol change AT ALL? (Not to even mention that there was no prior notice.)
Well, maybe the old bitstream contained some critical flaw in the signcryption code that was fixed in the new one? I can't think of a different (rational) explanation. But OTOH it wouldn't be the first time for ET to act in a completely irrational way.

My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
ShadesOfMarble
Donator
Hero Member
*
Offline Offline

Activity: 543



View Profile
October 04, 2012, 11:46:11 PM
 #776

I still don't get why he didn't opt to open source his bitstream. Donations worth hundred of BTC instead of zero revenue from forced donations.
Yes, his next project will yield "much more than those few BTC" but what does this project has to do with that? FPGA mining will be dead in a few months.

In my opinion this already *was* irrational...

Review of the Spondoolies-Tech SP10 „Dawson“ Bitcoin miner (1.4 TH/s)

[22:35] <Vinnie_win> Did anyone get paid yet? | [22:36] <Isokivi> pirate did!
makomk
Hero Member
*****
Offline Offline

Activity: 686


View Profile
October 05, 2012, 12:10:39 AM
 #777

Indeed, besides pushing a new bitstream he also implemented difficulty >1 support, wow!
But why on earth does this warrant a breaking protocol change AT ALL? (Not to even mention that there was no prior notice.)
Well, maybe the old bitstream contained some critical flaw in the signcryption code that was fixed in the new one? I can't think of a different (rational) explanation. But OTOH it wouldn't be the first time for ET to act in a completely irrational way.
I suspect he accidentally released enough information for a clever hacker to bypass the signcryption. Been resisting the temptation to try.

Quad XC6SLX150 Board: 860 MHash/s or so.
SIGS ABOUT BUTTERFLY LABS ARE PAID ADS
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
October 05, 2012, 12:27:20 AM
 #778

Indeed, besides pushing a new bitstream he also implemented difficulty >1 support, wow!
But why on earth does this warrant a breaking protocol change AT ALL? (Not to even mention that there was no prior notice.)
Well, maybe the old bitstream contained some critical flaw in the signcryption code that was fixed in the new one? I can't think of a different (rational) explanation. But OTOH it wouldn't be the first time for ET to act in a completely irrational way.
I suspect he accidentally released enough information for a clever hacker to bypass the signcryption. Been resisting the temptation to try.
So ... someone was hashing with his bitstream for free ... instead of ?

Sounds like a good reason to kill off everyone (without notification) mining using his bitstream until they work out what is happening ... NOT!

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
eldentyrell
Donator
Legendary
*
Offline Offline

Activity: 966


felonious vagrancy, personified


View Profile WWW
October 05, 2012, 12:21:43 PM
 #779

Elden blocked a huge group of miners from using his system because he claims we need a "TML Update"

Below is an excerpt from an email I sent to TheSeven which does a good job of explaining the situation.

All of the anger is completely justified.  This was a screwup on my part.  The only consolation I offer is that this wasn't the result of me doing something, it was the result of me failing to do something.

The leibniz bitstream doesn't expire for another 40 days.  Long before then I will make sure this doesn't happen again, most likely by removing the ntime check.

FWIW, I had no idea so many people were using the TML.  I suppose that means that when I turn on the commissions I will get a nontrivial income from this, in which case I will have a strong motivation to take uptime very seriously.


Quote
Quote
On Oct 4, 2012, at 11:07 AM, theseven wrote:
((theseven being justifiably cranky about the service interruption))

TL;DR: it was not intentional, nor was it something done "on my end".  It has nothing to do with signcryption.

The pre-commission (i.e. free) bitstreams have a two-month expiration, something left over from back before I really trusted the signcryption.  The circuit won't work on jobs with an ntime more than 60 days past the date I built the bitstream -- it deliberately corrupts them.  The signcryption server simply gives you a helpful message instead of sending back invalid nonces -- the "is gateware version more than 60 days old" check is on the server side rather than in the client software.  If you don't believe me, modify your client software to lie about the gatewareVersion and try sending a piece of work from two days ago -- it'll hash just fine.

This will be removed once (if) I start charging money.  It was an insurance policy in case the signcryption backend servers got hacked or I did something wildly stupid like post a bitstream that works on non-signcrypted jobs, although I haven't built any of those in at least three months now.  My own rigs use the signcryption servers and run the same bitstream as everybody else, and I get a text message if they stop mining in the middle of the night.  This is why there was a fix posted within 15 minutes of the expiration.

At least one other ultra-high-performance bitstream has the same feature.  It has absolutely nothing to do with the signcryption.  You're going to find it in any bitstream that somebody has put a serious amount of work into.

I still have limited email until Monday.

Blue portions were edited relative to the email I sent him (due to wider audience).  Bold added for those who are skimming.

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
October 05, 2012, 12:28:16 PM
 #780

Indeed, besides pushing a new bitstream he also implemented difficulty >1 support, wow!

Yeah, because I had a similar unexpected-downtime experience with EclipseMC -- they recently started rejecting two-low-difficulty shares.

Unfortunately since the X-Reject-Reason headers aren't standardized the safest thing to do is assume that when a share is rejected that work ought to be thrown out.  This wrecks the hashrate.

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.
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!