Cairnsmore1 - Quad XC6SLX150 Board

[dodegkr]

thanks, so that seems to work :-)

is this ok ?
 [2013-05-23 21:58:32] ECM 0: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 1: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 2: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 3: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 4: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 5: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 6: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 7: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 8: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 9: Frequency scaling not supported

[1713857844]

1713857844

[1713857844]

1713857844

[1713857844]

1713857844

[1713857844]

1713857844

[1713857844]

1713857844

[1713857844]

1713857844

[jml]

thanks, so that seems to work :-)

is this ok ?
 [2013-05-23 21:58:32] ECM 0: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 1: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 2: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 3: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 4: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 5: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 6: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 7: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 8: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 9: Frequency scaling not supported

Yes, I get that too except for my ZTEX FPGA's.

[Luke-Jr]

thanks, so that seems to work :-)

is this ok ?
 [2013-05-23 21:58:32] ECM 0: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 1: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 2: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 3: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 4: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 5: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 6: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 7: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 8: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 9: Frequency scaling not supported

This suggests you don't have the dynamic clocking bitstream installed on them.

[jml]

thanks, so that seems to work :-)

is this ok ?
 [2013-05-23 21:58:32] ECM 0: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 1: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 2: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 3: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 4: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 5: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 6: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 7: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 8: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 9: Frequency scaling not supported

This suggests you don't have the dynamic clocking bitstream installed on them.

The bitstream came pre-setup from the manufacturer.

[dodegkr]

Yes they arrived with Makomk 200 on them.

Would I expect a better result with the dynamic clocking if so where can i find that?

thanks btw, day 2 and the learning continues !

[yohan]

thanks, so that seems to work :-)

is this ok ?
 [2013-05-23 21:58:32] ECM 0: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 1: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 2: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 3: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 4: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 5: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 6: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 7: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 8: Frequency scaling not supported
 [2013-05-23 21:58:32] ECM 9: Frequency scaling not supported

This suggests you don't have the dynamic clocking bitstream installed on them.

The bitstream came pre-setup from the manufacturer.

The current preloaded bitstreams are Makomk200 so dynamic clocks are not supported.

[kano]

Being newbie, whats the main difference between cg and bfgminer?
I of course want the miner best suited to the cm1 boards.

In brief, cg = original GPU miner bfg was based on, plus old bfgminer FPGA code with various things broken and a few minor things added

These days it usually only makes sense to use BFGMiner.

I use cgminer on my cairnsmore's and it runs flawlessly week after week after week.  Am I missing something by not running bfgminer then?

Dynamic clocking.

Plus the usual other BFGMiner improvements (bugfixes, asynchronous share submissions, etc)

asynchronous share submissions was in cgminer by ckolivas almost 2 years ago
https://github.com/ckolivas/cgminer/commit/a45c54aaf8a0db0951b8c5f3cfc6cd40f678d5e0 <- 2011-06-26

It looks like it was there before that change, but I didn't bother to check.

So you are saying that you've replaced his code with something else or that you removed it from your clone before and finally after all this time caught up to cgminer on that particular aspect?

Luke-Jr the FUD master and ASIC bricker.

[Doff]

Yes they arrived with Makomk 200 on them.

Would I expect a better result with the dynamic clocking if so where can i find that?

thanks btw, day 2 and the learning continues !

Yes you will get better results with the dynamic clocking bitstream from glasswalker, mine has run for months stable on the glasswalker bitstream at 215-229 m\hash. However there is a problem with Bfgminer where they aggressivly downclock, some sort of wierd bug., if this bug wasent there Id use Bfgminer. I use MPBM Miner instead since thats what Glasswalker built them to run on and it works great other than failover. For whatever reason when MPBM failover accurs a few times the cm1 Downclock and you have to reboot MPBM.

[LazyOtto]

I have a couple of CM1s and also have found that MPBM works better with dynamic clocking control than BFG.

Currently running both the CM1s and a BFL single clocked at 800mh/s using MPBM on a Raspberry Pi.

Once had an uptime of over a month. A week at at time is common place - and that's merely because I've been mucking about in the server room for the last couple months. (New UPS, re-arranging equipment, etc.)

[dodegkr]

I switched back to cgminer as after a night on bfg i did 21% rejected !

[glowkeeper]

I have a couple of CM1s and also have found that MPBM works better with dynamic clocking control than BFG.

Currently running both the CM1s and a BFL single clocked at 800mh/s using MPBM on a Raspberry Pi.

Once had an uptime of over a month. A week at at time is common place - and that's merely because I've been mucking about in the server room for the last couple months. (New UPS, re-arranging equipment, etc.)

