Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 29. (Read 1193208 times)

How to use bfgmier for asicminer blade , cube ?
I have hard time to run it from my pc. ( solo mine )


It not running.
My bat file.
bfgminer --http-port 3338 -o http://127.0.0.1:8336 -u u -p p

Hmmm, tried this, and getting:

 [2014-02-23 22:09:47] OCL 0: set_device is not implemented (trying to apply rule: OCL:gpu-fan=100)
 [2014-02-23 22:09:47] OCL 0: set_device is not implemented (trying to apply rule: OCL:temp-overheat=90)
 [2014-02-23 22:09:47] OCL 0: set_device is not implemented (trying to apply rule: OCL:temp-cutoff=100)
 [2014-02-23 22:09:47] OCL 0: set_device is not implemented (trying to apply rule: OCL:temp-target=80)

./bfgminer -S opencl:auto --scrypt

That is the key string.  Just make sure your executing against the one you just compiles, not the system one.  A ./bfgminer --help will make that obvious.  If you don't see the CPU and --scrypt options in the help, you running the wrong version.

Just did a "make" for bfgminer 3.10 to include cpu and gpu mining with scrypt, however, my 5450 card is not being used.  I'm not sure what else I needed to include in the configure portion, or if there's some dependency I'm missing to allow for GPU / OpenCL mining...any hints on this one?  Using Wheezy on an old Sony Vaio from the early 2000's

Thanks Luke!

Will modify when I get home tonight.

./bfgminer -S opencl:auto --set OCL:fan=100 --set OCL:clock= --set OCL:intensity=17 --set all:temp_overheat=90 --set all:temp_cutoff=100 --set temp_target=80 --scrypt

