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

Thank you for the quit answer Luke

F:\Easy Miner\bfgminer>bfgminer -G -D -T -d?
[2013-06-21 22:59:36] setrlimit: Not supported by platform
[2013-06-21 22:59:36] ft232r_scan: Found 15c2:ffdc - not a ft232r

[2013-06-21 22:59:36] ft232r_scan: Found 1002:4396 - not a ft232r

[2013-06-21 22:59:36] ft232r_scan: Found 1002:4396 - not a ft232r

[2013-06-21 22:59:36] ft232r_scan: Found 1002:4399 - not a ft232r

[2013-06-21 22:59:36] ft232r_scan: Found 1002:4398 - not a ft232r

[2013-06-21 22:59:36] ft232r_scan: Found 1002:4397 - not a ft232r

[2013-06-21 22:59:36] ft232r_scan: Found 1002:4398 - not a ft232r

[2013-06-21 22:59:36] ft232r_scan: Found 050d:815f - not a ft232r

[2013-06-21 22:59:36] ft232r_scan: Found 0403:6014 - not a ft232r

[2013-06-21 22:59:36] ft232r_scan: Found 1002:4397 - not a ft232r

[2013-06-21 22:59:36] Started bfgminer 3.1.0
[2013-06-21 22:59:36] FTDI reports 1 devices
[2013-06-21 22:59:36] FTDI reports 1 devices
[2013-06-21 22:59:36] BFL: Attempting to open \\.\COM3
[2013-06-21 22:59:36] Found BitForce device on \\.\COM3
[2013-06-21 22:59:37]   DEVICE: BitFORCE SC
[2013-06-21 22:59:37]   FIRMWARE: 1.0.0
[2013-06-21 22:59:37]   MINIG SPEED: 5.13 GH/s
[2013-06-21 22:59:37]   PROCESSOR 3: 14 engines @ 182 MHz
[2013-06-21 22:59:37]   PROCESSOR 7: 13 engines @ 200 MHz
[2013-06-21 22:59:37]   ENGINES: 27
[2013-06-21 22:59:37]   FREQUENCY: 189 MHz
[2013-06-21 22:59:37]   XLINK MODE: MASTER
[2013-06-21 22:59:37]   CRITICAL TEMPERATURE: 0
[2013-06-21 22:59:37]   XLINK PRESENT: NO
[2013-06-21 22:59:37] FTDI reports 1 devices
[2013-06-21 22:59:37] Not a ZTEX device 15c2:ffdc
[2013-06-21 22:59:37] Not a ZTEX device 1002:4396
[2013-06-21 22:59:37] Not a ZTEX device 1002:4396
[2013-06-21 22:59:37] Not a ZTEX device 1002:4399
[2013-06-21 22:59:37] Not a ZTEX device 1002:4398
[2013-06-21 22:59:37] Not a ZTEX device 1002:4397
[2013-06-21 22:59:37] Not a ZTEX device 1002:4398
[2013-06-21 22:59:37] Not a ZTEX device 050d:815f
[2013-06-21 22:59:37] Not a ZTEX device 0403:6014
[2013-06-21 22:59:37] Not a ZTEX device 1002:4397
[2013-06-21 22:59:37] Devices detected:
[2013-06-21 22:59:37]   0. BFL 0  (driver: bitforce_queue)
 devices listed

F:\Easy Miner\bfgminer>

This is the output i get when i give the command in the easyminer\bfgminer map
Its actually connected to my old htpc at the moment since it does not work at all on my new intel i7 system even if i install any of them given winsub drivers
The new machine has many usb3 ports i am not sure if this is the reason why it totally fails to see the device even though its clearly listed in the usb devices under hardware.

Is this with BFGMiner version 3.1.0? Can you post the output from

I received a jalapeno mini miner from bfl and run into some weird problems
To recover some of the stolen btc and the financial losses with buying from BFL
So i decided to mine enough to get a better miner someday

When i use the easyminer software i can run it on some pools and seem to run ok but kinda sluggish

Now comes the idiot part when i use cgminer or bfgminer from a command batch it simply does not find the asic miner
So i start the easyminer crap and poof it runs again.
For parameters i used the help provided on eligius wiki and help pages

I do not want the miners to use any gpu they find since that would kill any income considering the electircal costs in my country for little extra hashes

bfgminer -G -o stratum+tcp://stratum.mining.eligius.st:3334 -O my btc address

for the other i used cgminer -o http://stratum.mining.eligius.st:3334 -u address -p x -G

When i start both it takes a while to start and then i get the message no comm devices detected.

So i took another test with bitminter client and guess what: it simply runs instant without any problem

Thanks, this was just what I was looking for!  Just now got my cute little Erupter up and running.  It worked the first time!

I'm running P2Pool, so my payout address and bitcoind RPC username/password are not set here, they're in P2Pool instead.  Here's my command line, in case it helps others:


Edit: I donated!  Much thanks, very nice and powerful program.

Josh

-S all is sufficient if the driver is in order.

I'm not missing the driver. Each time ubuntu updates it makes a new kernel version folder. each with a  build and updates folder. The original kernel folder has all the drivers and etc....

I rebooted and ran bfgminer again with -S /dev/ttyUSB0 and it appears to still be using my GPU. What flags do I need to use to make it use the block erupter? I've googled all day and can't find any clear instructions for linux. Plenty for Windoze 7 though.

Linux is a a monolithic kernel. So its "drivers" are technically builtin, even if they're loaded at runtime.
This means you cannot use a driver compiled for any other version, with the current one; it must be the matching version.
Where did you get your kernel from that it is missing the driver? :/

Could you check, why I cannot add stratum pool through API?

This stratum pool is added but it is DEAD. When I add pool from bfgminer GUI, it is OK, pool is ALIVE. When I add getwork pool from API, it is ALIVE.

Another example of pool that is DEAD when added through API:

and I see this error in bfgminer:


UPDATE:
I found that when I add stratum pool with echo -n "addpool|URL,USER,PASS", it is ALIVE. It means, that trailing newline was troublemaker; I still don't understand, why trailing newline was problem for stratum but was working fine for getwork. And why it was problem for stratum, because password is not important in my examples and newline was added to password that was the last parameter in the line....

Correct code looks like this:

I've been using bfgminer for GPU mining for several months now and it's been working great. I have a new question. I looked at the ReadMe and didn't see what I was looking for. I'm sure this has been asked a million times, but I'm still nooby.

I got an asicminer block erupter yesterday. Can I set up bfgminer to use it and my gpu together? I'd like to get both hashing, just not sure what I need to do to do it.

Should I run 2 instances of bfgminer: one for the asic, and one for the gpu? Trying to get my head around this. Any help would be great.

Also, I'm running Ubuntu 13.04. I know I have to put -s in the command line, but do I have to put anything else in?

Edit: using -s /dev/ttyUSB(#) gives error /dev/ttyUSB(#) is not a number.(Yes, I'm using the number of my port for (#))  

Edit 2: I got bfgminer to start by using the -S /dev/ttyUSB0 flag, but it's not mining anything. I looked around in my folders and the usb to uart bridge drivers(cp210x.ko in linut) are in the "3.8.0-19-generic" directory, but not in the newer kernel directories. Does this make a difference? Shouldn't it access it from the previous kernel directories? I'm at a loss here. I'd like to get this block erupter hashing. 

Thanks now it works again. One problem though:
Intensity settings > 0 don't seem to have a lot of effect (compared to 3.0.2)
Intensity settings < 0 reduce GPU usage properly but consume huge amounts of CPU (2 cores 100%)
Dynamic works great (low CPU usage, good hashing performance)

Tested with Catalys 13.4 on Win 7 x64 and

Maybe it is related to the debug build?

EDIT: when looking at bfg's threads there are the two gpu threads that seem to use all the cycles:
atiocl64.dll!clGetSamplerInfo+0x36a80
They also exist for dynamic intensity but only with 0.5% CPU instead of double digits.

Theoretical bug in libblkmaker:

parse_txn populates txn->hash but is missing a call to "my_flip(txn->hash, 32);".

Windows 64-bit 3.1.0 is broken for GPU mining.
Either turn it off with the -G option or replace the EXE with this fixed one until 3.1.1.

Thanks to unit3 for the initial bug report (though neither of us imagined it'd crash Win64!) and TelVoSRS for finishing the bisect first

Edit: Details: I changed the OpenCL driver to use the common open_bitstream function to find its kernels, to allow installing them to the standard location for such data files on GNU/Linux. However, I forgot to include the fpgautils.h headers which contained the definition of how to call the function. When the compiler doesn't know, it makes an educated guess based on the syntax used. For Win64, that guess happened to be wrong, and resulted in the build crashing when it attempted to open an OpenCL kernel. When unit3 went to update the Ubuntu PPA, it refused to build because it knew the educated-guess function was a bad idea and broke IA-64. Nobody really uses IA-64, so I simply fixed it and he finished the build. It wasn't until later that the bisection results identified the change to blame for the crash that I realized what happened there - in fact, I'd say I probably wouldn't have figured it out without hours (if not days) of debugging had Launchpad and unit3 not caught the problem earlier.

Windows 64 bit version of bfgminer 3.1.0 never starts for me at all - it crashes back to command line immediately. 
BFL's Easyminer (running bfgminer) seems to work fine.

Yes, my 32bit version running on win7 has crashed about 3 times in the last 24 hours.  I couldn't get the 64bit version to run. 

I've had numerous crashes with 3.1.0 over the past 24 hours across 3 separate clusters. I need to babysit this one too much, so it has turned out to be impractical for me. This is the 32-bit Windows version running on both 32-bit and 64-bit Win7 instances.

I've since reverted to the previous experimental version bfgminer-w32-320e7ed (reports itself as 3.0.99) which is much more stable.

Something is wrong with the w64 build. It crashes after starting on my AMD A10-5800K and my AMD E2-1800. The w32 build and the old 3.0.99 w64 build are without problems.

Fixed

The tag for 3.1.0 is missing on github.  Thanks!

Can you meet me on IRC some time to try to debug this regression?

Please follow the compile instructions in README.

Hi,

Just a few issues.  version 3.1.0 crashes when running on my Win7 64bit.  Had to go back to 3.0.3.  It seems to work good.

I would like to run BFGMiner 3.1.0 on my linux computer.  I am not that familiar with linux.  I have tried to compile it on my
linux mint debian edition but get an error when using make.  "No targets specified and no makefile found.  Stop."  Any
help would be greatly appreciated.

Thanks!