Pages:
Author

Topic: [Work in progess] Burnins Avalon Chip to mining board service - page 67. (Read 624200 times)

hero member
Activity: 700
Merit: 500
I'm mining at BTCGuild right now and noticed quite a difference between local hashrate (as reported by cgminer) and the estimated speed at BTCGuild.
cgminer reports 128.9 GH/s on average, while BtCGuild reports 106.7 GH/s.
Is this difference within usual ranges?
legendary
Activity: 2674
Merit: 1083
Legendary Escrow Service - Tip Jar in Profile
Burnin did some OC tests already and it looks like you'll need 1.34V to run at 450Mhz.

https://bitcointalksearch.org/topic/m.2745262

Quote
And i have some numbers to go with those from yesterday:
Slightly different air cooling setup therefore different temperatures with air cooling. (fan placement)
TL;DL : 450Mhz [9Ghash/s] - STABLE
But at the cost of 94Watts of power.

Air:
431 - 54, 48, 1.30V, 87W, stable
450 - 56, 48, 1.30V, 90W, HW Errors
450 - 57, 52, 1.34V, 94W, slightly increased error rate compared to what i normally call "stable" but close enough

Water:
450 - 54, 32, 1.34V, 94W, slightly less hw errors then with air

I know, but when i would test out the real limits i would lose not a few money. Burnin has the possibility to do this for a low price and when we donate for this test he maybe is willing to do it. Of course he would need a recompiled cgminer then.
hero member
Activity: 700
Merit: 500
I set up team "BitBurner" on BTCGuild – feel free to join.
Need PIN
Sorry, just removed the PIN. Please try again.
hero member
Activity: 700
Merit: 500
I set up team "BitBurner" on BTCGuild – feel free to join.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
I set the limit to 1.31 since I was thinking that 1.28 was the normal limit to use ... I can't remember why Tongue

burnin what would you say people shouldn't go above?

(i.e. I'll set that limit in cgminer and if anyone wants to destroy their board they can just recompile with a higher limit)

Can you put it up to 1.35 instead and give out some kind of warning or make the default option not take values above 1.3 and have a separate option that takes values above that and stating higher risk of stuff being broken?
No, I'm not adding another option.
The limits will be the expected, non-destructive limits, and, as I said, if you want to exceed them, simply recompile cgminer.
At the moment, if you do a java API "ascset|0,help" then it will tell you the limits also.
Having those defined means people will know what they can use.
... the more adventurous, or those who don't care if it destroys their hardware, simply edit and recompile, it's very simple to compile cgminer ... and we even include the details how to Smiley
full member
Activity: 154
Merit: 100
I set the limit to 1.31 since I was thinking that 1.28 was the normal limit to use ... I can't remember why Tongue

burnin what would you say people shouldn't go above?

(i.e. I'll set that limit in cgminer and if anyone wants to destroy their board they can just recompile with a higher limit)

Can you put it up to 1.35 instead and give out some kind of warning or make the default option not take values above 1.3 and have a separate option that takes values above that and stating higher risk of stuff being broken?
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
I set the limit to 1.31 since I was thinking that 1.28 was the normal limit to use ... I can't remember why Tongue

burnin what would you say people shouldn't go above?

(i.e. I'll set that limit in cgminer and if anyone wants to destroy their board they can just recompile with a higher limit)
legendary
Activity: 1062
Merit: 1003
Burnin did some OC tests already and it looks like you'll need 1.34V to run at 450Mhz.

https://bitcointalksearch.org/topic/m.2745262

Quote
And i have some numbers to go with those from yesterday:
Slightly different air cooling setup therefore different temperatures with air cooling. (fan placement)
TL;DL : 450Mhz [9Ghash/s] - STABLE
But at the cost of 94Watts of power.

Air:
431 - 54, 48, 1.30V, 87W, stable
450 - 56, 48, 1.30V, 90W, HW Errors
450 - 57, 52, 1.34V, 94W, slightly increased error rate compared to what i normally call "stable" but close enough

Water:
450 - 54, 32, 1.34V, 94W, slightly less hw errors then with air

Does cgminer allow this voltage?  It seems the best/only way to deal with the errors experienced at 400+ MHz.
newbie
Activity: 11
Merit: 0
Burnin did some OC tests already and it looks like you'll need 1.34V to run at 450Mhz.

https://bitcointalksearch.org/topic/m.2745262

Quote
And i have some numbers to go with those from yesterday:
Slightly different air cooling setup therefore different temperatures with air cooling. (fan placement)
TL;DL : 450Mhz [9Ghash/s] - STABLE
But at the cost of 94Watts of power.

Air:
431 - 54, 48, 1.30V, 87W, stable
450 - 56, 48, 1.30V, 90W, HW Errors
450 - 57, 52, 1.34V, 94W, slightly increased error rate compared to what i normally call "stable" but close enough

Water:
450 - 54, 32, 1.34V, 94W, slightly less hw errors then with air
legendary
Activity: 2674
Merit: 1083
Legendary Escrow Service - Tip Jar in Profile

I believe burnin wrote 1.5V is a sure way to kill the chips. I wonder what is the max. I want to find out but dont like to risk the chips too much too... im not sure if it could be found out safely. The only way i can think of is to use only one miner for the test but that doesnt say anything about longer runtimes.


The way to do this is to pay burnin to make a board with only 1 or 2 chips on it, and to ramp it up.  Keep it at each step an hour or two.  Keep a database of voltage, frequency, HW, and hashrate.

If I ran the test on my chips, I would set it as 400 MHz or whatever the max spec is, and run the voltage up and plot HW & hashrate.  I would stay inside the design spec on this test.

So ... the thing is to get a quote from burnin to run the test, set a pay-to address, and when enough money is there, those are the people who learn the results...

Thats an idea... i would contribute to such test since burnin has the ability to do this relatively cheap to find the result. When i want to go above 440MHz i need to go higher thatn 1310mV. Thats not possible with standard cgminer so a special cgminer is needed where the constants are changed to allow higher voltage.
Burnin? Can you do such test?

The only risk then remains is hot environments that could break the chips and that the chips then might only run for some weeks. But one could go a bit under he breaking values...
legendary
Activity: 1246
Merit: 1002

I believe burnin wrote 1.5V is a sure way to kill the chips. I wonder what is the max. I want to find out but dont like to risk the chips too much too... im not sure if it could be found out safely. The only way i can think of is to use only one miner for the test but that doesnt say anything about longer runtimes.


The way to do this is to pay burnin to make a board with only 1 or 2 chips on it, and to ramp it up.  Keep it at each step an hour or two.  Keep a database of voltage, frequency, HW, and hashrate.

If I ran the test on my chips, I would set it as 400 MHz or whatever the max spec is, and run the voltage up and plot HW & hashrate.  I would stay inside the design spec on this test.

So ... the thing is to get a quote from burnin to run the test, set a pay-to address, and when enough money is there, those are the people who learn the results...



legendary
Activity: 2674
Merit: 1083
Legendary Escrow Service - Tip Jar in Profile
I did a number of overclocking testruns now. The normal Voltage i used was 1300mV.

I found its a bit strange when i sat the fan to 100% this setting became active only after 30seconds to 1 minutes after the start. I dont know why that is. Its the same with Temp 40°C but it seems to be a bit faster. Normally i would think a 100% setting means 100% from the start but it isnt.

One should keep in mind, when using windows, that cgminer seems not to keep windows from closing down automatically. Its not like showing a video that prevents windows from going to hibernation. So when you dont change that setting in windows before it will stop after some time. I had this over night.

Results:

Code:
MHz % more Accep- HW- HW to Tempe- Addit- Result Real Hash- Note
Hash- ted Errors Accep- rature ional rate gained
rate shares ted setting compared to
shares previous
hashrate

282
400 41.8% 3400 0 0% 49°C Effect positive + 41.8%
410 2.5% 3000 1 0.033% 48°C Effect positive + 2.467%
420 2.44% 3000 4 0.1333% 49°C Effect positive + 2.3067%
430 2.38% 3040 12 0.3947% 48°C Effect positive + 1.9853%
440 2.32% 3008 68 2.26% 49°C Effect compensatory + 0.06%
440 2.32% 34000 677 1.99% 48°C 1310mV Effect compensatory + 0.33% Its not possible to set 1 more millivolt with Standard cgminer
440 2.32% 12000 248 2.066% 49°C Temp40° Effect compensatory - 0.77%
440 2.32% 23504 297 1.263% 46°C Temp40° Effect compensatory + 1.057%
1310mV
450 2.27% 3008 473 15.724% 48°C Effect negative - 13.454%
450 2.27% 10224 901 8.8125% 45°C 100%Fan Effect negative - 6.542%
450 2.27% 13336 807 6,05% 49°C 1310mV Effect negative - 3.78%
450 2.27% 14024 895 6.38% 49°C 1310mV Effect negative - 4.11%
Temp40°

It looks like a lower temperature doesnt have a big effect. The more effect has a higher voltage. Even 10mV is helping not bad. 1311mV is not possible but 1310 is the last possible value. When you want to use more you have to compile cgminer and change a constant. What i will do later.

I believe burnin wrote 1.5V is a sure way to kill the chips. I wonder what is the max. I want to find out but dont like to risk the chips too much too... im not sure if it could be found out safely. The only way i can think of is to use only one miner for the test but that doesnt say anything about longer runtimes.

@burnin... is there a way to only use 10 chips of one miner? Maybe with a jumper?

Is it possible to power a raspberry pi with 5v power and gnd from a atx-psu-cable connected to pin 2 and 6 or 4 and 6 at the rpi? See here for the pins: http://elinux.org/RPi_Low-level_peripherals#General_Purpose_Input.2FOutput_.28GPIO.29

Im not sure about the gain in hashrate with higher clockrate and the correlation between accepted shares and HW-Errors are a correct indicator since i think that HW-Errors have a bigger impact on the hashrate than my calculations show. At least the average hashrate drops by more percents than i calculate it. The best indicator probably would be to let it run until 10 or 20k accepted shares and check the second hashrate value (avg) until you find the best value.
full member
Activity: 154
Merit: 100
Picked up my BitBurner today after work and it's happily mining @ 8GH/s and 46C, HW faults below 2%

#feelsgood Cheesy
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
As I mentioned on the previous page, to get the timeout correct:
https://bitcointalksearch.org/topic/m.2921457
Quote
When you switch the frequency via the API it recalculates the timeout for you.
(so if you just set the frequency the same as it currently is, it will correct the timeout)
But it also shows you on the screen (and it's in the API stats)

If you have 1 board 2x10 then the options are 115200:2:10...
If you have two boards chained together with 4x10 then the options are 115200:4:10...
etc.

And what about 1x20 and 1x10?
Should be possible =)
There is no 1x20 Tongue it's 2x10 to cgminer.
newbie
Activity: 31
Merit: 0
As I mentioned on the previous page, to get the timeout correct:
https://bitcointalksearch.org/topic/m.2921457
Quote
When you switch the frequency via the API it recalculates the timeout for you.
(so if you just set the frequency the same as it currently is, it will correct the timeout)
But it also shows you on the screen (and it's in the API stats)

If you have 1 board 2x10 then the options are 115200:2:10...
If you have two boards chained together with 4x10 then the options are 115200:4:10...
etc.

And what about 1x20 and 1x10?
Should be possible =)
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
As I mentioned on the previous page, to get the timeout correct:
https://bitcointalksearch.org/topic/m.2921457
Quote
When you switch the frequency via the API it recalculates the timeout for you.
(so if you just set the frequency the same as it currently is, it will correct the timeout)
But it also shows you on the screen (and it's in the API stats)

If you have 1 board 2x10 then the options are 115200:2:10...
If you have two boards chained together with 4x10 then the options are 115200:4:10...
etc.
hero member
Activity: 700
Merit: 500
Anything wrong with these parameters?

You got them from me, they are correct.  Wink

Of course Smiley
You gave me the config for a 8 board cluster, I just wanted to make sure my config would be correct for a 16 board cluster as well.
EDIT: Actually, I'm running 2 separate units with 8 boards each, so I'm not quite sure whether I should use 16 or 32 as number of miners. (cgminer shows BTB 0 and BTB 1)

Seems to be working good, 16 boards running at 128 GH/s.

Still not sure about the timeout part though (and about its exact meaning).

btw if you hook 16 boards up to a single 1000W PSU don't exceed 360Mhz.

Thanks for letting me know. I got me another PSU so this should be no problem.
sr. member
Activity: 322
Merit: 250
Got this from the DHL track and trace:

Tue, 13.08.2013 07:58 h --- The shipment was misrouted and could not be delivered. The shipment will
be readdressed and forwarded to the recipient.


Called DHL Express, said they couldn't help, as the shipping number doesn't up on their system, and that it was shipped by German post?

Confused here, i thought it was DHL - Burnin - sent you an email about it, can you check the shipping details?

Thanks!
sr. member
Activity: 243
Merit: 250
ALTCOM Ab9upXvD7ChnJxDRZgMmwNNEf1ftCGWrsE
Anything wrong with these parameters?

You got them from me, they are correct.  Wink

btw if you hook 16 boards up to a single 1000W PSU don't exceed 360Mhz.
hero member
Activity: 700
Merit: 500
With 35:350, the 35 timeout is important to get correct to stop duplicates.

What would be the correct timeout for 430?
I'm currently running my 16 boards with this config:
Quote
--avalon-options 115200:32:10:35:430 --bitburner-voltage 1300 --avalon-temp 45

Anything wrong with these parameters?
Pages:
Jump to: