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?
Topic: Avalon ASIC users thread - page 95. (Read 438516 times)
Has anyone successfully power cycled after update?
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
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.
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
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.
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.
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. 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.
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? 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. 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.
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+ ... Im 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.
So my MHSav is constantly 84GH+ ... Im 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.
The avalon web interface does not report the API devs command back, so you don't see the hw error% reported anywhere unless you're logged into the avalon some other way, using the devs command. The calculated HW error percentage is wrong in that lua modification by BenTuras as kano said.
Cant remember how to read the hw error rate though.
HW error rate in % = HW / (diff1shares + HW) x 100
Or better yet, apply the patch:
https://bitcointalksearch.org/topic/modification-to-show-hw-and-rejected-on-avalon-cgminer-status-page-254331
Use current cgminer and it reports the % figures directly, and correctly, in the API
... but not in the cgminer status page of the avalon itself, and not in the miner.php generate page.
The 0817 avalon firmware reports that it is using cgminer 3.3.4.
I don't have an avalon - so I can only guess someone missed something or the avalon does something different to my miner.php ...
Cant remember how to read the hw error rate though.
HW error rate in % = HW / (diff1shares + HW) x 100
Or better yet, apply the patch:
https://bitcointalksearch.org/topic/modification-to-show-hw-and-rejected-on-avalon-cgminer-status-page-254331
Use current cgminer and it reports the % figures directly, and correctly, in the API
... but not in the cgminer status page of the avalon itself, and not in the miner.php generate page.
The 0817 avalon firmware reports that it is using cgminer 3.3.4.
excellent work ckolivas with new FW 130818. after 4 hours, utility is increased due to more accepted shares!
Cant remember how to read the hw error rate though.
HW error rate in % = HW / (diff1shares + HW) x 100
Or better yet, apply the patch:
https://bitcointalksearch.org/topic/modification-to-show-hw-and-rejected-on-avalon-cgminer-status-page-254331
Use current cgminer and it reports the % figures directly, and correctly, in the API
... and in older versions of cgminer, through the API, they are called: "Hardware Errors" and "Diff1 Work" to calculate them
I'm getting very good results so far with the new 20130818 firmware. Orange LED is blinking but I don't care.
Today I discovered a potential problem with my Fractal Newton 1000W PSU, the PSU Fan doesn't work at all, it just stands still. I don't know how the Fan Control is implemented in this PSU, but I can't imagine the Fan not running at all @ 680W load. I already contacted Fractal about this, but I don't expect an answer before monday. So I'll just let it run like this and see what happens. Cooling should be enough with those powerful Avalon fans.
Today I discovered a potential problem with my Fractal Newton 1000W PSU, the PSU Fan doesn't work at all, it just stands still. I don't know how the Fan Control is implemented in this PSU, but I can't imagine the Fan not running at all @ 680W load. I already contacted Fractal about this, but I don't expect an answer before monday. So I'll just let it run like this and see what happens. Cooling should be enough with those powerful Avalon fans.
Cant remember how to read the hw error rate though.
HW error rate in % = HW / (diff1shares + HW) x 100
Or better yet, apply the patch:
https://bitcointalksearch.org/topic/modification-to-show-hw-and-rejected-on-avalon-cgminer-status-page-254331
Quote
What's your hashrate?
Batch3 4module 1200wPSU, 110.8 GH/s, 352-353 MHz, 0.3% reject rate, 1.75% HW errors
Batch3 4module stock PSU, 111.6 GH/s, 355 MHz, 0.2% reject rate, 0.94% HW errors
The new FW fixed a high reject rate problem on the first unit. Was running 2-3% rejects on the 0703 firmware.
Mine looks worst. Batch 1 4 module
Hashrate swings wildly so it's hard to judge.
1250w psu and around 0.56% rejected.
Cant remember how to read the hw error rate though.
The fact that I'm in a tropical country doesn't help much with thr temps
Changed options 1 hour ago:
--avalon-options 115200:24:10:d:355 --avalon-auto --avalon-freq 256-375 --avalon-temp 50
My match_work_count shows more spread:
min: 3001
max: 3288
0.5 * (3288-3001) / (3288+3001) --> 0.002_28
When the uptime is several days, these numbers become very close.
My freq dropped to 351 MHz.
The orange light is still blinking.
Temperatures are now 22, 46, 47°C
Fans are 2760, 3720, 3720 and seem to vary a lot, and the temperature wanders around also.
[timeout] => 35
I show 3387 accepted, 4 rejects, 83372 diff1shares at 1h 11m 18s
--avalon-options 115200:24:10:d:355 --avalon-auto --avalon-freq 256-375 --avalon-temp 50
My match_work_count shows more spread:
min: 3001
max: 3288
0.5 * (3288-3001) / (3288+3001) --> 0.002_28
When the uptime is several days, these numbers become very close.
My freq dropped to 351 MHz.
The orange light is still blinking.
Temperatures are now 22, 46, 47°C
Fans are 2760, 3720, 3720 and seem to vary a lot, and the temperature wanders around also.
[timeout] => 35
I show 3387 accepted, 4 rejects, 83372 diff1shares at 1h 11m 18s
I'm a bit concerned with the thermal paste used. The manufacturer seems to use so much of it that it overflows thru the holes and on to the circuit board itself and contacting the chip and other components.
Unless they use non conductive thermal paste.
Unless they use non conductive thermal paste.
Jump to: