JBT
|
 |
April 01, 2014, 04:15:35 AM |
|
This is something wrong with your pool.
Thanks. I used solo mining, I have found a block after I running BFGMiner few hours, so the error message seems doesn't matter. what speed you hashing at to find a block?
|
|
|
|
phuture
Newbie
Offline
Activity: 3
Merit: 0
|
 |
April 02, 2014, 08:39:03 AM |
|
i'm just trying run bfgminer with my gridseeds, but without success. my OS is Centos 6 with 3.10.20 kernel. i have enabled vcom low level driver, gridseed driver and scrypt. the kernel driver cdc_acm is removed, ftdi_sio module is loaded with product=0x5740 vendor=0x0483 and gridseeds are detected and gets /dev/ttyUSB*. when i start bfgminer with -S gridseed:all there is problem with initialization of miner and doesn't show in list of devices. it doesn't matter if i trying default BTC mode or LTC mode. i'm trying nwools branches features/gridseed-support(-new|-clean).
original cgminer from gridseed branch works fine with cooperation with minerd for scrypt. also cgminer from dtbartle's repository works fine.
please, what's wrong with my setup and cooperation with bfgminer?
|
|
|
|
salfter
|
 |
April 03, 2014, 12:08:37 AM |
|
i'm just trying run bfgminer with my gridseeds, but without success. my OS is Centos 6 with 3.10.20 kernel. i have enabled vcom low level driver, gridseed driver and scrypt. the kernel driver cdc_acm is removed, ftdi_sio module is loaded with product=0x5740 vendor=0x0483 and gridseeds are detected and gets /dev/ttyUSB*. when i start bfgminer with -S gridseed:all there is problem with initialization of miner and doesn't show in list of devices. it doesn't matter if i trying default BTC mode or LTC mode. i'm trying nwools branches features/gridseed-support(-new|-clean).
original cgminer from gridseed branch works fine with cooperation with minerd for scrypt. also cgminer from dtbartle's repository works fine.
please, what's wrong with my setup and cooperation with bfgminer?
Gridseed miners (the six I have, anyway) don't use FTDI serial chips. This is how they show up in the output from lsusb: Bus 001 Device 028: ID 0483:5740 SGS Thomson Microelectronics It's supported by the cdc_acm module and shows up as /dev/ttyACM*. And now for something completely different, here's a bit of weirdness: I've been running the feature/gridseed-support branch of bfgminer for a bit now. With 4 miners, it ran like a champ. I just received two more and hooked them into my rig. With 6 miners plugged in and configured, though, it runs for a minute or two and then stops finding shares. If I split the miners between two instances of bfgminer (three on each), they all run like they should. Someone else asked about the feature/gridseed-support-new branch. There's also a feature/gridseed-support-clean branch. A diff between the two shows some differences possibly pertaining to SHA-256 support for Gridseed miners...dual-mining support, possibly? driver-gridseed.c is the same between these two branches, and is newer than the version in the feature/gridseed-support branch. I think I'll try the feature/gridseed-support-clean branch and see if it works better with six miners.
|
|
|
|
phuture
Newbie
Offline
Activity: 3
Merit: 0
|
 |
April 03, 2014, 03:23:36 AM |
|
Gridseed miners (the six I have, anyway) don't use FTDI serial chips. This is how they show up in the output from lsusb: Bus 001 Device 028: ID 0483:5740 SGS Thomson Microelectronics they use FTDI! check my modprobe command where i specify vendor and product id. after that i see: ftdi_sio 1-5.4.6:1.0: FTDI USB Serial Device converter detected usb 1-5.4.6: Detected FT2232C usb 1-5.4.6: Number of endpoints 1 usb 1-5.4.6: Endpoint 1 MaxPacketSize 8 usb 1-5.4.6: Setting MaxPacketSize 8 ftdi_sio ttyUSB0: Unable to read latency timer: -32 ftdi_sio ttyUSB0: Unable to write latency timer: -32 usb 1-5.4.6: FTDI USB Serial Device converter now attached to ttyUSB0
It's supported by the cdc_acm module and shows up as /dev/ttyACM*.
they are, but afaik proper driver should be ftdi_sio. all in all, i can't run bfgminer (any with gridseed patches) with ftdi_sio or cdc_acm driver 
|
|
|
|
MobileWill
|
 |
