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

dani, did you try other pools/difficulties?

Hi,
Niko
I've send you a few Emails asking about bulk chip order prices.
Is there any problem ?

You are right, but I also look at pool stats. here you can see my units hashing. http://eligius.st/~wizkid057/newstats/userstats.php/14cbUKDLpZPJUMfr3DcKWZXmiaQRYpaZbd
the speed right now is clearly too low. same happend yesterday evening and for a shorter period yesterday afternoon, as you can see. The spike going to 80+ was a 2nd unit hashing on the same adress, so you can ignore that

Edit:
I set the last 60gh-setting to best.cnf and rebooted, for now its at 58+ slowly reaching 60 as before. I don't see why it performs like this sometimes, there are no chips turned off (besides the ones that are always off, dead chips) at the time of bad slow hashing. It's just that every card starts to perform bad/slow

Please note that your looking at a 5-minute sample, seems like normal variance to me. Does you pool have any stats you could use, with longer intervals ?

What is wrong with my cards? It sometimes drops speed from 60-62 to 50 and sometimes even lower (right now its down to 40). Everything seemed fine, I switched everything back to autotune because the results were more or less the same. Stop/start doesnt help. Before restart I saw in putstat log instead of 0 qeued work numbers between 1 and 10, switchen positions randomly. After a restart it's back to:

0 1343 47 47

• http://127.0.0.1:8332/

0 1323 39 39 [1]http://127.0.0.1:8333/
0 1330 51 51 [2]http://127.0.0.1:8334/

any thoughts?

Do you want to mine? If yes, it is.
If you are for the quick buck, probably not. Buy BTC instead.

Only slot one of a bank though...
If I plug it into another in the same bank it wont run...
I have a card in bank 2,1 running happily at 24ghs, so aint touching that one lol

http://mining.thegenesisblock.com/a/f7ffb1dbca

so is it a good deal ?

-30 BTC...

you can try other slots too. Check that it plugs totally even.

Try to set Autotune off for whole card, and all chips speed to 54. Let them run for an hour then check .stat.log. You can also try setting whole card speed for 55 and 56. And pick the best results (after one hour test).

It helped with my poor performing hcards.

damn...

Is there anyway other than a reboot to get them restarted...

The hash for a bit, and get valid shares etc, but error rate seems higher than software likes...
Id rather have high errors and a few shares, than no errors and no shares tbh

I fear not, I went as low as 45, but after a while they stop hashing with or without autotuning, at least in my worst card.

spiccioli

tried 2 slots...bank 1,1 and bank 3,1
Checked for solder defects too...not seeing any

I would try it in a different slot and check for a firm seating.

One of my boards drops to ~10ghs
The chips turn off...anyone got any suggestions on getting a bit more out of it ?

Is it worth turning auto-tune off on those chips and setting them to 52 or something ?

ChipID is made up by board number 0-F and chip number 0-F they're expressed in hexadecimal notation.

spiccioli

The putstat.log seems to be constantly changing, for me it sits at 0 or 1 most of the time, but I have seen it as high as 40. I suppose the solution to this is to try out different pools, but I personally didnt bother moving: 1% fees and sub 0,1% rejects dont justify running to a pool with higher fees for me.

Great answers! Thanks, Isokivi!

I think the only one you missed is E)
Oh, and on G) having 3 or a 9 value in the .putstat file, is that too small to be concerned or too bad? what's a reasonable range to have?   Also, Dave said that pools are parallel and not failover, do you have a sample file on how to format the pool file. I'm just accessing the rPI IP per as Dave recommendation but would love how to edit the file directly. The current pool file location provided by Punin in my SD card is empty so not sure if there are 2 files managing pools in my SD.

A) In my posts and testing I have been assessing errors in general, I havent seen a large number of SPI or Miso errors at any point and havent seen changes in it.
B) I've been looking at errors on a chip by chip basis when tweaking the speeds.
C) the stat.log is a log thats being rewritten every 5 minutes, the best.log is the best results that autotune has reached. I started off by copying the best.log to /opt/bitfury/best.cnf, which is loaded when the miner starts.
D) Yes.
F) The boards with the most Miso errors should be the last ones on the 4-slot bus so they do not interfere with better boards.
G) You appear to have one pool in the configuration now and it's the top one.

When people talk about fixing "errors":

  A) Do they mean SPI or Miso-Errors?? Other errors??
  B) Do they mean the errors shown at the bottom summary section of the log or in the upper, detail section of the log at the individual chip level??
  C1) Do they mean looking at this file ---> /tmp/.best.log or at this file --> /run/shm/.stat.log ??  C2) What's the difference between these 2 files?
  D) Is this the file that ultimately needs to be manually edited --> /opt/bitfury/best.cnf ??
  E) When I look at the file /tmp/.best.log, one of the chips I'm looking has this ChipID: "[E:F]"  , what the heck does that mean? My board is numbered from 0-16 (I have m-board v1.0) and even if it was m-board v2.0, why is the second part of the ChipID a letter and not a number??
  F) How do I fix each of the errors individually? Just by changing speed/auto-tunning and/or relocating boards? Which change fixes which errors?
  G) Punin said to verify that the queue size in /run/shm/.putstat.log to be zero. However, my file (see below) has 3 records/values (3, 0, 0)  which one should I look at, only the last one??

Queue length   Getworks         Nonces found      Nonces submitted        Server IP

Many thanks for clarifying these questions!!! I'm sure I'm not the only one trying to piece together all these little details..