Pages:
Author

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

sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
Been doing a lot of major cleanups to the OpenCL driver as part of the big 4.0 release upcoming, bringing it up to par with the rest of the drivers.

I'm wondering if anyone uses the --gpu-dyninterval option, or has ever had any success with it?
Looking at the code, it seems to be broken and do the opposite of what it claims...
If nobody cares about it, I'll probably just remove it entirely.

Is dynamic intensity being turned on when we do an "--auto-gpu"?  If so, I'm using the feature, but not tweaking it with gpu-dyninternal, having never made the connection.
full member
Activity: 207
Merit: 100
I think I figured out why my Antminers arent being found.. I took a old USB 2.0 hub and connected 2 Antminers to it, and they were found but when I connect my USB 3.0 hubs they do not get detected. Here are my hubs:

http://www.amazon.com/gp/product/B00CBEVTIA/ref=oh_details_o07_s00_i00?ie=UTF8&psc=1

http://www.amazon.com/gp/product/B00EYXZI4M/ref=oh_details_o05_s00_i00?ie=UTF8&psc=1

Any reason they wouldnt work?

The Pi has some pretty well-documented driver problems with USB 3.0.
hero member
Activity: 868
Merit: 1000
I think I figured out why my Antminers arent being found.. I took a old USB 2.0 hub and connected 2 Antminers to it, and they were found but when I connect my USB 3.0 hubs they do not get detected. Here are my hubs:

http://www.amazon.com/gp/product/B00CBEVTIA/ref=oh_details_o07_s00_i00?ie=UTF8&psc=1


Any reason they wouldnt work?

I have 8 of these hubs, they work perfectly when I connect them through an unpowered usb2 hub

https://www.dropbox.com/s/guzc6y5c8wt2jxg/2013-10-20%2019.31.47.jpg

Edit:-  Half of these erupters have now been replaced with Ants
newbie
Activity: 27
Merit: 0
I think I figured out why my Antminers arent being found.. I took a old USB 2.0 hub and connected 2 Antminers to it, and they were found but when I connect my USB 3.0 hubs they do not get detected. Here are my hubs:

http://www.amazon.com/gp/product/B00CBEVTIA/ref=oh_details_o07_s00_i00?ie=UTF8&psc=1

http://www.amazon.com/gp/product/B00EYXZI4M/ref=oh_details_o05_s00_i00?ie=UTF8&psc=1

Any reason they wouldnt work?
legendary
Activity: 2576
Merit: 1186
Been doing a lot of major cleanups to the OpenCL driver as part of the big 4.0 release upcoming, bringing it up to par with the rest of the drivers.

I'm wondering if anyone uses the --gpu-dyninterval option, or has ever had any success with it?
Looking at the code, it seems to be broken and do the opposite of what it claims...
If nobody cares about it, I'll probably just remove it entirely.
hero member
Activity: 868
Merit: 1000
Is there an easy way to replug AntMiner U1 device in bfgminer? New cgminer introduced a menu to work with broken USB devices. From time to time, U1 device dies, it is not mining and it is not dead, like in this example, AMU 3 device was mining for some time at 2GHps but it is not mining for a while (or mining at low hashrate):

Code:
4            |  8.35/ 8.33/ 6.61Gh/s | A:3492 R:1+0(.03%) HW:0/none
--------------------------------------------------------------------------------
 AMU 0:       |  2.06/ 2.06/ 1.99Gh/s | A:1015 R:0+0(none) HW:0/none
 AMU 1:       |  2.07/ 2.06/ 2.01Gh/s | A:1084 R:1+0(.09%) HW:0/none
 AMU 2:       |  2.06/ 2.06/ 1.99Gh/s | A:1081 R:0+0(none) HW:0/none
 AMU 3:       |  2.10/ 2.14/ 0.62Gh/s | A: 314 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------

I am not sure what is a problem but devices were running at 2GHps for several days but they make trouble today... ;-) I know, I can restart bfgminer, it will fix the problem.
That's odd, BFGMiner's watchdog should automatically restart it in this case...
Any idea what's going on that stops it?

