OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 70.

angryrob

sr. member

Activity: 287

Merit: 250

Quote from: Luke-Jr on January 08, 2014, 02:17:43 PM

Quote from: angryrob on January 08, 2014, 02:04:08 PM

When running a windows terminal, how do you configure/disable the colors of the terminal?

I want to remove of the red background on the top line, remove the blue background on the second line, and change the top line font color to the default light-grey.

Basically I want the entire window to be a uniform black background and light grey text.

Not supported at this time.
What is the use case?

oh, it's just that I'm running bfgminer on my windows machine and I don't like the way it looks and wanted to change it.

maybe that's a config option that can be added in the future then... thanks for the quick reply.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: angryrob on January 08, 2014, 02:04:08 PM

When running a windows terminal, how do you configure/disable the colors of the terminal?

I want to remove of the red background on the top line, remove the blue background on the second line, and change the top line font color to the default light-grey.

Basically I want the entire window to be a uniform black background and light grey text.

Not supported at this time.
What is the use case?

angryrob

sr. member

Activity: 287

Merit: 250

When running a windows terminal, how do you configure/disable the colors of the terminal?

I want to remove of the red background on the top line, remove the blue background on the second line, and change the top line font color to the default light-grey.

Basically I want the entire window to be a uniform black background and light grey text.

dave111223

legendary

Activity: 1190

Merit: 1001

Quote from: Mudbankkeith on January 08, 2014, 06:18:12 AM

Quote from: dave111223 on January 08, 2014, 06:08:01 AM

Formatted the SDCard and USB drive and now working correctly. Corrupted filesystem seems to have been the problem.

I have 3 rPi in my system

Just one of them, occasionally corrupts the sd card when shutting down, the other 2 have behaved well up to now.
Its always worth having 1 or 2 spare cards formatted and ready to go.

My 3 rPi corrupted the SDCards so often (almost daily) that i had to switch them all to using USB thumbdrives from the OS; SDcard only for boot sector. After that they almost never corrupt (except for today Tongue

)

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: dave111223 on January 08, 2014, 06:08:01 AM

Formatted the SDCard and USB drive and now working correctly. Corrupted filesystem seems to have been the problem.

I have 3 rPi in my system

Just one of them, occasionally corrupts the sd card when shutting down, the other 2 have behaved well up to now.
Its always worth having 1 or 2 spare cards formatted and ready to go.

dave111223

legendary

Activity: 1190

Merit: 1001

Formatted the SDCard and USB drive and now working correctly. Corrupted filesystem seems to have been the problem.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: dave111223 on January 08, 2014, 04:22:19 AM

Having a weird problem.

On one Raspberry i've got about 35 antminters hooked up and running find.

On another Raspberry I cannot get it to detect any devices. Using -S antminer:all or -S all just saying:

Code:

NO DEVICES FOUND: Press 'M' and '+' to add

I installed bfgminer the exact same way on both raspberries.

Try swapping the sd cards

dave111223

legendary

Activity: 1190

Merit: 1001

Having a weird problem.

On one Raspberry i've got about 35 antminters hooked up and running find.

On another Raspberry I cannot get it to detect any devices. Using -S antminer:all or -S all just saying:

Code:

NO DEVICES FOUND: Press 'M' and '+' to add

I installed bfgminer the exact same way on both raspberries.

prehistoric

newbie

Activity: 18

Merit: 0

Quote from: Luke-Jr on January 07, 2014, 06:05:53 PM

Quote from: prehistoric on January 07, 2014, 05:50:46 PM

Quote from: Luke-Jr on January 07, 2014, 05:39:32 PM

Quote from: prehistoric on January 07, 2014, 05:34:39 PM

That's interesting, somehow bfgminer 3.9.0 or btcguild pool switched from worker's diff 8 to diff 16 with olddifficulty rejection message
...

Expected. There is a workaround for very old (no longer a problem?) pools that treated difficulty wrong. This results in invalid shares being submitted unnecessarily, but is otherwise harmless.

Seems strange, because bfgminer never lowers the diff, even if it is set to lower number in worker's property while mining. Can bfgminer only get worker difficulty correctly only at start?

It does, just not right away.
Essentially it works as lowest-of(job-difficulty, current-difficulty)

So (without understanding how exactly mining works) there is nothing to worry about this on-the-fly difficulty changing?

dave111223

legendary

Activity: 1190

Merit: 1001

Oh well, thanks for the driver, it's already running more reliably than cgminer. Got it running 27 on a Pi at the moment, cgminer would only handle about 20 before it crapped out. Will push it to the max later, see how many I can hook up.

Wish I knew how to code C so that i could help out with the overclocking.

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: dave111223 on January 08, 2014, 12:54:46 AM

Thanks working now.

Would overclocking them just involve tweaking this line in the driver?

Code:

#define ANTMINER_HASH_TIME 0.0000000029761

Or is there more to it than that?

No there is more to it than that. There are commands that must be sent to the device.

dave111223

legendary

Activity: 1190

Merit: 1001

Thanks working now.

Would overclocking them just involve tweaking this line in the driver?

Code:

#define ANTMINER_HASH_TIME 0.0000000029761

Or is there more to it than that?

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: dave111223 on January 08, 2014, 12:47:52 AM

Also they show as ICA0, ICA1, etc..not as "ANT 0, ANT 1" etc...

You have to run bfgminer with the -S antminer argument (e.g. -S antminer:all).

Also, make sure after cloning the repository you checked out the branch feature/antminer-u1-support.

You can check to see if bfgminer is compiled with AntMiner support by running bfgminer --help and looking at the list of drivers at the top.

dave111223

legendary

Activity: 1190

Merit: 1001

Quote from: nwoolls on January 07, 2014, 12:32:23 AM

Quote from: dave111223 on January 06, 2014, 10:49:17 AM

For some reason I am unable to make the antminer version of bfgminer, I get this on "make":

...

Also from looking at your driver code there does not appear to be any way to overclock the USBs?

Make sure you run autogen.sh first so that libblkmaker is pulled down from Git.

There's no options support at all right now. Still getting it stable and working but the options shouldn't be hard.

Ok, got it compiled, bfgminer runs, but devices are running way slow (ie 500-900MH/s)

Also they show as ICA0, ICA1, etc..not as "ANT 0, ANT 1" etc...

EDIT: needed to add commend "-S antminer:all" instead of just "-S all"

rmolby

member

Activity: 75

Merit: 10

Quote from: SpaceCadet on January 07, 2014, 10:31:35 PM

Quote from: nwoolls on January 07, 2014, 02:15:10 PM

Quote from: HellDiverUK on January 07, 2014, 01:56:40 PM

Any update on overclocking the Antminer U1?

Just going to need time. It's not difficult, just a lot on my plate (I have a day job and another side job outside of all this Bitcoin bidness Grin

)

I also want to try to figure out how to properly ID these buggers so I can tell them from BEs.

The good news is I got in touch with Bitmaintech and they are providing me with info to keep development going so that should be a great help.

Also interested in this. Currently running my BEs and U1s on separate machines to avoid the conflict and get the best performance from each (U1s running at about 1.9 Gh/s each using the '0981' freq setting). Of course, if I sell my BEs to a ~~suck~~, er, another miner and replace them with all U1s, then it's a moot point

Do you have to start the U1s one at a time with BFGMiner like I have to do with the ANT branch of cgminer (on a Win7 box)? Sure would be nice if they all just started like the BEs do!

The ANTminers act just like BEs when running nwoolls BFG390, so just have them plugged in and start BFG

SpaceCadet

full member

Activity: 165

Merit: 100

Just mining my own business...

Quote from: nwoolls on January 07, 2014, 02:15:10 PM

Quote from: HellDiverUK on January 07, 2014, 01:56:40 PM

Any update on overclocking the Antminer U1?

Just going to need time. It's not difficult, just a lot on my plate (I have a day job and another side job outside of all this Bitcoin bidness Grin

)

I also want to try to figure out how to properly ID these buggers so I can tell them from BEs.

The good news is I got in touch with Bitmaintech and they are providing me with info to keep development going so that should be a great help.

Also interested in this. Currently running my BEs and U1s on separate machines to avoid the conflict and get the best performance from each (U1s running at about 1.9 Gh/s each using the '0981' freq setting). Of course, if I sell my BEs to a ~~suck~~, er, another miner and replace them with all U1s, then it's a moot point

Do you have to start the U1s one at a time with BFGMiner like I have to do with the ANT branch of cgminer (on a Win7 box)? Sure would be nice if they all just started like the BEs do!

Question_is

newbie

Activity: 4

Merit: 0

BFGMiner : https://github.com/luke-jr/bfgminer
Where should I work to modify the sha256_nonce find code for CPU-64bit or GPU ?

I know that CPU and GPU mining is looked as: overcome by FPGA and Asics, but I want to
do that; in spite of all the odds.

I want to write my code for CPU-64bit or GPU mining, but I see that,
"sha256" and "nonce" are in all the following files below.
They are quite a lot. Probably there are files, with code for
different architectures.

Can someone suggest me the files that I have to work in ?

Thankyou anyway

------These files have "sha2" as text inside-------------
/driver-cpu.h
/sha2.c
/sha2.h
/libblkmaker/base58.c
/libblkmaker/private.h
/x86_32/Makefile.am
/x86_32/Makefile.in
/x86_32/sha256_xmm.asm
/x86_64/Makefile.am
/x86_64/Makefile.in
/x86_64/sha256_xmm_amd64.asm

-----These files have both "sha2" and "nonce" as text inside----------
/api.c
/diablo130302.cl
/driver-bitforce.c
/driver-cpu.c
/driver-ztex.c
/findnonce.c
/Makefile.am
/Makefile.in
/miner.c
/miner.h
/scrypt130511.cl
/scrypt.c
/sha256_4way.c
/sha256_altivec_4way.c
/sha256_cryptopp.c
/sha256_generic.c
/sha256_sse2_amd64.c
/sha256_sse2_i386.c
/sha256_sse4_amd64.c
/sha256_via.c
/util.c
/libblkmaker/blkmaker.c
/libblkmaker/blkmaker.h
/libblkmaker/example.c
/x86_64/sha256_sse4_amd64.asm

--------------------------------------------

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: rmolby on January 07, 2014, 05:50:12 PM

Quote from: rmolby on January 07, 2014, 10:12:36 AM

I noticed my BEs are running at less than 50 Mhash, I assume that is due to the Antminer configuration being pushed down on them despite of me running the following?

bfgminer.exe -Q 8 -L log.txt -S antminer:all -S erupter:all

Even though I only have two Antminers, I am mining at a slightly higher rate than with all the BEs (with 2 BEs removed to make room on one of the hubs)

OK, so I decided to use nwoolls Antminer version of BFG, and leave all the BEs unplugged, let AntBFG fire up and stabilize, then I plug in the hubs with the BEs and fire up BFG 3.2.8 (most stable with BEs on my system). Am now mining at full speed with all my mining gear

This is to be expected and I hope to find a way around it soon. Basically the AntMiner U1 design and implementation is very close to the Block Erupter. That is why there are issues in both cgminer and bfgminer when running both. Right now there is no way to determine the difference between the two in the code. I am glad you found a way to get it working. Another would be to use something like:

Code:

bfgminer -S antminer:/path/to/antminer -S erupter:/path/to/erupter

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: prehistoric on January 07, 2014, 05:50:46 PM

Quote from: Luke-Jr on January 07, 2014, 05:39:32 PM

Quote from: prehistoric on January 07, 2014, 05:34:39 PM

That's interesting, somehow bfgminer 3.9.0 or btcguild pool switched from worker's diff 8 to diff 16 with olddifficulty rejection message
...

Expected. There is a workaround for very old (no longer a problem?) pools that treated difficulty wrong. This results in invalid shares being submitted unnecessarily, but is otherwise harmless.

Seems strange, because bfgminer never lowers the diff, even if it is set to lower number in worker's property while mining. Can bfgminer only get worker difficulty correctly only at start?

It does, just not right away.
Essentially it works as lowest-of(job-difficulty, current-difficulty)

prehistoric

newbie

Activity: 18

Merit: 0

Quote from: Luke-Jr on January 07, 2014, 05:39:32 PM

Quote from: prehistoric on January 07, 2014, 05:34:39 PM

That's interesting, somehow bfgminer 3.9.0 or btcguild pool switched from worker's diff 8 to diff 16 with olddifficulty rejection message
...

Expected. There is a workaround for very old (no longer a problem?) pools that treated difficulty wrong. This results in invalid shares being submitted unnecessarily, but is otherwise harmless.

Seems strange, because bfgminer never lowers the diff, even if it is set to lower number in worker's property while mining. Can bfgminer only get worker difficulty correctly only at start?

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