Topic: Cairnsmore1 - Quad XC6SLX150 Board - page 6. (Read 286370 times)

I did reply to message 1, message 2 and message 4 of your 4 messages.
Would you like me to post them here? - I don't mind doing that.
I have answered this to you already - your patches are for code that has been removed from cgminer.
(and the ID patch is a bug)

kano, can you please tell us  

I offered you Cairnsmore1 access, I can give you ssh or something to debug - you refuse
I gave you 3 patches:
You said not possible to add them, because they not compatible or something - so why they are working for me with cgminer for months?
And finally you didn't even bother to reply to my last two messages  

If it makes you two feel better, I run both cgminer and bfgminer! Thanks for your work... whoever wrote whichever parts. 

cgminer was ok running a 6800 gpu next to a 7900 series
bfgminer out of the box runs the stock cairnsmore

If I had to vote on forum profile pictures alone, the sword is pretty cool.

You left out the part where you also intimidate and coerce people into paying you BTC in IRC ...
Or that more than half the Icarus code was written by me and you copied it and claimed it was yours.

Edit: though I should also point out the TYPICAL Luke-Jr lie there.
I wrote the code for the first support for Cairnsmore1 ... yet I still don't have one.
(Yohan had a version of cgminer before me where they only changed the baud but nothing else)

So to summarize things a bit ... if anyone were to donate a device, there's two people interested:

• a guy who refuses to do anything for the device until it's been given to him, and threatens to remove support at all unless people help him because he's rewriting the code using an inferior interface for no reason (Kano)
• a guy who's actually put effort and hours of time into providing full support for a device he doesn't have, and uses standard interfaces to ensure maximum compatibility (myself)

A few people offered (though I don't remember yours) and I'm pretty sure I replied to each about waiting for the 1st person to get me info.
It has to be Linux.
gingernuts has now supplied the missing info he thought he couldn't so that answers one question clearly.
Getting there ...

However, if your CMR is FT232H product=0x6014 (gingernuts is product=0x8350) it would be good to provide 2 things:
usbmon (or direct access to it via /sys or /proc or /dev or wherever your Linux OS puts it - yes it must be Linux)
output of plugging it in and also running the usbtest.py that comes with cgminer current git like:
./usbtest.py /dev/ttyUSB? icarus (whatever the USB? is)
and make sure it gave the right answers (or rerun it)
and lsusb -v of the device
If it actually creates multiple /dev/ttyUSB? you'll need to run that whole process on each of them (from plug in to usbtest.py)

Put that somewhere I can download it (PM or posting is too big)

... and I guess this sort of thing points out why I need the hardware ... coz if it doesn't work once I update it to matching the settings people give me, I'll give up
A big part of the motivation for me to get cgminer to work is having the hardware and then of course anyone else can use it too.
I currently have one of each of: Icarus, BFL FPGA Single, ModMinerQuad, Jalapeno, (Black Arrow) Lancelot, Block Erupter USB ... and a 6950 GPU I bought back when I started in bitcoin - I bought 2x6950, the other is on my kids computer playing minecraft
(I also bought a second Icarus that I sold recently)
Looks cool them all running on 1 cgminer

If you're connected via getwork and not stratum with a high enough difficulty you're gonna get amber lights and idle fpgas. I use MPBM and set the getwork connections to 10 or more to keep my miners busy although I have 24 boards running.

I have been running for months too, abd before I added my new boards, it was running flat out - now its as though the pool or the s/w just doesn't know how fast the array is. Is there a parameter I need to tweak somewhere?

I offered! You didn't reply!

Exactly...

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

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.

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.

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

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.

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

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

Why mpbm over cgminer?

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

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