I guess the device runs at edge of electrical or thermal limits. You see 4 devices in the rig, and one of them is the worst one. The situation illustrates what happens when the worst device "fails". AMU3 device is not completely dead but it runs with low hashrate. I can fix this situation when I quit bfgminer and start it again. After restart, all devices were mining at 2GHps for a while but the AMU3 device switched to slower mode again. I fixed that by decreasing hashrate of the whole rig from 2000 to 1950 MHps...

I have a separate session of BFG running at one speed setting slower than the rest.
Most run at 0A01 = 2100
the bad one needs 0981 = 2000

Then they are all stable again
PSL
member
Activity: 166
Merit: 10
Is there an easy way to replug AntMiner U1 device in bfgminer? New cgminer introduced a menu to work with broken USB devices. From time to time, U1 device dies, it is not mining and it is not dead, like in this example, AMU 3 device was mining for some time at 2GHps but it is not mining for a while (or mining at low hashrate):

Code:
4            |  8.35/ 8.33/ 6.61Gh/s | A:3492 R:1+0(.03%) HW:0/none
--------------------------------------------------------------------------------
 AMU 0:       |  2.06/ 2.06/ 1.99Gh/s | A:1015 R:0+0(none) HW:0/none
 AMU 1:       |  2.07/ 2.06/ 2.01Gh/s | A:1084 R:1+0(.09%) HW:0/none
 AMU 2:       |  2.06/ 2.06/ 1.99Gh/s | A:1081 R:0+0(none) HW:0/none
 AMU 3:       |  2.10/ 2.14/ 0.62Gh/s | A: 314 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------

I am not sure what is a problem but devices were running at 2GHps for several days but they make trouble today... ;-) I know, I can restart bfgminer, it will fix the problem.
That's odd, BFGMiner's watchdog should automatically restart it in this case...
Any idea what's going on that stops it?

I guess the device runs at edge of electrical or thermal limits. You see 4 devices in the rig, and one of them is the worst one. The situation illustrates what happens when the worst device "fails". AMU3 device is not completely dead but it runs with low hashrate. I can fix this situation when I quit bfgminer and start it again. After restart, all devices were mining at 2GHps for a while but the AMU3 device switched to slower mode again. I fixed that by decreasing hashrate of the whole rig from 2000 to 1950 MHps...
newbie
Activity: 27
Merit: 0
newbie
Activity: 27
Merit: 0
When you build the github source, and do the .configure line, you should get final output that looks something like this:

Enabled..Drivers.....: antminer avalon bifury bigpic bitforce bitforce:uio bitfury_gpio cairnsmore drillbit erupter hashbusterusb hashfast icarus klondike littlefury modminer proxy proxy:stratum twinfury x6500 ztex

Note the antminer at the front of that list.  Your list may vary of course, depending on what options you passed configure.

Are there any instuctions for Rasp Pi and Antminer install?
newbie
Activity: 24
Merit: 0
16:41] KLN0:0 failed to update stats
 [2014-02-22 12:16:41] KLN0:0 went idle before work was sent

 

Is this normal? for the KLN?
legendary
Activity: 2576
Merit: 1186
Is there an easy way to replug AntMiner U1 device in bfgminer? New cgminer introduced a menu to work with broken USB devices. From time to time, U1 device dies, it is not mining and it is not dead, like in this example, AMU 3 device was mining for some time at 2GHps but it is not mining for a while (or mining at low hashrate):

Code:
4            |  8.35/ 8.33/ 6.61Gh/s | A:3492 R:1+0(.03%) HW:0/none
--------------------------------------------------------------------------------
 AMU 0:       |  2.06/ 2.06/ 1.99Gh/s | A:1015 R:0+0(none) HW:0/none
 AMU 1:       |  2.07/ 2.06/ 2.01Gh/s | A:1084 R:1+0(.09%) HW:0/none
 AMU 2:       |  2.06/ 2.06/ 1.99Gh/s | A:1081 R:0+0(none) HW:0/none
 AMU 3:       |  2.10/ 2.14/ 0.62Gh/s | A: 314 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------

I am not sure what is a problem but devices were running at 2GHps for several days but they make trouble today... ;-) I know, I can restart bfgminer, it will fix the problem.
That's odd, BFGMiner's watchdog should automatically restart it in this case...
Any idea what's going on that stops it?
newbie
Activity: 24
Merit: 0
I am running windows, not sure what batch file is or where its at. sorry.
PSL
member
Activity: 166
Merit: 10
Is there an easy way to replug AntMiner U1 device in bfgminer? New cgminer introduced a menu to work with broken USB devices. From time to time, U1 device dies, it is not mining and it is not dead, like in this example, AMU 3 device was mining for some time at 2GHps but it is not mining for a while (or mining at low hashrate):

Code:
4            |  8.35/ 8.33/ 6.61Gh/s | A:3492 R:1+0(.03%) HW:0/none
--------------------------------------------------------------------------------
 AMU 0:       |  2.06/ 2.06/ 1.99Gh/s | A:1015 R:0+0(none) HW:0/none
 AMU 1:       |  2.07/ 2.06/ 2.01Gh/s | A:1084 R:1+0(.09%) HW:0/none
 AMU 2:       |  2.06/ 2.06/ 1.99Gh/s | A:1081 R:0+0(none) HW:0/none
 AMU 3:       |  2.10/ 2.14/ 0.62Gh/s | A: 314 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------

I am not sure what is a problem but devices were running at 2GHps for several days but they make trouble today... ;-) I know, I can restart bfgminer, it will fix the problem.
newbie
Activity: 42
Merit: 0
No.

Are you running Windows or Linux?

The Batch file I mentioned is for Windows only. For Linux you'll need a different approach.




like this? Sorry I'm not sure if i have a Batch file and if i do i don't know where it is.

{
"pools" : [
 {
  "url" : "stratum+tcp://mint.bitminter.com:3333",
  "user" : "cro",
  "pass" : "1",
  "pool-priority" : "2"
 }
],
"failover-only" : true,
"queue" : "3",
"log" : "1",
"scan-time" : "60",
"no-submit-stale" : true,
"set-device":["antminer:freq=0981"],
"klondike-options":"355:60",
pause
}
newbie
Activity: 24
Merit: 0
like this? Sorry I'm not sure if i have a Batch file and if i do i don't know where it is.

{
"pools" : [
 {
  "url" : "stratum+tcp://mint.bitminter.com:3333",
  "user" : "cro",
  "pass" : "1",
  "pool-priority" : "2"
 }
],
"failover-only" : true,
"queue" : "3",
"log" : "1",
"scan-time" : "60",
"no-submit-stale" : true,
"set-device":["antminer:freq=0981"],
"klondike-options":"355:60",
pause
}
newbie
Activity: 42
Merit: 0
If you are using Windows, add the PAUSE command to the end of your batch file. See my post above for an example (it's in green text towards the bottom of the post).



Hi guys, anyone know and where to add command to bfgminer so that when i quit i can read the stats before the window closes?
like in my .conf file.
Thank you


i think this is it ( Summary of runtime statistics:) when i hit Q i don't get to read it window scrolls by to quickly then closes.
newbie
Activity: 24
Merit: 0
Hi guys, anyone know and where to add command to bfgminer so that when i quit i can read the stats before the window closes?
like in my .conf file.
Thank you


i think this is it ( Summary of runtime statistics:) when i hit Q i don't get to read it window scrolls by to quickly then closes.
newbie
Activity: 42
Merit: 0
Hi all. Seeking guidance from the group once again.

Serendipity played a big part in me acquiring an awesome desktop PC second hand (ASRock MB with 3xPCIe slots, Intel i7 with a monster aftermarket heat sink, 8GB RAM, 210GB SSD, 2TB HDD, ATI Radeon 6970 2GB, Windows 7 Ultimate x64, lots of USB 1,2 and 3 ports, and a bunch of lesser important stuff, all housed in a tower case with around 4 fans. Cost? A$700

So I thought great, I'll use the on-board VGA or DVI as my main monitor, and set the GPU up for mining (which is what I've done).

I installed the drivers from the AMD website (it auto sensed what card I had and it downloaded and installed Catalyst etc etc etc).

http://i59.tinypic.com/xm22oz.png

Then I installed my (now) favorite miner, bfgminer 3.10.0 app (x64), kicked it into gear with a moderate intensity of 9, and it started hashing around 450MH. After 5 mins it drops to 0MH. I looked for obvious clues (well, obvious to me), but found nothing. I repeated the test 3 times and each time, around the 5 min mark, it dropped to 0MH (not a slow drop - straight to 0).

I'm mining DOGE. I have other workers in this pool (CPUminers) and they are doing just fine so I know the pool works.

I am at a loss why. Here's my CMD file:

bfgminer -S opencl:auto -o stratum+tcp://doge.pool.mn:3333 -u mfread.storm1 -p 123456 -I 9

I've also read the various TXT files, trying to decipher them, and came up with:

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

I am not entirely sure what the --auto params do. Are they good or bad for the life of my GPU card?

There are no HW errors.

Note: 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 (liek the AMD SDK stuff) I should be installing?

I've search multiple forums but can't seem to get a grasp on what's going on. Ideas anyone?


As another test, I installed MultiMiner (and let it download and install bfgminer in it's subfolder). It runs but only shows the 6970 doing 19 kh/s. I've searched hi and lo in the MultiMiner app re: how to change card params (like intensity, concurrent threads etc) but to no avail.


Hmmm, now I'm thinking why is bfgminer reporting MH and not KH for a scrypt coin (with 1xGPU card)? The litecoin wiki tells me to expect around 450kh/s for a AMD HD6970 card.

So I added the 2 x setx arguments and --scrypt into my bfgminer line (as I see it in MultiMiner) and now I'm getting 48MH/s?? No HW errors. I see acceptances too. So it looks like it's behaving. After 8 mins it has climbed to 67MH/s. Is this normal? After 44 mins it is reporting 144MH/s and now HW errors. The mining pool says this worker is doing 48KH/S.

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

Do I / should I add in the 'shaders' param? If so what should it be?

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

Cheers for now.

Mark
member
Activity: 73
Merit: 10
Hi guys i had two miners that now i use with cgminer, but i want do the same thing with bfgminer.
The miners are 1 Technobit Hex16A2 and 1 BitBurner 52GH/s
How i can find the drivers to use them in BFGminer?
TechnoBit HEX16A2: For some reason, these are incompatible with Linux's USB CDC/ACM drivers, so I have been unable to complete a driver for them; while I've tried to get Linux developers involved to fix it, they just don't seem interested. In lieu of that, I recently shipped the sample unit to nwoolls, who does his development on Mac/Windows, and will be sending him my notes and incomplete driver code so he can complete it.

BitBurner: No contact, docs, or samples from this vendor. Support is not planned at this time. Please contact the manufacturer and/or vendors to recommend they get in touch.

Thanks Luke, the reason of this question is that bfgminer platform give more information than cgminer, I'm use now this OS, windows XP Professional not Linux.
I hope that future realeases had the support for these machines.... Wink
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
Getting several of these a second now:

Feb 21 16:38:46 miner2 bfgminer[29929]: Testing pool stratum+tcp://multicoin.zapto.org:3320
Feb 21 16:38:46 miner2 bfgminer[29929]: HTTP request failed: Protocol stratum+tcp not supported or disabled in libcurl
Feb 21 16:38:46 miner2 bfgminer[29929]: Testing pool stratum+tcp://multicoin.zapto.org:3320
Feb 21 16:38:46 miner2 bfgminer[29929]: HTTP request failed: Protocol stratum+tcp not supported or disabled in libcurl
Feb 21 16:38:46 miner2 bfgminer[29929]: Testing pool stratum+tcp://multicoin.zapto.org:3320
Feb 21 16:38:46 miner2 bfgminer[29929]: HTTP request failed: Protocol stratum+tcp not supported or disabled in libcurl
^C
miner2 local.d # 20s: 7.13 avg:11.29 u:11.81 Gh/s | A:19 R:0+0(none) HW:0/none 

As you can see from the last line, bfgminer is connecting and doing work with the pool.

Any way to quiet it up?

From "ps ax":  29929 pts/0    Sl     0:00 ./bfgminer -S antminer:all --set-device antminer:clock=x0981 --text-only --real-quiet --syslog --cmd-sick /sbin/reboot --cmd-dead /sbin/reboot --balance -o stratum+tcp://us-east.multipool.us:8888 -O Cassey.miner2am:x -o stratum+tcp://multicoin.zapto.org:3320 -O Cassey.miner2am:x

Pages:
Jump to: