Avalon ASIC users thread

[pjcltd]

I'm sorry to post this a second time but what settings do I change to be able to remotely view the Avalons cgminer stats?

Edit: Never mind I see the answer several pages back.

Hi
witch page is it on ?

[1713414594]

1713414594

[1713414594]

1713414594

[jddebug]

Just to clarify, In Network settings for ethernet I will be manually setting IPv4 to 192.168.1.2 and then using the terminal to ssh 192.168.1.1.
(Just tried this and ssh connection timed out)

EDIT: And yes, was using your most recent FW, booted first time (with non-saved settings), then could not connect once reset. Was I missing something?

If you have set the IPv4 address of your avalon to 192.168.1.2 you also have to ssh to the same address or use your webbrowser (the address of the avalon thus 192.168.1.2).

Cheers

Thanks, but I am still getting 'connection refused' when trying to ssh.  With and without hitting the reset button. Hrmmm.

Your powering on and holding the reset switch for about 5 to 10 seconds until the blue light is flashing rapidly?

[jddebug]

Hi i have 4 Avalon Mini's
and they are all having the same problem

The is this when i start up the unit

Load Average   0.12, 0.14, 0.14

but after the miner has been on for 5 - 6 hours the load average goes high
to

 Load Average   24.10, 23.4, 22.10

then the miner has gin rate will drop to 3.05 GH/s
i then have to power off the miner witch is a pain if i am at work
any advice ?

thanks in advance
Paul

Paul,

A number of mine do that from time to time too. I found it stopped when I put them in a cooler environment. A few degrees was all it took for all but one of mine.

What I'm now dealing with is the mini will start doing duplicates instead of new work for some reason. My hashrate is the same at the pool but its sending thousands of duplicates.

Hi thanks for the reply
There is so much info on this thread 
i have just added this to one of my miners

*/5 *  *   *   *     cgminer-api devs | grep "MHS 5s] => 0.00" && /sbin/reboot
in Scheduled Tasks

so lets see if that helps

also  have upgraded the firmware to 20130923 (yes i did do a backup first) 

What does that task do exactly?

i found it here
https://bitcointalk.org/index.php?topic=303376.msg3362789#msg3362789

ok slight change to this
if you set it to list
*/5 *  *   *   *     cgminer-api devs | grep "MHS 5s] => ....\.." && /sbin/reboot
once the miner gets below 10000 Ghz the server will reboot

i am testing this on 2 miners that have had this problem

i will let you know how i get on.

pjcltd,

I woke up to mine in that non hashing mode again.

Hows the task working for you? What does the ...\.. mean?

Thanks.

[GrapeApe]

I'm sorry to post this a second time but what settings do I change to be able to remotely view the Avalons cgminer stats?

Edit: Never mind I see the answer several pages back.

Hi
witch page is it on ?

It does accept port 80, so create a rule on your firewall to port forward some external port to your Avalon on port 80. ie. incoming port -> TCP 37000 to 192.168.1.99 ->TCP 80, this way from the outside you will have to http://externalIP:37000/ to see the webpage on the Avalon.

Thanks that was the first thing I tried xxxx->80 and it didn't work but will give it another go.

[pjcltd]

pjcltd,

I woke up to mine in that non hashing mode again.

Hows the task working for you? What does the ...\.. mean?

Thanks.
[/quote]

OK
what we need to add is this
*/5 *  *   *   *     cgminer-api devs | grep "MHS 5s] => ....\.." && /sbin/reboot

ok the ....\.. bit means that we are looking for a hashing speed less than 10000 mhz and if it  finds it
it will reboot the miner and this will clear the cache issue.

i have also added

*/5 *  *   *   *      cat /proc/loadavg | grep "2.\."  && /sbin/reboot
this will check the CPU load every 5 mins and if it finds that the cpu load is high then it will reboot the miner

I have 4 miners with this setup and they have all been working all day (i'm in the UK)
i would have normally had to reboot them twice today.

I'm not saying that this has fixed the issue but its a dam good start at a workaround.

Let me know how you get on with this.
(don't forget this only adds 2 checks in your scheduled tasks and nothing else
if you find this has not worked for you let me know.

[jddebug]

pjcltd,

I woke up to mine in that non hashing mode again.

Hows the task working for you? What does the ...\.. mean?

Thanks.

OK
what we need to add is this
*/5 *  *   *   *     cgminer-api devs | grep "MHS 5s] => ....\.." && /sbin/reboot

ok the ....\.. bit means that we are looking for a hashing speed less than 10000 mhz and if it  finds it
it will reboot the miner and this will clear the cache issue.

i have also added

*/5 *  *   *   *      cat /proc/loadavg | grep "2.\."  && /sbin/reboot
this will check the CPU load every 5 mins and if it finds that the cpu load is high then it will reboot the miner

I have 4 miners with this setup and they have all been working all day (i'm in the UK)
i would have normally had to reboot them twice today.

I'm not saying that this has fixed the issue but its a dam good start at a workaround.

Let me know how you get on with this.
(don't forget this only adds 2 checks in your scheduled tasks and nothing else
if you find this has not worked for you let me know.

[/quote]

I'm trying to understand how ...\.. = 10000 mhz  I tried a google search and nothing.

What do you mean by this? (don't forget this only adds 2 checks in your scheduled tasks and nothing else

Thanks,

jddebug (linux newbie)

[pjcltd]

pjcltd,

I woke up to mine in that non hashing mode again.

Hows the task working for you? What does the ...\.. mean?

Thanks.

OK
what we need to add is this
*/5 *  *   *   *     cgminer-api devs | grep "MHS 5s] => ....\.." && /sbin/reboot

ok the ....\.. bit means that we are looking for a hashing speed less than 10000 mhz and if it  finds it
it will reboot the miner and this will clear the cache issue.

i have also added

*/5 *  *   *   *      cat /proc/loadavg | grep "2.\."  && /sbin/reboot
this will check the CPU load every 5 mins and if it finds that the cpu load is high then it will reboot the miner

I have 4 miners with this setup and they have all been working all day (i'm in the UK)
i would have normally had to reboot them twice today.

I'm not saying that this has fixed the issue but its a dam good start at a workaround.

Let me know how you get on with this.
(don't forget this only adds 2 checks in your scheduled tasks and nothing else
if you find this has not worked for you let me know.

I'm trying to understand how ...\.. = 10000 mhz  I tried a google search and nothing.

What do you mean by this? (don't forget this only adds 2 checks in your scheduled tasks and nothing else

Thanks,

jddebug (linux newbie)


[/quote]

ok when you use 'grep' to find something in a file you can use wildcards
i am using ....\.. to look for any number thats less than 10000 that has a decimal point
i.e.
9959.01 = match (reboot the miner)
10110.11  = no match (do nothing)

hope that makes a bit more sense

'What do you mean by this? (don't forget this only adds 2 checks in your scheduled tasks and nothing else'
ok i am just telling everyone that we are adding 2 check's into the system.
some times people will get you to add things to your miner that could cause you issues.

[jddebug]

Is the fact that the task is invoked logged anywhere? I'm thinking it would be handy to know which task and how often its happening. Not necessary but would be interesting. I guess just watching how long its been running will tell me that its been run.

Thanks for the explanations. I'm going to add it to mine now too.

Whats the temperature where your miners are? I'm wondering if its caused by them getting to warm or ?

[pjcltd]

Is the fact that the task is invoked logged anywhere? I'm thinking it would be handy to know which task and how often its happening. Not necessary but would be interesting. I guess just watching how long its been running will tell me that its been run.

Thanks for the explanations. I'm going to add it to mine now too.

Whats the temperature where your miners are? I'm wondering if its caused by them getting to warm or ?

Hi ok you can see if it's been called in your system logs
As for temps


34 46 50

Mine are in a small garage
3 side by side
I also have a knc 275ghz miner
2 * bfl sc 60

Not sure on the temp in there as I have fans pulling in the cold air at the bottom of the doors and a big fan pushing the hot air out at the top

[crazyearner]

any idea when you will of fixed the new Avalon firmware as I noticed Bad next to it

[-ck]

any idea when you will of fixed the new Avalon firmware as I noticed Bad next to it

I'm a bit worried because I didn't change anything from how I usually built firmware and it was fine for me, yet it was bad for the 2 users who tried it, so until I can figure out what the actual issue was, I won't release a newer one.

[jermwerty]

any idea when you will of fixed the new Avalon firmware as I noticed Bad next to it

I'm a bit worried because I didn't change anything from how I usually built firmware and it was fine for me, yet it was bad for the 2 users who tried it, so until I can figure out what the actual issue was, I won't release a newer one.

ck - Always been a huge fan of your releases, thanks for all the great work!  

I had a buddy just upgrade his to the latest release no issue, I was about to until I saw the -bad also...  Is it just not coming back up on restart for people or  He says he gets better performance with the new firmware so I really wanted to try it probably will do so tomorrow on one of the minis since it sounds like we can still recover.  Anyone else tried it with either success or fail?

[-ck]

any idea when you will of fixed the new Avalon firmware as I noticed Bad next to it

I'm a bit worried because I didn't change anything from how I usually built firmware and it was fine for me, yet it was bad for the 2 users who tried it, so until I can figure out what the actual issue was, I won't release a newer one.

ck - Always been a huge fan of your releases, thanks for all the great work!  

I had a buddy just upgrade his to the latest release no issue, I was about to until I saw the -bad also...  Is it just not coming back up on restart for people or  He says he gets better performance with the new firmware so I really wanted to try it probably will do so tomorrow on one of the minis since it sounds like we can still recover.  Anyone else tried it with either success or fail?

You're welcome. Mine certainly took longer than usual to come up after flashing to that one, but it's been working very well except for my status line not showing up as per normal. However if you read the posts from the two people who tried it, theirs didn't come up at all (no idea why!?). It's fixable if that happens though (see my post later on on how to reset it), it's not like it bricks the avalon.

[Pyr3x]

What is considered too hot temperature wise for an Avalon mini?

[ste0024]

Ooops typo on my part but I guess you weren't smart enough to figure that out... it needs to be support@ not suppor@ LOL

i send same message to this email but their never answer. how to lost BTC with avalon

[driksson]

Just to clarify, In Network settings for ethernet I will be manually setting IPv4 to 192.168.1.2 and then using the terminal to ssh 192.168.1.1.
(Just tried this and ssh connection timed out)

EDIT: And yes, was using your most recent FW, booted first time (with non-saved settings), then could not connect once reset. Was I missing something?

If you have set the IPv4 address of your avalon to 192.168.1.2 you also have to ssh to the same address or use your webbrowser (the address of the avalon thus 192.168.1.2).

Cheers

Thanks, but I am still getting 'connection refused' when trying to ssh.  With and without hitting the reset button. Hrmmm.

It's telnet, not ssh from what i know in failsafe mode.

[-ck]

Here's the full and very confusing link

http://wiki.openwrt.org/doc/howto/generic.failsafe

But yes, telnet is supposed to work first after a reset before you need ssh.

[driksson]

Here's the full and very confusing link

http://wiki.openwrt.org/doc/howto/generic.failsafe

But yes, telnet is supposed to work first after a reset before you need ssh.

That could be. Also there is a config file with the fixed ip on normal boot when in failsafe mode (that could be reason of not able to access it in browser mode as the ip could become an old one, was the case for me).

this is where you set ip in openwrt if you entered it wrong:
vi /etc/config/network
config interface 'lan'
        option ifname 'eth0'
        option type 'bridge'
        option proto 'static'
        option ipaddr '192.168.0.100'
        option netmask '255.255.255.0'
        option gateway '192.168.0.1'
        option broadcast ''
        option dns ''

[bitcad]

So I have managed to get failsafe working (thru telnet), but running into problems when trying to ssh.

root@(none):/# ssh 192.168.1.1 -l root
ssh: Exited: Error connecting: Connection timed out
root@(none):/# ssh 192.168.1.2 -l root
ssh: Exited: Error connecting: Connection refused

Here's the full and very confusing link

http://wiki.openwrt.org/doc/howto/generic.failsafe

But yes, telnet is supposed to work first after a reset before you need ssh.

[driksson]

So I have managed to get failsafe working (thru telnet), but running into problems when trying to ssh.

root@(none):/# ssh 192.168.1.1 -l root
ssh: Exited: Error connecting: Connection timed out
root@(none):/# ssh 192.168.1.2 -l root
ssh: Exited: Error connecting: Connection refused

Here's the full and very confusing link

http://wiki.openwrt.org/doc/howto/generic.failsafe

But yes, telnet is supposed to work first after a reset before you need ssh.

Hm, if you are logged in on telnet, where are you trying to connect with ssh? i mean, the failsafe is already running on telnet for you to access. and it shows that you are logged in..

I suggest you, when logged in on telnet do:
more /etc/config/network

Show the output here. I assume it is a fixed ip-address you set a while back.
Put your pc on an ip on the same subnet, with that, you will be able to access the web admin using the ip you got from the above command and configure the unit again.