dog1965
|
|
December 24, 2014, 12:15:34 AM |
|
|
|
|
|
|
|
Remember that Bitcoin is still beta software. Don't put all of your money into BTC!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
vabchgent
|
|
December 24, 2014, 12:45:18 AM |
|
Try running this command via SSH with the beta firmware. cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot I am not disputing its effectivenes, but what does that accomplish? Care to explain? Its essentially a factory reset except it preserves the network and pool settings, good to make sure you don't have any weird remnants from older firmwares. You need to be careful using this command it reset my miner and I had to use the rest button to get the miner back up and running. Thanks Dogie your firmware is awesome I had to use the resets below on my miner but so far so good. low hardware errors GHS look constant so far. I have to give it 24hrs but so far so good. uci set cgminer.default.voltage=0725 && uci commit uci set cgminer.default.freq=18:225:0882 && uci commit
|
|
|
|
bitsolutions
|
|
December 24, 2014, 12:51:27 AM |
|
Try running this command via SSH with the beta firmware. cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot I am not disputing its effectivenes, but what does that accomplish? Care to explain? Its essentially a factory reset except it preserves the network and pool settings, good to make sure you don't have any weird remnants from older firmwares. You need to be careful using this command it reset my miner and I had to use the rest button to get the miner back up and running. Thanks Were you on the beta Dec 19th firmware? I've tested this on about 300 miners without any issues.
|
Mining Software Developer.
|
|
|
vabchgent
|
|
December 24, 2014, 01:14:34 AM |
|
Try running this command via SSH with the beta firmware. cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot I am not disputing its effectivenes, but what does that accomplish? Care to explain? Its essentially a factory reset except it preserves the network and pool settings, good to make sure you don't have any weird remnants from older firmwares. You need to be careful using this command it reset my miner and I had to use the rest button to get the miner back up and running. Thanks Were you on the beta Dec 19th firmware? I've tested this on about 300 miners without any issues. I am on Dogies . I was having big problems with my miners dropping hash rate. Just waiting to see if it drops off again. I was sent the Dec 19th and it looks like Dogies is from the same date.
|
|
|
|
bitsolutions
|
|
December 24, 2014, 01:17:12 AM |
|
Try running this command via SSH with the beta firmware. cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot I am not disputing its effectivenes, but what does that accomplish? Care to explain? Its essentially a factory reset except it preserves the network and pool settings, good to make sure you don't have any weird remnants from older firmwares. You need to be careful using this command it reset my miner and I had to use the rest button to get the miner back up and running. Thanks Were you on the beta Dec 19th firmware? I've tested this on about 300 miners without any issues. I am on Dogies . I was having big problems with my miners dropping hash rate. Just waiting to see if it drops off again. I was sent the Dec 19th and it looks like Dogies is from the same date. Check the MD5 if you want to make sure. MD5 (antminer_S320141219.bin) = 7df1b12d28b25e10aac37e2eafc7397b
|
Mining Software Developer.
|
|
|
pekatete
|
|
December 24, 2014, 01:24:10 AM |
|
I am on Dogies . I was having big problems with my miners dropping hash rate. Just waiting to see if it drops off again. I was sent the Dec 19th and it looks like Dogies is from the same date.
What version of cgminer is on both dogie's and the 19th Dec firmware? log in via ssh and enter:
|
|
|
|
vabchgent
|
|
December 24, 2014, 01:25:47 AM |
|
Try running this command via SSH with the beta firmware. cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot I am not disputing its effectivenes, but what does that accomplish? Care to explain? Its essentially a factory reset except it preserves the network and pool settings, good to make sure you don't have any weird remnants from older firmwares. You need to be careful using this command it reset my miner and I had to use the rest button to get the miner back up and running. Thanks Were you on the beta Dec 19th firmware? I've tested this on about 300 miners without any issues. I am on Dogies . I was having big problems with my miners dropping hash rate. Just waiting to see if it drops off again. I was sent the Dec 19th and it looks like Dogies is from the same date. Check the MD5 if you want to make sure. MD5 (antminer_S320141219.bin) = 7df1b12d28b25e10aac37e2eafc7397b Do I pull that from the putty and whats the command. Thanks
|
|
|
|
dog1965
|
|
December 24, 2014, 02:30:02 AM |
|
Get a MD5 checker program. there free on google if you google it.
|
|
|
|
bitsolutions
|
|
December 24, 2014, 03:43:43 AM |
|
Try running this command via SSH with the beta firmware. cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot I am not disputing its effectivenes, but what does that accomplish? Care to explain? Its essentially a factory reset except it preserves the network and pool settings, good to make sure you don't have any weird remnants from older firmwares. You need to be careful using this command it reset my miner and I had to use the rest button to get the miner back up and running. Thanks Were you on the beta Dec 19th firmware? I've tested this on about 300 miners without any issues. I am on Dogies . I was having big problems with my miners dropping hash rate. Just waiting to see if it drops off again. I was sent the Dec 19th and it looks like Dogies is from the same date. Check the MD5 if you want to make sure. MD5 (antminer_S320141219.bin) = 7df1b12d28b25e10aac37e2eafc7397b Do I pull that from the putty and whats the command. Thanks no, you would run that check on the firmware file that's on your computer I am on Dogies . I was having big problems with my miners dropping hash rate. Just waiting to see if it drops off again. I was sent the Dec 19th and it looks like Dogies is from the same date.
What version of cgminer is on both dogie's and the 19th Dec firmware? log in via ssh and enter: [VERSION] => ( [0] => VERSION [CGMiner] => 4.7.0 [API] => 3.1 [Miner] => 7.0.0.3 [CompileTime] => Fri Dec 19 12:18:59 CST 2014 [Type] => S3 )
|
Mining Software Developer.
|
|
|
vabchgent
|
|
December 24, 2014, 03:55:45 AM |
|
Try running this command via SSH with the beta firmware. cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot I am not disputing its effectivenes, but what does that accomplish? Care to explain? Its essentially a factory reset except it preserves the network and pool settings, good to make sure you don't have any weird remnants from older firmwares. You need to be careful using this command it reset my miner and I had to use the rest button to get the miner back up and running. Thanks Were you on the beta Dec 19th firmware? I've tested this on about 300 miners without any issues. I am on Dogies . I was having big problems with my miners dropping hash rate. Just waiting to see if it drops off again. I was sent the Dec 19th and it looks like Dogies is from the same date. Check the MD5 if you want to make sure. MD5 (antminer_S320141219.bin) = 7df1b12d28b25e10aac37e2eafc7397b Check sum 7df1b12d28b25e10aac37e2eafc7397b Figured out what the problem was. I changed the /etc/init.d/cgminer file to turn on the API. I copied in one of the forum and it was missing the tail end of the original code PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb --api-listen --api-network --api-allow W:127.0.0.1,W:192.168.1.0/24 This is the tail end that was missing --bitmain-checkn2diff --bitmain-hwerror --bitmain-voltage $_vl --version-file /usr/bin/compile_time --queue 4096" So it look like voltage and error checking was gone Fixed now working great Right now I am getting some incredible numbers 430Ghs +++++ Like S3+ on nitrous oxide
|
|
|
|
bitsolutions
|
|
December 24, 2014, 04:01:45 AM |
|
Check sum 7df1b12d28b25e10aac37e2eafc7397b
Figured out what the problem was. I changed the /etc/init.d/cgminer file to turn on the API. I copied in one of the forum and it was missing the tail end of the original code
PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb --api-listen --api-network --api-allow W:127.0.0.1,W:192.168.1.0/24
This is the tail end that was missing
--bitmain-checkn2diff --bitmain-hwerror --bitmain-voltage $_vl --version-file /usr/bin/compile_time --queue 4096"
So it look like voltage and error checking was gone
Fixed now working great
The firmware is the same then, are you using the API to change settings or just as read only monitoring?
|
Mining Software Developer.
|
|
|
bitsolutions
|
|
December 24, 2014, 05:46:48 AM |
|
Hello: I have a batch of S3+ I bought, all are running on 1300W power supplies, At first they worked, but now suddenly I can only get 228Gh/s out of them ( I see many post with the same issue), even when i reboot or try 1013 image. I am not too happy about this, what can I do? I guess I have beg you now to use a beta firmware? what to do to fix this. I just found out I missed days of mining because of these miners which are not stable. Can I send these piece of crap defective S3+'s back and get a refund for S5? No, because you charged me out my butt for shipping so I can't return them to you... Every other tab i get some HTML error message. XML Parsing Error: not well-formed Location: http://192.168.1.118/cgi-bin/luci/xxx/admin/status/miner/ Line Number 348, Column 34: Modify voltage and Save&Apply, then need to Power off and Restart -------------------------------------------------------------^ Can anyone tell me what to do with these half baked pieces of junk that dont work, and I tried all the images, still same crap. And dont give me any crap about it's my power supply, I am using G2 1300W. SSH in using a tool such as putty and execute the following command(username and password are "root") sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua Can you take a picture of how you have your power lines hooked up and your status page in the web interface?
|
Mining Software Developer.
|
|
|
dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
December 24, 2014, 07:00:31 AM |
|
Hello: I have a batch of S3+ I bought, all are running on 1300W power supplies, At first they worked, but now suddenly I can only get 228Gh/s out of them ( I see many post with the same issue), even when i reboot or try 1013 image. I am not too happy about this, what can I do? I guess I have beg you now to use a beta firmware? what to do to fix this. I just found out I missed days of mining because of these miners which are not stable. Can I send these piece of crap defective S3+'s back and get a refund for S5? No, because you charged me out my butt for shipping so I can't return them to you... Every other tab i get some HTML error message. XML Parsing Error: not well-formed Location: http://192.168.1.118/cgi-bin/luci/xxx/admin/status/miner/ Line Number 348, Column 34: Modify voltage and Save&Apply, then need to Power off and Restart -------------------------------------------------------------^ Can anyone tell me what to do with these half baked pieces of junk that dont work, and I tried all the images, still same crap. And dont give me any crap about it's my power supply, I am using G2 1300W. Can you take a picture of how you have your power lines hooked up and your status page in the web interface? This please.
|
|
|
|
nitrox1
Newbie
Offline
Activity: 28
Merit: 0
|
|
December 24, 2014, 09:08:19 AM |
|
I have a batch of S3+ I bought, all are running on 1300W power supplies, At first they worked, but now suddenly I can only get 228Gh/s out of them ( I see many post with the same issue), even when i reboot or try 1013 image. I am not too happy about this, what can I do? I guess I have beg you now to use a beta firmware? what to do to fix this. I just found out I missed days of mining because of these miners which are not stable. Can I send these piece of crap defective S3+'s back and get a refund for S5? No, because you charged me out my butt for shipping so I can't return them to you... Every other tab i get some HTML error message. XML Parsing Error: not well-formed Location: http://192.168.1.118/cgi-bin/luci/xxx/admin/status/miner/ Line Number 348, Column 34: Modify voltage and Save&Apply, then need to Power off and Restart -------------------------------------------------------------^ Can anyone tell me what to do with these half baked pieces of junk that dont work with bad code, and I tried all the images, still same crap. And dont give me any crap about it's my power supply, I am using EVGA G2 1300W. And it's not just one miner. How many S3+ on your power supply? you say batch of? you say not just one? what's the watts at the wall?
|
|
|
|
siampumpkin
|
|
December 24, 2014, 09:59:54 AM |
|
Any price reductions on the S3+? They should price them to sell since the S5 is out.
|
|
|
|
dog1965
|
|
December 24, 2014, 10:54:06 AM |
|
|
|
|
|
dog1965
|
|
December 24, 2014, 11:09:52 AM |
|
Does anybody think antpool.com is better then f2pool.com "Discus Fish" ?
Sorry to post that question here.
|
|
|
|
bitsolutions
|
|
December 24, 2014, 11:41:25 AM |
|
Does anybody think antpool.com is better then f2pool.com "Discus Fish" ?
Sorry to post that question here.
Not sure, but Antminers seem to be very stable on ckpool.
|
Mining Software Developer.
|
|
|
SunnyIgor
|
|
December 24, 2014, 11:55:15 AM |
|
Is there a setting with the new firmware to make the S3 more energy efficent? Does changing the voltage and frequenty lead to better power efficiency. I need to make some room in my farm for 2 S5's and only have 4 kw.
|
|
|
|
vabchgent
|
|
December 24, 2014, 01:52:17 PM |
|
Check sum 7df1b12d28b25e10aac37e2eafc7397b
Figured out what the problem was. I changed the /etc/init.d/cgminer file to turn on the API. I copied in one of the forum and it was missing the tail end of the original code
PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb --api-listen --api-network --api-allow W:127.0.0.1,W:192.168.1.0/24
This is the tail end that was missing
--bitmain-checkn2diff --bitmain-hwerror --bitmain-voltage $_vl --version-file /usr/bin/compile_time --queue 4096"
So it look like voltage and error checking was gone
Fixed now working great
The firmware is the same then, are you using the API to change settings or just as read only monitoring? I had to add the --api-allow W:127.0.0.1,W:192.168.1.0/24 . But I commented out the one that was there and copied a new line in that was missing the --bitmain-checkn2diff --bitmain-hwerror --bitmain-voltage $_vl --version-file /usr/bin/compile_time --queue 4096" . I allowed full control and monitoring. Thanks
|
|
|
|
|