April 03, 2014, 04:00:41 AM |
|
(First time I wrote this it wouldn't let me post, and now have to rewrite it.) Hi, I have 2 Gridseed and 4 GPU's. Is it possible to have all under control of once instance of BFGMiner? Prefer with config file. My main reason is so I can use CGWatcher to manage all hardware. If I use the default basic BAT file I get the Gridseeds working and the GPU's are OFF. But with the config I get just the Gridseeds. Here is my config. "scrypt" : "true", "gpu-threads" : "1", "gpu-engine" : "1200,950,950,1100", "gpu-fan" : "85", "gpu-memclock" : "1350,1000,1000,1500", "gpu-powertune" : "10,10,10,20", "intensity" : "17,17,17,19", "temp-target" : "75", "temp-overheat" : "80", "temp-cutoff" : "95", "worksize" : "256,256,256,256", "device" : "all", "scan-serial" : ["gridseed:all"], "set-device" : ["gridseed:clock=850"]
|
miningrigrentals.com/register?ref=80
|
|
|
salfter
|
 |
April 03, 2014, 05:27:23 AM |
|
Gridseed miners (the six I have, anyway) don't use FTDI serial chips. This is how they show up in the output from lsusb: Bus 001 Device 028: ID 0483:5740 SGS Thomson Microelectronics they use FTDI! check my modprobe command where i specify vendor and product id. after that i see: ftdi_sio 1-5.4.6:1.0: FTDI USB Serial Device converter detected usb 1-5.4.6: Detected FT2232C usb 1-5.4.6: Number of endpoints 1 usb 1-5.4.6: Endpoint 1 MaxPacketSize 8 usb 1-5.4.6: Setting MaxPacketSize 8 ftdi_sio ttyUSB0: Unable to read latency timer: -32 ftdi_sio ttyUSB0: Unable to write latency timer: -32 usb 1-5.4.6: FTDI USB Serial Device converter now attached to ttyUSB0
It's supported by the cdc_acm module and shows up as /dev/ttyACM*.
they are, but afaik proper driver should be ftdi_sio. all in all, i can't run bfgminer (any with gridseed patches) with ftdi_sio or cdc_acm driver  Are you sure you're not confusing them with some other mining hardware plugged into your rig, or is there some other device that combines one or more Gridseed chips with an FTDI chip? If it's the latter, it's possible that bfgminer doesn't support it. These are what I'm using (image hotlinked from Zoomhash's website, as that's where I've bought mine):  I have all of them running with the feature/gridseed-support-clean branch, though I think it might be a little bit touchy about switching pools on-the-fly. It's been running about 4.5 hours so far at 2.07 MH/s.
|
|
|
|
povlhp
Newbie
Offline
Activity: 35
Merit: 0
|
 |
April 03, 2014, 07:16:23 AM |
|
I have one question.
Been trying to solo-mine bfgminer -> bitcoind, but bfgminer keeps working on old stuff way after the block has changed.
How can I use blocknotify of bitcoind to tell bfgminer to actually pick up the new block and new work ? With eloipool in between, all works fine, but it is overkill, and it eats 100% CPU on one core.
Any SIGxxx to send ? Something else ?
|
|
|
|
pauljbl
Newbie
Offline
Activity: 39
Merit: 0
|
 |
April 03, 2014, 05:17:49 PM |
|
Hi
Can anyone help I have debian on my laptop with bfgminer 3.10.0 compiled and hidapi install. I am running nano fury's but I get lots of HW errors and keep getting nfy 8 of the last results were bad reinitiialising and dont get a good hash rate.
Using the same setup in windows I dont get theses problems and a good hash rate I dont understand what is wrong
|
|
|
|
poopypants
|
 |
April 03, 2014, 07:37:59 PM |
|
Nwoolls & Luke-Jr thank you for the work you guys put in!
Question, is it possible to manage Gridseed devices with different frequencies within one instance of bfgminer? Anyone have any solutions or am I missing something? I tried to read through a lot of the recent posts to see if someone stated a solution but could not find one. Thanks
|
|
|
|
MobGod
|
 |
April 04, 2014, 03:35:03 PM |
|
|
|
|
|
pallas
Legendary
Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
 |
April 04, 2014, 03:36:50 PM |
|
Nwoolls & Luke-Jr thank you for the work you guys put in!
Question, is it possible to manage Gridseed devices with different frequencies within one instance of bfgminer? Anyone have any solutions or am I missing something? I tried to read through a lot of the recent posts to see if someone stated a solution but could not find one. Thanks
I belive you can with this: https://github.com/girnyau/cgminer-gc3355/commits/masternot bfgminer, though.
|
|
|
|
MobGod
|
 |
April 04, 2014, 05:49:04 PM |
|
|
|
|
|
|
|
MobGod
|
 |
April 04, 2014, 06:55:25 PM |
|
|
|
|
|
pauljbl
Newbie
Offline
Activity: 39
Merit: 0
|
 |
April 04, 2014, 08:58:44 PM |
|
Nwools and Luke have you ever tried 15 Nanofurys on Linux as wondering if the drivers are buggy as on the same machine with windows they run fine.
|
|
|
|
chanberg
|
 |
April 05, 2014, 12:09:12 AM |
|
Wonder if the auto dynamic freq change ever been implemented for the gridseeds? Would be nice if bfgminer just auto dialed the freq and let it do its thing to find its best frequency
|
|
|
|
everest556
Newbie
Offline
Activity: 38
Merit: 0
|
 |
April 05, 2014, 04:51:00 AM |
|
How soon are we going to see support for Technobit's HEX16A2?
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2604
Merit: 1186
|
 |
April 05, 2014, 09:05:08 AM |
|
Pushed a "gridseed" branch to the main BFGMiner git based on nwoolls's code. I'm not sure how these are supposed to perform, but I get some inconsistent results in benchmark mode: DMU 0: | 36.8/ 68.2/ 41.7kh/s | A: 28 R:0+0(none) HW:0/none GSD 0: | 0.73/ 1.27/ 0.17Mh/s | A:112 R:0+0(none) HW:8/none How's it work for others who have been using them in production?
|
|
|
|
Mr. Jinx
Member

Offline
Activity: 112
Merit: 10
|
 |
April 05, 2014, 09:27:43 AM Last edit: April 05, 2014, 09:56:06 AM by Mr. Jinx |
|
How's it work for others who have been using them in production?
I'm running this for a while now with good results: bfgminer version 3.99.0 - Started: [2014-04-04 21:06:45] - [ 0 days 12:18:32] [M]anage devices [P]ool management [S]ettings [D]isplay options [H]elp [Q]uit Connected to x diff 1m with stratum as user x Block: ...b53afe02 #544104 Diff:5.75k (41.13Gh/s) Started: [09:24:58] ST:102 F:0 NB:305 AS:0 BW:[ 3/ 0kB/s] E:0.00 I:11.33mBTC/hr BS:196 0 | 6.95/ 7.01/ 6.21Mh/s | A:26713 R:2704+0(8.6%) HW:17/none ------------------------------------------------------------------------------------------------------ GSD 0: | 338.6/348.9/264.6kh/s | A: 1138 R: 119+0(none) HW: 0/none GSD 1: | 346.6/350.5/323.2kh/s | A: 1388 R: 128+0(none) HW: 0/none GSD 2: | 344.4/351.1/320.7kh/s | A: 1383 R: 135+0(none) HW: 0/none GSD 3: | 339.4/349.2/283.3kh/s | A: 1207 R: 111+0(none) HW: 0/none GSD 4: | 338.4/350.2/300.9kh/s | A: 1303 R: 147+0(none) HW: 0/none GSD 5: | 345.4/350.6/316.2kh/s | A: 1359 R: 155+0(none) HW: 0/none GSD 6: | 345.4/351.0/330.8kh/s | A: 1431 R: 142+0(none) HW: 0/none GSD 7: | 356.6/350.8/334.8kh/s | A: 1435 R: 132+0(none) HW: 0/none GSD 8: | 343.9/350.6/329.5kh/s | A: 1415 R: 122+0(none) HW: 0/none GSD 9: | 349.7/350.1/303.3kh/s | A: 1314 R: 116+0(none) HW: 0/none GSD10: | 347.2/349.6/295.9kh/s | A: 1272 R: 143+0(none) HW: 0/none GSD11: | 357.0/350.5/307.9kh/s | A: 1332 R: 144+0(none) HW:12/none GSD12: | 344.4/348.9/271.1kh/s | A: 1167 R: 116+0(none) HW: 0/none GSD13: | 339.6/350.2/318.7kh/s | A: 1358 R: 130+0(none) HW: 0/none GSD14: | 352.7/350.3/310.1kh/s | A: 1330 R: 164+0(none) HW: 0/none GSD15: | 344.9/350.5/317.0kh/s | A: 1372 R: 148+0(none) HW: 0/none GSD16: | 347.0/350.2/312.9kh/s | A: 1342 R: 130+0(none) HW: 1/none GSD17: | 342.5/351.2/335.5kh/s | A: 1440 R: 156+0(none) HW: 0/none GSD18: | 344.6/350.6/316.4kh/s | A: 1350 R: 129+0(none) HW: 4/none GSD19: | 351.0/351.1/320.8kh/s | A: 1387 R: 138+0(none) HW: 0/none ------------------------------------------------------------------------------------------------ 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?).
|
|
|
|
|