Avalon ASIC users thread

[ToRs]

sorry if this question has already been asked before (i am still currently backtracking the whole thread.. wew!)


but i got a few question about a knock-off avalon from china....


1. i noticed every morning when i checked the dashboard.. running time is at 2hrs or so.. seems like the miners has been restarting itself? is it normal?

2. anyone got a recommended setting for the clone avalon? i seems to be having an awful lot of hardware errors and rejects / stale

3. checking the CGMiner Api Log.. noticed that 1 worker is not working... any possible way i can do to wake up that chip?

4. best firmware version so far for this type of machine? currently using 20131123

5. mod for the cooling fan? it has been so loud and sounds like living in a runway where in a jet plane is trying to take off 24/7... =D

thanks in advance...

[1714283750]

1714283750

[pepo]

sorry if this question has already been asked before (i am still currently backtracking the whole thread.. wew!)


but i got a few question about a knock-off avalon from china....


1. i noticed every morning when i checked the dashboard.. running time is at 2hrs or so.. seems like the miners has been restarting itself? is it normal?

2. anyone got a recommended setting for the clone avalon? i seems to be having an awful lot of hardware errors and rejects / stale

3. checking the CGMiner Api Log.. noticed that 1 worker is not working... any possible way i can do to wake up that chip?

4. best firmware version so far for this type of machine? currently using 20131123

5. mod for the cooling fan? it has been so loud and sounds like living in a runway where in a jet plane is trying to take off 24/7... =D

thanks in advance...

Probablt the temperature raises and the avalon stops , you cant do anithing about the noise , it is how it is. I cant understand what you mean at point 3 , workers and chips got nothing to do.

[-ck]

A new openwrt with 4.2.0 ? TY.

Here you go, firmware based on cgminer 4.2.0 (with efficient solo mining!):

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

[holders]

Thank you for 4.2.0! 

[ManeBjorn]

That is fast.
You really crank out the good work.
Thanks I will try it later.

A new openwrt with 4.2.0 ? TY.

Here you go, firmware based on cgminer 4.2.0 (with efficient solo mining!):

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

[ManeBjorn]

I added a new string to the config so it would report to MultiMiner. 
Now I am getting that dam socket error again and no mining.  I have been offline with it for over and hour.  If anyone can help please let me know.
Here is my string.

Code:

--log 5 --api-listen --api-allow W:127.0.0.1,192.168.0.0/24

I changed nothing else.  Cold boot and soft boots and no results.
I am feeling quite dumb right now. 

[ManeBjorn]

I am flashing this while it is not mining.  I will let you know if it gets me back up and mining.

A new openwrt with 4.2.0 ? TY.

Here you go, firmware based on cgminer 4.2.0 (with efficient solo mining!):

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

[mitak64]

I added a new string to the config so it would report to MultiMiner. 
Now I am getting that dam socket error again and no mining.  I have been offline with it for over and hour.  If anyone can help please let me know.
Here is my string.

Code:

--log 5 --api-listen --api-allow W:127.0.0.1,192.168.0.0/24

I changed nothing else.  Cold boot and soft boots and no results.
I am feeling quite dumb right now. 

do this:  --api-allow W:127.0.0.1,W:192.168.0/24

and no, I did not miss a zero ...

[ManeBjorn]

Hi
I put it in now.  I am rebooting and will let you know if it starts mining again.

I added a new string to the config so it would report to MultiMiner. 
Now I am getting that dam socket error again and no mining.  I have been offline with it for over and hour.  If anyone can help please let me know.
Here is my string.

Code:

--log 5 --api-listen --api-allow W:127.0.0.1,192.168.0.0/24

I changed nothing else.  Cold boot and soft boots and no results.
I am feeling quite dumb right now. 

do this:  --api-allow W:127.0.0.1,W:192.168.0/24

and no, I did not miss a zero ...

[ManeBjorn]

It's still not mining.
I am getting some help via team viewer I will let you know how it goes.
Thanks

Hi
I put it in now.  I am rebooting and will let you know if it starts mining again.

I added a new string to the config so it would report to MultiMiner. 
Now I am getting that dam socket error again and no mining.  I have been offline with it for over and hour.  If anyone can help please let me know.
Here is my string.

Code:

--log 5 --api-listen --api-allow W:127.0.0.1,192.168.0.0/24

I changed nothing else.  Cold boot and soft boots and no results.
I am feeling quite dumb right now. 

do this:  --api-allow W:127.0.0.1,W:192.168.0/24

and no, I did not miss a zero ...

[Coinagect]

A new openwrt with 4.2.0 ? TY.

Here you go, firmware based on cgminer 4.2.0 (with efficient solo mining!):

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

Thanks for the post.  Any reason to suspect this may cause an increase is discards?

[-ck]

A new openwrt with 4.2.0 ? TY.

Here you go, firmware based on cgminer 4.2.0 (with efficient solo mining!):

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

Thanks for the post.  Any reason to suspect this may cause an increase is discards?

Discards are totally and utterly and completely and absolutely irrelevant.

[ManeBjorn]

It's all good now.
There were doubled arguments I was missing.  gjpminingco found them for me.
Thanks for the help.

It's still not mining.
I am getting some help via team viewer I will let you know how it goes.
Thanks

Hi
I put it in now.  I am rebooting and will let you know if it starts mining again.

I added a new string to the config so it would report to MultiMiner. 
Now I am getting that dam socket error again and no mining.  I have been offline with it for over and hour.  If anyone can help please let me know.
Here is my string.

Code:

--log 5 --api-listen --api-allow W:127.0.0.1,192.168.0.0/24

I changed nothing else.  Cold boot and soft boots and no results.
I am feeling quite dumb right now. 

do this:  --api-allow W:127.0.0.1,W:192.168.0/24

and no, I did not miss a zero ...

[haaggus]

It's funny, when I install the NOOBS operating system onto my Raspberry Pi, it boots; but when I install the OPENWRT OS in order to start mining with my Avalon, the Raspi does not boot fully.

The raspberry pi also works with MinePeon, but MinePeon does not find my Avalon2 in order to start mining with it. SO, I'm stuck. Is there something missing from OPENWRT that is incomplete or keeps the boot from happening?  As you can see I'm not quite an expert with Linux.

[mc1225]

Hi All,

My China clone Avalon 200G all in a sudden stops working.  I tried to restart cgminer but only saw the followings.

Sat Mar 22 01:22:44 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 138.236.128.112
Sat Mar 22 01:22:44 2014 daemon.info sysinit: ntpd: sent query to 138.236.128.112
Sat Mar 22 01:22:44 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 59.148.184.7
Sat Mar 22 01:22:44 2014 daemon.info sysinit: ntpd: sent query to 59.148.184.7
Sat Mar 22 01:22:44 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 218.189.210.10
Sat Mar 22 01:22:44 2014 daemon.info sysinit: ntpd: sent query to 218.189.210.10
Sat Mar 22 01:22:44 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 59.148.184.7
Sat Mar 22 01:22:44 2014 daemon.info sysinit: ntpd: sent query to 59.148.184.7
Sat Mar 22 01:22:54 2014 daemon.info sysinit: Alarm clock
Sat Mar 22 01:22:54 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 66.7.96.2
Sat Mar 22 01:22:54 2014 daemon.info sysinit: ntpd: sent query to 66.7.96.2
Sat Mar 22 01:22:54 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 137.189.4.10
Sat Mar 22 01:22:54 2014 daemon.info sysinit: ntpd: sent query to 137.189.4.10
Sat Mar 22 01:22:54 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 103.5.12.41
Sat Mar 22 01:22:54 2014 daemon.info sysinit: ntpd: sent query to 103.5.12.41
Sat Mar 22 01:22:54 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 137.189.4.10
Sat Mar 22 01:22:54 2014 daemon.info sysinit: ntpd: sent query to 137.189.4.10
Sat Mar 22 01:23:04 2014 daemon.info sysinit: Alarm clock
Sat Mar 22 01:23:04 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 138.236.128.112
Sat Mar 22 01:23:04 2014 daemon.info sysinit: ntpd: sent query to 138.236.128.112
Sat Mar 22 01:23:04 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 59.148.184.7
Sat Mar 22 01:23:04 2014 daemon.info sysinit: ntpd: sent query to 59.148.184.7
Sat Mar 22 01:23:04 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 218.189.210.10
Sat Mar 22 01:23:04 2014 daemon.info sysinit: ntpd: sent query to 218.189.210.10
Sat Mar 22 01:23:04 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 59.148.184.7
Sat Mar 22 01:23:04 2014 daemon.info sysinit: ntpd: sent query to 59.148.184.7

Anyone can help to advise?  Thank you so much

[gjpminingco]

It's funny, when I install the NOOBS operating system onto my Raspberry Pi, it boots; but when I install the OPENWRT OS in order to start mining with my Avalon, the Raspi does not boot fully.

The raspberry pi also works with MinePeon, but MinePeon does not find my Avalon2 in order to start mining with it. SO, I'm stuck. Is there something missing from OPENWRT that is incomplete or keeps the boot from happening?  As you can see I'm not quite an expert with Linux.

What do you mean it dont fully boot under the openwrt

[haaggus]

What do you mean it dont fully boot under the openwrt

I mean that the Raspberry Pi turns on, the PSU and Avalon both turn on, but there are no green/yellow lights on the Raspi and nothing displays to the screen. It just sits in that state with the solid red light.

It can't be a problem with win32diskimgr because MinePeon works fine. I would use MinePeon if I could. But the Avalon only works with the custom OPENWRT firmware apparently found here http://downloads.canaan-creative.com/software/avalon2/latest/raspberrypi/

I have no idea why this custom avalon raspi OS won't work.

[Carlton Banks]

What do you mean it dont fully boot under the openwrt

I mean that the Raspberry Pi turns on, the PSU and Avalon both turn on, but there are no green/yellow lights on the Raspi and nothing displays to the screen. It just sits in that state with the solid red light.

It can't be a problem with win32diskimgr because MinePeon works fine. I would use MinePeon if I could. But the Avalon only works with the custom OPENWRT firmware apparently found here http://downloads.canaan-creative.com/software/avalon2/latest/raspberrypi/

I have no idea why this custom avalon raspi OS won't work.

I think it might be that OpenWRT doesn't have a direct display driver (or even any display driver at all). So lack of any video output from the RaspPi is probably feature-not-bug kind of situation. Default IP for a fresh OpenWRT (on the standard Avalon controller at least) is 192.168.0.100 (check for sure with the provider of this firmware before going any further). So, if your subnet is already 192.168.0, then you should be able to log into the OpenWRT web interface by accessing 192.168.0.100 in a web browser on another network device. If not, change the whole IP on any computing device with video output & ethernet to 192.168.0.x, plug the ethernet connection directly between the raspPi and then access the Pi via web interface the same way. Change the Pi's IP to the subnet you're using. 

[haaggus]

I don't understand why I can't just plug the Avalon 2 (single modular) into my laptop and connect to it with BFGminer like I do with my BFlabs Jalapeno... why do I have to go through all this bullshit with Raspberry Pi and WR703 ?

[gjpminingco]

cgminer -S/dev/ttyUSB0 --avalon2-fan 100 --avalon2-freq 1500 --avalon2-voltage 10000 -o stratum+tcp://poolinfohere:3333 -O workerinfohere.worker1:x -o stratum+tcp://poolinfohere:3333 -O workerinfohere.worker1:x --api-allow W:127.0.0.1 --api-listen --real-quiet -Q 13 -s 11 -E 10 --no-submit-stale --hotplug 20 -l 5