 Show Posts
|
|
Pages: [1]
|
|
18Lew8uugRR8phFdsWT29DGVxHsquXFDD4
|
|
|
|
I imagine I would do this from the SSH (putty) instance on the machine that i have modified already? ie: scp /etc/config/asic-freq-high 192.168.1.201:/etc/config
scp /etc/config/asic-freq-low 192.168.1.201:/etc/config
scp crontab 192.168.1.201:/ I imagine that it the crontab copy method will not work like this though? is it possible to do something like this to have it operate to all IP addresses with antminer units (and is a user/pass not needed for each?)?: scp /etc/config/asic-freq-high 192.168.1.201-192.168.1.220:/etc/config
scp /etc/config/asic-freq-low 192.168.1.201-192.168.1.220:/etc/config
scp crontab 192.168.1.201-192.168.1.220:/ You can optimize little bit, but it's not possible to make it for every antminer at once. Not without certificates and scripting. scp /etc/config/asic-freq-* 192.168.1.201:/etc/config
scp /etc/crontabs/root 192.168.1.201:/etc/crontabs |
|
|
|
Is there any easy way to modify files for this (the two asic-freq files and crontab) on all my miners simultaneously?
Simultaneously not, but there is faster way then edit everything again and again. You can copy files directly from one antminer to another. For example: scp /etc/config/asic-freq-high 192.168.something.something:/etc/config |
|
|
|
My both miners were redirected to 46.28.205.80 again. I hate thieves. I received nothing from last round because of them... Someone should do something about that.
I fyou have access to your router you might go in and block the IP. You won't get anything but neither will they. Thanks for the tip. I have already added rule to iptables into one of my antminers to drop all packets to this address, but he went offline and did not reconnect. Now I made better solution. I made simple script which is executed every minute by cron. It kills cgminer if connection to this address is detected. |
|
|
|
|
My both miners were redirected to 46.28.205.80 again. I hate thieves. I received nothing from last round because of them... Someone should do something about that.
|
|
|
|
I will receive my s1 next week, what altcoins you mine with s1? . And i want to buy a corsair cx750m is a good psu? Thanks
You will spend to much money for PSU, just go for dell poweredge 2950 750w and it will cost you like $25 or 15gbp The more powerful versions of those server power supplies (2000w) that can handle 3-4 S1s are the only way to go if you have an isolated remote set-up where jetnoise is a non issue because the cost advantage over ATX form factor power supplies is huge. On the other hand if your just looking to power 1 or 2 S1's in your house I would rather go the with an ATX PS that just plugs right in without the need for adapters or soldering wires, is quiet and can be reused for other things or easily sold. This jet noise is easy to work around with adding resistor 47kohm to red wire on psu fan. This resistor will lower speed about 2/3 which is more than enough cool and keep noise down. 47 kOhm is nonsense. You probably mean 47 Ohm... But guys, you should really care about psu efficiency, not price. If it's running 24/7, it's much more important. |
|
|
|
I have a question that is probably already answered somewhere, but, I haven't been able to find the answer.
The "MH/s" shown on the "My Account" page, for each worker. Over what time period is that? I assume it's an average over some time period, but, what is the time period?
Thanks....
current round It's not true. Column name is "Mhash/s*". And below that is "* Average hash rate in last 60 minutes. Calculated each 5 minutes.". I really think that this means, that it's not calculated over whole current round  |
|
|
|
It looks like my share count is not reflectingon the Slush. anyone having this as well?
Because SLush changed algorithm and table "workers" is not working as it should now. It is showing shares in last 60 minutes, not last round. So there is still almost the same values in column "Current shares". But we have bigger problem. When you are pirated the column "Current shares" shows 0. |
|
|
|
Pool users should check their connections to Slush. I noticed with two miners that I hadn't submitted a share in the last ten minutes. My miners were showing that they were still connected to pool 0, but 46.28.205.80 instead of the normal address. There is talk on Eligius about a malicious player doing a man in the middle attack, it's worth reading up on.
I had this problem about 3 times in last few days. 15 minutes ago my both antminers were submitting work and nothing looked different, but for about one hour they were sending results somewhere else, because slush pool was reporting 0 shares. After reconnection everything is ok again... I really hate how many thieves are attracted around bitcoin. It might be that the password is left to default, so it's the same password to all ants if it wasn't changed. I guess the 'thief' needs to find the IP and then log into that ant's account using the well known default password. Or maybe the other 2 pools weren't changed, so if Slush is down, it switches to the other default pool which was preset by Bitmain. Just a thought. No it's not my case. I don't have default passwords and antminer was showing that he is submitting work to Slush pool. And my only failover pool in ant configuration is my bitcoin wallet a it wasn't used. |
|
|
|
Pool users should check their connections to Slush. I noticed with two miners that I hadn't submitted a share in the last ten minutes. My miners were showing that they were still connected to pool 0, but 46.28.205.80 instead of the normal address. There is talk on Eligius about a malicious player doing a man in the middle attack, it's worth reading up on.
I had this problem about 3 times in last few days. 15 minutes ago my both antminers were submitting work and nothing looked different, but for about one hour they were sending results somewhere else, because slush pool was reporting 0 shares. After reconnection everything is ok again... I really hate how many thieves are attracted around bitcoin. |
|
|
|
I have undervolted my Antminer to 1,0V (R3 = 3.9kOhm) and I am really happy with results. Before mod my antminer was consuming 348W on the wall on 180GH/s but now it takes only 260W on 165GH/s. So 8,3% performance decrease means 25.3% power input decrease. Nice  I am running about hour now and no HW errors at all. I also tried 180GH/s with lowered voltage, but a lot of HW errors resulted in 170GH/s output performance too. Mod was really easy. 10 minutes of work and everything worked on the first try. Thanks for the guide. |
|
|
|
|
