Avalon ASIC users thread

[bitdaniel]

where do they stash the wireless antenna?  Inside the case?  I can't see it anywhere.

It seems that the antenna is sometimes not shiped with the Avalon...

[1715033953]

1715033953

[1715033953]

1715033953

[1715033953]

1715033953

[SolarSilver]

ok... but if it was shipped, where would I find it?

None of the Batch #2 units shipped with a power cord, antenna or gloves. No Ikea tools either.

[ProfMac]

how long does it typically take to be delivered from China to the US? Any feedback would be greatly appreciated!
Thanks for time,
Brian

Mine shipped Monday, arrived Wednesday.

Did it stop in Cincinnati?

[allinvain]

how long does it typically take to be delivered from China to the US? Any feedback would be greatly appreciated!
Thanks for time,
Brian

Mine shipped Monday, arrived Wednesday.

Did it stop in Cincinnati?

They all stop in Cincinnati as far as I can tell. DHL has a shipping hub there.

[ProfMac]

how long does it typically take to be delivered from China to the US? Any feedback would be greatly appreciated!
Thanks for time,
Brian

Mine shipped Monday, arrived Wednesday.

Did it stop in Cincinnati?

They all stop in Cincinnati as far as I can tell. DHL has a shipping hub there.

No, I'm in the southwest.  It went Beijing, HK, LA

The outdoor temperature in some parts of the SouthWest today is 51°C.

[SolarSilver]

The outdoor temperature in some parts of the SouthWest today is 51°C.

Damn... it's about 18 to 22 degrees Celsius here, and it's summer holidays. Poor students that just graduated. Happy miners that can open the window :-)

[Syke]

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

How about making the target error rate a parameter?

[invader]

Backported my changes to latest cgminer source ( --avalon-invert-pwm , --avalon-hysteresis ), build new firmware.
Looks uberstable since reflash, 8+ 16+ hrs cgminer works without restart
( previous version was usually restarting in 2-3 hrs )

[Tesla71]

Nice thanks, maybe that fix my issue:

- my cgminer process seems to restart after every 4 hours or so.. must watch longer to see if it happens regulary. could it have something to do with the --avalon-auto, maybee the freq gets to high and it restarts? I am using --avalon-freq 300-340

One possibility. There are a few different ways that it restarts. One is an actual error in the code that makes it hang and stop submitting work, which should be fixed in this latest firmware. The other is multiple pool or network outages - and this is where the watchdog is trigger happy, as any period of 2+ minutes without work is enough for cgminer to stop being able to make work and the watchdog is not smart enough to detect what it is. Another is fpga screwups, but they are getting less likely with more fixes going into the cgminer direct USB code than they used to be with the old serial interface thereby bypassing one potential point of failure. An operating system error is also possible, and seems more common with the wifi enabled for reasons that aren't clear. Finally there's true hardware failure of one sort or another - overheat, inadequate power etc.

I could confirm that the newest firmware 2130703 fixed the restarts of cgminer. It's running since 18 hours so far.

[Bogart]

Nice thanks, maybe that fix my issue:

- my cgminer process seems to restart after every 4 hours or so.. must watch longer to see if it happens regulary. could it have something to do with the --avalon-auto, maybee the freq gets to high and it restarts? I am using --avalon-freq 300-340

One possibility. There are a few different ways that it restarts. One is an actual error in the code that makes it hang and stop submitting work, which should be fixed in this latest firmware. The other is multiple pool or network outages - and this is where the watchdog is trigger happy, as any period of 2+ minutes without work is enough for cgminer to stop being able to make work and the watchdog is not smart enough to detect what it is. Another is fpga screwups, but they are getting less likely with more fixes going into the cgminer direct USB code than they used to be with the old serial interface thereby bypassing one potential point of failure. An operating system error is also possible, and seems more common with the wifi enabled for reasons that aren't clear. Finally there's true hardware failure of one sort or another - overheat, inadequate power etc.

I could confirm that the newest firmware 2130703 fixed the restarts of cgminer. It's running since 18 hours so far.

Same here.  I installed it on 2 units last night (Batch 1 and Batch 2), and both now show 10+ hours of cgminer uptime.

It also seems to solve the issue where cgminer would sometimes not start hashing, and have to be restarted.  I was doing some config changes which let to a bunch of restarts last night, and it started hashing every time.

[silverston]

Hello!
please help!
I can not connect to the Avalon ...
Connecting to laptop via patchcord, I type in the browser 192.168.0.100 and wrote some time - Error connecting.
how to stop it?
only from box ...
sorry for my english

[shmadz]

Hello!
please help!
I can not connect to the Avalon ...
Connecting to laptop via patchcord, I type in the browser 192.168.0.100 and wrote some time - Error connecting.
how to stop it?
only from box ...
sorry for my english

Did you set a static address on your laptop?

May or may not need a crossover cable,

google "How to set static IP"

[elasticband]

one of my avalons connects via 192.168.0.110

[silverston]

after static ip configuration i see black screen with LuCI - Lua Configuration Interface, still loading and after again  - can not connect!!

[el_rlee]

Can it be that --avalon-auto is only working with a reading for the fan rpm's? I use water cooling and have no fans...
Also is it possible that the setting for 16 miners instead of 24 is not working?

@ckolivas: I got some water cooling blocks on spare - if you like I would send you one over as a donation  Just PM me if interested.

[silverston]

after static ip configuration i see black screen with LuCI - Lua Configuration Interface, still loading and after again  - can not connect!!

If you changed the IP you also need to change the IP of the computer you are connecting with.

Can such as reset to default?

[cypherdoc]

Is it stratum vardiif ramping up so you are submitting far less shares but same hashrate?

is there a way to tell?

Yes,

look at the lines with "Checking retarget for...", you'll see that it grows slowing down share submission.

spiccioli

so please tell me what these details mean:

Code:

2013-07-04 12:01:33,573 INFO BasicShareLimiter # Checking Retarget for 1 (30) avg. 1 target 30+-15
2013-07-04 12:01:33,573 INFO BasicShareLimiter # Retarget for 1 870 old: 30 new: 900

[ProfMac]

after static ip configuration i see black screen with LuCI - Lua Configuration Interface, still loading and after again  - can not connect!!

If you changed the IP you also need to change the IP of the computer you are connecting with.

Can such as reset to default?

Google for OpenWRT failsafe
Also, search in these forums.

[tiktoc]

so please tell me what these details mean:

Code:

2013-07-04 12:01:33,573 INFO BasicShareLimiter # Checking Retarget for 1 (30) avg. 1 target 30+-15
2013-07-04 12:01:33,573 INFO BasicShareLimiter # Retarget for 1 870 old: 30 new: 900

Checking difficulty, connection 1  at 30 diff on average. 1 second per share, target  is 30seconds avg plus or minus 15 seconds

change in retarget diff for connection 1 for  1 share in 30 seconds is 870, so old diff which is 30 plus new diff change of 870 = new diff total of 900 difficulty

so each 1 share is now worth 900 normal diff shares.

edit slight change to wording after reading more logs

[invader]

Can it be that --avalon-auto is only working with a reading for the fan rpm's? I use water cooling and have no fans...
Also is it possible that the setting for 16 miners instead of 24 is not working?

Last time i looked at your screen i found a huge amount of hw errors even at moderate frequencies,
i would try in simular case (if auto fails) to increment manually in 5 Mhz steps and look at hw error rate.
The only possible way fan data can make a "collision" with auto frequency option in this piece of code,

Code:

			if (!info->optimal) {
				if (info->fan_pwm >= opt_avalon_fan_max) {
					applog(LOG_WARNING,
					       "AVA%i: Above optimal temperature, throttling",
					       avalon->device_id);
					avalon_dec_freq(info);
				}

but info->fan_pwm is not rpm sensor reading, its pwm setting for fan speed. Even if you don't have one or
it just not connected - it will keep on passing pwm value to controller. So if your fan reading is zero -
there is no protection besides --avalon-cutoff option, its just for info purpose in current version.
Thats how i figured it out after looking at sources when my new fans went to 0 rpm and temperature starts growing.
I see no reason for changing 24 to 16 miners options to not work, only one thing - they must be plugged in DATA_P1 and P2 ports.