Pages:
Author

Topic: OLD: BFGMiner 4.10.0: GBT+Stratum, RPC, Mac/Linux/Win64, Spondoolies SP30 - page 22. (Read 308659 times)

sr. member
Activity: 467
Merit: 250

Any chance of Bitmain S1/S2/S3 support?

newbie
Activity: 2
Merit: 0
Hey everyone,

I don't mean to intrude with a noob "how do I use this" question, but that is where this has left me.

I've been able to run bfg miner 3.10 on my PC, connectuong to my gridseeds and running them. My issue lies in getting bfg 4.4.0 (and now also 4.5.0) to recognize not only my gridseeds but also my Zeus Thunder X3. And as a note, I have admin rights, and have tried running it from the root of my C: drive as well. I have noticed (in 3.4.0 and 3.5.0) an error regarding a registry value not being read?

In any canse, I have used the correct drivers for the gridseed blades (stm electronics) and they still work fine with CPUminer (the sandor111 fork) but bfg 4.5.0/4.4.0 just won't recognize them.

As for the Zeus, I have a friend running it for me right now, but when I tried it on 4.4.0 (using the correct commands I believe) bfg refused to recognize it. Sad

If anyone can share with me the complete setup procedure (including drivers and commands on windows) for Zeus and gridseed blades (preferably in the same instance) I would be greatly appreciative. Smiley

Sorry again for the "How to" noobish post - I do some android development and understand how annoying it may be Sad

Thanks guys,
 - NellyWhads
hero member
Activity: 770
Merit: 500
Antminer U1 Trouble....

For some reason bfgminer wont detect my U1 anymore.  The green lights are on, so there is power.  Once I do m, +, all it will blink some but then say no devices found.  I've also tried ./bfgminer -S amu:all and -S antminer:all to no avail.  Any ideas? The jalapeno is running fine though.  This just stopped working one day and now it can't seem to pick it up. 

Thanks,

 Fuglie

P.S. - It might be the u1 itself....cgminer cant find the dang thing either.  But I like bfgminer more so if y'all can help that would be awesome.
I have a U1 that acts the same way. It just dies and I need to reseat it in the USB port several times sometimes before it starts working again.. It also won't overclock very high so I just write it off as a flaky stick.
full member
Activity: 161
Merit: 100
Hi all.  

I'm still at it with the random no-hashing issue I keep having everyday with my Raspberry Pi & now 8 Gridseed G-blades, up from 6 G-blades, new 6FT USB Cables (down from 10 & 15 footers).  And again, I even replaced the hub with a new Turcom 24 Port USB 2.0 Monster USB HUB W/ac Adapter Power Station.

I'm still not sure if this is a BFGminer issue with too many G-blades or not.  
However, it works fine with up to 5 G-blades.

I updated BFGminer to the latest version, as of this writing, to v4.5.0.

Here are my results.




No Over-clocking used. They are setup at their "Sweet Spot" as recommended by most.  See below:



Same thing but from the Minepeon WEBUI below:





See my previous post here, with the same results.


I don't know what else to do.

I get the same thing using Multiminer with bfgminer.  It's always a different G-blade that stays stuck on zero, always & only using BFGminer since all I do is LTC mine with these.



Any suggestions?
newbie
Activity: 4
Merit: 0
Hello,

Trying to help a friend set up his blade in bfgminer got it running and everything.  But ocl keeps showing up as a device.  How do you disable the GPU?  He can go into settings and shut if  off there.



I use this in .bat : -S noauto -S gridseed:all --set-device gridseed:clock=800,usefifo=0,btc=0 --scrypt


Alberto

Thanks Alberto for the info on the startup bat.  Does the -S noauto stop the gpu from mining?

Yes

newbie
Activity: 3
Merit: 0
how do you get BFGMiner to see the NANOFury devices, as they are recognized by windows as a HID-compliant device. i am trying to get a miner to recognize the nanofury so it can mine with it, but i cant seem to get the program to see the HID-compliant device. please help me. i need to figure out what in the source code allows the recognition of the devices.
newbie
Activity: 18
Merit: 0
Antminer U1 Trouble....

For some reason bfgminer wont detect my U1 anymore.  The green lights are on, so there is power.  Once I do m, +, all it will blink some but then say no devices found.  I've also tried ./bfgminer -S amu:all and -S antminer:all to no avail.  Any ideas? The jalapeno is running fine though.  This just stopped working one day and now it can't seem to pick it up. 

Thanks,

 Fuglie

P.S. - It might be the u1 itself....cgminer cant find the dang thing either.  But I like bfgminer more so if y'all can help that would be awesome.
hero member
Activity: 840
Merit: 1002
NEW VERSION 4.5.0, JULY 26 2014

Human readable changelog:
  • bitforce: A new setup-vfio shell script is included to simplify configuring VFIO for Monarchs on PCIe.
  • bitforce: Support for PCIe on Windows.
  • cairnsmore, icarus, zeusminer: Per-core mining statistics support.
  • gridseed: Ability to set clock speed via Manage TUI.
  • hashfast: Include chip/core address in RPC procdetails.
  • hashfast: Implement ability to change clock setting at runtime.
  • rockminer: Allow setting clock 300-2560 as long as prefixed by "unsafe:".
  • zeusminer: Support for the GAW War Machine.
  • zeusminer: Ability to set clock speed via Manage TUI.

Some Scrypt-specific notes on 4.5 (beyond what is called out above):

  • Per-core mining statistics for GridSeed devices
  • Ability to set ZeusMiner clock speed via RPC API
  • Increased compatibility (for now) with broken Scrypt pools

Happy mining!

Edit 1: Updated firmware for 703n is available here.
Edit 2: Here is a detailed post on changes for Scrypt miners.
legendary
Activity: 2576
Merit: 1186
NEW VERSION 4.5.0, JULY 26 2014

Human readable changelog:
  • bitforce: A new setup-vfio shell script is included to simplify configuring VFIO for Monarchs on PCIe.
  • bitforce: Support for PCIe on Windows.
  • cairnsmore, icarus, zeusminer: Per-core mining statistics support.
  • gridseed: Ability to set clock speed via Manage TUI.
  • hashfast: Include chip/core address in RPC procdetails.
  • hashfast: Implement ability to change clock setting at runtime.
  • rockminer: Allow setting clock 300-2560 as long as prefixed by "unsafe:".
  • zeusminer: Support for the GAW War Machine.
  • zeusminer: Ability to set clock speed via Manage TUI.

Full changelog:
  • Bugfix: zeusminer: Fix crash in TUI with newly introduced feature
  • Bugfix: gridseed: Fix crash in TUI with newly introduced feature
  • gridseed: Add the ability to set clock speed via the TUI
  • bitforce: Support for Monarch devices on Windows using new "mswin" lowlevel interface to scan for KMDF driver
  • Bugfix: gridseed: Implement a proper scanhash routine for GridSeeds
  • zeusminer: Add the ability to set clock speed via the TUI
  • Bugfix: gridseed: Only set PLL frequency once (not once per processor)
  • Bugfix: zeusminer: Retry detection on failure - ZM fails detection 1 / ~30 times
  • Bugfix: zeusminer: Enabling the ZeusMiner driver should flag needing lowl-vcom
  • aan: Silence false warnings
  • Include broad udev rules when configured with --enable-broad-udevrules option
  • Bugfix: util: Lower the threshold for considering pool Scrypt diff broken
  • Bugfix: gc3355: Do not send work_id (or anything) in the last 4 bytes of work
  • gridseed: Refactor code to clean up and organize
  • gridseed: Document GridSeed specifics with comments and URLs
  • Copyright cleanups and updates
  • Bugfix: zeusminer: using icarus timing can lead to false positive Idle detection
  • zeusminer: Return the Chip # via the RPC API call procdetails
  • zeusminer: Display the Chip # in the UI when viewing per-proc details
  • Bugfix: miner: Check work->blk.nonce to see if work should be abandoned
  • rockminer: Allow setting clock 300-2560 as long as prefixed by "unsafe:"
  • util: Work around broken Scrypt pools automatically using realistic pdiff assumptions
  • scanhash: Document scanhash related methods with comments
  • Bugfix: gridseed: Report communication errors using dev_error()
  • gc3355: Return bytes read to distinguish 0 bytes from error
  • Bugfix: gridseed: Add delay between Scrypt reset and sending work
  • gridseed: Bugfix: fix the constant used for estimated hash rates
  • klondike: zero_stats support
  • bitforce: zero_stats support (Temperature, Voltage, and Avg Wait)
  • avalon: zero_stats support (temp_max, no_matching_work, match_work_count%d)
  • Add driver interface for zero_stats function
  • Bugfix: bitforce: Short-circuit bitforce_read(0) to avoid lowlif issues
  • Bugfix: bitforce: Ensure data for the current command is always read (and only once), with lowl-pci
  • Bugfix: setup-vfio: Add device ids to vfio-pci even if they didn't have a driver previously
  • Bugfix: lowl-pci: Use volatile qualifier for PCI mmaps
  • Bugfix: bitforce: Use lowlevel interface device was probed with, for actual mining
  • setup-vfio: New shell script to automatically configure VFIO
  • README.ASIC: Monarch: Need to do new_id for every affected device, and only after unbinding them
  • README.ASIC: Monarch: Use shell variables for commands
  • gridseed: Bugfix: Revert earlier changes to scanhash based on feedback
  • hashfast: Support for changing clock at runtime
  • hashfast: Store a copy of what we believe to be the chip configuration data
  • hashfast: Store firmware revision
  • util: pk_uNle macro for changing a number inside a packed structure
  • README.ASIC: KnCMiner: Talk about additional i2c-tools dependency
  • README.ASIC: KnCMiner: Remove mention of now-obsolete Bertmod
  • README.ASIC: KnCMiner: Grammatical corrections
  • Bugfix: RPC: Avoid processor-specific details in devdetails
  • gridseed: Bugfix: log invalid detect responses as debug info, not an error
  • zeusminer: Support setting clock via RPC API procset call
  • README: Add Controla and Minera controller software links & info
  • gridseed: Bugfix: Fix hash-rate calculation when no nonces are being found
  • dualminer: Bugfix: assign the proper value for work_division
  • gridseed: Refactor to clarify GridSeed terminology
  • gridseed: Add support for displaying per-chip statistics
  • gridseed: Convert to use newer set_device_funcs interface
  • Bugfix: gridseed: Don't leak cgpu_info when devices are already claimed
  • icarus: Processor detail support
  • DevAPI: Allow using device_proc_by_id with const struct cgpu_info
  • icarus: Ensure fpga_count is finalised before add_cgpu is called
  • icarus: Move work_division autodetection code into new icarus_probe_work_division function
  • icarus: Remove ability to change fpga_count at runtime
  • Bugfix: gen-version.sh: Replace bashism ("here string")
  • gridseed: Support devices with more than 255 physical processors
  • Use `git describe` to generate version.h to avoid user confusion over builds from git
  • zeusminer: Support devices with more than 255 physical processors
  • hashfast: Include chip/core address in RPC procdetails
  • gridseed: Reduce traffic sending work to GridSeed devices
  • gridseed: Bugfix: previous refactor (unpublished) changed logic
  • gc3355: Refactor to remove SHA2 code specific to the 5-Chip GridSeed Orb
  • lowl-vcom: Bugfix: do not attempt to open the USB devices when enumerating
member
Activity: 94
Merit: 10
Is he a time traveler?

Hello Taugeran were you responding to my post or loszhor's?
member
Activity: 94
Merit: 10
Hello,

Trying to help a friend set up his blade in bfgminer got it running and everything.  But ocl keeps showing up as a device.  How do you disable the GPU?  He can go into settings and shut if  off there.



I use this in .bat : -S noauto -S gridseed:all --set-device gridseed:clock=800,usefifo=0,btc=0 --scrypt


Alberto

Thanks Alberto for the info on the startup bat.  Does the -S noauto stop the gpu from mining?
newbie
Activity: 4
Merit: 0
Hello,

Trying to help a friend set up his blade in bfgminer got it running and everything.  But ocl keeps showing up as a device.  How do you disable the GPU?  He can go into settings and shut if  off there.



I use this in .bat : -S noauto -S gridseed:all --set-device gridseed:clock=800,usefifo=0,btc=0 --scrypt


Alberto
sr. member
Activity: 737
Merit: 262
Me, Myself & I
Good day, is there a native way to automatically schedule BFGMiner to restart without the need of an outside API application? It would cut out a middle man and save resources if it is possible and if not is there a modification available for such a command?

Thank you.

Code:
bfgminer 4.4.0

Usage: bfgminer
Options for both config file and command line:

--sched-start             Set a time of day in HH:MM to start mining (a
                               once off without a stop time)
--sched-stop              Set a time of day in HH:MM to stop mining (will
                               quit without a start time)

As far as I understand help description, stop and start of mining is possible. For restarting the miner better option is "middle man" in a form of CGWatcher. It's free.
hero member
Activity: 658
Merit: 500
CCNA: There i fixed the internet.
member
Activity: 94
Merit: 10
Hello,

Trying to help a friend set up his blade in bfgminer got it running and everything.  But ocl keeps showing up as a device.  How do you disable the GPU?  He can go into settings and shut if  off there.
sr. member
Activity: 369
Merit: 250
Good day, is there a native way to automatically schedule BFGMiner to restart without the need of an outside API application? It would cut out a middle man and save resources if it is possible and if not is there a modification available for such a command?

Thank you.
legendary
Activity: 1237
Merit: 1010
So for Zeus it would then be zus@//./COM1:342?

Make sure your slashes are facing the right way:  \ instead of /  But yeah, that should do it.

--set-device zus@\\.\COM1:Clock=342

It's actually working better with forward slashes. Otherwise you need to escape them but even then it might not work.
Forward slashes shouldn't work at all. The code looks for backslashes explicitly:
https://github.com/luke-jr/bfgminer/blob/65a7398457a858a9a22d5bb3b309d1e7bf21a2d4/miner.c#L537

Would this work in a config file?

"set-device" : [
     "zus@\\.\COM1:clock=342",
     "zus@....",
     ...
]
sr. member
Activity: 361
Merit: 267
I'm able to run all of them at either 0781 or 0881 without any issues; I've been running at 0881 (1.8gh/s) for the last 8 hours without hardware errors.  But I have the Rockminers coming this week and I want to have everything tuned correctly.
newbie
Activity: 42
Merit: 0
Can I use BFGMiner with 2 different types of ASIC devices at the same time?  Currently I’m running 10 AntMiner U2’s, I just ordered a few Rockminer R-BOX units.  I’d like to run all from 1 instance of BFG.

Yep, Currently have 3 NanoFurys (F1/F2), 23 Antminer U1/U2 and 6 r-boxes all running.

I could use some help writing a config file, mine seems to only save pools.


Do you specify different speeds for the U1 and U2?  I have both and I have everything running at the same speed because I couldn't figure out how to run some at 0981 and others at 0781.


Code:
bfgminer.exe -o stratum+tcp://stratum.bitcoin.cz:3333 -u worker -p xxx -S antminer:all --set-device antminer:clock=x0781

I'm in the same boat really. I tried using the command for U2 but that just drove U1s and U2 crazy with tons of hardware errors
sr. member
Activity: 361
Merit: 267
Can I use BFGMiner with 2 different types of ASIC devices at the same time?  Currently I’m running 10 AntMiner U2’s, I just ordered a few Rockminer R-BOX units.  I’d like to run all from 1 instance of BFG.

Yep, Currently have 3 NanoFurys (F1/F2), 23 Antminer U1/U2 and 6 r-boxes all running.

I could use some help writing a config file, mine seems to only save pools.


Do you specify different speeds for the U1 and U2?  I have both and I have everything running at the same speed because I couldn't figure out how to run some at 0981 and others at 0781.


Code:
bfgminer.exe -o stratum+tcp://stratum.bitcoin.cz:3333 -u worker -p xxx -S antminer:all --set-device antminer:clock=x0781

To set individual frequencies on those beasts, you need to use:

-S antminer:all --set-device antminer@\\.\com#:clock=x####  so you'll need to know the COM#

I went through my control panel and made sure I had the correct COM ports then I tries both of these without any success:
Code:
bfgminer.exe -o stratum+tcp://stratum.bitcoin.cz:333 -u worker1 -p x -S antminer:all --set-device antminer@\\.\COM4:clock=x0881 --set-device antminer@\\.\COM5:clock=x0881 --set-device antminer@\\.\COM6:clock=x0881 --set-device antminer@\\.\COM7:clock=x0981 --set-device antminer@\\.\COM8:clock=x0881 --set-device antminer@\\.\COM9:clock=x0881 --set-device antminer@\\.\COM10:clock=x0881 --set-device antminer@\\.\COM11:clock=x0981 --set-device antminer@\\.\COM12:clock=x0981

Code:
bfgminer.exe -o stratum+tcp://stratum.bitcoin.cz:333 -u worker1 -p x -S antminer:all -d antminer@\\.\COM4 --set-device antminer@\\.\COM4:clock=x0881 -d antminer@\\.\COM5 --set-device antminer@\\.\COM5:clock=x0881 -d antminer@\\.\COM6 --set-device antminer@\\.\COM6:clock=x0881 -d antminer@\\.\COM7 --set-device antminer@\\.\COM7:clock=x0981 -d antminer@\\.\COM8 --set-device antminer@\\.\COM8:clock=x0881 -d antminer@\\.\COM9 --set-device antminer@\\.\COM9:clock=x0881 -d antminer@\\.\COM10 --set-device antminer@\\.\COM10:clock=x0881 -d antminer@\\.\COM11 --set-device antminer@\\.\COM11:clock=x0981 -d antminer@\\.\COM12 --set-device antminer@\\.\COM12:clock=x0981
Pages:
Jump to: