Pages:
Author

Topic: Avalon ASIC users thread - page 89. (Read 438596 times)

member
Activity: 113
Merit: 10
https://www.chynge.net/
August 23, 2013, 09:15:50 PM
Frequency field set to 450 with Options at --avalon-auto <  WORKS

Bump frequency field to 451 < DEAD waited at least 5 minutes.  API log shows "Socket connect failed: Connection refused"
Did you try it with --avalon-auto without other parameters? It might just be the web interface that doesn't allow it.
Meaning the web interface has a 450 limit even if cgminer doesn't. See what it gets to with auto without any other parameters?

Blank Freq field  with --avalon-auto and nothing else < DEAD
I did NOT say blank freq lol this is crazy. Use your previous settings, set 450 in frequency and then just add --avalon-auto to MoreOptions
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
August 23, 2013, 09:12:48 PM
Frequency field set to 450 with Options at --avalon-auto <  WORKS

Bump frequency field to 451 < DEAD waited at least 5 minutes.  API log shows "Socket connect failed: Connection refused"
Did you try it with --avalon-auto without other parameters? It might just be the web interface that doesn't allow it.
Meaning the web interface has a 450 limit even if cgminer doesn't. See what it gets to with auto without any other parameters?

Blank Freq field  with --avalon-auto and nothing else < DEAD
I did NOT say blank freq lol this is crazy. Use your previous settings, set 450 in frequency and then just add --avalon-auto to MoreOptions
member
Activity: 113
Merit: 10
https://www.chynge.net/
August 23, 2013, 09:11:24 PM
Frequency field set to 450 with Options at --avalon-auto <  WORKS

Bump frequency field to 451 < DEAD waited at least 5 minutes.  API log shows "Socket connect failed: Connection refused"
Did you try it with --avalon-auto without other parameters? It might just be the web interface that doesn't allow it.
Meaning the web interface has a 450 limit even if cgminer doesn't. See what it gets to with auto without any other parameters?

Blank Freq field  with --avalon-auto and nothing else < DEAD
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
August 23, 2013, 09:00:59 PM
Frequency field set to 450 with Options at --avalon-auto <  WORKS

Bump frequency field to 451 < DEAD waited at least 5 minutes.  API log shows "Socket connect failed: Connection refused"
Did you try it with --avalon-auto without other parameters? It might just be the web interface that doesn't allow it.
Meaning the web interface has a 450 limit even if cgminer doesn't. See what it gets to with auto without any other parameters?
member
Activity: 113
Merit: 10
https://www.chynge.net/
August 23, 2013, 08:57:46 PM
There is no reason it wouldn't start with the same settings you used previously. Try those first, and then add just --avalon-auto to the More Options box. Sometimes people are impatient and it can take it up to 2 mins before you start seeing the output from cgminer.

Its definitely not working.  with the Main frequency field at 440 and the Options field as "--avalon-auto --avalon-freq 440-455 --avalon-fan 50"  
Waited for at least 5 min here.

Adjusted only the "--avalon-freq 440-455"  down to "--avalon-freq 440-450" and the system starts within 30sec.

Is the an SSH command line only method I could try?
Edited, kept highlighting wrong part.

Frequency field set to 450 with Options at --avalon-auto <  WORKS

Bump frequency field to 451 < DEAD waited at least 5 minutes.  API log shows "Socket connect failed: Connection refused"

sr. member
Activity: 294
Merit: 250
August 23, 2013, 08:56:24 PM
Having some problems with the avalon again.

need some help

for some reason, the miner has been stoppping every now and then and refuses to restart mining unless i manually power down.

it was running at 350mhz for sometime and running fine. so i tried running at 355mhz but it stops every few hours so i lowered it to 350mhz

as for cooling, i've added heatsinks to the side of the case (where the main heatsinks are mounted), added thermal paste between the main heatsinks and case (the contact between the heatsinks and case) and added 2 exhaust fans

6hrs ago it stopped mining when i checked the miner's page, the time elasped was just 1min, meaning the miner had restarted a min ago. so for 6hrs, it was doing nothing?


I mean, so 1 min ago, it restarted on its own but not yet hashing?

what was it doing during the 6hrs and why isn't it restarting and hashing?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
August 23, 2013, 08:41:23 PM
There is no reason it wouldn't start with the same settings you used previously. Try those first, and then add just --avalon-auto to the More Options box. Sometimes people are impatient and it can take it up to 2 mins before you start seeing the output from cgminer.

Its definitely not working.  with the Main frequency field at 440 and the Options field as "--avalon-auto --avalon-freq 440-455 --avalon-fan 50"  
Waited for at least 5 min here.

Adjusted only the "--avalon-freq 440-455"  down to "--avalon-freq 440-450" and the system starts within 30sec.

Is the an SSH command line only method I could try?
Edited, kept highlighting wrong part.
member
Activity: 113
Merit: 10
https://www.chynge.net/
August 23, 2013, 08:39:22 PM

Did you try it with --avalon-auto without other parameters? It might just be the web interface that doesn't allow it.

In the web GUI in the "Chip Frequency(Default: 300)" field Is where I have been setting the frequency.

The only "More options" I have set is "--avalon-fan 50"
Try what I suggested, and put your range you're interested in More Options as well: --avalon-auto --avalon-freq 450-500 or something

Still doesn't work

More options:  --avalon-auto --avalon-freq 450-465 --avalon-fan 50

What am I supposed to do with the main frequency field?   Both with Blank and 450mhz the system doesn't start.
There is no reason it wouldn't start with the same settings you used previously. Try those first, and then add just --avalon-auto to the More Options box. Sometimes people are impatient and it can take it up to 2 mins before you start seeing the output from cgminer.

Its definitely not working.  with the Main frequency field at 440 and the Options field as "--avalon-auto --avalon-freq 440-455 --avalon-fan 50" 
Waited for at least 5 min here.

Adjusted only the "--avalon-freq 440-455"  down to "--avalon-freq 440-450" and the system starts within 30sec.

Is the an SSH command line only method I could try?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
August 23, 2013, 08:34:06 PM

Did you try it with --avalon-auto without other parameters? It might just be the web interface that doesn't allow it.

In the web GUI in the "Chip Frequency(Default: 300)" field Is where I have been setting the frequency.

The only "More options" I have set is "--avalon-fan 50"
Try what I suggested, and put your range you're interested in More Options as well: --avalon-auto --avalon-freq 450-500 or something

Still doesn't work

More options:  --avalon-auto --avalon-freq 450-465 --avalon-fan 50

What am I supposed to do with the main frequency field?   Both with Blank and 450mhz the system doesn't start.
There is no reason it wouldn't start with the same settings you used previously. Try those first, and then add just --avalon-auto to the More Options box. Sometimes people are impatient and it can take it up to 2 mins before you start seeing the output from cgminer.
member
Activity: 113
Merit: 10
https://www.chynge.net/
August 23, 2013, 08:05:52 PM

Did you try it with --avalon-auto without other parameters? It might just be the web interface that doesn't allow it.

In the web GUI in the "Chip Frequency(Default: 300)" field Is where I have been setting the frequency.

The only "More options" I have set is "--avalon-fan 50"
Try what I suggested, and put your range you're interested in More Options as well: --avalon-auto --avalon-freq 450-500 or something

Still doesn't work

More options:  --avalon-auto --avalon-freq 450-465 --avalon-fan 50

What am I supposed to do with the main frequency field?   Both with Blank and 450mhz the system doesn't start.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
August 23, 2013, 07:58:03 PM

Did you try it with --avalon-auto without other parameters? It might just be the web interface that doesn't allow it.

In the web GUI in the "Chip Frequency(Default: 300)" field Is where I have been setting the frequency.

The only "More options" I have set is "--avalon-fan 50"
Try what I suggested, and put your range you're interested in More Options as well: --avalon-auto --avalon-freq 450-500 or something
member
Activity: 113
Merit: 10
https://www.chynge.net/
August 23, 2013, 07:53:19 PM

Did you try it with --avalon-auto without other parameters? It might just be the web interface that doesn't allow it.

In the web GUI in the "Chip Frequency(Default: 300)" field Is where I have been setting the frequency.

