Topic: Avalon ASIC users thread - page 143. (Read 438600 times)

It will usually continue to fluctuate indefinitely but you'll find it hovering +/-2 MHz, and that value's about the optimal. It will of course go lower if it starts getting too hot. Most seem to fall into two camps, close to 350 or close to 365. I run mine slightly lower than 350 since it seems to end up rebooting the router eventually at the highest setting (not cgminer but the whole hardware which is a little disconcerting). This is why I was experimenting with a less aggressive firmware yesterday, but in this world maximum hashrate seems to be the only thing that matters for most people...

How long do I have to wait till "avalon-auto" finds the optimal frequency? Or after what time I can say thats the optimal freq now to lock?

Also what do I have to put in the single frequency field when using --avalon-auto? Is that the start frequency?

I installed Altium viewer, and I attempt to open Avalon_BP.PcbDoc or Avalon_BP.schDoc and I can't see that anything happens.  The example files all work.  I re-downloaded the files.  All is now good.

I am not "logged in."

Total

Is this hardware error target per module? If one module has 3% error, and the other 2 modules have 0% error, that would be fine.

Slightly updated firmware:

http://ck.kolivas.org/apps/cgminer/avalon/20130702-1/openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin

This rolls back to the previous hardware error target of <2% when using avalon-auto which is worth about 1.5GH more on average.

EDIT: Adds a check for maximum fanspeed before throttling speed at higher temps as well.

Anyone tried to build avalon image from sources?
I've got this error in the end of process
But i found ready image openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin in /avalon/openwrt/bin/ar71xx
(not in avalon/bin/ as stated, probably because script is not exited correctly)
Should i just ignore this error and use it or something goes wrong?

ADD:

Seems that image only builds successfully on initial --clone option.
Found this, but it's not a solution. Seems that build script is not working "out of box"
If anyone already successfully build a working firmware, please share your experience.

ADD:

Fixed this errors by putting in makefiles "-I/home/build-image/avalon/openwrt/staging_dir/target-mips_r2_uClibc-0.9.33.2/usr/include/" where compiler can't find this file. Something is wrong with the path where make for luci starts. I feel this is not the right way to do this (better solution anyone?), but received .bin image file in result.

You're welcome!

You are now No.1 on Ozcoin  

Thanks, much appreciated hash donation!

Memory usage on linux looks like that often as it includes all sorts of cached data as well as what's actually in use. It's of no major significance.

Hello ckolivas

Great job!
Everything is going great.
I love the fix value for the fans speed!
Let my 5 Avalon for a few hours on your donation pool!

Many thanks

Greetings from Switzerland
Tinu

PS: What I see is, "memory usage" in the "process status" is at 119%

If any avalon users have managed to brick their wr703n and dont have serial access to it , I can offer an unbricking service for 0.50 btc or if they have blown it up somehow ... a new ready programmed modified wr703n with the additional memory for 1btc.. pm if interested ..Prices include p&p in the Uk  for overseas users , there will be additional nominal postage . Turnaround should be same day ... pm if interested


 

tested again with the latest firmware
flash it without keep settings , restart , change root pass and change ip , restart power off 1min
try to hash for donation , stop start cgminer   power off 1 min
apply settings again 282 , cgminer stop , power off
0 hash rate
I think there must be something wrong with the fpga bord   in my av ver 1
went back to 519b
Regards
Thor

Well, i would finish soon code for custom fans to allow setting MIN/MAX_PWM value (currently hardcoded 0x20, 0xA0 values) and inverse pwm option behavior when 0x00 = full speed (im back to original solution when change in temp_rise(), temp_drop() functions is needed) would you also include this changes after i test them on my inverse PWM fans?
To allow avalon be more flexible with different type of fans - like this :

ADD:

Edited fresh sources, now with --avalon-fan i think only one additional option is needed,
so i added options --avalon-invert-pwm and functions temp_rise_invert(), temp_drop_invert(), adjust_fan_invert()
also changed some places where DEFAULT_PWM_MIN/MAX constants appears.
I will post the changes once i test them on my setup.

ADD:

So it works as expected! I think im done here.
Now what i have done to the latest cgminer sources from git :

in cgminer.c , inserted @ LINE 1063

in driver-avalon.h , inserted @ LINE 164

in driver-avalon.c

inserted @ LINE 13

changed in function avalon_init_task()
to

changed in function avalon_detect_one()
to

changed in function avalon_update_temps()
to

added function adjust_fan_invert()

added function temp_rise_invert()

added function temp_drop_invert()


So, this change allow to use inverted PWM fans, and also correctly works with --avalon-fan options
ckolivas, please include this changes in future releases! (donation would be send)

love it!

thanks a lot for this options, especially the fans
will try it later

yea thanks, I am not frightend of the firmware itself but with my luck I will brick the wr703 while updating...

You can, but the new firmware doesn't overclock, it just gives you the ability to overclock if you desire...

As I am a little frightend to flash it right after it arrives, could I instead disconnect the wr703 and use a pi to test the overclockin so I have a fallback with the original firmware?

It is for all avalons. The settings you choose will depend on your hardware but default settings are safe on all of them.

just to be safe, the firmware is also for avalon batch #2 ?

Excellent. Thank you.