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

Run it with -S gridseed:all and specify frequency with --set-device gridseed:clock=freq, e.g. 850 (default is 600).

Any way to set clock speed of the 5chip gridseed miners?

the windows binary looks fine ... except of the clocking ...

Awesome, works like a charm!

Awesome - that's great news! Haven't had a chance to play on Windows just yet.

To ignore GPUs, pass in:


That will prevent any auto-detection. To specify the devices, instead of:


use:


where the bit after the colon is the COM port or path to the device.

Works for me, any way I can specify COM ports to be used and others to be ignored?  Also how to ignore my GPU's?  OCL0, OCL1, OCL2

https://www.dropbox.com/s/ho5lf1vqj57f5a2/bfgminer_gridseed_pr1.7z

I give this my I Haven't Tried It And It May Take A Custom INF stamp.

Need sleep but I'll poke that on Windows tomorrow and see how it shakes out.

^^ Need a windows compiled version, but I could give it a shot with 5 x 5 chip units.   

The previous driver I linked is for the GridSeed 1-chip device, so far resold by DualMiner.

For support for the GridSeed 5-chip devices, if you are feeling crazy you can try this out (Scrypt-only currently):

https://github.com/nwoolls/bfgminer/commits/feature/gridseed-support

I give it the It Works For Me(tm) stamp of approval. Run it with -S gridseed:all and specify frequency with --set-device gridseed:clock=freq, e.g. 850 (default is 600).



For OS X users, these should be loaded automatically but in case they aren't:


SHA2 support will be next followed by dual-algorithm support. If you have some of these and are feeling froggy, feedback is welcome.

Thanks very much nwools, that's great news, I really appreciate all your help! 

I've gotten my hands on some AntMiner U2s but bfgminer is not seeing them.

This is on a Raspi.

Check out this post here:

https://bitcointalksearch.org/topic/m.5572568

That is the DualMiner branch for BFGMiner and is just waiting on another code review before being merged. Should be both feature-complete and stable.


The current version of MultiMiner has DualMiner support. You just need a version of BFGMiner with DualMiner support installed.

I'm not sure what the timeline looks like for 4.0. Fairly certain it should be soon. It just got delayed by Luke speaking at a Bitcoin conference and me having some hardware issues at the same time.

Hats off to all you guys who keep BFG at the forefront of development with all the new mining hardware that keeps being introduced  

I remember receiving some Blue Furies a few months back and thinking, "The BFG guys will have something worked out soon," and sure enough within a few days native support in BFG was available - what old schoolers know as 'just in time'.

I know you're busy working on a number of projects, one of which is the DualMiner compatibility project, so just wanted to share my appreciation for all your hard work and hoping that I haven't missed anything in the thread as I've a number of DualMiner units sitting on the desk here awaiting BFG compatibility. I hear there's some sort of CGMiner workable solution to get them mining but to be honest I'm not really interested in CGMiner, I run all my miners using BFG and would rather wait a few weeks and have another instance or two of BFG working alongside the BFG instances I have open for my various usb miners already than deal with other mining programs, which in my experience, have been less than suitable for my needs and tended to be far more trouble than they are worth.

I've heard some rumour that there's a Multiminer workaround for DualMiner but I'm kinda over the tweak, re-tweak, tweak-ad-nausuem, so I'd prefer to wait until there was more formalised BFG support as it's just not worth the aggravation to me to have any different miners or untested workarounds play havoc with my rig. If I see the lights flashing on my rig and check the hash speed at the pool and all is well, then that's confirmation why I use BFG in the first place.

So please let me know if I've missed anything.

Thanks folks.

Ya that's what I assumed - I think having a constant key in there for current hashrate would be a good idea for forward compatibility with this left in there for backwards compatibility.

It's one of those things kept for cgminer compatibility (yes, it changes with --log there, too).
Perhaps we should mirror it to another constant-named key?

That change caught me by surprise too. The good news is you can pass in --log XY and then you can always count on the key for current hashrate being constant. While I understand why --log changes the way current hashrate is measured, I'm not sure why that should change its key an an API.

Hi All and Luke,

I am having an issue with the API, in particular I am having problems with switchpool (though changing MHS5s to MHS20s in the device output caught me a bit unaware).

When you use switchpool the first time it works fine, the second time you use it though it does nothing, unfortunately it does not return anything either to (via the api or miner screen).  It seems to just silently fail.

To make it worse I just introduced pool switching to the MinePeon status screen.

Is anyone else seeing the same?

Neil

EDIT: Hold off, I think another person might have spotted the problem with switchpool, I will be back .

nvidia win7
 
n how if usin linux ?

I think one of the bigger problems with scrypt mining in general is the fragmentation of drivers vs current software.  Many people with large rigs (or even smaller ones) found older driver configurations that work great, but when combined with newer drivers those configurations do not function as well.  Add in the changes to AMD's SDK and compiling, and we are not seeing scrypt CL advance and keeping pace with new drivers in both stability and performance. 

Without a willingness to optimize for the newest SDK's (because of reduced performance or reprieved reduced performance/stability) and try to increase performance using future centric thought (modern SDKs and modern driver support), scrypt is stuck in a rut as far as gpu performance.  If anything, scrypt asics will become desirable simply for "plug and play" that should do away with these complicated factors.

If I could get my old 5770 to mine without rolling all the way back to 2012 Catylist drivers, I'd be mining scrypt with it right now.  However, seeing as it is my only desktop graphics cards, I want my gaming and scrypt too, and I can't have both (SGMiner, or BFGMiner be damned, neither work correctly for me).

what Operating System are you using?

teach me please , how do you using the software, n how i can get ?