The only "More options" I have set is "--avalon-fan 50"
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
August 23, 2013, 07:46:00 PM
Yes perfectly stable .49% hw error at 41c Batch3

could you lift that 450 limit easily?

Thanks!
There's a special one-off firmware just for you that lifts the limit to 1000 here:
http://ck.kolivas.org/apps/cgminer/temp/

This firmware isnt working past 450.

CGMiner API log shows:

[Firmware Version] => 20130824
cgminer-bdac063+
luci-d854edc+
cgminer-openwrt-packages-800cc58
Socket connect failed: Connection refused


Thanks again for all your work!




Did you try it with --avalon-auto without other parameters? It might just be the web interface that doesn't allow it.
member
Activity: 113
Merit: 10
https://www.chynge.net/
August 23, 2013, 07:42:52 PM
Yes perfectly stable .49% hw error at 41c Batch3

could you lift that 450 limit easily?

Thanks!
There's a special one-off firmware just for you that lifts the limit to 1000 here:
http://ck.kolivas.org/apps/cgminer/temp/

This firmware isnt working past 450.

CGMiner API log shows:

[Firmware Version] => 20130824
cgminer-bdac063+
luci-d854edc+
cgminer-openwrt-packages-800cc58
Socket connect failed: Connection refused


Thanks again for all your work!



sr. member
Activity: 472
Merit: 250
August 23, 2013, 07:07:14 PM
Has anyone had the problem where the box will be just fine for the first day, but then hashrate just drops off to ~60Ghash?  I have a 3-mod B2 and 4-mod B3 that both do this when using auto with a range of 325-350 after a while.  What is interesting is the hashrate reported on the GUI stays the same, but the pool shows the reduced rate.  I also end up noticing a large amount of HW errors it seems during this same time (one time I had a whole module seem to stop reporting shares).  (all Aug firmwares)

Funny thing is, if I set it to 340mhz max the errors drop to 0.6-0.8%.  345mhz shows around 1.9% or so.  Seems to be the same on both boxes. I have an AC unit blowing directly into the intakes and the B2 runs 45C and the B3 runs 58C.  Fans are default speeds, it almost seemed like upping them manually caused more issues?

At this point I am leaning towards just setting 335mhz or something and say forget it, I had weeks of uptime at 300mhz clocks and just got around to OCing as of late.
sr. member
Activity: 364
Merit: 250
August 23, 2013, 06:10:03 PM
What kind of hash rates are people achieving with Batch 2s now? I'm hanging out at 79-83, around 350 freq. Is the new firmware of interest to me?
member
Activity: 113
Merit: 10
https://www.chynge.net/
August 23, 2013, 06:06:19 PM
Yes perfectly stable .49% hw error at 41c Batch3

could you lift that 450 limit easily?

Thanks!
There's a special one-off firmware just for you that lifts the limit to 1000 here:
http://ck.kolivas.org/apps/cgminer/temp/


AWESOME!!  THANK YOU!!!
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
August 23, 2013, 05:24:03 PM
Yes perfectly stable .49% hw error at 41c Batch3

could you lift that 450 limit easily?

Thanks!
There's a special one-off firmware just for you that lifts the limit to 1000 here:
http://ck.kolivas.org/apps/cgminer/temp/
sr. member
Activity: 434
Merit: 250
August 23, 2013, 03:45:02 PM
Hi Tigggger. I did try --avalon-temp 70 as that's what was specified for the b3s by default. I don't recall setting the cutoff temp though. I'll give that a shot, thanks.

Edit: That worked a treat, thanks!
legendary
Activity: 1098
Merit: 1000
August 23, 2013, 03:28:11 PM
I'm having difficulty with your latest releases on batch 3, 4 module rigs however, and I apologize if this has been discussed and I missed it. These are restarting cgminer when temp 2 = > 60. I've tried every firmware from 20130703 to 20130821 and they all exhibit this behavior. The only firmware that seems to work properly on these rigs is their factory firmware 20130723. Do you have any idea how this issue can be resolved?

Have you used --avalon-temp 70 --avalon-cutoff 90 ?  These need to be added to the 'more options' for batch 3, not had any restarts on mine except when upgading the firmware.
Pages:
Jump to: