[ANN] Bitfury ASIC sales in EU and Europe - page 71.

darkfriend77

sr. member

Activity: 434

Merit: 265

Quote from: dani on September 05, 2013, 04:20:18 PM

Quote from: darkfriend77 on September 05, 2013, 03:35:09 PM

Quote from: Isokivi on September 05, 2013, 03:21:31 PM

I collected 68 5-minute samples of temperature, noncerate and errors yesterday and concluded that I should have enough data to reach a conclusion of some sort. But was too tired to analyse it right away. After a good night sleep I got to it. The highest measured temperature was 48.6c and the lowest measured temperature was 25.5c

To be honest after pondering over the results for a long time it would appear I've come up with a fairly decent rng.

The only concution I can reach that the boards would seem to appear to operate optimally when the air between them is 25-35c.

Hmm ... are you measuring the air ... I have my temp meter on the backside of the h-board ... they get around 60° with out fans .... gona do some testing too ...

Did you attach it directly to the backside? Is it made of metal (is it conductive)? Should be no problem aslong as you don't short some of the tin holes on the back, right?

i haven't had an issue ... right now ...

dani

hero member

Activity: 525

Merit: 500

..yeah

Quote from: darkfriend77 on September 05, 2013, 03:35:09 PM

Quote from: Isokivi on September 05, 2013, 03:21:31 PM

I collected 68 5-minute samples of temperature, noncerate and errors yesterday and concluded that I should have enough data to reach a conclusion of some sort. But was too tired to analyse it right away. After a good night sleep I got to it. The highest measured temperature was 48.6c and the lowest measured temperature was 25.5c

To be honest after pondering over the results for a long time it would appear I've come up with a fairly decent rng.

The only concution I can reach that the boards would seem to appear to operate optimally when the air between them is 25-35c.

Hmm ... are you measuring the air ... I have my temp meter on the backside of the h-board ... they get around 60° with out fans .... gona do some testing too ...

Did you attach it directly to the backside? Is it made of metal (is it conductive)? Should be no problem aslong as you don't short some of the tin holes on the back, right?

juhakall

sr. member

Activity: 658

Merit: 250

Quote from: eleuthria on September 05, 2013, 03:11:14 PM

BTC Guild has now deployed a workaround for the reverse auth/subscribe order in slush's Stratum Mining Proxy to prevent it from spamming low difficulty shares when a worker has a pre-set starting difficulty.

Thanks! I set my minimum difficulty back to 32 and restarted the proxy, working correctly now.

darkfriend77

sr. member

Activity: 434

Merit: 265

Quote from: Isokivi on September 05, 2013, 03:21:31 PM

I collected 68 5-minute samples of temperature, noncerate and errors yesterday and concluded that I should have enough data to reach a conclusion of some sort. But was too tired to analyse it right away. After a good night sleep I got to it. The highest measured temperature was 48.6c and the lowest measured temperature was 25.5c

To be honest after pondering over the results for a long time it would appear I've come up with a fairly decent rng.

The only concution I can reach that the boards would seem to appear to operate optimally when the air between them is 25-35c.

Hmm ... are you measuring the air ... I have my temp meter on the backside of the h-board ... they get around 60° with out fans .... gona do some testing too ...

klondike_bar

legendary

Activity: 2128

Merit: 1005

ASIC Wannabe

Quote from: -Redacted- on September 05, 2013, 01:22:58 PM

How can you say Slush doesn't still care? I prepaid for a Trezor months ago. Oh, well, I mean, when I mine on his pool we only get a couple of invalids or bad block reward calculations per day.... Usually... When the servers aren't down... Maybe he just lost his BitcoinTalk password ??

Errrrrrmm. Never mind...

so is this to say i *should not* use slush's pool? I am using it now for an FPGA with no issues, but obviously i will want to squeeze every drop from my bitfury

Isokivi

hero member

Activity: 910

Merit: 1000

Items flashing here available at btctrinkets.com

I collected 68 5-minute samples of temperature, noncerate and errors yesterday and concluded that I should have enough data to reach a conclusion of some sort. But was too tired to analyse it right away. After a good night sleep I got to it. The highest measured temperature was 48.6c and the lowest measured temperature was 25.5c

To be honest after pondering over the results for a long time it would appear I've come up with a fairly decent rng.

