I will however try tinkering with the time min read/write timeout function, since it could be triggering too early.
Tinkered with the min read/write timeout in the advance usb settings for the ports... no... OMG, don't do it, it did nothing, and swear made it worse. Also changing bauds rates / bits per second has no effect either. I now agree with the others, I can't see any use in trying to tinker with the usb settings, it does not help. I'm now testing it one on my linux laptop, while the other remains on my windows laptop. |
|
|
|
A tip for stability, make sure you disable the fifo on the fpga com ports, go into your com ports under device manager and select advanced, then disable the 16550 uart.
kind regards
None of them have this, so not sure why you are advising that. I know I'm looking in the right place, since my blackberry has it's own com port (tethering it) and it has that option in the advance tab. These FPGA's have not, instead a whole array of other things. None of which relate to Fifo, or buffers. I will however try tinkering with the time min read/write timeout function, since it could be triggering too early. |
|
|
|
|
So it's mostly luck right now, until a new control can improve stability? However I will try a few different usb settings just in case it helps.
I'm sure others have no problems at all, I seem to have the performance, but not the stability.
Later I will try my Linux rig, in case their is any difference there, it doesn't do much most of the time, so it will be far more dedicated to mining than this windows laptop is.
|
|
|
|
|
Any tips or advice on getting the hardware stable for more than 2 hours plus. It tells me that both of the units have failed.
I'll get an exact copy of the message next time it occurs. At first I figure maybe it was the usb slot was powering down or something.
But it's also happened in under 30minutes of me running it. I've also set all my usb slots to not turn them off to save power early on in testing these.
The com ports are often what disappears from the device manager, at which point I assume that is why they stop working.
Is their anything that that can help force them to stay... hmm maybe I'll go look.
I've solved all the software stability problems just by moving upto to Cgminer 2.5. That is far more stable than previous versions, good work on that Kano and the team (there is more than 1 of you right?)
|
|
|
|
|
2.5 seems more stable right now, than the others, we shall see if it remains that way in the morning.
|
|
|
|
|
haha, I most definitely don't know what a rock solid internet connection is, I've just moved house and currently mining via my laptop which is tethering via my blackberry. I have a feeling my phone provider is rather unhappy with me right now. Cable broadband just 24 hours away, yay!
|
|
|
|
Had no luck getting both boards to mine in the same instance of CGminer so far, had to run one for each board.
Not that is a problem, since at the end of the day, it allows me to keep and eye on them, in case one decides to crash.
Out of curiosity I switched from using the cgminer source provided on the support page, to the cgminer that I usually use (3.43), which is more up to date, and it happily works with more than 1 board at once. Will try 3.50 soon, but will trial run this one first, see if it runs it any more stable. |
|
|
|
|
According to my pool I use, one of my boards is averaging (over 1 hour) 375 Mh/s and the other is 400 Mh/s.
Impressed so far.
|
|
|
|
What we would like to do in the nearest future:
1. More markets USD, GBP
I like your method of doing things. I look forward to when GBP is an option in your exchange. Thank you. We are sorry we are unable to to provide you with 4 markets at the beggining, but we would like to take things slower but precisely. So when we hit to 4 markets, all transaction would be automatic or semi automatic with different authentication options available. In addition we would like to have Multilingual support first, not only limited to english, or at least different user interface language available. Best Regards Thanks, I will keep track of how your company does, this is very few in the British Pound (GPP) market at the moment. |
|
|
|
Is their a list I've just not found yet, that lists all the exchanges that happily work in GBP (Local currency in United kingdom) and more ideally have a presence here so not to be screwed on unnecessary bank fees.
I'm only aware of two and while both are well established, don't exactly have an ideal track record to trust them. Does one just accept thats whom I have to deal with? or is their other options?
Which two, what track record. Thx. Their is only 2 that really natively trade in GBP, both have had a mixture of problems with their site, customer support issues and comprises since their start. I did not want to name them, at the end of the day, I was kinda hoping they and others would at least be interested in promoting their services in my thread. They are some of the oldest in the business and yes they are bound to have issues from time to time. But my paranoia tends to get in the way a lot, when it comes to trust others with my money. I don't mind stock my coins for a while, I do want to feel comfortable trading. I've seen what happens when people trust a company too much with their money and bitcoins. Just look what happened with bitcoinia, ouch. |
|
|
|
Thanks the link for the Trade page on the Wiki is very useful. It appears according to that, their is only that 2. Guess I've got to decide which one I can trust the most. |
|
|
|
|
*bump*
I think I see a tumble weed go by. Hmmmm
|
|
|
|
What we would like to do in the nearest future:
1. More markets USD, GBP
I like your method of doing things. I look forward to when GBP is an option in your exchange. |
|
|
|
The port numbers may change so you need to keep an eye on what is used.
We are going to try and shortcut some of this stuff so bear with us whilst get those materials get produced. It's been impossible to keep documentation up with the development progress and changes but that should be improving now as it settles down. What we should have today is a contstraints file for the array FPGA. That will tell you where dip switches and leds are. It's not going to be very complicated as there is a very small set of I/O.
The LEDs depend a lot on what is on the board has as configuration bitstreams and these do vary with them. Recently the back two are being shipped without a configuration bitstream. That will change with the next major release of bitstream when we bring all 4 FPGAs into operation.
The FPGAs notionally operate as 2 pairs at least in this iniial phase.
Understandable, I am happy documentation is starting to catch up, it will help many who do want to contribute to it's development. I've got both boards mining now and humming away at as fast as I expect 2 cores can do. I look forward to every update, especially if your close to the bitstream for all 4 cores to be working. Had no luck getting both boards to mine in the same instance of CGminer so far, had to run one for each board. Not that is a problem, since at the end of the day, it allows me to keep and eye on them, in case one decides to crash. I use a pretty simple command line, since the rest is in a cgminer.conf file: cgminer_twintest --disable-gpu -S noauto -S \\.\COM25 -S \\.\COM26 -S \\.\COM22 -S \\.\COM27 Let me know if I'm doing it wrong. 25 and 26 are for board 1, 22 and 27 are for board 2. How they managed to auto-configure themselves that way I don't know, not going to change it now  However the below is the only way I get them to work, running them separately. cgminer_twintest --disable-gpu -S noauto -S \\.\COM25 -S \\.\COM26
cgminer_twintest --disable-gpu -S noauto -S \\.\COM22 -S \\.\COM27 The cgminer.conf file is nearly identical except for the pool data, which I'm purposefully blanked out and is slightly different for each one, separate worker, at first allows me to alert me if one stops. {
"pools" : [
{
"url" : "xxx",
"user" : "yyy",
"pass" : "zzz"
},
{
"url" : "xxx",
"user" : "yyy",
"pass" : "zzz"
}
],
"api-port" : "4028",
"disable-gpu" : true,
"expiry" : "120",
"log" : "5",
"queue" : "2",
"retry-pause" : "5",
"scan-time" : "60",
"kernel-path" : "/usr/local/bin"
}Hey, it works, can't complain just giving you my feedback and loving my new hardware. |
|
|
|
So Yohan, there is a lot of other switches on this board, what do the rest do, or do I start play guessing games with seeing what they do?
You have 68 pages to read to 100% catch up on this topic. I suggest you start doing it in reverse chronological order looking for your answer. By your tone, my impression is that you are asking to be spoon fed answers without trying to find them on your own. If doing that research is too much work, then yeah, I suggest you start randomly flipping switches and see where that gets you. BTW, it takes a full day, or two, for the cgminer U metric to be fully settled down to a solid number. Actually, longer than that, but a couple of days will get you to about a 95% accurate number. I know what SW1 and 6 do. It's the other 4 I don't. If he did say what they did, I missed it. No need to assume I wanted to be spoon feed answers, I was asking a question I believe hadn't been answered yet. Page 66, has a nice little graph, but it only describes SW1 and 6. If the other switches are described elsewhere I will go look, I didn't know. You should have received the boards with DIP switches set for the loaded twin bitstream which does only run 2 FPGAs so expect hasing about 380MH/s. We are getting U here between 5 and 6 which what to expect at the moment. DIP switches SW2-5 usage is entirely dependent on the bitstream used. When we release our native bitstream they won't be used at all but settings for the "twin" are on http://www.enterpoint.co.uk/cairnsmore/cairnsmore1_support_materials.html. We are now shipping all boards now with the "twin" bitstream running on positions 0 and 3. For the twin only the first 2 bits of each switch are actually used. One bit is a reset the other is the hash start point. There are 4 com ports of which only 2 are used for coms. the other 2 are used for JTAG and SPI programming functions. If running windows the easy way to check what ones correspond to coms is to look in the Device Manager. It's usually fairly obvious in there. We do have a small utility coming that will do some port scanning that's mainly aimed at testing but might have some general application in helping setup. Thanks for explaining that Yohan. Lets just make sure I understood it correctly. I'm sorry if I sounded newbish. I'm just trying to discover in my own way how this all works. Yeah, I know it's not always a good idea. SW 2-5 were not setup for the Twin bitstream, looked more like the initial shipping build, it was no bother, I got things working either way. SW 2-5 are bitstream specific and your saying most settings most end users will tweak would be SW 1 and 6? However when new bitsteams are made, those will be more important to make sure they are in the right place, or ignored entirely, depending on the bitsteam. I already expressed to you I would like a chance to make my own, once I learn how. So I'm going to go read up on what info their is on SW 2-5 to see if that will have any effect on how do a bitstream. So the com ports are suppose to be sharing 2 of these spartan chips per port, but at the moment only 1 is being used per port. The other 2 ports related to the JTAG and SPI (I first assumed it was for each chip). So for me, that would be port 23 and 24 for JTAG and SPI, I can quiet happily remove those from the list of ports to be trying. I notice how when first turned on all 4 leds of different colors come on next to the dip switches 2-5. I gathered this relates to a response by the chips themselves, slowly the front 2, one by one turn like a orange color, almost like it's "ready". But the back two don't. Thus they look like they are completely idle. Interesting Stuff, but apparently I do need to go do abit more reading, since I have forgotten what was posted earlier in this now very long thread. |
|
|
|
So Yohan, there is a lot of other switches on this board, what do the rest do, or do I start play guessing games with seeing what they do?
You have 68 pages to read to 100% catch up on this topic. I suggest you start doing it in reverse chronological order looking for your answer. By your tone, my impression is that you are asking to be spoon fed answers without trying to find them on your own. If doing that research is too much work, then yeah, I suggest you start randomly flipping switches and see where that gets you. BTW, it takes a full day, or two, for the cgminer U metric to be fully settled down to a solid number. Actually, longer than that, but a couple of days will get you to about a 95% accurate number. I know what SW1 and 6 do. It's the other 4 I don't. If he did say what they did, I missed it. No need to assume I wanted to be spoon feed answers, I was asking a question I believe hadn't been answered yet. Page 66, has a nice little graph, but it only describes SW1 and 6. If the other switches are described elsewhere I will go look, I didn't know. |
|
|
|
|
Did some tinkering, I noticed the default for queue was still at 1, same as my little laptop uses on it's GPU's.
I figured something 5-10x more powerful would need to have a bit of room as it eats through it's queue of work.
It did increase the U rate, it appears to now hover over 7, has done for a while now. It's still rising a little as I type this.
Takes a little while before it does, but it did not get to 7 the first hour I had it at a queue of 1, it barely got to 6.
However I have no idea what this is? E: 220% + (it's often this high)
It's only recognising 2 of the 4 ports.
This one is using ports 23, 24, 25 and 26. However complains about ports 23 and 24 at start up of CGminer.
"Cairnsmore Detect: Test failed at \\.\COM23: get 00000000, should: 000187a2"
"Cairnsmore Detect: Test failed at \\.\COM24: get 00000000, should: 000187a2"
So Yohan, there is a lot of other switches on this board, what do the rest do, or do I start play guessing games with seeing what they do?
|
|
|
|
CGminer tells me it's hashing away at 825Mhash/s, so I'll wait for my pool to confirm this.
If your U:rate is 10-11 then its doing 800Mh/s, but more likely its doing alot less than that. Most users are reporting between U:1-4 per board. kind regards Right now it's hovering between 5 and 6. That U rate is the shares per minute as I understand it. Which in comparison to my laptops 80 Mhash/s U rate of nearer to 1, would make it feasible it's doing 400Mhash/s. Lets go back to tinkering, lets see why the other chips don't want to play with the others  |
|
|
|
The problem with me having one core working much slower that the other ones is back.
I am running 3 boards with an unpowered usb-hub at an usb3 port (the boards do not even detect correctly in regular usb ports). Running the twin_test bitstream, with the correct dipswich positions used while flashing and operating, as indicated in your pdf. The miner I am using is yor cgminer_twintest.exe I am starting it with the command cgminer_twintest -o mint.bitminter.com:8332 -u USR -p PASS --disable-gpu -S noauto -S\\.\COM22 -S \\.\COM23 -S \\.\COM26 -S \\.\COM27 -S \\.\COM30 -S \\.\COM31
Any other relevant information that would help identifying this, just ask.
Just quoting this, since the command line stuff was useful for me to start getting these working for me. Needed to modify mine for the right com ports. Will provide feedback and results later today. Just got my 2 boards. Doing one at a time, I'm sure the other works fine. Got one working and flashed to latest bitstream. CGminer tells me it's hashing away at 825Mhash/s, so I'll wait for my pool to confirm this. |
|
|
|
|
While I do not have anything invested or did not have anything invested in bitcoinica, I do have an interested in the outcome.
Two very big exchanges are wrapped up in this and it massively effects our community both the more business side as well as from the side of the miners.
The exchange was clearly run in a way that was negligent in how lax they took their security, their is multiple examples of this expressed in this thread.
From single point of authorisation, where double is becoming the norm. As well as passwords being found in source code available in the public domain and not changed for the live site.
Quiet frankly they made it as easy for the hacker, as hiding 1 key under the doormat and let him walk in unlocking the single lock on the door. Nothing stopping him afterwards from just going around and stealing anything he wanted after that.
I'm no expert in this, but in the insurance business I do know this, if the criminal managed to gain access because you left your doors open or left the keys available to him, they will blame you and you get no compensation. Very few small business have insurance for the same style of thing in the digital business, but the blame game works the same way.
Their lack of security were entirely at blame, the same applies here, the hacker was just a opportunist who did his act, with so little effort, the blame is entirely upon the person(s) responsible for placing passwords into the public domain and to a smaller (but still important) whom should of put in place double authorisation for accessing the sites "main vault".
The sounds like the both of these issues, can be laid upon the original guys.
But the "new" owners are also responsible for not fixing these glaring issues, if they had access and rights to do so.
I wish everyone the best of luck getting your bitcoin and/or fiat currency
|
|
|
|
|
Show Posts
