sepehr
Sr. Member
 Offline
Activity: 399
Merit: 250
Cryptocurrency Evangelist
|
 |
November 23, 2014, 09:57:01 AM |
|
I have the miner plugged in to the router directly. I originally had it running on static IP 192.168.1.98. Router setting is default 192.168.1.1. I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware. I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31. Web interface works great on all three IPs but the thing just wont start hashing. The Red LED stays red when all my other miners red LED go out once its connected to pool. I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.
Log into the unit's web UI and change network to DHCP. Remember to apply the settings. It may change it's address after this, but that is all you have to do. yes, but he said it did not work, which is strange. maybe OP did not "save and apply" You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange. I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does. oh, well, he has enough info to figure it now. sometimes doing twice the same thing brings "them" to life for one mysterios reason or another. Any clue to solve this? I have the exact same issue and did everything but not succeeded! Please help! |
Sepehr, A Cryptocurrency Evangelist
|
|
|
|
|
|
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, which will follow the rules of the network no matter what miners do. Even if every miner decided to create 1000 bitcoins per block, full nodes would stick to the rules and reject those blocks.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
jackbox
Legendary
Offline
Activity: 1246
Merit: 1024
|
|
November 23, 2014, 10:02:31 AM |
|
I have the miner plugged in to the router directly. I originally had it running on static IP 192.168.1.98. Router setting is default 192.168.1.1. I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware. I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31. Web interface works great on all three IPs but the thing just wont start hashing. The Red LED stays red when all my other miners red LED go out once its connected to pool. I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.
Log into the unit's web UI and change network to DHCP. Remember to apply the settings. It may change it's address after this, but that is all you have to do. yes, but he said it did not work, which is strange. maybe OP did not "save and apply" You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange. I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does. oh, well, he has enough info to figure it now. sometimes doing twice the same thing brings "them" to life for one mysterios reason or another. Any clue to solve this? I have the exact same issue and did everything but not succeeded! Please help! An S3 will hash on a static IP but the subnet must be the same. For example if the static IP of the S3 is 198.162.1.99 then the network it is on must be 198.162.1.xxx. Many new routers come set to .2, .3 or another subnet to avoid IP conflicts with other devices. |
|
|
|
unkers
Newbie
Offline
Activity: 38
Merit: 0
|
|
November 23, 2014, 11:23:31 AM |
|
Good day guys! I need your help .. my s3 + ceased to see one card ... it is now running at half power board ... cold .. that it is possible to do .. or have everything  firmware me ... cut off the charge ... ((   |
|
|
|
|
jackbox
Legendary
Offline
Activity: 1246
Merit: 1024
|
|
November 23, 2014, 11:32:59 AM |
|
Good day guys! I need your help .. my s3 + ceased to see one card ... it is now running at half power board ... cold .. that it is possible to do .. or have everything firmware me ... cut off the charge ... (( Mine did that once. Turning off the power supply, waiting a bit and then turning back on fixed it. |
|
|
|
unkers
Newbie
Offline
Activity: 38
Merit: 0
|
|
November 23, 2014, 11:37:13 AM |
|
I tried, nothing changes? !! |
|
|
|
|
sepehr
Sr. Member
Offline
Activity: 399
Merit: 250
Cryptocurrency Evangelist
|
|
November 23, 2014, 12:36:00 PM |
|
I have the miner plugged in to the router directly. I originally had it running on static IP 192.168.1.98. Router setting is default 192.168.1.1. I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware. I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31. Web interface works great on all three IPs but the thing just wont start hashing. The Red LED stays red when all my other miners red LED go out once its connected to pool. I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.
Log into the unit's web UI and change network to DHCP. Remember to apply the settings. It may change it's address after this, but that is all you have to do. yes, but he said it did not work, which is strange. maybe OP did not "save and apply" You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange. I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does. oh, well, he has enough info to figure it now. sometimes doing twice the same thing brings "them" to life for one mysterios reason or another. Any clue to solve this? I have the exact same issue and did everything but not succeeded! Please help! An S3 will hash on a static IP but the subnet must be the same. For example if the static IP of the S3 is 198.162.1.99 then the network it is on must be 198.162.1.xxx. Many new routers come set to .2, .3 or another subnet to avoid IP conflicts with other devices. I have 26 S3's running on the same network all with static IP and same settings. This S3 have problem and the problem exactly as above user: The Red LED stays red when all my other miners red LED go out once its connected to pool. And Not hashing at all. I have access to GUI but hashing is 0 and fans are working fast. Any clue? |
Sepehr, A Cryptocurrency Evangelist
|
|
|
sepehr
Sr. Member
Offline
Activity: 399
Merit: 250
Cryptocurrency Evangelist
|
|
November 23, 2014, 12:53:13 PM |
|
I have the miner plugged in to the router directly. I originally had it running on static IP 192.168.1.98. Router setting is default 192.168.1.1. I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware. I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31. Web interface works great on all three IPs but the thing just wont start hashing. The Red LED stays red when all my other miners red LED go out once its connected to pool. I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.
Log into the unit's web UI and change network to DHCP. Remember to apply the settings. It may change it's address after this, but that is all you have to do. yes, but he said it did not work, which is strange. maybe OP did not "save and apply" You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange. I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does. oh, well, he has enough info to figure it now. sometimes doing twice the same thing brings "them" to life for one mysterios reason or another. Any clue to solve this? I have the exact same issue and did everything but not succeeded! Please help! An S3 will hash on a static IP but the subnet must be the same. For example if the static IP of the S3 is 198.162.1.99 then the network it is on must be 198.162.1.xxx. Many new routers come set to .2, .3 or another subnet to avoid IP conflicts with other devices. I have 26 S3's running on the same network all with static IP and same settings. This S3 have problem and the problem exactly as above user: The Red LED stays red when all my other miners red LED go out once its connected to pool. And Not hashing at all. I have access to GUI but hashing is 0 and fans are working fast. Any clue? Also in diagnostics my S3 can ping outside networks! |
Sepehr, A Cryptocurrency Evangelist
|
|
|
imagina
Newbie
Offline
Activity: 35
Merit: 0
|
|
November 23, 2014, 03:01:52 PM |
|
Hello,
I have a new s3+ that i am strugling to configure the load balance settings in the miner's web page.
Once i activate the load balance profile and configure the miner like:
"80;stratum_url:3333",
"20;stratum_url:3333" and
"0;stratum_url:3333"
the miner does not stratum to work.
I have tried to flash different firmware versions and the output is always the same.
Is anyone else having the same problem?
Cheers
|
|
|
|
|
|
hagbase
|
|
November 23, 2014, 03:10:41 PM |
|
Did u try balance instead of load balance? I'm using load balance with 2 pools without quota, both get 50% shares/ Gh/s. No Problem at all, works even with 3 pools.
|
|
|
|
|
unkers
Newbie
Offline
Activity: 38
Merit: 0
|
|
November 23, 2014, 03:11:02 PM |
|
himself a miner works, produces half the power ... a miner .. two boards in the menu there are two aysika .. I have not determined a capacity of 250 ... (( |
|
|
|
|
imagina
Newbie
Offline
Activity: 35
Merit: 0
|
|
November 23, 2014, 04:01:08 PM |
|
Did u try balance instead of load balance? I'm using load balance with 2 pools without quota, both get 50% shares/ Gh/s. No Problem at all, works even with 3 pools.
I did.. I am now running with the Balanced profile with three pools, but the pool that is placed on 3rd place is not very stable, it goes from 0Ghs to 130Ghs max, most of the time the pool is reporting that worker with 0Ghs.. Shouldn't the load balance profile work as it should? Is it a firmware/cgminer issue? Thank you |
|
|
|
|
jackbox
Legendary
Offline
Activity: 1246
Merit: 1024
|
|
November 23, 2014, 04:04:07 PM |
|
Did u try balance instead of load balance? I'm using load balance with 2 pools without quota, both get 50% shares/ Gh/s. No Problem at all, works even with 3 pools.
I did.. I am now running with the Balanced profile with three pools, but the pool that is placed on 3rd place is not very stable, it goes from 0Ghs to 130Ghs max, most of the time the pool is reporting that worker with 0Ghs.. Shouldn't the load balance profile work as it should? Is it a firmware/cgminer issue? Thank you Did you try another stratum server? It could just be a flakey stratum. I tested out load balancing on mine the other day and it seemed to work pretty well with one stratum having a slower hash rate. |
|
|
|
imagina
Newbie
Offline
Activity: 35
Merit: 0
|
|
November 23, 2014, 04:08:36 PM |
|
Did u try balance instead of load balance? I'm using load balance with 2 pools without quota, both get 50% shares/ Gh/s. No Problem at all, works even with 3 pools.
I did.. I am now running with the Balanced profile with three pools, but the pool that is placed on 3rd place is not very stable, it goes from 0Ghs to 130Ghs max, most of the time the pool is reporting that worker with 0Ghs.. Shouldn't the load balance profile work as it should? Is it a firmware/cgminer issue? Thank you Did you try another stratum server? It could just be a flakey stratum. I tested out load balancing on mine the other day and it seemed to work pretty well with one stratum having a slower hash rate. I did.. Same output. If i change the profile mode from load Balanced to Failover, the stratum servers work. Do you know what firmware version do you have? Cheers |
|
|
|
|
|
hagbase
|
|
November 23, 2014, 04:13:26 PM |
|
Latest firmware : antMiner_S320141024.bin
|
|
|
|
|
imagina
Newbie
Offline
Activity: 35
Merit: 0
|
|
November 23, 2014, 04:20:26 PM |
|
Latest firmware : antMiner_S320141024.bin
Same as mine.. have tried old firmware but the result is always the same.. |
|
|
|
|
heldertb
Full Member
Offline
Activity: 242
Merit: 100
Blockchain-based Financial Ecosystem
|
|
November 24, 2014, 01:43:36 PM |
|
I know this question has been asked before a long time ago, but I can't find it anymore...
Is there a way to automatically let an AntMiner S3 reboot every eg 24 hours?
Thank you!
|
Keep Crypto. Get Cash  █▮ The highest Loan-to-Value ratio ▮ No minimum monthly payments and no hidden fees ▮ Major cryptocurrencies as collateral ▮█ |
|
|
|
|
heldertb
Full Member
Offline
Activity: 242
Merit: 100
Blockchain-based Financial Ecosystem
|
|
November 24, 2014, 02:42:13 PM
Last edit: November 24, 2014, 02:56:07 PM by heldertb |
|
Thank you for your help, but I don't want cgminer to restart, I want the whole miner to reboot. Isn't there a linux command for rebooting with a timer like "shutdown -p 300" but then for rebooting? EDIT: I got it, the command is reboot -d [SECONDS], so you could type in the command in system > startup so the command will be executed at startup and will repeat everytime after boot! |
Keep Crypto. Get Cash █▮ The highest Loan-to-Value ratio ▮ No minimum monthly payments and no hidden fees ▮ Major cryptocurrencies as collateral ▮█ |
|
|
chinesebob
Newbie
Offline
Activity: 64
Merit: 0
|
|
November 24, 2014, 05:28:21 PM |
|
In Linux it would be "shutdown -r +1440" but, I'm not seeing a shutdown command on my S3, it has reboot, so that should be "reboot -d 86400"
heh, nevermind, looks like you found it already
|
|
|
|
|
|
pekatete
|
|
November 24, 2014, 05:33:07 PM |
|
Thank you for your help, but I don't want cgminer to restart, I want the whole miner to reboot. Isn't there a linux command for rebooting with a timer like "shutdown -p 300" but then for rebooting? EDIT: I got it, the command is reboot -d [SECONDS], so you could type in the command in system > startup so the command will be executed at startup and will repeat everytime after boot! Edit crontab via SSH like in the thread linked or WebUI via System -> Scheduled Tasks, and to reboot every day you'd add: 0 23 * * * /sbin/shutdown -rebootto reboot at 11 pm every day (you change the hour to suit). |
|
|
|
|
