Pages:
Author

Topic: Avalon ASIC users thread - page 59. (Read 438739 times)

legendary
Activity: 1778
Merit: 1003
NodeMasters
October 29, 2013, 10:45:17 AM
Long time Avalon owner.  Always had an issue on my Batch 2/3 4 module where if I oc'd too much I would get a decrease in GH eventually (sometimes 20-40%).  Run those @ 335 (auto 325-335) 24/7 around 107GH and they maybe restart cgminer once or twice a week but never slow down.  Really loved the 20130821 firmware.

So I now have 7 minis running (stock 20130723), and let me tell you now 2-3 of them have so far had this issue where they slow down to under 30GH as low as 4GH or so?  GAH!  Changed the worst two to 20130821 and will see.  However I am disappointed, it appears the --avalon-auto option doesn't work?    (currently set 350 clock on page with these options: --quiet --avalon-auto --avalon-temp 50 --avalon-cutoff 70 --avalon-freq 350-375 )  < Those settings never show above 350 on the status page.  Setting 375 manually works.   Huh


put a sheduled task to restart cgminer, hash is same, hw error increases. i had same issue, after restarting cgminer every 4 hrs untouched for weeks, and constant max..

im having problems with my miner dropping low hash rate after hashing for a while, how do i set a scheduled task to restart cgminer? sorry. very new here! thanks for any help

Scroll back a few pages. it's here!
hi if you start reading from here https://bitcointalksearch.org/topic/m.3419505

you should find the info you need
any problems let me know
sr. member
Activity: 294
Merit: 250
October 29, 2013, 10:30:43 AM
Long time Avalon owner.  Always had an issue on my Batch 2/3 4 module where if I oc'd too much I would get a decrease in GH eventually (sometimes 20-40%).  Run those @ 335 (auto 325-335) 24/7 around 107GH and they maybe restart cgminer once or twice a week but never slow down.  Really loved the 20130821 firmware.

So I now have 7 minis running (stock 20130723), and let me tell you now 2-3 of them have so far had this issue where they slow down to under 30GH as low as 4GH or so?  GAH!  Changed the worst two to 20130821 and will see.  However I am disappointed, it appears the --avalon-auto option doesn't work?    (currently set 350 clock on page with these options: --quiet --avalon-auto --avalon-temp 50 --avalon-cutoff 70 --avalon-freq 350-375 )  < Those settings never show above 350 on the status page.  Setting 375 manually works.   Huh


put a sheduled task to restart cgminer, hash is same, hw error increases. i had same issue, after restarting cgminer every 4 hrs untouched for weeks, and constant max..

im having problems with my miner dropping low hash rate after hashing for a while, how do i set a scheduled task to restart cgminer? sorry. very new here! thanks for any help

Scroll back a few pages. it's here!
member
Activity: 82
Merit: 10
October 29, 2013, 09:28:43 AM
Long time Avalon owner.  Always had an issue on my Batch 2/3 4 module where if I oc'd too much I would get a decrease in GH eventually (sometimes 20-40%).  Run those @ 335 (auto 325-335) 24/7 around 107GH and they maybe restart cgminer once or twice a week but never slow down.  Really loved the 20130821 firmware.

So I now have 7 minis running (stock 20130723), and let me tell you now 2-3 of them have so far had this issue where they slow down to under 30GH as low as 4GH or so?  GAH!  Changed the worst two to 20130821 and will see.  However I am disappointed, it appears the --avalon-auto option doesn't work?    (currently set 350 clock on page with these options: --quiet --avalon-auto --avalon-temp 50 --avalon-cutoff 70 --avalon-freq 350-375 )  < Those settings never show above 350 on the status page.  Setting 375 manually works.   Huh


put a sheduled task to restart cgminer, hash is same, hw error increases. i had same issue, after restarting cgminer every 4 hrs untouched for weeks, and constant max..

im having problems with my miner dropping low hash rate after hashing for a while, how do i set a scheduled task to restart cgminer? sorry. very new here! thanks for any help
member
Activity: 82
Merit: 10
October 29, 2013, 09:14:37 AM
hi guys, my avalon mini will be hashing at full capacity for close to 24 hrs and then all of the sudden drop to like 3gh/s, the machine continues to mine but at a reduced hashrate ~3-5gh/s. i have to log in to the avalon interface and reboot it before it will go back hashing at ~60gh/s, any idea why?

any help is appreciated! thanks!
sr. member
Activity: 294
Merit: 250
October 29, 2013, 09:09:21 AM
Man seriously, a handful of avalon minis, got server room up from 20dgr to 24dgr running 2 ac units on full 16dgr.
These would be incredible placeheaters if one would be deaf!
sr. member
Activity: 294
Merit: 250
October 29, 2013, 09:08:13 AM
So I have managed to get failsafe working (thru telnet), but running into problems when trying to ssh.
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.
newbie
Activity: 59
Merit: 0
October 28, 2013, 05:44:30 AM
So I have managed to get failsafe working (thru telnet), but running into problems when trying to ssh.
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.

sr. member
Activity: 294
Merit: 250
October 28, 2013, 05:41:18 AM
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 ''
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
October 28, 2013, 05:38:27 AM
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.
sr. member
Activity: 294
Merit: 250
October 28, 2013, 05:35:31 AM
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.
sr. member
Activity: 462
Merit: 250
October 28, 2013, 04:22:00 AM
Quote
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
full member
Activity: 602
Merit: 100
October 27, 2013, 11:17:14 PM
What is considered too hot temperature wise for an Avalon mini?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
October 27, 2013, 11:03:30 PM
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 Huh  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.
sr. member
Activity: 472
Merit: 250
October 27, 2013, 10:59:30 PM
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 Huh  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
legendary
Activity: 4088
Merit: 1631
Ruu \o/
October 27, 2013, 09:48:21 PM
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.
legendary
Activity: 1820
Merit: 1001
October 27, 2013, 09:19:41 PM
any idea when you will of fixed the new Avalon firmware as I noticed Bad next to it
legendary
Activity: 1778
Merit: 1003
NodeMasters
October 27, 2013, 05:46:41 PM
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
sr. member
Activity: 446
Merit: 250
October 27, 2013, 05:42:38 PM
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 ?
legendary
Activity: 1778
Merit: 1003
NodeMasters
October 27, 2013, 05:19:26 PM

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. Smiley

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.



sr. member
Activity: 446
Merit: 250
October 27, 2013, 05:11:55 PM

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. Smiley

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)

Pages:
Jump to: