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

You can set clock speeds for each individual device. Use the following command to list the devices including their paths:


Then you can use the following to set the clock speed per-device



Yes it does.

But it looks like (based on searches of this thread and the site at large) that bfgminer does not support setting individual frequencies on a per Gridseed device basis. Is that the case?

Also, does bfgminer disable the BTC cores in the Gridseed units when mining scrypt?

I have been using CGMiner 3.7.2 modified because it supports overclocking gridseeds with the following frequency selections built in: 250, 400, 450, 500, 550, 600, 650, 700, 706, 713, 719, 725, 731, 738, 744, 750, 756, 763, 769, 775, 781, 788, 794, 800, 813, 825, 838, 850, 863, 875, 888, 900, 913, 925, 938, 950, 963, 975, 988, 1000, 1013, 1025, 1038, 1050, 1063, 1075, 1088, 1100, 1113, 1125, 1138, 1150, 1163, 1175, 1188, 1200, 1213, 1225, 1238, 1250, 1263, 1275, 1288, 1300, 1313, 1325, 1338, 1350, 1363, 1375, 1388, 1400.

My question is, can I do this with the BFGminer? I have been running CGMiner with gridseeds for a couple weeks, and haven't had any issues running at 1200Mhz on all the gridseeds, I'm just curious whats different about BFGminer than CGMiner for overclocking gridseeds? Trying to establish the best fit.

http://cryptomining-blog.com/1828-updated-cgminer-3-7-2-and-cpuminer-for-overclocking-gridseed-5-chip-gc3355-asics/

 

I'm running this for a while now with good results:


This is on p2pool so rejects are a bit high. Only wish for now is individual freq settings.
Right now it's running gridseed-support-clean branche. With the default branche the hashrates looked higher (but maybe it is more accurate now?).

Yeah this describes my issues well. Sucks cause i got excited when i saw 15mh from 39 units but the effective hashrate is only 11.45mh

Hi,,
I have a problem with API command.

With this code:

I have this error

I don't understand because in the README.RPC, command "summary" exist.

Anyone can help me ?

It pops up a message dialog if the main window is hidden.
In theory, it should be difficult for the malware to hide it also.
But it seems it'll be a problem for GUIs

I did but I was not sure how the msg would combat Malware.  Would it be to let us know it was ok or clear?

Read the link?

What kind of information is it that you want to display?

Frontend/GUI authors: Do you hide the BFGMiner window? Will an informational notice annoy you or your users?

Frontend/GUI authors: Do you hide the BFGMiner window? Will an informational notice annoy you or your users?

I would expect something like /dev/cuaU0 on BSD.

I don't know why, but configure does not search uthash headers in the /usr/local/include.

I modified configure.ac, and wrote direct path to include files (added part is bold):
#include </usr/local/include/utlist.h>
#include </usr/local/include/uthash.h>

Thereafter, configure runs OK.

Sorry, but something wrong. see terminal output:

# lsusb
Bus /dev/usb Device /dev/ugen2.2: ID 0403:6014 Future Technology Devices International, Ltd
Bus /dev/usb Device /dev/ugen2.1: ID 0000:0000
Bus /dev/usb Device /dev/ugen1.1: ID 0000:0000
Bus /dev/usb Device /dev/ugen0.1: ID 0000:0000

# ls -la /dev/ugen2.2
lrwxr-xr-x  1 root  wheel  9 Apr 19 20:27 /dev/ugen2.2 -> usb/2.2.0
# ls -la /dev/usb/2.2.0
crw-------  1 root  operator    0, 120 Apr 19 20:27 /dev/usb/2.2.0


# ./bfgminer/bfgminer -o pool.xxx.com:0000 -u username -p secret -D -T --verbose -S all
 [2014-04-19 20:32:46] setrlimit: Changed soft fd limit from 11095 to 1024 (FD_SETSIZE=1024; hard limit=11095)         
 [2014-04-19 20:32:46] Started bfgminer 3.99.0
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=0000, pid=0000, manuf=CMDTECH, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:000:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found ft232r device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Device rescan requested
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=0000, pid=0000, manuf=CMDTECH, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:000:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found ft232r device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Device rescan requested a second time, delaying
 [2014-04-19 20:32:46] schedule_rescan: Scheduling rescan (no rescans currently pending)
 [2014-04-19 20:32:46] No devices detected!
 [2014-04-19 20:32:46] Waiting for devices
 [2014-04-19 20:32:46] Probing for an alive pool
 
I seen this message, and decided, probably some problems with a driver.

Also, I tried to use M+, with line:
Enter target:bitforce/dev/ugen2.2

Anyway see:
(no devices)
[Plus] Add device(s)  [Enter] Close device manager
No new devices found

So, this time I have no idea, what is happening...