Here's version 3.8. This version adds proper support for C1s, and fixes some minor issues for the Ant scanning logic. Also, note that today I'm selling my last S1. After this version there's no guarantee S1s will work properly (but they should). Download link: MAntMonitor38.zipM |
|
|
|
waiting for the "sold out" sign on curent batches  Almost pulled the trigger but saw they wanted $119 for shipping. I hit the little red x. yeah it comes to 814 . if you have a psu that will work these are pretty good if you do not have a psu the s-4's may be a better deal for you. an s-4 comes to 930 . An S4 comes to 930 where? You mean if you buy a set of 16? I'm seeing $1200 + shipping.. M EDIT: Duh, $400 coupon. <face palm> |
|
|
|
Does Spondoolies ship to the US? I'm trying to place an order to the east coast of the US and I receive this on checkout: Unfortunately there is no Shipping Rate available for your destination and/or weight of your cart.  M Please try again Thanks. It works now. But I'm confused. First of it, is the deal through Monday, or until Monday, meaning through Sunday? Second, it says "$695 shipped". But on checkout, it wants to add $119 in shipping? Which is it? M |
|
|
|
Does Spondoolies ship to the US? I'm trying to place an order to the east coast of the US and I receive this on checkout: Unfortunately there is no Shipping Rate available for your destination and/or weight of your cart. M |
|
|
|
I think your formulas are a bit arbitrary. For instance, getwork latency is given way too much importance in the pool formula. And everything is linear.. and so on (latencies are mostly ok within a range before the problems they cause skyrocket).
Thanks for the comments Naplam. Based off of what you said I changed the criteria and reduced how much GWL matters to the p2pool score. In regards to most of my equations being linear, do you have any suggestions on how to make the ranking more accurate? Perhaps through tiering? The latest criteria used can be found on the bottom of the p2pool node finder page, nodes.p2pool.coI agree about the getwork latency comment, that's weighted too high IMHO. My node ( http://96.44.166.190:9332) is ranked at 51% solely because of the getwork latency. Everything else is stellar including 111% efficiency. I played with the bitcoind settings quite a bit before I settled on what it's set to now. I decided getting more transactions was worth a slightly higher getwork latency, and as shown, it didn't affect the efficiency rating at all. M |
|
|
|
Deal has been adjusted to purchase the 3 s3 & 1 s1
Confirmed. Thanks! M |
|
|
|
|
I can't help but wonder, the folks with the burnt out pumps, is the pump intake coming from the radiator (hence cool) or the C1 (hence warm/hot)?
M
|
|
|
|
Deal to purchase the 2 S3 & the 1 S3+ has been setup.
I'm glad you said that! It was a long day yesterday, I misread what you wrote, you almost got two S3s and an S1! M |
|
|
|
Anyone have a C1 pointing at p2pool? Mine seems to behave like my S2 pre-fix ... abysmal.
I was expecting the C1 to act like a S3, but it doesn't, it acts like an S2. Including the annoying "have to set queue to 0 every reboot" problem.
M
I have C1's using P2Pool. Mine are getting the full 1000GH/s, but they do require the same re-setting of queue after a reboot. I also set the pseudo share difficulty. It has been discussed that setting pseudo difficulty does not effect the overall performance, however setting pseudo difficulty will make cgminer and the UI show the expected hashrate. I use +1028 (If you use +1024, Best Share is not displayed. But with +1028, best Share works. I have no idea why.) Regarding setting the queue, S2/S4/C1 all have the same OS configuration. Thanks, I was using 518. Are you using queue 0 or 1? M Doing as you said, setting queue to 0, gives me 965GH/s and 9% rejects. Completely unreasonable, just like my S2. M Why am I not surprised by this... Bitmain claims to want to support p2pool... but the only products they've ever released that worked with p2pool out of the gate are the S1 and S3. Even those products use forked versions of cgminer that until recently was based on 3.x. Furthermore, their binaries throw away stale shares, which can lead to potential block solutions being tossed. I'm not able to get my S2 working reasonably either, even with the latest firmware.  M |
|
|
|
It shows as already on cgminer 4.6.1, and when I try to upgrade it to the current firmware, I get this:
What system version does it show its on at the moment? Should look like a date. - Navigate to System -> Overview and look at "File System Version". Wed Nov 26 10:27:37 CST 2014 M |
|
|
|
Got my C1. Hooked it up. All is well. I'm surprised that it behaves like an S2, not an S3. Including the poor results with p2pool. It shows as already on cgminer 4.6.1, and when I try to upgrade it to the current firmware, I get this: runme.sh exe
Content-type: text/html
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Script-Type" content="text/javascript" />
<meta http-equiv="cache-control" content="no-cache" />
<link rel="stylesheet" type="text/css" media="screen" href="/css/cascade.css" />
<!--[if IE 6]><link rel="stylesheet" type="text/css" media="screen" href="/css/ie6.css" /><![endif]-->
<!--[if IE 7]><link rel="stylesheet" type="text/css" media="screen" href="/css/ie7.css" /><![endif]-->
<!--[if IE 8]><link rel="stylesheet" type="text/css" media="screen" href="/css/ie8.css" /><![endif]-->
<script type="text/javascript" src="/js/xhr.js"></script>
<script type="text/javascript" src="/js/jquery-1.10.2.js"></script>
<script type="text/javascript" src="/js/json2.min.js"></script>
(and more) So far I'm not impressed. Fortunately it works fine with Eligius. M |
|
|
|
Anyone have a C1 pointing at p2pool? Mine seems to behave like my S2 pre-fix ... abysmal.
I was expecting the C1 to act like a S3, but it doesn't, it acts like an S2. Including the annoying "have to set queue to 0 every reboot" problem.
M
I have C1's using P2Pool. Mine are getting the full 1000GH/s, but they do require the same re-setting of queue after a reboot. I also set the pseudo share difficulty. It has been discussed that setting pseudo difficulty does not effect the overall performance, however setting pseudo difficulty will make cgminer and the UI show the expected hashrate. I use +1028 (If you use +1024, Best Share is not displayed. But with +1028, best Share works. I have no idea why.) Regarding setting the queue, S2/S4/C1 all have the same OS configuration. Thanks, I was using 518. Are you using queue 0 or 1? M Doing as you said, setting queue to 0, gives me 965GH/s and 9% rejects. Completely unreasonable, just like my S2. M |
|
|
|
Anyone have a C1 pointing at p2pool? Mine seems to behave like my S2 pre-fix ... abysmal.
I was expecting the C1 to act like a S3, but it doesn't, it acts like an S2. Including the annoying "have to set queue to 0 every reboot" problem.
M
I have C1's using P2Pool. Mine are getting the full 1000GH/s, but they do require the same re-setting of queue after a reboot. I also set the pseudo share difficulty. It has been discussed that setting pseudo difficulty does not effect the overall performance, however setting pseudo difficulty will make cgminer and the UI show the expected hashrate. I use +1028 (If you use +1024, Best Share is not displayed. But with +1028, best Share works. I have no idea why.) Regarding setting the queue, S2/S4/C1 all have the same OS configuration. Thanks, I was using 518. Are you using queue 0 or 1? M |
|
|
|
|
Anyone have a C1 pointing at p2pool? Mine seems to behave like my S2 pre-fix ... abysmal.
I was expecting the C1 to act like a S3, but it doesn't, it acts like an S2. Including the annoying "have to set queue to 0 every reboot" problem.
M
|
|
|
|
|
I also have an underperforming S3 that runs at 410 GH/s on p2pool and 420 or so on Eligius. It regularly has 1X that I haven't taken the time to try to fix yet. I suspect it's just a matter of re-applying the thermalpaste, but I don't know for sure. Will part with it for less than the other S3 if bundled shipping. I'll try to work on it this weekend to see if I can get it back to par and clear the X.
M
|
|
|
|
|
I'm looking for a new home for some of my Ants.
The S1 ran great at 200GH/s until it was no longer profitable to do so. Now it runs great at 180GH/s, whether it's profitable or not is your decision. After 3-4 days of running it'll throw a bunch of Xs. That has yet to affect the hashrate, and a soft reboot fixes it until next time.
The S3 is from a later batch, I don't know which. It runs great around 439GH/s at stock speeds. I did OC it once for perhaps an hour to see what it would do, then put it back to stock speeds.
The S3+ I bought in mid September. Like all S3+s, it's a champ, running at 466GH/s at stock speeds. Like the S3, I OC'd it once to see what it would do, then put it back to stock speeds.
Shipping from the east coast of the US. I have all the packing material. Can ship individually or together, but would rather together to save on shipping costs.
S1 price - make an offer.
S3 price - 0.4 BTC
S3+ price - 0.45 BTC
We can negotiate on shipping. I would rather ship to domestic US only, as international shipping is a PITA.
Would prefer avoiding escrow because it's a hassle, but if wanted, can use OgNasty. Check my rating, I've been around a long time, and have a good rep.
M
|
|
|
|
all these pools too many to choose from, how do i kno which ones are the good ones?
Most of the big ones are good ones. Most of the small ones are small for a reason. M |
|
|
|
EDIT: You'll have to do this after every reboot unfortunately, as it will reset to defaults. Just don't reboot it......  Seriously?? Wow. Isn't this easier? /usr/bin/cgminer-api "setconfig|queue,0"
M Dunno, never tried it.....if it works - let me know  It works on S2s. Haven't figured out how to get privileged API commands to work on S3s yet. M The S3's are even easier because it will save over a power cycle, unlike the S2/S4/C1. Just change the PARAMS variable in /etc/init.d/cgminer. That is where you add --api-allow and whatever other cgminer params you want. Like so: PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-allow W:0/0 --bitmain-checkn2diff --bitmain-hwerror --queue 0" Yes, thanks, I figured that out. Now if I could just get the API commands to work. I tried --api-allow W:192.168.0/32 and cgminer wouldn't start. M |
|
|
|
EDIT: You'll have to do this after every reboot unfortunately, as it will reset to defaults. Just don't reboot it...... Seriously?? Wow. Isn't this easier? /usr/bin/cgminer-api "setconfig|queue,0"
M Dunno, never tried it.....if it works - let me know It works on S2s. Haven't figured out how to get privileged API commands to work on S3s yet. M |
|
|
|
|
Show Posts
