Hey everyone,
I'm tearing apart the LUCI interface and am trying to figure out how to call the 'Save&Apply' button though the CLI. I want to edit the crontab. Really wish it were just a php controller or something....
Topic: ANTMINER S3+ Discussion and Support Thread - page 337. (Read 710164 times)
Are they really loud? If they are truly running the indicated RPM that would be a little loud.
Just reflashed them both. Fan 1 on both units 5500 and 6000 rpm. Fan 2 on both units 10350 and 11050.
Anyone seeing weird fan speeds with Batch 4? I got fans showing 9000 rpm's.
Yes, it's the first thing that I noticed right after checking to see if there were any x's or -'s.
Now that is odd because I think the max RPMs from the B1 fans are 3700-3900. Please let us know if rebooting or reloading the firmware helps.
This is a problem...on this particular boot its showing a time difference of 24 minutes which causes this result...Im sure I have seen as much as 8-9 hour difference between the uptimes
This miner was rebooted only 3 minutes yet the miner status page claims its been running 27 minutes which is impossible and the "hashrate" shows it...so how often is the cgminer process restarting behind the scenes or what is going on here BITMAIN?
How did you reboot it? Web UI, or ssh? I see this whenever I reboot through ssh... or if I just turn off the PSU. If I reboot through the web UI, or if I use the poweroff command in ssh, everything comes back up properly.This miner was rebooted only 3 minutes yet the miner status page claims its been running 27 minutes which is impossible and the "hashrate" shows it...so how often is the cgminer process restarting behind the scenes or what is going on here BITMAIN?
I rebooted through the web interface reboot option...when I power off via PSU Im suspecting that is when the multiple hour time difference happens and that is when the times are reversed...the miner status page shows minutes and the main miner uptime claims to be hours...haven't tested that aspect enough...for the record when I first turn the machines on the first thing I also do is go in and reboot them through the UI..have done this since S1 days...so many issues so many miners so little time
I can confirm that this is the case with all of my B3 miners. SSH reboots cause the cgminer uptime to be erroneous upon restart. Web interface restarts reset the values appropriately.
I have managed to keep my hash rate at about 420gh on both units but only by using 218 (212 in the cases where 218 is not stable) and by restarting cgminer every 2 hours. Any longer and the hashrates begins to fall below 380 and begins the slow pull down of the average hashrate value.
Anyone seeing weird fan speeds with Batch 4? I got fans showing 9000 rpm's.
Also looked at the firmware in the kernel log and mine is showing July 28. No corresponding FW on Bitmain's webiste.
Also looked at the firmware in the kernel log and mine is showing July 28. No corresponding FW on Bitmain's webiste.
Same here, I've got 4860/8580 and 2700/7860. 2700 is probably correct, but the other three certainly aren't!
As for the firmware, both of mine have July 21...
Code:
[ 0.000000] Linux version 3.10.12 (xxl@ubuntu) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2013.05 r38031) ) #140 Mon Jul 21 17:27:04 CST 2014
Anyone seeing weird fan speeds with Batch 4? I got fans showing 9000 rpm's.
Yes, it's the first thing that I noticed right after checking to see if there were any x's or -'s.
Anyone seeing weird fan speeds with Batch 4? I got fans showing 9000 rpm's.
Also looked at the firmware in the kernel log and mine is showing July 28. No corresponding FW on Bitmain's webiste.
Also looked at the firmware in the kernel log and mine is showing July 28. No corresponding FW on Bitmain's webiste.
I'm a very very satisfied b1 customer. Miners have been running without a hitch for almost two weeks now with no problem whatsoever. To get them up and hashing took less effort than what I thought. I still have the beeping from the original firmware and haven't flashed it yet. But the beeps aren't too bad, and I don't want to take them offline while they are hashing so well.
Are people happy with their S3 units on p2pool?
If you're on p2pool, are you using the stock queue option (4096) or did you change it?
If you're on p2pool, are you using the stock queue option (4096) or did you change it?
I'm very happy with the performance of my S3s on p2pool so far, my second batch is arriving today and will pointed at p2pool without a doubt.
Its just a better pool
I have been testing the queue set to 1 on a single machine, after 21 hours the results are as follows:
queue=1 error rate: 0.00086971453%
queue=4096 error rate: 0.00180255332 %
It is worth noting that both of these are impressively low, I'll keep testing with a couple more machines, but I'm 99% confident queue =1 is the way to go.
do me a favor clock accepted shares for two days with 1 and for 2 days with 4096 use a diff of 256 test it on p2p . mine come today I will run them on btcguild and give my results
This is a problem...on this particular boot its showing a time difference of 24 minutes which causes this result...Im sure I have seen as much as 8-9 hour difference between the uptimes
This miner was rebooted only 3 minutes yet the miner status page claims its been running 27 minutes which is impossible and the "hashrate" shows it...so how often is the cgminer process restarting behind the scenes or what is going on here BITMAIN?
How did you reboot it? Web UI, or ssh? I see this whenever I reboot through ssh... or if I just turn off the PSU. If I reboot through the web UI, or if I use the poweroff command in ssh, everything comes back up properly.This miner was rebooted only 3 minutes yet the miner status page claims its been running 27 minutes which is impossible and the "hashrate" shows it...so how often is the cgminer process restarting behind the scenes or what is going on here BITMAIN?
I rebooted through the web interface reboot option...when I power off via PSU Im suspecting that is when the multiple hour time difference happens and that is when the times are reversed...the miner status page shows minutes and the main miner uptime claims to be hours...haven't tested that aspect enough...for the record when I first turn the machines on the first thing I also do is go in and reboot them through the UI..have done this since S1 days...so many issues so many miners so little time
Question: Does this batch 4 come with the new firware? Anyone know which batch has what firmware? How can I tell which firmware my new B4 has on it? I flashed a few of them, but maybe its not smart enough to know it already has the latest firmware on it.
Go to "Status" "Kernel Log". The first line looks like this:[ 0.000000] Linux version 3.10.12 (xxl@ubuntu) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2013.05 r38031) ) #140 Mon Jul 21 17:27:04 CST 2014The highlighted part is your firmware version. Look at the .bin file name. The date is encoded in the name and you should compare it with this.
Are people happy with their S3 units on p2pool?
If you're on p2pool, are you using the stock queue option (4096) or did you change it?
If you're on p2pool, are you using the stock queue option (4096) or did you change it?
I'm very happy with the performance of my S3s on p2pool so far, my second batch is arriving today and will pointed at p2pool without a doubt.
Its just a better pool
I have been testing the queue set to 1 on a single machine, after 21 hours the results are as follows:
queue=1 error rate: 0.00086971453%
queue=4096 error rate: 0.00180255332 %
It is worth noting that both of these are impressively low, I'll keep testing with a couple more machines, but I'm 99% confident queue =1 is the way to go.
I ran for 36 hours with a very low return (I know 3 days to level out) on P2P but I did get a share. The queue was set stock to 4096 (yes I changed it back to test more for those who have read this entire thread) then I changed it back to Queue=1 and within minuets my chart started going up and now starting day 3 from making the change it looks like it is going where it should be. Now could this have been luck/variance/coincidence, not sure some may say yes or just dumb luck. Take it for what it's worth but I made the change around 8 PM. What you do not see is the level remaining below 4.0mBTC for the first ~24 hours. There is also a very good P2P thread https://bitcointalk.org/index.php?topic=18313.9840
Batch 4 in the house - Will update later
Point a few of these S3's to my P2Pool
Point a few of these S3's to my P2Pool
any advantage of P2Pool over eligius?
Batch 4 in the house - Will update later
Point a few of these S3's to my P2Pool
Point a few of these S3's to my P2Pool
Question: Does this batch 4 come with the new firware? Anyone know which batch has what firmware? How can I tell which firmware my new B4 has on it? I flashed a few of them, but maybe its not smart enough to know it already has the latest firmware on it.
Bitmain uses the date the firmware version was created at the start of the file name.Ok, I guess I can see that where you upload the firmware? I will check it next time I plug in another S3 batch 4. (still have a few to set up)
Question: Does this batch 4 come with the new firware? Anyone know which batch has what firmware? How can I tell which firmware my new B4 has on it? I flashed a few of them, but maybe its not smart enough to know it already has the latest firmware on it.
Bitmain uses the date the firmware version was created at the start of the file name. 
I did a PSU power off reboot and when it came back up it said it was running for 45 minutes so even thought the 5sec hashrate is fine the average is in the toilet.
I hope Bitmain is working on a firmware update for these S3's...lots of little things like this could use to be fixed.
I hope Bitmain is working on a firmware update for these S3's...lots of little things like this could use to be fixed.
obviously a bug, however, web gui reboot fixes it...Direct PSU reboot messes everything up for me too, so i either use web gui or "poweroff -d 3" command in ssh with 3 being a number of sec before the shutdown and could be different from 3. In the latter case, after disconnect, fans continue to run for 20 sec or so.
Question: Does this batch 4 come with the new firware? Anyone know which batch has what firmware? How can I tell which firmware my new B4 has on it? I flashed a few of them, but maybe its not smart enough to know it already has the latest firmware on it.
This is a problem...on this particular boot its showing a time difference of 24 minutes which causes this result...Im sure I have seen as much as 8-9 hour difference between the uptimes
This miner was rebooted only 3 minutes yet the miner status page claims its been running 27 minutes which is impossible and the "hashrate" shows it...so how often is the cgminer process restarting behind the scenes or what is going on here BITMAIN?
How did you reboot it? Web UI, or ssh? I see this whenever I reboot through ssh... or if I just turn off the PSU. If I reboot through the web UI, or if I use the poweroff command in ssh, everything comes back up properly.This miner was rebooted only 3 minutes yet the miner status page claims its been running 27 minutes which is impossible and the "hashrate" shows it...so how often is the cgminer process restarting behind the scenes or what is going on here BITMAIN?
I just had one do this for the first time today. I did a PSU power off reboot and when it came back up it said it was running for 45 minutes so even thought the 5sec hashrate is fine the average is in the toilet.
I hope Bitmain is working on a firmware update for these S3's...lots of little things like this could use to be fixed.
Jump to: