what goes wrong, what does this mean?
Code:
BFL 1a: Ran out of buffer space for results, discarding extra data
Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 108. (Read 1193422 times)
October 20, 2013, 02:02:45 PM
BFL LS:
what goes wrong, what does this mean?
often after a time BFL LS get sick, stops and no restart; - only with unconnecting power and restart Bfgminer...
what goes wrong, what does this mean?
October 20, 2013, 09:16:48 AM
Oh, OK, so you're changing the terms, because classically a stratum proxy (like slush's one) allows a getwork client to mine on a stratum pool. 
Slush's Stratum proxy refers only to the upstream protocol.It supports both getwork and Stratum clients.
So, back to the question - is the getwork proxy available on OpenWRT?
Should be. 
October 20, 2013, 09:15:43 AM
Oh, OK, so you're changing the terms, because classically a stratum proxy (like slush's one) allows a getwork client to mine on a stratum pool.
That's cool, as long as I know what you're calling what.
So, back to the question - is the getwork proxy available on OpenWRT?
That's cool, as long as I know what you're calling what.
So, back to the question - is the getwork proxy available on OpenWRT?
October 20, 2013, 09:07:18 AM
The stratum proxy is fully supported on all platforms, including Win64.
It's only the getwork proxy that can't do Win64.
It's only the getwork proxy that can't do Win64.
There's a difference?
Surely:
stratum proxy is for allowing getwork clients to mine on a stratum pool?
getwork proxy is for allowing getwork clients to mine on a stratum pool?
Confused.
getwork proxy is for allowing getwork clients to mine on any pool(s).
October 20, 2013, 09:06:26 AM
The stratum proxy is fully supported on all platforms, including Win64.
It's only the getwork proxy that can't do Win64.
It's only the getwork proxy that can't do Win64.
There's a difference?
Surely:
stratum proxy is for allowing getwork clients to mine on a stratum pool?
getwork proxy is for allowing getwork clients to mine on a stratum pool?
Confused.
October 20, 2013, 09:00:11 AM
Luke-Jr, have you any idea if/when you'll be adding the stratum proxy module to the OpenWRT version of BFGMiner?
IIRC, it should be there in 3.3.0?OK, cool. I didn't see anything specific in the READMEs about it being added, so assumed it was still not on OpenWRT, like it's still not on Win64 version.
I'll give it a spin sometime on OpenWRT...
It's only the getwork proxy that can't do Win64.
October 20, 2013, 07:46:24 AM
Luke-Jr, have you any idea if/when you'll be adding the stratum proxy module to the OpenWRT version of BFGMiner?
IIRC, it should be there in 3.3.0?OK, cool. I didn't see anything specific in the READMEs about it being added, so assumed it was still not on OpenWRT, like it's still not on Win64 version.
I'll give it a spin sometime on OpenWRT...
October 20, 2013, 12:06:18 AM
./bfgminer: --http-port: unrecognized option
This means libmicrohttpd wasn't found when you ran configure. October 19, 2013, 11:59:12 PM
I'm trying to run ASICMINER Block Erupter Blades with BFGminer.
I'm running xubuntu and I installed the libmicrohttpd as was required.
However when I type:
./bfgminer --http-port 8330
I get this error:
./bfgminer: --http-port: unrecognized option
What am I doing wrong?
Also what should I put on the Blade for address and password?
Thanks.
I'm running xubuntu and I installed the libmicrohttpd as was required.
However when I type:
./bfgminer --http-port 8330
I get this error:
./bfgminer: --http-port: unrecognized option
What am I doing wrong?
Also what should I put on the Blade for address and password?
Thanks.
October 19, 2013, 05:32:40 AM
Request for ppcoin solo mining support.
I tried to solo mining with bfgminer, however, it returned with a error message:
Code:
./bfgminer: --coinbase-addr: Invalid address
which seems that bfgminer only supports bitcoin address and doesn't support ppcoin address.
October 18, 2013, 09:20:27 PM
Hello..
Using bfgminer and a jalapeno..
When I press M to manage devices, I can then use up/down to select processor, but a couple times I did something to show all of them at once??? Anyone know how I did that or what is the command???
Thanks!
Using bfgminer and a jalapeno..
When I press M to manage devices, I can then use up/down to select processor, but a couple times I did something to show all of them at once??? Anyone know how I did that or what is the command???
Thanks!
October 18, 2013, 03:48:25 PM
^^ perfect, thanks.. will go fix all my scripts.. Might want to update miner.php while you're at it to work with the API changes.
It already does. There is a $per_proc setting which controls how the data is displayed.
October 18, 2013, 03:28:56 PM
^^ perfect, thanks.. will go fix all my scripts.. Might want to update miner.php while you're at it to work with the API changes.
October 18, 2013, 03:28:10 PM
Luke-Jr:
Any reason why the extended-core information for BFL's (seeing all cores per Single, for example) went away from 3.2.90 to 3.3.0 via the API?
I used to get all 16 cores per single, now I see only summary information.
Quote
API V2.0 (BFGMiner v3.3.0)
Removed API commands:
'devdetail' - Use newer 'devdetails' for same information.
Modified API commands:
'devs' - display status of each full device only (not processors)
'pga' - lookup and display device by device (not processor) number
'pgacount' - count only full devices (not processors)
'pgaenable' - enable all processors for a numbered full device
'pgadisable' - disable all processors for a numbered full device
'pgaidentify' - choose first processor of numbered full device
'pgaset' - choose first processor of numbered full device
Added API commands:
'procs'
'proc'
'proccount'
'procenable'
'procdisable'
'procidentify'
'procset'
Removed API commands:
'devdetail' - Use newer 'devdetails' for same information.
Modified API commands:
'devs' - display status of each full device only (not processors)
'pga' - lookup and display device by device (not processor) number
'pgacount' - count only full devices (not processors)
'pgaenable' - enable all processors for a numbered full device
'pgadisable' - disable all processors for a numbered full device
'pgaidentify' - choose first processor of numbered full device
'pgaset' - choose first processor of numbered full device
Added API commands:
'procs'
'proc'
'proccount'
'procenable'
'procdisable'
'procidentify'
'procset'
October 18, 2013, 03:24:29 PM
Luke-Jr:
Any reason why the extended-core information for BFL's (seeing all cores per Single, for example) went away from 3.2.90 to 3.3.0 via the API?
I used to get all 16 cores per single, now I see only summary information.
October 18, 2013, 09:36:15 AM
Luke-Jr, have you any idea if/when you'll be adding the stratum proxy module to the OpenWRT version of BFGMiner?
IIRC, it should be there in 3.3.0? 
October 18, 2013, 04:47:43 AM
Hello all! I recently compiled bfgminer on my linux box. It's an old machine with a quite outdated video card. I'm doing this strictly as a learning experience, not for profit. That being said, I created an account at 50BTC. I issued the command
and then it appeared that it logged on successfully. However, it produced no mining results. I hit the M option and then tried both auto and all options and both times No Device Found. I'd like it to use my old video card. What am I doing wrong? Any help would be much appreciated. Thank you!
Code:
./bfgminer -o http://pool.50btc.com:8332 -u (my email address) -p (my 50btc password)
and then it appeared that it logged on successfully. However, it produced no mining results. I hit the M option and then tried both auto and all options and both times No Device Found. I'd like it to use my old video card. What am I doing wrong? Any help would be much appreciated. Thank you!
3.3.0 turns off the GPU by default.
Edit:- turns off the GPU by default if asic is found.
Try your line:-./bfgminer -o http://pool.50btc.com:8332 -u (my email address) -p (my 50btc password) -S all
Take a look at the "read me" notes.
If your card is an older Nvidia then you will struggle.
is 50btc a getwork pool? 8332 is a getwork port. If it is stratum pool try 3333 instead.
October 18, 2013, 03:38:21 AM
Hello all! I recently compiled bfgminer on my linux box. It's an old machine with a quite outdated video card. I'm doing this strictly as a learning experience, not for profit. That being said, I created an account at 50BTC. I issued the command
and then it appeared that it logged on successfully. However, it produced no mining results. I hit the M option and then tried both auto and all options and both times No Device Found. I'd like it to use my old video card. What am I doing wrong? Any help would be much appreciated. Thank you!
Code:
./bfgminer -o http://pool.50btc.com:8332 -u (my email address) -p (my 50btc password)
and then it appeared that it logged on successfully. However, it produced no mining results. I hit the M option and then tried both auto and all options and both times No Device Found. I'd like it to use my old video card. What am I doing wrong? Any help would be much appreciated. Thank you!
3.3.0 turns off the GPU by default.
Edit:- turns off the GPU by default if asic is found.
Try your line:-./bfgminer -o http://pool.50btc.com:8332 -u (my email address) -p (my 50btc password) -S all
Take a look at the "read me" notes.
If your card is an older Nvidia then you will struggle.
October 18, 2013, 02:51:39 AM
Luke-Jr, have you any idea if/when you'll be adding the stratum proxy module to the OpenWRT version of BFGMiner?
October 17, 2013, 09:13:45 PM
Are others seeing this kind of error flood after a reboot with BFSB hardware?:
I can see the device/proc counter slowly increase in the top area. During 3-4 minutes the errors gradually stop, and all chips start working.
Code:
[2013-10-17 22:19:55] BSB 2af: bitfury_init_oldbuf: Giving up after 4 tries
[2013-10-17 22:19:55] BSB 2ag: bitfury_init_oldbuf: Giving up after 4 tries
[2013-10-17 22:19:55] BSB 2aj: bitfury_init_oldbuf: Giving up after 4 tries
[2013-10-17 22:19:55] BSB 2aw: bitfury_init_oldbuf: Giving up after 4 tries
[2013-10-17 22:19:55] BSB 1a: bitfury_init_oldbuf: Giving up after 4 tries
I can see the device/proc counter slowly increase in the top area. During 3-4 minutes the errors gradually stop, and all chips start working.
Not sure if this helps but i have noticed that if you go to far with the pencil mod ie up the voltage to much, it causes this to happen
Back the voltage off a bit and it goes away
Jump to: