Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 588. (Read 5805546 times)

I don't know what to tell you ... it didn't work before, now it works with gpu disabled.  Is there a reason why bfl's are not auto detected like they are in ufasoft's miner?

No, it is not necessary to disable the GPU functionality, but you do need to specify the com ports.

epoch indicated in his post that i needed to disable the gpu functionality then manually select the com port of the bfl ... that worked and i'm now able to run one instance of cgminer for the gpu and a separate instance for the bfl with gpu disabled

Wait where did you hear that? That was never said, and you can run GPUs with BFL. Gigavps runs 14 BFL with 2 GPUs getting 13GH on one machine.

Well as i was on my way to update to 2.3.6, I felt the desire to remove my current running drivers, Because i was getting 60mh/s less with the newer version of cgminer, Knowing that this was Not cgminers fault, And that it was a fault of the whole SDK .bin install compile= performance dealio, I ran into an issue where i can nolonger install ANY display drivers

Please help me! https://bitcointalksearch.org/topic/magically-fixed-inf-file-not-found-after-26-removal-78479

got it ... thank you very much ... didn't realize you had to disable the gpu to get the bfl to work ... guess i'll have to run two instances ...thanks again

If you are in Windows, your basic command line should look something like this:


The '-S COM6' is the relevant part for your Single. It happens to be COM6 for me, but it will likely be something else for you.

You'll need to open up Device Manager, go to the Ports section, and you should see an entry that looks like 'USB Serial Port (COMx)'. Whatever 'COMx' is in your case, that's what you put into cgminer's '-S COMx' setting. Then your Single should be detected.

edit: I should add that if your COM port is greater than 9, you need to use the 'longhand' form for cgminer. So if, for example, your assigned COM port for your Single was COM12, your command line would need to look like this:

The detection code is quite straight forward for each FPGA.

If you wish to force it to be specifically BFL or ICA you can e.g. "-S bitforce:COM6" or "-S icarus:COM6"
ZTX detection is completely different so there is no real overlap (you don't specify the ztex devices, it always directly detects them)

It checks for BFL first:
It sends it a command (ZGX) which the BFL replies and is checked for the string "SHA256" in it - part of the reply is also where the "Model" in the API command 'devdetails' comes from

Next it checks for Icarus:
It simply just sends it some work and waits 0.1s for the answer
(I checked the block chain for a low nonce and found Ozcoin block 171874 nonce = (0xa2870100) = 0x000187a2 takes ~0.53ms on Rev3 Icarus to be the lowest nonce in the thousands I got a script to look at until the script bugged out)
This is mandatory for ICA since there is no identification anywhere other than the USB device identification
(which course could be used by other non Icarus devices since it's not unique)

Thus with that code (above) the ordering naturally should be BFL first and ICA 2nd if you don't specify "-S bitforce:COM6" or "-S icarus:COM6"

ZTX is detect third since that was added 3rd (though I might consider moving it up to first since it's very direct how it works and unlikely to ever affect any other device)
You don't specify -S for ZTX

Edit: for auto detection of course ZTX is always auto
ICA doesn't ever do auto
BFL does auto only in linux and only when you specify -S auto - however it has 2 methods:
 1) where it looks in /dev/serial/by-id (which can sometimes only show 1 BFL on some linux versions if you have more than 1 BFL)
 2) by libudev checking the USB Model when libudev is compiled in

Some senior moment at my side, I guess. This thread became too long but I remember a discussion with xiangfu that due to the way how an Icarus is detected (you have to feed some work and check the resulting share for success) there are corner-cases where it becomes unreliable (like looking for a BFL first can kill its state-machine). That was when the initial Icarus support was planned, and since it works for you it was obviously solved meanwhile.

cgminer does not seem to detect my connected bfl single ... is there a setting that i'm missing?

Yes all binaries have it. Peddle not ye wares here.

Hmm, I would have thought the autodetect routines for FPGAs are fine in cgminer. My command line for 2 Singles looks something like this:


Notice there is nothing in that command line to tell cgminer that I have a Single, an Icarus, or Ztex. But cgminer detects and starts the Singles on COM6 and COM7 fine.

So I'm more or less a noob at all the ins and outs with cards, drivers and SDK's and have tried to follow more or less what is said here and to stick with the basics when setting up and running various miners. I went ahead and updated my drivers today while leaving the SDK at 2.4 and I'm seeing what I think is small decrease in performance. I also updated from 2.3.1 to 2.3.6 and if anything I find it slower but it could be the drivers.

Anyway that's not really my comment or question. I'm more interested in knowing where the I (intensity) setting comes into play. My command line has been all default except for I 9 forever, mainly because somebody else suggested the setting. Since I was playing with things today I thought I would try other intensity levels to see what happens and the difference was HUGE in terms of CPU use. I found that just about any setting 1-10 resulted in the same 50% CPU use I had been seeing and accepting as normal to only 1-5% CPU use by cgminier using I 7. Now what would CPU cycles be higher at 5 or 6 than 7, as well as 8,9,10 I can understand if it's a rising scale? I'm seeing maybe 7Mh/s less with 2.3.6 and Intensity 7 but my CPU is idling while GPU is maybe a touch hotter but overall machine heat is way down due to lower CPU use.

CARD: 5770
GPU/Mem: 975/350
OS: Win7X64
SDK: 2.4
Catalyst: 12.4

You're always friendly and respectful, just my reference on how people should behave on this forum to make a better community.

As for the Singles in your bedroom: water-cooled ones ahead in the pipeline. Time for you to silently raffle away your old loud ones for 150% resale value

Topic: true, there is no hot-plug support for FPGAs implemented. I understood that it's not safe since auto-detecting routines between different board types collide, i.e. if you scan on serial port X for a single and have actually an Icarus attached, you'd hang in a loop (or vice-versa, not sure).

What I noticed as problematic (but this might be a Linux specific thing) is, I added cgminer to the autostart service and it usually worked fine with the GPU setup and assured that system is automatically restarted when a card hangs. With the 5 BFLs attached I see every now and then that only two or three of them are detected immediately after reboot. Re-starting cgminer activates them all again. Kind of bad if you plan to leave your miner unattended for two weeks


Edit: sorry you talked about hot-removal, not hot-plugging. With Linux you do not stop cgminer completely. You just stop the threads dedicated to that BFL. If it was the last/only one, then cgminer stops, but otherwise it just continues with one unit less (though statistics are displayed further, no indication that device is gone). Plugging the unit back will not make it operating again automatically.

Much appreciated, Zefir! Although I'm sure the temporary loss of hashing power was more than compensated for by gaining a better understanding of the Singles' behavior.

Yes, lucky me ... none of my Singles throttle with the stock fans.  I do have some marginal ones now, since I've swapped in slower fans. Apparently, with BFL's EasyMiner software, users will be able to adjust the clocks and that should help the throttling situation. Although that won't help Linux users such as yourself. 

On the topic of cgminer, I've noticed that 'hot removal' is not handled well. If you remove a Single from a hashing cluster, cgminer quits. It doesn't crash or lock up, but it quits. My workaround is calling cgminer in a batch file with a loop. If it quits, the batch file will just call it again. Not a big deal, but it does interrupt mining for half a minute or so while the next instance initializes.

jjdebug: Completely unnecessary, but much appreciated! For better or worse, I've become quite familiar with Single behavior under temperature throttling due to my obsession with finding a 'quiet' solution to the Singles' stock loud fans.  

Thanks Epoch for taking your time!

Yes, I'm running my setup from a Linux machine and did most of the measurements with cgminer-2.3.5. Plus, the same process is driving 3 GPUs worth 1.7GH/s that did not suffer while dealing with the throttling Single. I'm building an OpenWRT router to control the proper working units and leave the throttling one attached to the GPU rig.

Lucky you, you had to force your BFL to throttle

Thanks again. Sent you a coin to at least compensate you for the loss of hashing power during measurement.

Epoch,

Damn cool that you would take the time and effort to test that. I wanted to but didn't have time right now.

Thanks for verifying whether the problem was reproducible.

Tip sent.

Zefir, I cannot reproduce your observations on cgminer 2.3.4, 2.3.5, or 2.3.6 (under Windows 7 64-bit; I realize you are running on Linux so my observations may not be relevant here).

I have created 2 separate clusters of Singles, and have modified 1 unit in each cluster (by swapping in a too-weak fan) such that it throttles after 5-10 minutes of operation. That is, after 5-10 minutes the front LED blinks, the hashrate drops, temperature drops, it recovers, rinse, lather, repeat.

What I have observed after 24 hours of operation is that ALL of the non-throttling Singles in the cluster average 811-813Mhps (the peak sustained rate of each of my Singles as reported by cgminer is 826Mhps). This rate is unaffected by the presence (or absence) of a throttling unit in the same cluster.

My throttling ones average anywhere from 710-760Mhps. The key thing is that whether they throttle or not, it does not affect the hashrates of the others in the same cluster. Again, this has been my experience with cgminer 2.3.4, 2.3.5, and 2.3.6 under Windows 7 64-bit.

Pretty sure it should be in all BitFORCE-capable versions (since like 2.2.0); if not, I know it is for BFGMiner.