Avalon ASIC users thread - page 93. | Bitcointalksearch.org

Tigggger

legendary

Activity: 1098

Merit: 1000

Quote from: -ck on August 19, 2013, 07:40:56 AM

Your maths is almost certainly not correct, for there is not enough information on that screen to even determine the hw error percentage.

I wish people would stop being obsessed by hw error count...

I did the forumula that had been posted to arrive at the 6.7% (346,194 diff1), I cropped the screenshot just to show accepted/hw as in all the previous versions they were roughly the same number and it worked out at 1-2% (as it's 1/64).

I thought that discrepancy might be the reason for the 5GH drop in this version, was trying to help, appreciate the work you do.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Tigggger on August 19, 2013, 07:38:11 AM

Batch #3, 4 Modules and 20130819 not working so good for me, HW error rate has been 6.7% ~~if my maths is correct,~~ although cgminer reports 110GH pool has been saying around 105GH.

20130818 was running at 110GH, pool was reporting the same, and error rate was around 1-2% (accepted and HW were usually around the same number) so going to roll back to that and see what happens.

Your maths is almost certainly not correct, for there is not enough information on that screen to even determine the hw error percentage.

I wish people would stop being obsessed by hw error count...

Tigggger

legendary

Activity: 1098

Merit: 1000

Batch #3, 4 Modules and 20130819 not working so good for me, HW error rate has been 6.7% if my maths is correct, although cgminer reports 110GH pool has been saying around 105GH.

20130818 was running at 110GH, pool was reporting the same, and error rate was around 1-2% (accepted and HW were usually around the same number) so going to roll back to that and see what happens.

Bogart

legendary

Activity: 966

Merit: 1000

Quote from: -ck on August 18, 2013, 07:05:54 PM

Some of you have already spotted I uploaded a new firmware, 20130819

I upgraded my 4-module Batch 1 unit. 2h 40m later everything looks fine.

ProfMac

legendary

Activity: 1246

Merit: 1002

Quote from: ?? on ??

Quote from: -ck on August 18, 2013, 09:32:34 PM

Well that is then corresponding with when the avalon is ready/getting more work then. Why it suddenly started showing that, I don't know. Nor do I know why it doesn't show it on mine.

I am on Slush's Pool if that has anything to do with it.

Should my network activity light on the router show activity with this same pattern?

I am on eligius's pool. The 20130703 software did not do this. The '14, '14-1, '18, and now '19 software do. I typically flash and do not power down the unit. I did power it down 24 hours after the '18 flash, to be sure it would start correctly. Please never-mind the lack of logic in that behavior.

I have a version 1.52 controller board, very late batch #2 unit.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: ?? on ??

Quote from: -ck on August 18, 2013, 08:35:18 PM

Quote from: ?? on ??

Quote from: E on August 18, 2013, 08:20:40 PM

Dunno if the lights are blinking, and I'm not going to check so it won't bug me if they are

I can save on Christmas decorations as well as heat.

They are blinking at regular intervals. They look synchronized as they blink

Still trying to figure out what your lights are. Would it be approximately every 1.2 seconds? What batch avalon do you have?

Yes, that is it. I measured roughly 10 blinks in 11.6 seconds. Both batch 2 and 3. My batch 1 design does not have the light but the fan with the blue light stopped.

Well that is then corresponding with when the avalon is ready/getting more work then. Why it suddenly started showing that, I don't know. Nor do I know why it doesn't show it on mine.

regular

sr. member

Activity: 297

Merit: 250

My batch 2's orange light in blinking now too. It's still hashing away though.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: ?? on ??

Quote from: E on August 18, 2013, 08:20:40 PM

Dunno if the lights are blinking, and I'm not going to check so it won't bug me if they are

I can save on Christmas decorations as well as heat.

They are blinking at regular intervals. They look synchronized as they blink

Still trying to figure out what your lights are. Would it be approximately every 1.2 seconds? What batch avalon do you have?

E

full member

Activity: 234

Merit: 100

Quote from: -ck on August 18, 2013, 07:05:54 PM

Some of you have already spotted I uploaded a new firmware, 20130819

http://ck.kolivas.org/apps/cgminer/avalon/20130819/

There was a substantial rewrite of the timing code going into 20130818 which is where the hashrate rise from that version came from.

Just flashed 20130819 onto my Block 2 which is in ~25 Ambient. --avalon-auto stabilized around:

349 for 20130703 (Got more than 35 days of uptime from this one)
345 for 20130814-1, with similar utility as 20130703
357 for 20130819, with much lower eligius rejects! Like, 1/3rd the reject rate.

Have yet to get a 3hr update from eligius, but my 22.5 minute accepted rate is...

88MHash/s!!

Dunno if the lights are blinking, and I'm not going to check so it won't bug me if they are

Satobit

newbie

Activity: 42

Merit: 0

Quote from: -ck on August 18, 2013, 07:05:54 PM

Some of you have already spotted I uploaded a new firmware, 20130819

http://ck.kolivas.org/apps/cgminer/avalon/20130819/

There was a substantial rewrite of the timing code going into 20130818 which is where the hashrate rise from that version came from. I extended the timing code to encompass all the aspects of the usb communications with the avalon in 20130819 so it's more robust with respect to staying in sync with results and not losing data. However, overall it performs identically in my testing since the previous version dropped results only very rarely anyway since it is only likely to be a problem when CPU load is high and since the recent changes to cgminer it hardly uses any CPU now - it's only the background services on the avalon that may cause spikes in CPU and affect cgminer indirectly. So consider this a minor upgrade only.

I just flashed this firmware, and I can say that the HW rate has dropped about 30%-50%. Pretty amazing!

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Some of you have already spotted I uploaded a new firmware, 20130819

http://ck.kolivas.org/apps/cgminer/avalon/20130819/

There was a substantial rewrite of the timing code going into 20130818 which is where the hashrate rise from that version came from. I extended the timing code to encompass all the aspects of the usb communications with the avalon in 20130819 so it's more robust with respect to staying in sync with results and not losing data. However, overall it performs identically in my testing since the previous version dropped results only very rarely anyway since it is only likely to be a problem when CPU load is high and since the recent changes to cgminer it hardly uses any CPU now - it's only the background services on the avalon that may cause spikes in CPU and affect cgminer indirectly. So consider this a minor upgrade only.

ProfMac

legendary

Activity: 1246

Merit: 1002

Quote from: spiccioli on August 18, 2013, 03:39:33 PM

Hi,

the other day I've upgraded three batch #1 three modules Avalons from 20130519 to 20130814... I've lost a good 10% of hashing capacity Sad

Inside Avalon GUI I still see 70 GH, I'm not using --avalon-auto (nor any other option) given that I'm still using the stock PSU, but on pool graph you can clearly see when I've updated them

My question is: can I go back to 20130519 without problems or do I risk to brick them?

TIA

spiccioli

ps. I see that there is now 20130818, but I'd prefer to go back to what was working before trying next firmware.

20130703 worked very well for me.
20130814 & 20130814-1 worked poorly.
20130818 was an improvement. It has run 24+ hours.

thejestre

member

Activity: 76

Merit: 10

Quote from: spiccioli on August 18, 2013, 03:39:33 PM

Hi,

the other day I've upgraded three batch #1 three modules Avalons from 20130519 to 20130814... I've lost a good 10% of hashing capacity Sad

Inside Avalon GUI I still see 70 GH, I'm not using --avalon-auto (nor any other option) given that I'm still using the stock PSU, but on pool graph you can clearly see when I've updated them

My question is: can I go back to 20130519 without problems or do I risk to brick them?

TIA

spiccioli

ps. I see that there is now 20130818, but I'd prefer to go back to what was working before trying next firmware.

I used --avalon-auto without upgrading my batch #2 PSU. I have flashed older firmware after newer firmware successfully without much hassle. 20130818 is awesome firmware, I'd say try that at least before going backwards.

_theJestre

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Quote from: spiccioli on August 18, 2013, 03:39:33 PM

My question is: can I go back to 20130519 without problems or do I risk to brick them?

Logically, there's no way for the TP-LINK router to be aware of the difference between "backwards" FW flashes and "forwards" FW flashes. Still, if you don't take my word for it, then I won't take responsibility for your new brick Cheesy

. If it helps any more, I've already heard about people successfully re-flashing to older FW, in this thread I think.

spiccioli

legendary

Activity: 1379

Merit: 1003

nec sine labore

Hi,

the other day I've upgraded three batch #1 three modules Avalons from 20130519 to 20130814... I've lost a good 10% of hashing capacity Sad

Inside Avalon GUI I still see 70 GH, I'm not using --avalon-auto (nor any other option) given that I'm still using the stock PSU, but on pool graph you can clearly see when I've updated them

My question is: can I go back to 20130519 without problems or do I risk to brick them?

TIA

spiccioli

ps. I see that there is now 20130818, but I'd prefer to go back to what was working before trying next firmware.

Bogart

legendary

Activity: 966

Merit: 1000

I installed 20310818 on my 4-module batch 1 and 3-module batch 2, and they're both humming along fine. The batch 2 unit runs faster now, reporting WU 1182 now after 15 hours, where before WU was 1161. I think the batch 1 unit does also, though I didn't measure.

Quote from: PaJo2000 on August 18, 2013, 06:58:20 AM

Same problem here, batch #3 three blade miner:
[match_work_count24] => 0

other worker are fine, but box is hashing 1/24 less Sad

Looking for idea what to check.

If it were me, I would remove the board from the heatsink and reseat it. Maybe exchange it with one in a different position on the same module, and hope it was just a connector problem.

I'd also look at it to see if anything's obviously fried or otherwise damaged.

thejestre

member

Activity: 76

Merit: 10

Quote from: asjfdlksfd on August 18, 2013, 05:37:51 AM

On my batch #3 three blade miner the miner #24 looks like not working well:
[match_work_count24] => 0

Any idea what I can do to check them or to test them?

I've disabled it simply now by using only configuring Miner Count = 23 because it is latest miner which is not working.

Shoot, I checked my logs to see what was going on and found this:

[match_work_count3] => 0

EDIT: Batch #2 unit running 20130818

zoro

full member

Activity: 226

Merit: 100

it seems that with 0818 FW the avalon-temp in batch 1 and 2 is set by default to 52. this setting with previous FWs
resulted in cgminer restarts and lots of rejects. This is not the case with this FW.
ckolivas did something magic?! Roll Eyes

silverston

hero member

Activity: 952

Merit: 502

SAPG Pre-Sale Live on Uniswap!

Quote from: tarui on August 18, 2013, 07:02:11 AM

is it possible to have a temp log of the unit?

my avalon batch 1 seems to have random reboots where the miner just stops hashing and by the time i realised it, it has cooled down from possible overheating or just cooled down from all hashing, so i can't really tell if it's overheating.

if my miner is set --avalon-temp 54 , what is the cutoff temps for the miner to shutdown?

when it does overheat and shutsdown or goes idle, do i have to manually power down to let it cool or can i just let it run on idle and it will start hashing again once it's cool?

put --avalon-temp 48 or something and you will be happy

but noise

my setup is
--avalon-auto --avalon-temp 48

tarui

sr. member

Activity: 294

Merit: 250

is it possible to have a temp log of the unit?

my avalon batch 1 seems to have random reboots where the miner just stops hashing and by the time i realised it, it has cooled down from possible overheating or just cooled down from all hashing, so i can't really tell if it's overheating.

if my miner is set --avalon-temp 54 , what is the cutoff temps for the miner to shutdown?

when it does overheat and shutsdown or goes idle, do i have to manually power down to let it cool or can i just let it run on idle and it will start hashing again once it's cool?

Topic: Avalon ASIC users thread - page 93. (Read 438722 times)