|
Duplicate shares are fairly normal in the beginning, when the chips aren't initialized yet, but they should stop after a minute or so. Are you only getting them on one device and not the other ? If so, does it also happen when you only plug in one ?
What temperature are the devices running at ? I also added a temperature switch at 90 deg C. Above that temp, the bitfury chips are turned off.
|
|
|
|
I tried downloading the firmware from the support site, and I can reproduce the slow miner problem. I've uploaded a fix here: http://c-scape.nl/bi-fury/firmware.bin(the problem is that the new firmware sets the Bitfury ASIC clock speed at a very low level, and waits for the miner to adjust it. I've changed that to have it initialize at the old level, after which the miner can adjust it if necessary). I recommend only people with problems try the new firmware, until it is confirmed that it works. If you don't have a problem right now, just wait.. |
|
|
|
|
In the latest firmware, the red LED flashes every time the card has found a share that meets the difficulty.
|
|
|
|
I run 1.0.3 and seem to have higher hash rates:
That's because you got the board from me, not Technobit, so it has different chips and different voltage. |
|
|
|
Does anyone know how to change the pool management strategy on these? They seem to switch pools somewhat randomly
What firmware version are you using ? Some versions didn't have very good pool management. Latest version (0.1.10) works a lot better. |
|
|
|
Thanks - I downloaded the rpi image and had a play with spitest-D
Has anyone else seen their chips go into a mode where the in_miso pin starts oscillating very slowly - e.g. about 1Hz, even when the SPI clock isn't running?
My guess is that the MISO pin keeps showing the last bit that you read (or the one after that). In the case of normal miner operation, that would be the register that indicates the job it is working on, which toggles between 1 and 0 every 2^22 clock cycles. |
|
|
|
When you touch it with a wet finger and you hear a
hissing sound, you know it's >= 100 oC:)
Or if you touch it with a dry finger and you hear a hissing sound.... Anyway, I'm working on some auto protect feature for the Bi•Fury firmware that shuts down the ASICs when they get too hot. |
|
|
|
|
Why is the exchange rate so bad ? For instance, I see 1 oz gold for 1006 EUR, or 2.89 BTC, which means an exchange rate of 348 EUR/BTC.
At the same time, the bitpay rate is 492 EUR/BTC.
|
|
|
|
Bitcoin network hashrate is 5*10^15 ~ 2^52. So in 2^28 seconds (8 years) we'll reach this number. Doesn't look too large. And this is without the Moore's law.
It's also without consideration that mining hardware cannot be used for finding duplicates. |
|
|
|
|
If the boards run cool, it's probably a good idea to increase regulator voltage a bit. This can be done by using a lower value resistor for R01T (next to power regulator module).
|
|
|
|
U can generate addresses much faster coz u don't need to know the private key. Pick any set of bytes and say it's a public key. 2^80 is not a big number.
Edit:
2^80 == (2^10)^8 ~ 1000^8 == 10^24.
And now look at the hash rate of Bitcoin network.
Of course, when a normal miner checks a hash, it starts by checking the top 32 bits are zero, which is a trivial operation. Checking for a collision with a growing database of up to 2^80 previous hashes is a lot more effort. |
|
|
|
Just wanted to make note here that Eligius is the first pool to tentatively adopt a patch to our mining node to help deter address reuse.
...
This is experimental, has no real effect on miners or earnings, etc, and will be adjusted as needed as the patches evolve from here on.
If it has no real effect, what exactly is the deterrent ? |
|
|
|
It will be interesting to see how it performs with the power limitations of USB. Worth a keeping an eye out for any similar implementations at a more reaslistic price if it proves successful. I'd consider a more realistic price to be in the region of €100 (looking at techno's costs for singles).
When overclocked, it uses more than 500 mA, so it can't be powered from a standard USB 2.0 connector. You need USB 3.0, or special hub with external power. It can be underclocked, though, and I've seen mine do about 4GH/sec on a 500 mA budget. |
|
|
|
|
There's no harm in filling in the same pool more than once.
|
|
|
|
That LED indicates data on the USB interface, and is only valid when the USB cable is plugged in. It's not important for hashing. |
|
|
|
You can get debug information from the S-HASH board by connecting USB connector to a PC. You'll need a PC driver for virtual COM port for FT230x. If you have Win7, the OS will get the driver automatically (just wait a few minutes). Otherwise you can download driver from manufacturer: http://www.ftdichip.com/Drivers/VCP.htmAfter installing driver, download TeraTerm program: http://logmett.com/index.php?/download/tera-term-479-freeware.htmlIn TeraTerm, open serial connection to USB virtual COM port from S-HASH, and set baudrate to 115200. Reset the board, and you should get debug information in Teraterm screen. Paste the output to forum (if not too long), or PM to me. |
|
|
|
|
It's not based on Red/Blue fury, but an independently designed product. It's faster because it uses 2 ASICs.
|
|
|
|
|
That's a screenshot of the pool (BTC Guild), so it's the rate of accepted shares.
|
|
|
|
I want to be able to go to the person I have designing it and tell them which parts I would need to be included in the print for the board. I think this would save him time and money on designing. On the contrary. It is much better to find a competent designer, and tell him what you want to end up with. Picking the right parts is his job, and the more freedom the designer has, the better the design. |
|
|
|
|
Nee, is ook niet echt erg. En de bitcoins die ik nog over heb stijgen net zo hard mee.
|
|
|
|
|
Show Posts
