demkd
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 06:45:58 AM |
|
grishnakhMake sure that your PSU is not dead before doing anything. You can try restore factory defaults: (I never try it ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) ) picture https://en.bitcoin.it/wiki/File:Avalon-703n-front.JPG1. Reboot (Power Down and then UP) 2. When the blue LED starts flashing, press the SW2 button 3. Stop pressing the SW2 when the blue LED starts flashing quickly At this time the router is in failsafe mode. 4. Telnet 192.168.0.100. It will take you to the root prompt. 5. Enter "firstboot" at the prompt to reset the router to defaults 6. Restart If router is dead you can replace it with tplink 703n or connect avalon to computer via USB.
|
|
|
|
mtbitcoin
Legendary
Offline
Activity: 876
Merit: 1000
Etherscan.io
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 08:19:43 AM |
|
Hi, I'm having restarts every hour. Currently running the 20130703 firmware on my #2 module unit and 20130627 on my #4 module unit (I just merged 4 modules in another case).
Lower your overclock to 350 or less. As mentioned by another poster your HW% error rate seems above the norm
|
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 08:50:44 AM |
|
... Diff1shares vs DiffA ...
Diff1shares = work done DiffA = work accepted by the pool
|
|
|
|
GenTarkin
Legendary
Offline
Activity: 2450
Merit: 1002
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 09:02:29 AM |
|
... Diff1shares vs DiffA ...
Diff1shares = work done DiffA = work accepted by the pool ty =) I figured that... but I still cant make sense of the differences between the 2. I put vardiff on 1 one on the pool. Rejects + Stales + HW errors .. still dont come close to the difference between diff1 & diffa .. over a few hour period.
|
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 10:03:29 AM |
|
... Diff1shares vs DiffA ...
Diff1shares = work done DiffA = work accepted by the pool ty =) I figured that... but I still cant make sense of the differences between the 2. I put vardiff on 1 one on the pool. Rejects + Stales + HW errors .. still dont come close to the difference between diff1 & diffa .. over a few hour period. Well - since I wrote most of the original Icarus driver the Avalon was based on and wrote miner.php that the screen is based on I am assuming that they didn't screw it up ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) ckolivas did mention that the error counting was different in the avalon code (why? NFI) and I guess they could have used other fields to display the ones there ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif) On any other device the numbers are: Summary: "Accepted" and "Rejected" are at whatever difficulty each share is, so don't mean much, but "Difficulty Accepted" and "Difficulty Rejected" are of course the diff1 difficulty of all "Accepted" and "Rejected" shares. "Hardware Errors" are diff1. (WD) "Work Utility" * "Elapsed" / 60 is the amount of work done. There is, of course, no direct relationship between (WD) and "Difficulty Accepted", "Difficulty Rejected" and "Hardware Errors" (There's an FAQ I wrote in the README about that, that probably explains the answer to your question) At the pool level: "Diff1 Shares" is the number of nonces found, so that also doesn't correlate to any of the others directly either (except WD). The Avalon itself doesn't actually know how much work it has done. Although it was copied from the Icarus driver, the Avalon hardware is too random to work out exactly how much work it is doing, so it counts nonces to determine a good estimate of it ... however it is an estimate, not exact. Anyway, my suggestion would be to use the API directly and check the values there and then compare them to the screen to see if they have changed the name of anything. If not, then what I've said is the answer ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
tnkflx
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 10:38:49 AM |
|
Just as an aside, I am currently touring through Europe for the next 6 weeks. So while I will have generous internet access at times to answer questions, there is close to zero chance of me creating new firmware, especially since my main development machine with build environments and so on decided to fail about 1 hour before I left home and I just left it off in disgust. So please keep your requests on hold till then.
Care to elaborate which countries? ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
| Operating electrum.be & us.electrum.be |
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 10:40:38 AM |
|
I have a retail TP-Link 703n flashed with the Avalon software. It is running on my network so I can learn the interface before delivery.
Today I notice a large number of attempts to log in as root from 59.53.94.9 This may be an address in China, no DNS names are returned after the chinatelecom.10gigabitethernet6-1.core1.lax1.he.net hop.
Where did you find the logs for login attempts ? On the web page. status --> system log Do you suspect a backdoor or information leakage? Of course I do. But I don't think it passes the sanity test. In case anyone was still being paranoid about this ... ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif) If you have it on the internet, such issues are normal. I see at least a few hundred failed logins each day on my own and client servers connected to the internet. ... and yes China is a common source of those attempts.
|
|
|
|
grishnakh
Newbie
Offline
Activity: 49
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 11:17:39 AM |
|
grishnakhMake sure that your PSU is not dead before doing anything. You can try restore factory defaults: (I never try it ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) ) picture https://en.bitcoin.it/wiki/File:Avalon-703n-front.JPG1. Reboot (Power Down and then UP) 2. When the blue LED starts flashing, press the SW2 button 3. Stop pressing the SW2 when the blue LED starts flashing quickly At this time the router is in failsafe mode. 4. Telnet 192.168.0.100. It will take you to the root prompt. 5. Enter "firstboot" at the prompt to reset the router to defaults 6. Restart If router is dead you can replace it with tplink 703n or connect avalon to computer via USB. Thanks. I did the reset and got it back working after several failed attempts. Is it a normal symptom of OCing too much that the tplink stops responding? I'm trying to figure out what caused the problem, and how to prevent it.
|
|
|
|
demkd
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 12:05:22 PM |
|
Is it a normal symptom of OCing too much that the tplink stops responding?
No, but may be router overheating is a cause and active wi-fi interface is not a good idea. Avalon cooling is implemented extremely poorly so overheating common problem for PSU & router.
|
|
|
|
elasticband
Legendary
Offline
Activity: 1036
Merit: 1000
Nighty Night Don't Let The Trolls Bite Nom Nom Nom
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 12:09:36 PM |
|
Hi, I'm having restarts every hour. Currently running the 20130703 firmware on my #2 module unit and 20130627 on my #4 module unit (I just merged 4 modules in another case). ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Flookpic.com%2FO%2Fi2%2F339%2FSVjpXRaP.png&t=665&c=KVJ85zysN50T8A) I'm running stable at 375Mh/s with the other unit I have but still getting hashing power below the estimated 160Gh/s in total (I'm loosing 30 Gh/s !!). Maybe the restarts I'm having is due to the damaged board I received? Who knows how to locate the non-working piece? I already measured the temperature of each chip (they're all hot) ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) did you blow your avalon up yet? around 30% hadware errors i think. why would you think you can do this?
|
|
|
|
cypherdoc
Legendary
Offline
Activity: 1764
Merit: 1002
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 03:52:04 PM |
|
ok, what's all this mean? Sun Jul 7 12:40:05 2013 auth.info kernel: [126520.850000] eth0: link down Sun Jul 7 12:40:05 2013 auth.info kernel: [126520.850000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 12:40:07 2013 auth.info kernel: [126522.850000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 12:40:07 2013 auth.info kernel: [126522.850000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:40:07 2013 auth.info kernel: [126522.860000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:40:09 2013 auth.info kernel: [126524.860000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:42:01 2013 news.info crond[827]: crond: USER root pid 32406 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:44:01 2013 news.info crond[827]: crond: USER root pid 32557 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:46:01 2013 news.info crond[827]: crond: USER root pid 32708 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:48:01 2013 news.info crond[827]: crond: USER root pid 393 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:50:01 2013 news.info crond[827]: crond: USER root pid 545 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:52:01 2013 news.info crond[827]: crond: USER root pid 697 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:52:33 2013 auth.info kernel: [127269.050000] eth0: link down Sun Jul 7 12:52:33 2013 auth.info kernel: [127269.050000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 12:52:34 2013 auth.info kernel: [127270.050000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 12:52:34 2013 auth.info kernel: [127270.050000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:52:34 2013 auth.info kernel: [127270.060000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:52:36 2013 auth.info kernel: [127272.060000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:54:01 2013 news.info crond[827]: crond: USER root pid 852 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:56:01 2013 news.info crond[827]: crond: USER root pid 1007 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:58:01 2013 news.info crond[827]: crond: USER root pid 1158 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:00:01 2013 news.info crond[827]: crond: USER root pid 1309 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:01:58 2013 auth.info kernel: [127834.200000] eth0: link down Sun Jul 7 13:01:58 2013 auth.info kernel: [127834.200000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:01:59 2013 auth.info kernel: [127835.200000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:01:59 2013 auth.info kernel: [127835.200000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:01:59 2013 auth.info kernel: [127835.210000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:02:01 2013 auth.info kernel: [127837.210000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:02:01 2013 news.info crond[827]: crond: USER root pid 1460 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:04:01 2013 news.info crond[827]: crond: USER root pid 1611 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:05:15 2013 auth.info kernel: [128031.260000] eth0: link down Sun Jul 7 13:05:15 2013 auth.info kernel: [128031.260000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:05:16 2013 auth.info kernel: [128032.260000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:05:16 2013 auth.info kernel: [128032.260000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:05:16 2013 auth.info kernel: [128032.270000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:05:18 2013 auth.info kernel: [128034.270000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:06:01 2013 news.info crond[827]: crond: USER root pid 1762 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:08:01 2013 news.info crond[827]: crond: USER root pid 1913 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:08:56 2013 auth.info kernel: [128252.280000] eth0: link down Sun Jul 7 13:08:56 2013 auth.info kernel: [128252.280000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:08:58 2013 auth.info kernel: [128254.280000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:08:58 2013 auth.info kernel: [128254.280000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:08:58 2013 auth.info kernel: [128254.290000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:09:00 2013 auth.info kernel: [128256.300000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:10:01 2013 news.info crond[827]: crond: USER root pid 2064 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:11:00 2013 auth.info kernel: [128376.320000] eth0: link down Sun Jul 7 13:11:00 2013 auth.info kernel: [128376.320000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:11:01 2013 auth.info kernel: [128377.320000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:11:01 2013 auth.info kernel: [128377.320000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:11:01 2013 auth.info kernel: [128377.330000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:11:03 2013 auth.info kernel: [128379.330000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:12:01 2013 news.info crond[827]: crond: USER root pid 2215 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:14:01 2013 news.info crond[827]: crond: USER root pid 2366 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:16:01 2013 news.info crond[827]: crond: USER root pid 2517 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:18:01 2013 news.info crond[827]: crond: USER root pid 2668 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:20:01 2013 news.info crond[827]: crond: USER root pid 2819 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:22:01 2013 news.info crond[827]: crond: USER root pid 2970 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:23:15 2013 auth.info kernel: [129111.440000] eth0: link down Sun Jul 7 13:23:15 2013 auth.info kernel: [129111.440000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:23:16 2013 auth.info kernel: [129112.440000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:23:16 2013 auth.info kernel: [129112.440000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:23:16 2013 auth.info kernel: [129112.450000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:23:18 2013 auth.info kernel: [129114.450000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:24:01 2013 news.info crond[827]: crond: USER root pid 3121 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:26:01 2013 news.info crond[827]: crond: USER root pid 3272 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:28:01 2013 news.info crond[827]: crond: USER root pid 3423 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:30:01 2013 news.info crond[827]: crond: USER root pid 3574 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:32:01 2013 news.info crond[827]: crond: USER root pid 3725 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:34:01 2013 news.info crond[827]: crond: USER root pid 3876 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:36:01 2013 news.info crond[827]: crond: USER root pid 4027 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:38:01 2013 news.info crond[827]: crond: USER root pid 4178 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:40:01 2013 news.info crond[827]: crond: USER root pid 4330 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:42:01 2013 news.info crond[827]: crond: USER root pid 4481 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:44:01 2013 news.info crond[827]: crond: USER root pid 4632 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:46:01 2013 news.info crond[827]: crond: USER root pid 4783 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:48:01 2013 news.info crond[827]: crond: USER root pid 4934 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:50:01 2013 news.info crond[827]: crond: USER root pid 5083 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:52:01 2013 news.info crond[827]: crond: USER root pid 5234 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:54:01 2013 news.info crond[827]: crond: USER root pid 5385 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:55:59 2013 auth.info kernel: [131074.880000] eth0: link down Sun Jul 7 13:55:59 2013 auth.info kernel: [131074.880000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:56:00 2013 auth.info kernel: [131075.880000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:56:00 2013 auth.info kernel: [131075.880000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:56:00 2013 auth.info kernel: [131075.890000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:56:01 2013 news.info crond[827]: crond: USER root pid 5536 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:56:02 2013 auth.info kernel: [131077.890000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:58:01 2013 news.info crond[827]: crond: USER root pid 5687 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:00:01 2013 news.info crond[827]: crond: USER root pid 5838 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:02:01 2013 news.info crond[827]: crond: USER root pid 5989 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:04:01 2013 news.info crond[827]: crond: USER root pid 6140 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:04:50 2013 auth.info kernel: [131605.980000] eth0: link down Sun Jul 7 14:04:50 2013 auth.info kernel: [131605.980000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 14:04:51 2013 auth.info kernel: [131606.980000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 14:04:51 2013 auth.info kernel: [131606.980000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:04:51 2013 auth.info kernel: [131606.990000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:04:53 2013 auth.info kernel: [131608.990000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:06:01 2013 news.info crond[827]: crond: USER root pid 6291 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:08:01 2013 news.info crond[827]: crond: USER root pid 6442 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:10:01 2013 news.info crond[827]: crond: USER root pid 6593 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:12:01 2013 news.info crond[827]: crond: USER root pid 6744 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:13:21 2013 auth.info kernel: [132117.060000] eth0: link down Sun Jul 7 14:13:21 2013 auth.info kernel: [132117.060000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 14:13:23 2013 auth.info kernel: [132119.060000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 14:13:23 2013 auth.info kernel: [132119.060000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:13:23 2013 auth.info kernel: [132119.070000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:13:25 2013 auth.info kernel: [132121.070000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:14:01 2013 news.info crond[827]: crond: USER root pid 6895 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:16:01 2013 news.info crond[827]: crond: USER root pid 7046 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:18:01 2013 news.info crond[827]: crond: USER root pid 7197 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:20:01 2013 news.info crond[827]: crond: USER root pid 7348 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:21:05 2013 auth.info kernel: [132581.170000] eth0: link down Sun Jul 7 14:21:05 2013 auth.info kernel: [132581.170000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 14:21:06 2013 auth.info kernel: [132582.170000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 14:21:06 2013 auth.info kernel: [132582.170000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:21:06 2013 auth.info kernel: [132582.180000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:21:08 2013 auth.info kernel: [132584.180000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:22:01 2013 news.info crond[827]: crond: USER root pid 7499 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:24:01 2013 news.info crond[827]: crond: USER root pid 7650 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:26:01 2013 news.info crond[827]: crond: USER root pid 7801 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:28:01 2013 news.info crond[827]: crond: USER root pid 7952 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:30:01 2013 news.info crond[827]: crond: USER root pid 8103 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:32:01 2013 news.info crond[827]: crond: USER root pid 8254 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:34:01 2013 news.info crond[827]: crond: USER root pid 8405 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:36:01 2013 news.info crond[827]: crond: USER root pid 8556 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:38:01 2013 news.info crond[827]: crond: USER root pid 8707 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:40:01 2013 news.info crond[827]: crond: USER root pid 8873 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:42:01 2013 news.info crond[827]: crond: USER root pid 9038 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:44:01 2013 news.info crond[827]: crond: USER root pid 9203 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:46:01 2013 news.info crond[827]: crond: USER root pid 9354 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:48:01 2013 news.info crond[827]: crond: USER root pid 9520 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:49:22 2013 auth.info kernel: [134278.470000] eth0: link down Sun Jul 7 14:49:22 2013 auth.info kernel: [134278.470000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 14:49:23 2013 auth.info kernel: [134279.470000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 14:49:23 2013 auth.info kernel: [134279.470000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:49:23 2013 auth.info kernel: [134279.480000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:49:25 2013 auth.info kernel: [134281.480000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:50:01 2013 news.info crond[827]: crond: USER root pid 9671 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:52:01 2013 news.info crond[827]: crond: USER root pid 9822 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:54:01 2013 news.info crond[827]: crond: USER root pid 9973 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:56:01 2013 news.info crond[827]: crond: USER root pid 10124 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:58:01 2013 news.info crond[827]: crond: USER root pid 10275 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:00:01 2013 news.info crond[827]: crond: USER root pid 10426 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:02:01 2013 news.info crond[827]: crond: USER root pid 10577 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:04:01 2013 news.info crond[827]: crond: USER root pid 10728 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:06:01 2013 news.info crond[827]: crond: USER root pid 10879 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:08:01 2013 news.info crond[827]: crond: USER root pid 11030 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:08:54 2013 auth.info kernel: [135449.690000] eth0: link down Sun Jul 7 15:08:54 2013 auth.info kernel: [135449.690000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 15:08:55 2013 auth.info kernel: [135450.690000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 15:08:55 2013 auth.info kernel: [135450.690000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:08:55 2013 auth.info kernel: [135450.700000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:08:57 2013 auth.info kernel: [135452.700000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:10:01 2013 news.info crond[827]: crond: USER root pid 11181 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:12:01 2013 news.info crond[827]: crond: USER root pid 11332 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:14:01 2013 news.info crond[827]: crond: USER root pid 11483 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:16:01 2013 news.info crond[827]: crond: USER root pid 11634 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:18:01 2013 news.info crond[827]: crond: USER root pid 11785 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:20:01 2013 news.info crond[827]: crond: USER root pid 11937 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:22:01 2013 news.info crond[827]: crond: USER root pid 12088 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:24:01 2013 news.info crond[827]: crond: USER root pid 12239 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:26:01 2013 news.info crond[827]: crond: USER root pid 12390 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:28:01 2013 news.info crond[827]: crond: USER root pid 12539 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:30:01 2013 news.info crond[827]: crond: USER root pid 12704 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:32:01 2013 news.info crond[827]: crond: USER root pid 12855 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:32:49 2013 auth.info kernel: [136884.960000] eth0: link down Sun Jul 7 15:32:49 2013 auth.info kernel: [136884.960000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 15:32:50 2013 auth.info kernel: [136885.960000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 15:32:50 2013 auth.info kernel: [136885.960000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:32:50 2013 auth.info kernel: [136885.970000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:32:52 2013 auth.info kernel: [136887.970000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:34:01 2013 news.info crond[827]: crond: USER root pid 13006 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:36:01 2013 news.info crond[827]: crond: USER root pid 13171 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:38:01 2013 news.info crond[827]: crond: USER root pid 13322 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:40:01 2013 news.info crond[827]: crond: USER root pid 13473 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:42:01 2013 news.info crond[827]: crond: USER root pid 13624 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:44:01 2013 news.info crond[827]: crond: USER root pid 13775 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:45:28 2013 auth.info kernel: [137644.140000] eth0: link down Sun Jul 7 15:45:28 2013 auth.info kernel: [137644.140000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 15:45:29 2013 auth.info kernel: [137645.140000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 15:45:29 2013 auth.info kernel: [137645.140000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:45:29 2013 auth.info kernel: [137645.150000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:45:31 2013 auth.info kernel: [137647.150000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:46:01 2013 news.info crond[827]: crond: USER root pid 13926 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:48:01 2013 news.info crond[827]: crond: USER root pid 14077 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:50:01 2013 news.info crond[827]: crond: USER root pid 14228 cmd /usr/bin/cgminer-monitor the cgminer status page looks perfectly normal.
|
|
|
|
Bogart
Legendary
Offline
Activity: 966
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 04:36:51 PM |
|
Is it a normal symptom of OCing too much that the tplink stops responding?
No, but may be router overheating is a cause and active wi-fi interface is not a good idea. Avalon cooling is implemented extremely poorly so overheating common problem for PSU & router. Make sure the DHCP service in the Avalon is disabled. Network --> Interfaces --> Edit --> Disable DHCP for this interface
|
"All safe deposit boxes in banks or financial institutions have been sealed... and may only be opened in the presence of an agent of the I.R.S." - President F.D. Roosevelt, 1933
|
|
|
Bogart
Legendary
Offline
Activity: 966
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 04:38:45 PM |
|
ok, what's all this mean? Sun Jul 7 12:40:05 2013 auth.info kernel: [126520.850000] eth0: link down Sun Jul 7 12:40:05 2013 auth.info kernel: [126520.850000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 12:40:07 2013 auth.info kernel: [126522.850000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 12:40:07 2013 auth.info kernel: [126522.850000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:40:07 2013 auth.info kernel: [126522.860000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:40:09 2013 auth.info kernel: [126524.860000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:42:01 2013 news.info crond[827]: crond: USER root pid 32406 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:44:01 2013 news.info crond[827]: crond: USER root pid 32557 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:46:01 2013 news.info crond[827]: crond: USER root pid 32708 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:48:01 2013 news.info crond[827]: crond: USER root pid 393 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:50:01 2013 news.info crond[827]: crond: USER root pid 545 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:52:01 2013 news.info crond[827]: crond: USER root pid 697 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:52:33 2013 auth.info kernel: [127269.050000] eth0: link down Sun Jul 7 12:52:33 2013 auth.info kernel: [127269.050000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 12:52:34 2013 auth.info kernel: [127270.050000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 12:52:34 2013 auth.info kernel: [127270.050000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:52:34 2013 auth.info kernel: [127270.060000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:52:36 2013 auth.info kernel: [127272.060000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 12:54:01 2013 news.info crond[827]: crond: USER root pid 852 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:56:01 2013 news.info crond[827]: crond: USER root pid 1007 cmd /usr/bin/cgminer-monitor Sun Jul 7 12:58:01 2013 news.info crond[827]: crond: USER root pid 1158 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:00:01 2013 news.info crond[827]: crond: USER root pid 1309 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:01:58 2013 auth.info kernel: [127834.200000] eth0: link down Sun Jul 7 13:01:58 2013 auth.info kernel: [127834.200000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:01:59 2013 auth.info kernel: [127835.200000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:01:59 2013 auth.info kernel: [127835.200000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:01:59 2013 auth.info kernel: [127835.210000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:02:01 2013 auth.info kernel: [127837.210000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:02:01 2013 news.info crond[827]: crond: USER root pid 1460 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:04:01 2013 news.info crond[827]: crond: USER root pid 1611 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:05:15 2013 auth.info kernel: [128031.260000] eth0: link down Sun Jul 7 13:05:15 2013 auth.info kernel: [128031.260000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:05:16 2013 auth.info kernel: [128032.260000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:05:16 2013 auth.info kernel: [128032.260000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:05:16 2013 auth.info kernel: [128032.270000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:05:18 2013 auth.info kernel: [128034.270000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:06:01 2013 news.info crond[827]: crond: USER root pid 1762 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:08:01 2013 news.info crond[827]: crond: USER root pid 1913 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:08:56 2013 auth.info kernel: [128252.280000] eth0: link down Sun Jul 7 13:08:56 2013 auth.info kernel: [128252.280000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:08:58 2013 auth.info kernel: [128254.280000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:08:58 2013 auth.info kernel: [128254.280000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:08:58 2013 auth.info kernel: [128254.290000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:09:00 2013 auth.info kernel: [128256.300000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:10:01 2013 news.info crond[827]: crond: USER root pid 2064 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:11:00 2013 auth.info kernel: [128376.320000] eth0: link down Sun Jul 7 13:11:00 2013 auth.info kernel: [128376.320000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:11:01 2013 auth.info kernel: [128377.320000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:11:01 2013 auth.info kernel: [128377.320000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:11:01 2013 auth.info kernel: [128377.330000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:11:03 2013 auth.info kernel: [128379.330000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:12:01 2013 news.info crond[827]: crond: USER root pid 2215 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:14:01 2013 news.info crond[827]: crond: USER root pid 2366 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:16:01 2013 news.info crond[827]: crond: USER root pid 2517 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:18:01 2013 news.info crond[827]: crond: USER root pid 2668 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:20:01 2013 news.info crond[827]: crond: USER root pid 2819 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:22:01 2013 news.info crond[827]: crond: USER root pid 2970 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:23:15 2013 auth.info kernel: [129111.440000] eth0: link down Sun Jul 7 13:23:15 2013 auth.info kernel: [129111.440000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:23:16 2013 auth.info kernel: [129112.440000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:23:16 2013 auth.info kernel: [129112.440000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:23:16 2013 auth.info kernel: [129112.450000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:23:18 2013 auth.info kernel: [129114.450000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:24:01 2013 news.info crond[827]: crond: USER root pid 3121 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:26:01 2013 news.info crond[827]: crond: USER root pid 3272 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:28:01 2013 news.info crond[827]: crond: USER root pid 3423 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:30:01 2013 news.info crond[827]: crond: USER root pid 3574 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:32:01 2013 news.info crond[827]: crond: USER root pid 3725 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:34:01 2013 news.info crond[827]: crond: USER root pid 3876 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:36:01 2013 news.info crond[827]: crond: USER root pid 4027 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:38:01 2013 news.info crond[827]: crond: USER root pid 4178 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:40:01 2013 news.info crond[827]: crond: USER root pid 4330 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:42:01 2013 news.info crond[827]: crond: USER root pid 4481 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:44:01 2013 news.info crond[827]: crond: USER root pid 4632 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:46:01 2013 news.info crond[827]: crond: USER root pid 4783 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:48:01 2013 news.info crond[827]: crond: USER root pid 4934 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:50:01 2013 news.info crond[827]: crond: USER root pid 5083 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:52:01 2013 news.info crond[827]: crond: USER root pid 5234 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:54:01 2013 news.info crond[827]: crond: USER root pid 5385 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:55:59 2013 auth.info kernel: [131074.880000] eth0: link down Sun Jul 7 13:55:59 2013 auth.info kernel: [131074.880000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 13:56:00 2013 auth.info kernel: [131075.880000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 13:56:00 2013 auth.info kernel: [131075.880000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:56:00 2013 auth.info kernel: [131075.890000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:56:01 2013 news.info crond[827]: crond: USER root pid 5536 cmd /usr/bin/cgminer-monitor Sun Jul 7 13:56:02 2013 auth.info kernel: [131077.890000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 13:58:01 2013 news.info crond[827]: crond: USER root pid 5687 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:00:01 2013 news.info crond[827]: crond: USER root pid 5838 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:02:01 2013 news.info crond[827]: crond: USER root pid 5989 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:04:01 2013 news.info crond[827]: crond: USER root pid 6140 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:04:50 2013 auth.info kernel: [131605.980000] eth0: link down Sun Jul 7 14:04:50 2013 auth.info kernel: [131605.980000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 14:04:51 2013 auth.info kernel: [131606.980000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 14:04:51 2013 auth.info kernel: [131606.980000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:04:51 2013 auth.info kernel: [131606.990000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:04:53 2013 auth.info kernel: [131608.990000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:06:01 2013 news.info crond[827]: crond: USER root pid 6291 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:08:01 2013 news.info crond[827]: crond: USER root pid 6442 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:10:01 2013 news.info crond[827]: crond: USER root pid 6593 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:12:01 2013 news.info crond[827]: crond: USER root pid 6744 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:13:21 2013 auth.info kernel: [132117.060000] eth0: link down Sun Jul 7 14:13:21 2013 auth.info kernel: [132117.060000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 14:13:23 2013 auth.info kernel: [132119.060000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 14:13:23 2013 auth.info kernel: [132119.060000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:13:23 2013 auth.info kernel: [132119.070000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:13:25 2013 auth.info kernel: [132121.070000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:14:01 2013 news.info crond[827]: crond: USER root pid 6895 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:16:01 2013 news.info crond[827]: crond: USER root pid 7046 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:18:01 2013 news.info crond[827]: crond: USER root pid 7197 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:20:01 2013 news.info crond[827]: crond: USER root pid 7348 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:21:05 2013 auth.info kernel: [132581.170000] eth0: link down Sun Jul 7 14:21:05 2013 auth.info kernel: [132581.170000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 14:21:06 2013 auth.info kernel: [132582.170000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 14:21:06 2013 auth.info kernel: [132582.170000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:21:06 2013 auth.info kernel: [132582.180000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:21:08 2013 auth.info kernel: [132584.180000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:22:01 2013 news.info crond[827]: crond: USER root pid 7499 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:24:01 2013 news.info crond[827]: crond: USER root pid 7650 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:26:01 2013 news.info crond[827]: crond: USER root pid 7801 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:28:01 2013 news.info crond[827]: crond: USER root pid 7952 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:30:01 2013 news.info crond[827]: crond: USER root pid 8103 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:32:01 2013 news.info crond[827]: crond: USER root pid 8254 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:34:01 2013 news.info crond[827]: crond: USER root pid 8405 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:36:01 2013 news.info crond[827]: crond: USER root pid 8556 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:38:01 2013 news.info crond[827]: crond: USER root pid 8707 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:40:01 2013 news.info crond[827]: crond: USER root pid 8873 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:42:01 2013 news.info crond[827]: crond: USER root pid 9038 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:44:01 2013 news.info crond[827]: crond: USER root pid 9203 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:46:01 2013 news.info crond[827]: crond: USER root pid 9354 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:48:01 2013 news.info crond[827]: crond: USER root pid 9520 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:49:22 2013 auth.info kernel: [134278.470000] eth0: link down Sun Jul 7 14:49:22 2013 auth.info kernel: [134278.470000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 14:49:23 2013 auth.info kernel: [134279.470000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 14:49:23 2013 auth.info kernel: [134279.470000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:49:23 2013 auth.info kernel: [134279.480000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:49:25 2013 auth.info kernel: [134281.480000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 14:50:01 2013 news.info crond[827]: crond: USER root pid 9671 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:52:01 2013 news.info crond[827]: crond: USER root pid 9822 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:54:01 2013 news.info crond[827]: crond: USER root pid 9973 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:56:01 2013 news.info crond[827]: crond: USER root pid 10124 cmd /usr/bin/cgminer-monitor Sun Jul 7 14:58:01 2013 news.info crond[827]: crond: USER root pid 10275 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:00:01 2013 news.info crond[827]: crond: USER root pid 10426 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:02:01 2013 news.info crond[827]: crond: USER root pid 10577 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:04:01 2013 news.info crond[827]: crond: USER root pid 10728 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:06:01 2013 news.info crond[827]: crond: USER root pid 10879 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:08:01 2013 news.info crond[827]: crond: USER root pid 11030 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:08:54 2013 auth.info kernel: [135449.690000] eth0: link down Sun Jul 7 15:08:54 2013 auth.info kernel: [135449.690000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 15:08:55 2013 auth.info kernel: [135450.690000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 15:08:55 2013 auth.info kernel: [135450.690000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:08:55 2013 auth.info kernel: [135450.700000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:08:57 2013 auth.info kernel: [135452.700000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:10:01 2013 news.info crond[827]: crond: USER root pid 11181 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:12:01 2013 news.info crond[827]: crond: USER root pid 11332 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:14:01 2013 news.info crond[827]: crond: USER root pid 11483 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:16:01 2013 news.info crond[827]: crond: USER root pid 11634 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:18:01 2013 news.info crond[827]: crond: USER root pid 11785 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:20:01 2013 news.info crond[827]: crond: USER root pid 11937 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:22:01 2013 news.info crond[827]: crond: USER root pid 12088 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:24:01 2013 news.info crond[827]: crond: USER root pid 12239 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:26:01 2013 news.info crond[827]: crond: USER root pid 12390 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:28:01 2013 news.info crond[827]: crond: USER root pid 12539 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:30:01 2013 news.info crond[827]: crond: USER root pid 12704 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:32:01 2013 news.info crond[827]: crond: USER root pid 12855 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:32:49 2013 auth.info kernel: [136884.960000] eth0: link down Sun Jul 7 15:32:49 2013 auth.info kernel: [136884.960000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 15:32:50 2013 auth.info kernel: [136885.960000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 15:32:50 2013 auth.info kernel: [136885.960000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:32:50 2013 auth.info kernel: [136885.970000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:32:52 2013 auth.info kernel: [136887.970000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:34:01 2013 news.info crond[827]: crond: USER root pid 13006 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:36:01 2013 news.info crond[827]: crond: USER root pid 13171 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:38:01 2013 news.info crond[827]: crond: USER root pid 13322 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:40:01 2013 news.info crond[827]: crond: USER root pid 13473 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:42:01 2013 news.info crond[827]: crond: USER root pid 13624 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:44:01 2013 news.info crond[827]: crond: USER root pid 13775 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:45:28 2013 auth.info kernel: [137644.140000] eth0: link down Sun Jul 7 15:45:28 2013 auth.info kernel: [137644.140000] br-lan: port 1(eth0) entered disabled state Sun Jul 7 15:45:29 2013 auth.info kernel: [137645.140000] eth0: link up (100Mbps/Full duplex) Sun Jul 7 15:45:29 2013 auth.info kernel: [137645.140000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:45:29 2013 auth.info kernel: [137645.150000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:45:31 2013 auth.info kernel: [137647.150000] br-lan: port 1(eth0) entered forwarding state Sun Jul 7 15:46:01 2013 news.info crond[827]: crond: USER root pid 13926 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:48:01 2013 news.info crond[827]: crond: USER root pid 14077 cmd /usr/bin/cgminer-monitor Sun Jul 7 15:50:01 2013 news.info crond[827]: crond: USER root pid 14228 cmd /usr/bin/cgminer-monitor the cgminer status page looks perfectly normal. It looks like your ethernet link is unstable and resets some. I'd check the cable and maybe try a different switch port.
|
"All safe deposit boxes in banks or financial institutions have been sealed... and may only be opened in the presence of an agent of the I.R.S." - President F.D. Roosevelt, 1933
|
|
|
Bogart
Legendary
Offline
Activity: 966
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 04:43:04 PM |
|
I have 3 Avalons and I'm working on putting in a dedicated circuit in the basement for them. At an estimated 2100 watts at 110v (USA), I'm looking at 19A, which just pushes the limits of standard 20A breakers, with no room for future expansion.
What I've been thinking is that I can wire up an outlet at 220v, get slightly better power efficiency, and reduce my amps to about 10A, leaving plenty of room for future boxes.
Can anyone advise on a proper wiring diagram for 220v that's compatible with the 3-pin input on the Avalon PSUs?
As of right now, my understanding is that I'd wire black and white both to hot (on a dual-pole 20A breaker) and ground to ground, with no neutral. I should get 220v with the two hots as the breaker pulls in 110 and -110 for the two hots. I know I would need to get the correct outlets for 220v also as well as adapters or proper 220v PSU cables.
http://en.wikipedia.org/wiki/IEC_60320 . The biggest and longest pin is PE. Sorry, I don't understand your response. The C13 connector for the PSU has three pins that are all the same size. The middle pin is ground, and I assume I'd wire my two hot leads to the other two. For the receptacle, I was looking at something like this. Yup, that's correct. I have mine wired up that way, though I'm just using regular 120V-style outlets wired for 240V rather than using a special (proper) outlet and custom cable. BTW, in the US the actual voltage is 120/240V, not 110/220V.
|
"All safe deposit boxes in banks or financial institutions have been sealed... and may only be opened in the presence of an agent of the I.R.S." - President F.D. Roosevelt, 1933
|
|
|
GenTarkin
Legendary
Offline
Activity: 2450
Merit: 1002
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 06:19:47 PM |
|
... Diff1shares vs DiffA ...
Diff1shares = work done DiffA = work accepted by the pool ty =) I figured that... but I still cant make sense of the differences between the 2. I put vardiff on 1 one on the pool. Rejects + Stales + HW errors .. still dont come close to the difference between diff1 & diffa .. over a few hour period. Well - since I wrote most of the original Icarus driver the Avalon was based on and wrote miner.php that the screen is based on I am assuming that they didn't screw it up ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) ckolivas did mention that the error counting was different in the avalon code (why? NFI) and I guess they could have used other fields to display the ones there ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif) On any other device the numbers are: Summary: "Accepted" and "Rejected" are at whatever difficulty each share is, so don't mean much, but "Difficulty Accepted" and "Difficulty Rejected" are of course the diff1 difficulty of all "Accepted" and "Rejected" shares. "Hardware Errors" are diff1. (WD) "Work Utility" * "Elapsed" / 60 is the amount of work done. There is, of course, no direct relationship between (WD) and "Difficulty Accepted", "Difficulty Rejected" and "Hardware Errors" (There's an FAQ I wrote in the README about that, that probably explains the answer to your question) At the pool level: "Diff1 Shares" is the number of nonces found, so that also doesn't correlate to any of the others directly either (except WD). The Avalon itself doesn't actually know how much work it has done. Although it was copied from the Icarus driver, the Avalon hardware is too random to work out exactly how much work it is doing, so it counts nonces to determine a good estimate of it ... however it is an estimate, not exact. Anyway, my suggestion would be to use the API directly and check the values there and then compare them to the screen to see if they have changed the name of anything. If not, then what I've said is the answer ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Thanks for the answer. I guess, it comes down to MHSAV right? Doesnt that take everything into account and reflect pretty much what is valid and going to the pool?
|
|
|
|
alexKKK
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 82
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 06:26:00 PM |
|
A huge thank you for your dev work on cgminer and the customizations for the avalon. The July 3 firmware is rock solid, running for 4+ hrs on my units without restarts. The auto-overclocking is just way cool too.
1 BTC donation sent your way.
Keep up the great work!
Thanks ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Can I just take a step back now and point out to people there is absolutely no way I could have developed the avalon code to this level of maturity and features if I didn't have one myself. Avalon themselves offered me only one module to develop on, or to deliver me one quickly if I purchased one at a slight discount, and this was only at Xiangfu's insistence, who was their developer and understands how important developer access to hardware is. I'm certainly not happy that I actually had to pay for it since I never intended to be one of their customers effectively doing the software for their hardware for free, so I was torn about whether I should or not, but ultimately knowing it would pay itself off anyway I gave in. Ckolivas Thank you for bugs-free firmware for ours Avalons ! i donated 0.4+0.4+0.4 btc
|
|
|
|
AvenG
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 133
Merit: 101
Res Et Non Verbum
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 06:45:23 PM |
|
did you blow your avalon up yet? around 30% hadware errors i think. why would you think you can do this?
I have been running stable my batch #1 Avalon at 375mh/s with 3 modules since Strombom released his firmware.. believe me it's never going to blow up, I'm also using a 1600w PSU. I could manage to perform it smoothly for more than 2 days without restarts since >3 weeks. Now the problem is different, as you can see I got my batch #2 unit.. unfortunately the results are not as expected. I received a damaged module and it's causing me troubles. This explain the high HW rate. I couldn't figure out yet how to recognize the bad PCB in order to replace it. BTW, I already changed the freq. at 350mh/s but still getting a high HW error rate.. As Ckolivas stated, HW is not going to damage your unit is just a pointer of wasted energy. Currently I'm wasting 30 Gh/s and energy ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) I 'll donate to anyone who help me figuring out this.
|
not for sale
|
|
|
GenTarkin
Legendary
Offline
Activity: 2450
Merit: 1002
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 06:53:12 PM |
|
did you blow your avalon up yet? around 30% hadware errors i think. why would you think you can do this?
I have been running stable my batch #1 Avalon at 375mh/s with 3 modules since Strombom released his firmware.. believe me it's never going to blow up, I'm also using a 1600w PSU. I could manage to perform it smoothly for more than 2 days without restarts since >3 weeks. Now the problem is different, as you can see I got my batch #2 unit.. unfortunately the results are not as expected. I received a damaged module and it's causing me troubles. This explain the high HW rate. I couldn't figure out yet how to recognize the bad PCB in order to replace it. BTW, I already changed the freq. at 350mh/s but still getting a high HW error rate.. As Ckolivas stated, HW is not going to damage your unit is just a pointer of wasted energy. Currently I'm wasting 30 Gh/s and energy ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) I 'll donate to anyone who help me figuring out this. Im confused dude.... if the module is damaged... wouldnt you think the HW Error rate is going to be really high? lol...
|
|
|
|
BenTuras
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 06:58:58 PM |
|
Have a look at the Cgminer API Log, and check the match_work_countNN for the 24/32 chips. You'll probably see some out of ordinary values there. Have a look at mine:
[match_work_count1] => 8721 [match_work_count2] => 8502 [match_work_count3] => 937 [match_work_count4] => 0 [match_work_count5] => 8377 [match_work_count6] => 8735
Clearly 3 and 4 are not happy.
|
|
|
|
elasticband
Legendary
Offline
Activity: 1036
Merit: 1000
Nighty Night Don't Let The Trolls Bite Nom Nom Nom
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2013, 07:54:58 PM |
|
did you blow your avalon up yet? around 30% hadware errors i think. why would you think you can do this?
I have been running stable my batch #1 Avalon at 375mh/s with 3 modules since Strombom released his firmware.. believe me it's never going to blow up, I'm also using a 1600w PSU. I could manage to perform it smoothly for more than 2 days without restarts since >3 weeks. Now the problem is different, as you can see I got my batch #2 unit.. unfortunately the results are not as expected. I received a damaged module and it's causing me troubles. This explain the high HW rate. I couldn't figure out yet how to recognize the bad PCB in order to replace it. BTW, I already changed the freq. at 350mh/s but still getting a high HW error rate.. As Ckolivas stated, HW is not going to damage your unit is just a pointer of wasted energy. Currently I'm wasting 30 Gh/s and energy ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) I 'll donate to anyone who help me figuring out this. tun it on 345MHZ, this runs much more stable for me, or 355
|
|
|
|
|