The only concution I can reach that the boards would seem to appear to operate optimally when the air between them is 25-35c.

pbigmoon

newbie

Activity: 59

Merit: 0

punin

When an order is placed and paid via bitpay does it go to processing automatically after so many confirmations?

Only asking as it took a few hours for the first confirmation (usually only takes 10 or so mins) and the order is still on hold.

eleuthria

legendary

Activity: 1750

Merit: 1007

BTC Guild has now deployed a workaround for the reverse auth/subscribe order in slush's Stratum Mining Proxy to prevent it from spamming low difficulty shares when a worker has a pre-set starting difficulty.

-Redacted-

hero member

Activity: 574

Merit: 501

How can you say Slush doesn't still care? I prepaid for a Trezor months ago. Oh, well, I mean, when I mine on his pool we only get a couple of invalids or bad block reward calculations per day.... Usually... When the servers aren't down... Maybe he just lost his BitcoinTalk password ??

Errrrrrmm. Never mind...

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: ssi on September 05, 2013, 12:28:21 PM

Quote from: eleuthria on September 05, 2013, 12:24:47 PM

There's a protocol implementation error in the official Stratum proxy. The original spec always stated the first message a pool should be receiving is a mining.subscribe method. However, if you try to make the Stratum Proxy do the authorization (-cu -cp args), it sends those *before* the subscribe method. As a result, you're getting your difficulty set to 2/4/8/etc before the "default subscribe response" is sent. A workaround is being added to the BTC Guild stratum code today to hopefully prevent this mixup.

Would it be potentially easier just to fix the error in the proxy?

The problem is, fixing the error in the proxy would require slush to actually still care about mining. He hasn't been seen on bitcointalk in months. Additionally, it'd require every user to upgrade to a forked proxy that fixes the problem. It's much easier to just make the pool workaround the broken proxy rather than hope everybody else upgrades.

The error is only related to minimum difficulty though. If you have your minimum difficulty set to 1, it will work just fine, and vardiff will adjust your difficulty as needed.

vulgartrendkill

hero member

Activity: 518

Merit: 500

Quote from: -Redacted- on September 05, 2013, 12:55:10 PM

Hey spiccioli - go get your hashing card fixed and stop giving away secrets like that.... Tongue

Word will get around that people make lots of coins on HHTT and it will get too big...

uhuh

nice

*switches pools*

-Redacted-

hero member

Activity: 574

Merit: 501

Hey spiccioli - go get your hashing card fixed and stop giving away secrets like that.... Tongue

Word will get around that people make lots of coins on HHTT and it will get too big...

spiccioli

legendary

Activity: 1379

Merit: 1003

nec sine labore

Quote from: ssi on September 05, 2013, 12:15:45 PM

Quote from: juhakall on September 05, 2013, 12:13:47 PM

Quote from: darkfriend77 on September 05, 2013, 11:52:25 AM

I had a similar issue ... somehow if I use load balanced mining .... with 40-42GH on 3 pools im getting 13GH at BTCGuild ... 13GH .... at eligius ... and 12 GH at Bitminter ...

if I change to mine 100% on BTCGuild it shows me 20-30 GH only .... i tryed with 16,32 & 64 diff

You could be having a different issue, but I noticed the stratum proxy is behaving strangely with BTC Guild. If my minimum worker difficulty is set to 1, the proxy correctly picks up when the difficulty quickly increases, and doesn't try to send shares which don't meet the requirement. However, if I set the minimum difficulty so high that it never has to be increased, the proxy keeps on thinking that the target is diff 1, and sends every share to the pool. Obviously most of them get rejected, and this might even overload a router.

I had this issue as well... I had my difficulty set at 8 in btcguild, I only have 18GH. Stratum proxy would send everything back at diff 1, and none of them were accepted. I set my min difficulty to 1 in btcguild, and now it negotiates its way up to 8.

Hashing comrades!

HHTT works flawlessly and needs your hashing power a lot more than BTCGuild which is already the largest pool on Earth!

Roll Eyes

spiccioli

CryptoCluster

member

Activity: 84

Merit: 10

Hmmm. Another issue. I have disabled Autotune for all chips. I run miner with console output. And suddenly, after processing 800-1000 jobs, miner prints "SPI update chip xxx", and my Noncerate starts dropping drastically... If I check /run/shm/.stat.log chips have aIFDSo parameters.
How is it possible?

ssi

member

Activity: 70

Merit: 10

Quote from: eleuthria on September 05, 2013, 12:24:47 PM

There's a protocol implementation error in the official Stratum proxy. The original spec always stated the first message a pool should be receiving is a mining.subscribe method. However, if you try to make the Stratum Proxy do the authorization (-cu -cp args), it sends those *before* the subscribe method. As a result, you're getting your difficulty set to 2/4/8/etc before the "default subscribe response" is sent. A workaround is being added to the BTC Guild stratum code today to hopefully prevent this mixup.

Would it be potentially easier just to fix the error in the proxy?

eleuthria

legendary

Activity: 1750

Merit: 1007

There's a protocol implementation error in the official Stratum proxy. The original spec always stated the first message a pool should be receiving is a mining.subscribe method. However, if you try to make the Stratum Proxy do the authorization (-cu -cp args), it sends those *before* the subscribe method. As a result, you're getting your difficulty set to 2/4/8/etc before the "default subscribe response" is sent. A workaround is being added to the BTC Guild stratum code today to hopefully prevent this mixup.

MXRider

sr. member

Activity: 466

Merit: 250

Quote from: darkfriend77 on September 05, 2013, 11:52:25 AM

I had a similar issue ... somehow if I use load balanced mining .... with 40-42GH on 3 pools im getting 13GH at BTCGuild ... 13GH .... at eligius ... and 12 GH at Bitminter ...

if I change to mine 100% on BTCGuild it shows me 20-30 GH only .... i tryed with 16,32 & 64 diff

What shows? BTCGuild or the miner's web GUI? Check /run/shm/.putstat.log file. First number on each row is the amount of queued work. It should be zero. I had problems with BTCGuild. EMC works perfectly.

ssi

member

Activity: 70

Merit: 10

Quote from: juhakall on September 05, 2013, 12:13:47 PM

Quote from: darkfriend77 on September 05, 2013, 11:52:25 AM

I had a similar issue ... somehow if I use load balanced mining .... with 40-42GH on 3 pools im getting 13GH at BTCGuild ... 13GH .... at eligius ... and 12 GH at Bitminter ...

if I change to mine 100% on BTCGuild it shows me 20-30 GH only .... i tryed with 16,32 & 64 diff

You could be having a different issue, but I noticed the stratum proxy is behaving strangely with BTC Guild. If my minimum worker difficulty is set to 1, the proxy correctly picks up when the difficulty quickly increases, and doesn't try to send shares which don't meet the requirement. However, if I set the minimum difficulty so high that it never has to be increased, the proxy keeps on thinking that the target is diff 1, and sends every share to the pool. Obviously most of them get rejected, and this might even overload a router.

I had this issue as well... I had my difficulty set at 8 in btcguild, I only have 18GH. Stratum proxy would send everything back at diff 1, and none of them were accepted. I set my min difficulty to 1 in btcguild, and now it negotiates its way up to 8.

rammy2k2

legendary

Activity: 1974

Merit: 1003

Tomorrow ill receive my starter kit Grin

Soon ill order a board with Oct delivery

I hope i wont have any major issues with the kit, will keep u guys updated

juhakall

sr. member

Activity: 658

Merit: 250

Quote from: darkfriend77 on September 05, 2013, 11:52:25 AM

I had a similar issue ... somehow if I use load balanced mining .... with 40-42GH on 3 pools im getting 13GH at BTCGuild ... 13GH .... at eligius ... and 12 GH at Bitminter ...

if I change to mine 100% on BTCGuild it shows me 20-30 GH only .... i tryed with 16,32 & 64 diff

You could be having a different issue, but I noticed the stratum proxy is behaving strangely with BTC Guild. If my minimum worker difficulty is set to 1, the proxy correctly picks up when the difficulty quickly increases, and doesn't try to send shares which don't meet the requirement. However, if I set the minimum difficulty so high that it never has to be increased by the pool, the proxy keeps on thinking that the target is diff 1, and sends every share to the pool. Obviously most of them get rejected, and this might even overload a router.

I didn't have any actual problems with this, though. BTC Guild always reported my full hashrate, even when I was flooding it with tons of rejected shares. Of course flooding the server isn't exactly nice for the pool OP

Topic: [ANN] Bitfury ASIC sales in EU and Europe - page 71. (Read 250482 times)