[ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING*** - page 55.

goxed

legendary

Activity: 1946

Merit: 1006

Bitcoin / Crypto mining Hardware.

Code:

1 AIfDSo 56 2.777 2.558 194 0 0 0 242 [0:0] 1 12 12 12 12 13 13 12 12 12 12 12 12 12 12 12 12 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2 AIfDSo 55 2.477 2.494 173 1 0 0 236 [0:1] 37 11 11 11 11 11 10 10 11 11 11 11 11 11 10 11 11 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0
3 AIfDSo 54 2.334 2.452 163 3 0 0 232 [0:2] 38 11 11 11 11 11 10 10 10 10 10 10 9 10 10 9 10 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1
4 AIfDSo 56 2.620 2.336 183 1 0 0 221 [0:3] 2 12 11 11 11 11 11 11 11 11 12 11 12 12 12 12 12 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0
5 AIfDSo 54 2.520 2.632 176 12 0 0 249 [0:4] 1 10 11 11 12 11 11 9 12 12 11 11 11 11 12 11 10 1 0 0 0 1 1 3 0 0 1 1 1 1 0 1 1
6 AIfDSo 54 2.362 2.706 165 14 0 0 256 [0:5] 5 9 10 11 11 10 11 11 11 10 10 11 11 10 10 9 10 2 1 1 1 2 0 0 0 1 1 0 0 1 1 2 1
7 AIfDSo 55 2.033 2.759 142 26 0 0 261 [0:6] 36 8 9 9 8 8 8 9 10 10 8 10 9 10 9 11 6 2 1 1 2 2 2 1 1 1 3 1 2 1 2 0 4 speed down
8 AIfDSo 54 2.849 2.706 199 1 0 0 256 [0:7] 2 12 12 12 12 12 12 12 13 13 13 13 12 13 13 13 12 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0
9 AIfDSo 56 2.377 2.399 166 0 0 0 227 [0:8] 4 10 11 11 11 11 11 11 10 10 10 10 10 10 10 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
10 AIfDSo 56 2.448 2.399 171 0 0 0 227 [0:9] 6 10 10 10 11 11 11 11 11 11 11 11 11 11 11 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
11 AIfDSo 54 2.462 2.357 172 0 0 0 223 [0:A] 5 11 11 11 11 11 11 11 11 11 11 10 10 10 10 11 11 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed up
12 AIfDSo 54 2.248 2.378 157 0 0 0 225 [0:B] 26 10 10 10 10 10 10 10 10 10 10 10 10 10 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
13 AIfDSo 56 2.419 2.537 169 2 0 0 240 [0:C] 3 11 11 11 11 11 11 11 10 10 10 9 10 11 10 11 11 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0
14 AIfDSo 56 2.591 2.431 181 2 0 0 230 [0:D] 0 12 12 11 11 11 11 11 10 11 10 11 12 12 12 12 12 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0
15 AIfDSo 54 1.890 2.960 132 102 0 0 280 [0:E] 7 11 9 10 9 9 9 10 7 6 10 9 8 8 4 5 8 4 6 5 6 6 6 5 8 8 4 5 6 6 10 10 7
speed:824 noncerate[GH/s]:36.407 (2.427/chip) hashrate[GH/s]:38.104 good:2543 errors:164 spi-errors:0 miso-errors:0 jobs:375 (record[GH/s]:37.037)
0: 824 36.407 38.104 2543 164 0 0

Used a modded EOL card with 15 chips for this test. At 0.9V

greaterninja

hero member

Activity: 924

Merit: 1000

All of my avalons and bitfurys all stopped mining on us1.ghash.io:3333. I had to switch to nl1.ghash.io:3334 everything is working again now.

Doff

sr. member

Activity: 327

Merit: 250

Quote from: Lloydimiller4 on November 16, 2013, 10:31:46 PM

Quote from: Doff on November 16, 2013, 03:11:31 PM

Id love to have some updates about or maybe even a guide to Chainminer, my biggest issue is the lack of failover and how it provides so little info while running. Unless you check the logs on the PI its quite useless.

My miner stopped mining after ghash.io went down too. I have it pointed at btcguild right now, but I would still prefer to mine at ghash.io

What does the current setup in Chainminer provide? I know there are 3 spots to write your pool addresses in. Does that not have failover? Being able to failover to another pool seems absolutely necessary to have a long uptime.

As far as I am aware all the three pools does is split hashing power among the 3 pools. If you want to mine at ghash.io just use the nl1.ghash.io:3334 settings instead of us1.

Lloydimiller4

full member

Activity: 186

Merit: 100

Monero

Quote from: Doff on November 16, 2013, 03:11:31 PM

Id love to have some updates about or maybe even a guide to Chainminer, my biggest issue is the lack of failover and how it provides so little info while running. Unless you check the logs on the PI its quite useless.

My miner stopped mining after ghash.io went down too. I have it pointed at btcguild right now, but I would still prefer to mine at ghash.io

What does the current setup in Chainminer provide? I know there are 3 spots to write your pool addresses in. Does that not have failover? Being able to failover to another pool seems absolutely necessary to have a long uptime.

tom99

sr. member

Activity: 420

Merit: 250

Quote from: Morblias on November 16, 2013, 07:25:57 PM

Quote from: Luke-Jr on November 14, 2013, 01:17:13 PM

v1 M-boards can be fried if the software doesn't compensate.
I don't make any effort to compensate in BFGMiner.
Nobody has tested it, but I cannot recommend this combination.
Do so at your own risk...

Side note: I've never had problems with chainminer on Eligius... (via stratum proxy of course) O.o

Has anyone tried bfgminer with v1 m-boards? I would love to use bfgminer instead of chainminer, but am afraid it might fry my board.

bfgminer work good with V1 mboard but u need to mod code for it to work well.

you need to change 32 to 1" i < 1"

for (i = 0; i < 32; i++) {
      if (slot_on) {
         int chip_n;

         port = malloc(sizeof(*port));
         *port = *sys_spi;
         port->cgpu = &dummy_cgpu;
         port->txrx = bfsb_spi_txrx;
         port->speed = 625000;
         dummy_bitfury.slot = i;

then do compile it. please see back post 188 I think.

Asinine

member

Activity: 62

Merit: 10

Quote from: Keefe on November 16, 2013, 05:05:23 PM

Quote from: Asinine on November 16, 2013, 12:08:25 PM

Now that I got BFG running, I went through the voltages and adjusted them. The ones in the back ran away up to .88 and I trimmed them back down to .85-.87. I adjusted the ones in bank 0 up to .86. Bank 1 is at .83-.835. Bank 2 is at about .86.

You are now running the back cards at a much lower voltage than the front ones. Unless you accounted for the voltage rise on the ground plane from front to back of the M-board?

The voltage between the M-board's ground screw and the top of the inductor, will vary depending on how close that card is to the M-board's power input. But the chips only care about the voltage between the card's ground and power planes. The correct way to measure voltage is between the top of the inductor and the back of the card's VRM (the exposed silver pad). That will remain the same regardless of which slot the card is in (except for airflow and temperature affecting the VRM, trimpot, or pencil-modded resistor).

What do you mean by front?

I have yet to to much card shuffling. But, I am aware that the traces are not superconducting. I took it into account somewhat by putting the visually poorer quality cards further away from the terminals. They seem to run hot for the voltage anyway. Although, I suppose that could be inefficiency from the regulators working with the reduced voltage. Point being, they may be running at a lower voltage and have some of the slowest hash counts. But, they are also running the hottest, despite being given extra ventilation.

The pads are mostly covered by heat-sinks. Still, I plan on mounting a ring terminal with a lead to an alligator clip on the ground at the opposite end from the pci connector, so at least I have two different grounding points to measure from. The voltage drop should be somewhat linear, spherical chickens et al...

...

Updating, I went out this morning so I could get an 8 GB card to put the V2.5 Image on: Noncerate: 459.189GH/s - 441 W at the wall. So, I think I am at the point where it is just tweaking now. IE: upgrading to the v3 chainminer, tinkering with the voltages, and shuffling the weaker cards to the last slots of the groups.

Morblias

hero member

Activity: 576

Merit: 500

Quote from: Luke-Jr on November 14, 2013, 01:17:13 PM

v1 M-boards can be fried if the software doesn't compensate.
I don't make any effort to compensate in BFGMiner.
Nobody has tested it, but I cannot recommend this combination.
Do so at your own risk...

Side note: I've never had problems with chainminer on Eligius... (via stratum proxy of course) O.o

Has anyone tried bfgminer with v1 m-boards? I would love to use bfgminer instead of chainminer, but am afraid it might fry my board.

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: Keefe on November 16, 2013, 06:57:20 PM

Quote from: cypherdoc on November 16, 2013, 06:50:54 PM

Quote from: Bogart on November 16, 2013, 02:55:55 PM

Quote from: greaterninja on November 16, 2013, 02:20:06 PM

Last night my bitfury rig stopped mining on us1.ghash.io:3333 Specifically only my worker1 account.

Turns out my worker1 no longer mines on us1.ghash.io:3333.

it mines on nl1.ghash.io:3334[/b]

I ran into that same issue recently trying to mine on btcguild using the MPBM software.

It seems that not all mining software handles the stratum "client reconnect" message, where the pool asks the client to change hosts.

I'm guessing the included ChainMiner software also does not handle that message correctly.

(that's just a guess).

ok, this is weird.

i too am finding one of my miners won't mine on BTCGuild, Slush, or Ozcoin all of a sudden.

i think it's Chainminer.

What's chainminer doing?

Code:

sudo screen -r `sudo screen -r | grep -m1 Detached | cut -b2-7`

too late. i already rebooted.

something for sure though with cm.

i'm now back on the pool.

Keefe

hero member

Activity: 681

Merit: 500

Quote from: cypherdoc on November 16, 2013, 06:50:54 PM

Quote from: Bogart on November 16, 2013, 02:55:55 PM

Quote from: greaterninja on November 16, 2013, 02:20:06 PM

Last night my bitfury rig stopped mining on us1.ghash.io:3333 Specifically only my worker1 account.

Turns out my worker1 no longer mines on us1.ghash.io:3333.

it mines on nl1.ghash.io:3334[/b]

I ran into that same issue recently trying to mine on btcguild using the MPBM software.

It seems that not all mining software handles the stratum "client reconnect" message, where the pool asks the client to change hosts.

I'm guessing the included ChainMiner software also does not handle that message correctly.

(that's just a guess).

ok, this is weird.

i too am finding one of my miners won't mine on BTCGuild, Slush, or Ozcoin all of a sudden.

i think it's Chainminer.

What's chainminer doing?

Code:

sudo screen -r `sudo screen -r | grep -m1 Detached | cut -b2-7`

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: Bogart on November 16, 2013, 02:55:55 PM

Quote from: greaterninja on November 16, 2013, 02:20:06 PM

Last night my bitfury rig stopped mining on us1.ghash.io:3333 Specifically only my worker1 account.

Turns out my worker1 no longer mines on us1.ghash.io:3333.

it mines on nl1.ghash.io:3334[/b]

I ran into that same issue recently trying to mine on btcguild using the MPBM software.

It seems that not all mining software handles the stratum "client reconnect" message, where the pool asks the client to change hosts.

I'm guessing the included ChainMiner software also does not handle that message correctly.

(that's just a guess).

ok, this is weird.

i too am finding one of my miners won't mine on BTCGuild, Slush, or Ozcoin all of a sudden.

i think it's Chainminer.

tom99

sr. member

Activity: 420

Merit: 250

Quote from: Xian01 on November 16, 2013, 10:41:56 AM

Has anyone had success contacting sales re: RMA's ? Have been waiting on a response for an RMA on 3 bad h-cards Sad

RMA issues aside, these rigs are beasts once they are configured and placed in an environment with proper cooling ! The one full rig I have up and running has settled around 535 GHs !

yes, I did few weeks back for 2 hboards and I got replacement. I am now waiting for where to send back 2 bad hboards. You have to do rma at homesite and wait for someone to reply back to you.

goxed

legendary

Activity: 1946

Merit: 1006

Bitcoin / Crypto mining Hardware.

Quote from: Doff on November 16, 2013, 04:47:42 PM

Quote from: Bogart on November 16, 2013, 03:48:38 PM

I'm not a bitfury owner so I haven't been following the thread, but why is it that cgminer doesn't support the hardware?

Is it a closed design or something?

I couldn't say, I am talking with Kano currently about a version of Cgminer that supports Bitfury chips on Bitbuners V1 design, however it does not appear to work with the V3 miner. Kano posted about it in this thread back a few pages here https://bitcointalksearch.org/topic/m.3552824

If I remember correctly about 3 Months ago Con said something about it being a bit difficult to support the way it was designed to work with the RPI.

I think the problem Con mentioned was that you need root access on the rPI to get to the SPI bus that communicates with the ASICs.

Keefe

hero member

Activity: 681

Merit: 500

Quote from: cypherdoc on November 16, 2013, 02:23:13 PM

i haven't heard anybody talk about bad slots.

for instance, i have an m board where slots 1 & 3 in bank 1 appear to be dead. i've swapped multiple good h boards that previously were hashing @ 32-36 into these slots and they won't even boot up beyond 0. how do you deal with that?

another weird thing is, given those facts, why does Xian's strategy of swapping good cards to the front of the m board even work? does anyone understand the organizational structure of how voltage flows thru the 4 banks and 16 slots? Dave insinuated the concept of a bank doesn't apply for newer boards (v3 m boards) here:

"Don't pay attention to the Bank 1, Bank 2, etc. Those line up for V2 M-boards. The numbers of the slots do line up as 1-16 map to 1 - 9, A - F. There, you can see the output of each H-card."

https://bitcointalksearch.org/topic/us-bitfury-setup-guide-288109

Just forget about what Dave said there. V3 M-boards do have 4 banks of 4 slots each. If a chip or card is not forwarding messages properly, all chips after it within that bank will have a problem also. This is a communication issue. Power distribution is not chained like that; each card taps into the same power planes on the M-board, and each chip on a card taps into the same power planes on the card.

Here's the mapping from the slot numbers printed on the M-board and listed in the summary section of .stat.log, to the web interface:

M-board .stat.log	\|Web interface \|
0	\|Bank 1, slot 1
1	\|Bank 1, slot 2
2	\|Bank 1, slot 3
3	\|Bank 1, slot 4
4	\|Bank 2, slot 5
5	\|Bank 2, slot 6
6	\|Bank 2, slot 7
7	\|Bank 2, slot 8
8	\|Bank 3, slot 9
9	\|Bank 3, slot 10
A	\|Bank 3, slot 11
B	\|Bank 3, slot 12
C	\|Bank 4, slot 13
D	\|Bank 4, slot 14
E	\|Bank 4, slot 15
F	\|Bank 4, slot 16

(How can I put gridlines in a table in bbcode?)

Keefe

hero member

Activity: 681

Merit: 500

Quote from: cypherdoc on November 16, 2013, 01:41:58 PM

Quote from: Keefe on November 16, 2013, 03:01:40 AM

Quote from: Asinine on November 16, 2013, 01:03:16 AM

*Facepalm* Someone please tell me they have a copy of the Vanilla V3 image, or that one of the older ones works? I was shipped a blank SD card.

And, yes, I did have the sense to plug it into a PC to try to back it up prior to inserting it in the Pi.

Edit: Bah, V2 won't fit on the card and GandalfG's image, while booted, isn't generating any hashes. I don't know if it's my rig or not, yet.

Login with ssh and check what chainminer is doing:

Code:

sudo screen -r | grep -m1 Detached | cut -b2-7

i tried that command and got back a 4377..

what does that mean?

Oops, I left off an important part. Here's the complete command:

Code:

sudo screen -r `sudo screen -r | grep -m1 Detached | cut -b2-7`

Keefe

hero member

Activity: 681

Merit: 500

Quote from: Asinine on November 16, 2013, 12:08:25 PM

Now that I got BFG running, I went through the voltages and adjusted them. The ones in the back ran away up to .88 and I trimmed them back down to .85-.87. I adjusted the ones in bank 0 up to .86. Bank 1 is at .83-.835. Bank 2 is at about .86.

You are now running the back cards at a much lower voltage than the front ones. Unless you accounted for the voltage rise on the ground plane from front to back of the M-board?

The voltage between the M-board's ground screw and the top of the inductor, will vary depending on how close that card is to the M-board's power input. But the chips only care about the voltage between the card's ground and power planes. The correct way to measure voltage is between the top of the inductor and the back of the card's VRM (the exposed silver pad). That will remain the same regardless of which slot the card is in (except for airflow and temperature affecting the VRM, trimpot, or pencil-modded resistor).

Doff

sr. member

Activity: 327

Merit: 250

Quote from: Bogart on November 16, 2013, 03:48:38 PM

I'm not a bitfury owner so I haven't been following the thread, but why is it that cgminer doesn't support the hardware?

Is it a closed design or something?

I couldn't say, I am talking with Kano currently about a version of Cgminer that supports Bitfury chips on Bitbuners V1 design, however it does not appear to work with the V3 miner. Kano posted about it in this thread back a few pages here https://bitcointalksearch.org/topic/m.3552824

If I remember correctly about 3 Months ago Con said something about it being a bit difficult to support the way it was designed to work with the RPI.

Bogart

legendary

Activity: 966

Merit: 1000

I'm not a bitfury owner so I haven't been following the thread, but why is it that cgminer doesn't support the hardware?

Is it a closed design or something?

Doff

sr. member

Activity: 327

Merit: 250

Id love to have some updates about or maybe even a guide to Chainminer, my biggest issue is the lack of failover and how it provides so little info while running. Unless you check the logs on the PI its quite useless.

Doff

sr. member

Activity: 327

Merit: 250

Quote from: Bogart on November 16, 2013, 02:55:55 PM

Quote from: greaterninja on November 16, 2013, 02:20:06 PM

Last night my bitfury rig stopped mining on us1.ghash.io:3333 Specifically only my worker1 account.

Turns out my worker1 no longer mines on us1.ghash.io:3333.

it mines on nl1.ghash.io:3334[/b]

I ran into that same issue recently trying to mine on btcguild using the MPBM software.

It seems that not all mining software handles the stratum "client reconnect" message, where the pool asks the client to change hosts.

I'm guessing the included ChainMiner software also does not handle that message correctly.

(that's just a guess).

I noticed that cgminer was still using us1.ghash.io but non of the work was being registered on their site, so I had cgminer also switch to nl1. Even though it handled the switches something was still borked.

Bogart

legendary

Activity: 966

Merit: 1000

Quote from: greaterninja on November 16, 2013, 02:20:06 PM

Last night my bitfury rig stopped mining on us1.ghash.io:3333 Specifically only my worker1 account.

Turns out my worker1 no longer mines on us1.ghash.io:3333.

it mines on nl1.ghash.io:3334[/b]

I ran into that same issue recently trying to mine on btcguild using the MPBM software.

It seems that not all mining software handles the stratum "client reconnect" message, where the pool asks the client to change hosts.

I'm guessing the included ChainMiner software also does not handle that message correctly.

(that's just a guess).

Topic: [ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING*** - page 55. (Read 576798 times)

Topic: [ANN] US/North American Bitfury sales NEW STOCK NOW SHIPPING - page 55. (Read 576798 times)