A disconnect command is planned for future. It would allow to identify the disconnected device by the "configure-me" LED's
Ok, good. This makes it easier to spot a unit with a low hash rate due to heatsinking problems. |
|
|
|
|
I wonder if this could be causing some of the problems the boards are experiencing:
[urjtag:0:0] measuring clock frequency at icarus/carinsmore pin (fgg484.J1)
[urjtag:0:0] measured input clock frequency at 49 Mhz
[urjtag:0:0] assuming input clock frequency of 48 Mhz
|
|
|
|
|
2 Feature requests/suggestions:
- Would be nice to be able to print out boards stats with a command. Now it automatically does it from time to time, but the wait is pretty long..
- Also, identifying boards in a cluster is quite impossible (without labeling them). Would it possible to add a command to blink an LED on a board by entering it's serial number?
|
|
|
|
If you want to run ztex on RPi, there's an ARM port available: http://blog.villekangas.comYou will need to have java installed to run it: sudo apt-get install openjdk-6-jdk Then just make sure you have ZtexBTCMiner-120417-ARM.jar in the directory where you run it: java -cp ZtexBTCMiner-120417-ARM.jar BTCMiner etc.. You might want to tip the guy, and hopefully we'll have a RPi port of eldentyrrell's bitstream aswell. I'm running a cluster with: root@raspberrypi:~# uptime 14:46:34 up 2 days, 1:41, 1 user, load average: 0.37, 0.41, 0.46 |
|
|
|
|
I was informed that there was an AML (anti money laundering) issue taking place. I was asked to send scanned copies of my transfer to them?! They're definitely not communicating enough regarding this. It's been 8 days now since my transfer, and I still have no idea where my money is and when is it going to appear on my account.
If they have problems with the authorities, why not state that on their site? Why not warn people not to transfer money, if it will get frozen by the investigation? What are they thinking of achieving by this conduct?
|
|
|
|
Let me guess.. next bitstream will be called fraenkel?  Yes, but only because I couldn't find a name that starts with "E". How about eilenberg or euler? |
|
|
|
|
Made a transfer on 29th of june. Still hasn't appeared on my account.
|
|
|
|
Let me guess.. next bitstream will be called fraenkel? |
|
|
|
Heads up: there is a really stupid mistake in the host software that is causing it to simply lose up to 20% of the nonces. The higher the hashrate, the more it loses both because work is loaded more often and because each second of time spans a greater part of the nonce-space.
I wanted to go directly from 0.99 to 1.0 but this is too important. I will post a fix ASAP.
Fired it up with command: java -Xbootclasspath/a:ZtexBTCMiner-120221.jar -jar tml-0.999.jar ztex:0 http://mywallet:foo@mining.eligius.stResult: [ztex:0:1 ] decrypting nonce at address 0x000000b8 [ztex:0:1 ] encrypted nonce = 0x7e27cb87 [ztex:0:1 ] invalid nonce: 0x6986b80e [ztex:0:1 ] signcrypting ee52b1778658629c131a2fa600e293dd8f7b2eb34a16cfea39947b2f38770e03:a39a33904ff68ce71a099431 [ztex:0:1 ] loading job ee52b1778658629c131a2fa600e293dd8f7b2eb34a16cfea39947b2f38770e03:a39a33904ff68ce71a099431 [ztex:0:2 ] signcrypting ee52b1778658629c131a2fa600e293dd8f7b2eb34a16cfea39947b2f38770e03:a39a33904ff68ce81a099431 [ztex:0:2 ] loading job ee52b1778658629c131a2fa600e293dd8f7b2eb34a16cfea39947b2f38770e03:a39a33904ff68ce81a099431 [ztex:0:0 ] decrypting nonce at address 0x0000005c [ztex:0:0 ] encrypted nonce = 0xf95536c8 [ztex:0:0 ] invalid nonce: 0x30f95961 [ztex:0:0 ] signcrypting ee52b1778658629c131a2fa600e293dd8f7b2eb34a16cfea39947b2f38770e03:a39a33904ff68ce91a099431 H:0/0,0,0 X:223 C:152,136,157 E:100/100,100,0 T:15m | H:0/0,0,0 E:100/100,100,0 A:0 R:0 T:1m19s EDIT: Tried using church (0.95) bitstream with tml-0.999.jar . Seems to be working, I'll leave it running to see the performance. EDIT2: Best results so far by running with recalibrate_clock=false and setting clocks manually to 172,164,164 giving me X of whopping 250 on a standard ztex board |
|
|
|
If I have made the correct association you should have had an email on the 23rd of June. I will forward it again to you.
Thank you! Amazingly enough, I couldn't find that mail in either my inbox or junk box. I might have deleted it by accident. |
|
|
|
|
Interestingly I'm getting better results with 0.95. Setting same clocks on 0.99 gets me loads of errors.
|
|
|
|
Advance Warning
There are 1 or 2 people on our June delivery promise who have not responded to the notification that their unit is ready. We can only speculate why that might be but we do need to release reserved stock from our pending shelves in order to satisfy our general customer demand for more units and as fast as we can deliver. So some time later next week we be doing an order purge for anyone on a June delivery promise who has not responded, and that means orders will be cancelled from our side and you will lose your right to the offer price and your place in the queue.
We will do something similar in a few weeks time for July promise orders and so on until we eventually reach the point where Cairnsmore1 is a stock board with no pre-order structure.
Yohan
I've requested payment info several times, never got any. I got e-mail from you on 16th of june that my VAT had been verified. |
|
|
|
I've had strange issues with a cluster of 18 ztex boards connected through 2 separate powered hubs run by cgminer 2.4.2 and 2.4.4 on a Raspberry Pi. 1 random board dies (and gets a LED on). After 10 minutes cgminer pronounced it dead. I must stress that there's seems to be no logic in what board fails. It's completely erratic (4 different boards now after each restart of cgminer). Any clues? EDIT: And now segfault: [2012-07-03 22:18:27] ZTEX 04A32Exxxx-1: Failed readHashData with err -1
[2012-07-03 22:18:27] ZTEX 04A32Exxxx-1: Failed to read hash data with err -1, retrying
[2012-07-03 22:18:27] ZTEX 04A32Exxxx-1: Failed readHashData with err -4
[2012-07-03 22:18:27] ZTEX 04A32Exxxx-1: Disabling!
[2012-07-03 22:18:27] ZTEX 04A32Exxxx-1: Failed to read hash data with err -4, giving upSegmentation fault
EDIT: removed 1 board, restarted. 1 random dead again. |
|
|
|
|
I would personally love to see a well documented Bitcoin-specific ASIC that is sold by reel (or in smaller quantities to hobbyists by a retailer). This way there could be many companies developing and offering products from "coffee-warmers" to 4U Terahash-class racks. ASIC performance would this way be available to all at a reasonable cost, and the manufacturer/owner of IPR would get a fair flow of income without the hassles of consumer relations and warranty.
|
|
|
|
Stock volts. Need I say more?  |
|
|
|
Status update: 0.95 was running like a dream overnight finally converging to 240Mh/s on eligius. Unfortunately when I woke up I found this: [ztex:0:1 ] loading job 67dd99a96f74bda852f43c5e1a87a7dc8e18fae0b2276395274639a5b186798f:94f47e834ff26a021a09b78a
H:286/214,71,0 X:240 C:170,150,160 E:0/0,0,0 T:1m | H:234/81,73,79 E:0/0,0,0 A:1568 R:12 T:8h2m13s Exception in thread "Thread-2" java.lang.RuntimeException: java.io.EOFException
at com.triconemining.limp.LimpConnection.run(LimpConnection.java:53)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.EOFException
at com.triconemining.util.VarInt.read(VarInt.java:16)
at com.triconemining.limp.LimpConnection.run(LimpConnection.java:50)
... 1 more
[ztex:0:2 ] signcrypting 67dd99a96f74bda852f43c5e1a87a7dc8e18fae0b2276395274639a5b186798f:94f47e834ff26a031a09b78a
I'm gonna tweak my clocks up a notch to 245 total and let it run again. I'm quite happy with this performance and the fact no mods were required (apart from extra cooling). Although I'm tempted to try how far it can go with volt mod |
|
|
|
It's been running almost 6 hours now, and it's not getting the performance I was getting with .92b:
H:143/71,0,71 X:231 C:162,140,160 E:0/0,0,0 T:1m | H:178/60,59,58 E:18/22,11,20 A:777 R:14 T:5h17m3s
With eligius reporting 3h avg. of just ~180Mh/s. Lot's of invalids: [ztex:0:2 ] invalid nonce: 0x8b170ab6
It's probably the clock calibration code. What kind of results do you get when you set the frequencies manually and disable clock calibration with java -Dtriconemining.recalibrate_clock=false -jar tml.jar ztex:0 <mining-url>I've been running 0.95 for about an hour now as you instructed, with clocks set at 170, 150, 160 (~240Mhash) Looking good so far, no errors. Me likey! |
|
|
|
|
It's been running almost 6 hours now, and it's not getting the performance I was getting with .92b:
H:143/71,0,71 X:231 C:162,140,160 E:0/0,0,0 T:1m | H:178/60,59,58 E:18/22,11,20 A:777 R:14 T:5h17m3s
With eligius reporting 3h avg. of just ~180Mh/s. Lot's of invalids: [ztex:0:2 ] invalid nonce: 0x8b170ab6
|
|
|
|
|
Show Posts