Why mpbm over cgminer?

[LazyOtto]

cgminer does not support glasswalker's dynamic clock firmware. AFAIK.

[glowkeeper]

cgminer does not support glasswalker's dynamic clock firmware. AFAIK.

Ah right. Not running that though, since I'm getting a pretty solid 780-790 Mh/s out of the shipped firmware, and I wasn't certain how to flash on a pi....

[LazyOtto]

You might be able to get 5% more out of them using glasswalker's flash.

Might not, also. And you should consider ROI on that for the down time required to perform the flash.

And, one of mine once failed to flash successfully. I had to buy a JTAG cable to resurrect it.

Since that, I've been merrily hashing on them since last September.

As with all things, YMMV.

[gingernuts]

Does anyone know what would cause all my hashers to drift down to 50% throughput in bfgminer and cgminer after about 10mins? I'm not running a dynamic-clock bit stream, but my boards start off at 380ish per side (virtual Icarus) and pretty quickly move to 200 each, with lots of amber LED time showing they're not doing anything...

[SnitraM]

Does anyone know what would cause all my hashers to drift down to 50% throughput in bfgminer and cgminer after about 10mins? I'm not running a dynamic-clock bit stream, but my boards start off at 380ish per side (virtual Icarus) and pretty quickly move to 200 each, with lots of amber LED time showing they're not doing anything...

If you're running the bitstream that Enterpoint put on the unit at delivery, I'd suggest just use cgminer.
That works fine for me. Since 9 months. Right now I'm using 2.11.3.

[kano]

cgminer does not support glasswalker's dynamic clock firmware. AFAIK.

cgminer doesn't support any clock features on Cairnsmore1
We've never had the hardware (and none of the other Icarus I have: an original Icarus, a Black Arrow Lancelot and a Asicminer USB, have miner programmable clocking)
As I've mentioned before and long ago, if someone has one they want to send me, I'll be able to add support for that.

I did write the original --icarus-options code to support other Icarus bitstream devices with varying FPGA configurations (the code that is in cgminer and the clone) and could test that on a normal icarus with the correct settings for a normal Icarus.
But obviously can't write and test the clocking code without one.

At the moment I've been trying to track down someone with one to simply compile and run a binary and get me certain output rather than removing Cairnsmore1 from the next version (i.e. trying to at least have basic Icarus settings support)
I've had a few offers, but since the 1st one couldn't, I'll try the next shortly.

[shep80]

cgminer does not support glasswalker's dynamic clock firmware. AFAIK.

cgminer doesn't support any clock features on Cairnsmore1
We've never had the hardware (and none of the other Icarus I have: an original Icarus, a Black Arrow Lancelot and a Asicminer USB, have miner programmable clocking)
As I've mentioned before and long ago, if someone has one they want to send me, I'll be able to add support for that.

I did write the original --icarus-options code to support other Icarus bitstream devices with varying FPGA configurations (the code that is in cgminer and the clone) and could test that on a normal icarus with the correct settings for a normal Icarus.
But obviously can't write and test the clocking code without one.

At the moment I've been trying to track down someone with one to simply compile and run a binary and get me certain output rather than removing Cairnsmore1 from the next version (i.e. trying to at least have basic Icarus settings support)
I've had a few offers, but since the 1st one couldn't, I'll try the next shortly.

I'm happy to help run test versions. I have 6 CM1s. Drop me a PM if you still need a tester.

[glowkeeper]

You might be able to get 5% more out of them using glasswalker's flash.

Might not, also. And you should consider ROI on that for the down time required to perform the flash.

And, one of mine once failed to flash successfully. I had to buy a JTAG cable to resurrect it.

Since that, I've been merrily hashing on them since last September.

As with all things, YMMV.

Exactly...

[glowkeeper]

cgminer does not support glasswalker's dynamic clock firmware. AFAIK.

cgminer doesn't support any clock features on Cairnsmore1
We've never had the hardware (and none of the other Icarus I have: an original Icarus, a Black Arrow Lancelot and a Asicminer USB, have miner programmable clocking)
As I've mentioned before and long ago, if someone has one they want to send me, I'll be able to add support for that.

I did write the original --icarus-options code to support other Icarus bitstream devices with varying FPGA configurations (the code that is in cgminer and the clone) and could test that on a normal icarus with the correct settings for a normal Icarus.
But obviously can't write and test the clocking code without one.

At the moment I've been trying to track down someone with one to simply compile and run a binary and get me certain output rather than removing Cairnsmore1 from the next version (i.e. trying to at least have basic Icarus settings support)
I've had a few offers, but since the 1st one couldn't, I'll try the next shortly.

I offered! You didn't reply!