Also, please be advised that this code is all new, and overclocking is not something I test.
Unless someone steps up to test overclocking (probably best to remain very conservative initially), there is a possibility it could fry your video card quite easily.
(Alternatively, if someone wants to take on the risk, but perhaps doesn't trust themselves to be careful, I could SSH in and test as carefully as possible - but I cannot guarantee anything)

Looking to bring my configs up to current standards and seeing this message at startup:

[2014-02-23 11:44:19] temp-target is deprecated! Use --set-device for better control

What are the modern --set-device parameters I should be using?

Example command currently being issued:  

./bfgminer -S opencl:auto --gpu-fan 100 --auto-gpu --intensity 17,17 --temp-overheat 90 --temp-cutoff 100 --temp-target 80 --scrypt

OK... here is the secret that took me literally weeks to discover:  Use the [H]elp key   That does a pretty good job explaining the fields.  Essentially that are short term performance, longer term performance, effective performance after rejects, hardware errors, etc.

Here is the full command line I use, complete with a bunch of pools just to show how you can string them together.  I use "--balance" because I host a coin and need to send cycles to both my profit making pool and my coin pools (to show support).  [Pools names modified so that this doesn't come across as an advertisement.]  In a similar vein to my first comment, I've spent more than a few minutes reading the output of "./bfgminer --help".

./bfgminer -S opencl:auto --gpu-fan 100 --auto-gpu --intensity 17,17 --temp-overheat 90 --temp-cutoff 100 --temp-target 80 --scrypt --balance -S cpu:auto -o stratum+tcp://multicoin.poolmod.org:3310 -O Cassey.miner2:pass -o stratum+tcp://yacc.poolmod2.com:3777 -O Cassey.miner2:pass -o stratum+tcp://yacc.poolmod3.net:3337 -O Cassey.miner2:pass

I'm toying with this for long term usage:

./bfgminer -S opencl:auto --gpu-fan 100 --auto-gpu --intensity 17,17 --temp-overheat 90 --temp-cutoff 100 --temp-target 80 --scrypt --balance --text-only --quiet --syslog --cmd-sick /sbin/reboot --cmd-dead /sbin/reboot -S cpu:auto -o stratum+tcp://multicoin.poolmod.org:3310 -O Cassey.miner2:pass -o stratum+tcp://yacc.poolmod2.com:3777 -O Cassey.miner2:pass -o stratum+tcp://yacc.poolmod3.net:3337 -O Cassey.miner2:pass

I'd be using it but the syslog option is generating some stratum+tcp libcurl message I don't see anywhere else, and does so several times a second, generating a lot more syslog traffic than I like.

Since I run a number of different cards in each of my miners (typically 2 or 3), I just stick with the Intensity (-I) parameter to control their heat.  I too target a 80C temp.  Cooling can be a bitch btw, all but one of my miners is open-rack, and the only cased one has a single GPU.

Thanks Cassey.

I have my monitor plugged into the on-board (motherboard) VGA port. I am anticipating that any Word, Excel, Web browsing I do uses the on-baord (Intel) graphics chip and not the Radeon GPU.

I don't play games. This isn't a gaming machine. It will be used for my work (a lot of web & SQL coding - mainly in multiple virtual machines).

I am using the Radeon 6970 purely for GPU mining. It'll run 24x7 so I don't want to run the GPU too hot (I'm aiming to keep it below 80C but at the moment I'm only getting 220 Kh/s when below 80C).

I am still playing around with various combinations of intensity, threads, shaders etc. I wish there was just 1 doc that explained all the params in a simple language. For example, starting with a very simply command line (no params - but what are the defaults used??). Then slowly building the command line to improve performance (ie. what is the most important singula param to tweak first? intensity? Then 2nd param? Thread count? I don't know). At the moment I see too many params and I'm just confused as to which ones I need to tweak first. Yes, I could spend a whole day tweaking and recording params and the effect after 15 mins, but geeze, there's gotta be a better way!

What are the 3 sets of numbers in bfgminer? I've never been able to work this out and can't seem to find any screen shots etc in any of Luke's docs.

Ignore that third number until things stabilize a bit (like its run for at least 10-20 minutes).  What I was more focused on is the 0.04 MHash (40 KHash) shorter term numbers that are displayed.  That is a bit low, but possible with an "-I 9" setting.  Try it about "-I 15" and see how it does.  Inch it up one-by-one until you either see a hardware error (very bad) or performance becomes unacceptable. 

On the side:  Please don't be thinking about playing graphics games while mining - the two are NOT compatible.  Shut down mining when you are going to do so.  However you should be able to find a setting where basic web browsing, excel, powerpoint, etc. will work fine.

Cassey

BUMP.

Hi all. Seeking guidance from the group once again.

Environ: Windows 7 x64

Am running bfgminer via this bat file:

c:
cd C:\Users\Mark\Desktop\bfgminer-3.10.0-win64

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

bfgminer --scrypt -S opencl:auto -o stratum+tcp://doge.pool.mn:3333 -u mfread.storm1 -p 123456 -I 9 --auto-fan --auto-gpu --thread-concurrency 8192

pause

http://i62.tinypic.com/24156x4.png

http://i61.tinypic.com/4sjs3q.png

(1) Why am I getting 73 Mh/s?? No HW errors. Shouldn't I be in the 415 Kh/s range for a single GPU card mining? I see acceptances too. So it looks like it's behaving. After 44 mins it is reporting 144 Mh/s and no HW errors. The mining pool says this worker is doing 48 Kh/s.

(2) I notice that bfgminer doesn't show me the temp of the GPU (but in the bfgminer notes it says that Radeon 69xx is supported). Is there another driver (like the AMD SDK stuff) I should be installing?

Hoping some of you more experienced guys and gals can point me in the right direction.

Cheers for now.

Mark

To be more clear, I do not intend to remove dynamic intensity at all.
Only the --gpu-dyninterval option, which affects its logic.
Does anyone use that option specifically?

I use dynamic setting for GPU because if I don't my CPU shows 98 percent frequency and 94 percent in use. This is with Gigabyte GeForce GT630N but I found my other computer with a XFX Radeon HD 5450 works best with dynamic intensity as well.

Very cool.  Thanks.

-S opencl:auto -S cpu:auto

Ah, ok, well, at least there is one!

I tried doing both GPU and CPU Scrypt mining at the same time, it was looking encouraging, but I didn't see bfgminer eating any cycles.  Do I need something like "-S opencl:auto cpu:auto" to do both at once?

Yes, the algo setting is not valid in scrypt mode (there is only one not-really-optimise algo).

Played around a bit today and ONLY see these message if I do the --syslog option, and then only in the log file (ok, guess that is no big surprise!).

Is CPU mining with bfgminer possible for scrypt?  I see the algo setting for SSH256 cpu mining, but only do ASICs for that now.  Would like to have bfgminer do both GPU and CPU scrypt mining in one instance if possible.