Avalon ASIC users thread

[-ck]

I flashed 20130818 to an Avalon batch #2 at 11:20 CDT and kept the old settings.  I did not power off the system.  It has been running 58 minutes.

The Avalon now is at 350 MHz, up from it's typical 343-347 MHz.  Both temp2 and temp3 are at 50°C, temp1 is 22°C, the basement is 60°F.  This is hotter for temp2.  The fans are turning significantly faster, and they seem to change speeds frequently.

I think it is too soon to interpret the eligius statistics.  However, the preliminary impression is that variance is lower.

The orange led is flashing on and off at about 1 Hz.  I have never seen this behavior before.  I am curious what it means.


Edit -->

I bet it can get better.  Old config line:
--avalon-auto --avalon-freq 256-350 --avalon-temp 50

How should I incorporate the 'd' timeout option?  I have the idea that --avalon-auto & --avalon-options don't always play nice together.

I didn't do anything to the LED code. Remove your frequency range entirely and it might go even higher. Don't bother trying to use the "d" option as you're using firmware, it's for people who start the avalon by command line or via PC.

[1714164533]

1714164533

[1714164533]

1714164533

[1714164533]

1714164533

[1714164533]

1714164533

[-ck]

looks like the new firmware is super, but the flashing orange LED annoying. Is this normal?

I did nothing to the LED code. Maybe your avalon knows it's in overdrive?

[-ck]

Yeah the 0818 firmware is treating me well so far. I can now hold 360mhz @ less than 2% HW Errors. This was not possible before, 360mhz would be 3+ % HW error rate on previous firmware.
So my MHSav is constantly 84GH+ ... I'm wondering what exactly was changed?

Also, the results are during the hotter part during the day, so at night I imagine it will be even better.

I sacrificed a bit more latency for the higher hashrate. I made cgminer do better internal timeouts, largely ignoring when the avalon says it's ready for more work until enough time for a full nonce range has almost completely passed.

[crazyearner]

Any idea what the hell is with the orange light lol going on and off all the time is a wierd one I must admit as wasnt doing on any other versions hope its nothing to be alarmed by.

[-ck]

Any idea what the hell is with the orange light lol going on and off all the time is a wierd one I must admit as wasnt doing on any other versions hope its nothing to be alarmed by.

No idea at all. Mine's not doing it and I have got no idea what makes the LED even light up in the first place.

[Carlton Banks]

Any idea what the hell is with the orange light lol going on and off all the time is a wierd one I must admit as wasnt doing on any other versions hope its nothing to be alarmed by.

No idea at all. Mine's not doing it and I have got no idea what makes the LED even light up in the first place.

Indicating something or other about the FPGA status while the device initialises itself, IIRC

[crazyearner]

Well I know solid orange light is pool related and not configured. Normaly when orange lite bliking is partly when saving config and then goes out and stays out this an interesting one to say the least.

[crazyearner]

New problem after firmware system powered down. Restarted now have solid Red light and solid orange light and no access to Avalon any ideas how to fix

[ProfMac]

New problem after firmware system powered down. Restarted now have solid Red light and solid orange light and no access to Avalon any ideas how to fix

Has anyone successfully power cycled after update?

[mrSprinkles]

For some reason mine won't accept the --avalon-auto option. I've tried it with 20130703 20130814 and now 20130818. For example this works:

--avalon-temp 70 --avalon-cutoff 80

but this:

--avalon-auto --avalon-freq 256-275 --avalon-temp 70

results in the following cgminer API log error:

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

any ideas?

[thejestre]

Any idea what the hell is with the orange light lol going on and off all the time is a wierd one I must admit as wasnt doing on any other versions hope its nothing to be alarmed by.

I don't see an orange light.  It isn't very dark around my unit, so I'll check again later, but I see the white light and no orange.

[crazyearner]

New problem after firmware system powered down. Restarted now have solid Red light and solid orange light and no access to Avalon any ideas how to fix

Has anyone successfully power cycled after update?

well powed down and I have it powered up but now solid red light and orange and cant connect to device. Its as tho its crashed partly through firmware upgrade and gone tits up now unable to access even when trying to put into fail safe

[thejestre]

New problem after firmware system powered down. Restarted now have solid Red light and solid orange light and no access to Avalon any ideas how to fix

Has anyone successfully power cycled after update?

well powed down and I have it powered up but now solid red light and orange and cant connect to device. Its as tho its crashed partly through firmware upgrade and gone tits up now unable to access even when trying to put into fail safe

You probably already tried this, but have you tried to access it on the 192.168.0.100 IP as well as whatever static IP you had it on before the upgrade?  After one of my flashes I experienced the strange behavior that the unit remembered the old IP settings even though I told it to not remember the settings.

Good luck,

_theJestre

[Satobit]

For some reason mine won't accept the --avalon-auto option. I've tried it with 20130703 20130814 and now 20130818. For example this works:

--avalon-temp 70 --avalon-cutoff 80

but this:

--avalon-auto --avalon-freq 256-275 --avalon-temp 70

results in the following cgminer API log error:

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

any ideas?

you missed --avalon-cutoff 80

it needs both -cutoff and -temp options to run.

[ProfMac]

At 8h 15m uptime with version 20130818

   [timeout] => 35
   [frequency] => 353
   [fan1] => 2520
   [fan2] => 3720
   [fan3] => 3840
   [temp1] => 22
   [temp2] => 47
   [temp3] => 48
   [temp_max] => 51

   [match_work_count5] => 23945
   [match_work_count17] => 24590

[crazyearner]

New problem after firmware system powered down. Restarted now have solid Red light and solid orange light and no access to Avalon any ideas how to fix

Has anyone successfully power cycled after update?

well powed down and I have it powered up but now solid red light and orange and cant connect to device. Its as tho its crashed partly through firmware upgrade and gone tits up now unable to access even when trying to put into fail safe

You probably already tried this, but have you tried to access it on the 192.168.0.100 IP as well as whatever static IP you had it on before the upgrade?  After one of my flashes I experienced the strange behavior that the unit remembered the old IP settings even though I told it to not remember the settings.

Good luck,

_theJestre

The unit is saying its stuck on dchp on 192.168.1.65 and does not connect to it.

[crazyearner]

Sorted problem not sure wtf went on tho.

1 flashed to new firmware had running then all sudden when flashing system powered down powered back up solid red light and solid orange light had to telnet the fucker and firstboot didnt work mount_Root said a bunch of stuff then checked for ip and reverted to 192.168.0.100 so changed and manged to get access again.

[ProfMac]

Sorted problem not sure wtf went on tho.

1 flashed to new firmware had running then all sudden when flashing system powered down powered back up solid red light and solid orange light had to telnet the fucker and firstboot didnt work mount_Root said a bunch of stuff then checked for ip and reverted to 192.168.0.100 so changed and manged to get access again.

Can you power the system down then back up and have it work with version 20130818?
Does the orange light flash on your system?
 

[crazyearner]

Sorted problem not sure wtf went on tho.

1 flashed to new firmware had running then all sudden when flashing system powered down powered back up solid red light and solid orange light had to telnet the fucker and firstboot didnt work mount_Root said a bunch of stuff then checked for ip and reverted to 192.168.0.100 so changed and manged to get access again.

Can you power the system down then back up and have it work with version 20130818?
Does the orange light flash on your system?

Have powered down and back. Was blinking with settings --avalon-temp 50 --avalon-auto --avalon-freq 256-365.

Since removed and now have --avalon-auto no blinking. Maybe a conflict in settings or as ckolivas said maybe it knows its over driving etc.

Have added back --avalon-auto --avalon-freq 256-365 must be to do with avalon freq setting iver its conflicting or as ckolivas said it knows its overclocking over drive etc.

[mrSprinkles]

For some reason mine won't accept the --avalon-auto option. I've tried it with 20130703 20130814 and now 20130818. For example this works:

--avalon-temp 70 --avalon-cutoff 80

but this:

--avalon-auto --avalon-freq 256-275 --avalon-temp 70

results in the following cgminer API log error:

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

any ideas?

you missed --avalon-cutoff 80

it needs both -cutoff and -temp options to run.

that did the trick.