I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file. ***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT*** This is the first attempt, not sure if 0 is the optimal queue value for all pools but if you are a P2P miner you may want to try this out. I use a smaller pool and my numbers have gone up. This is along the same tune you could do for an S1 but a far cry from what we did in the GPU days. I have another unit running at a lower speed but have the same results. SSH in then: vim /etc/init.d/cgminer
--scan-time 1 --expiry 1 Find line 75 PARAMS...at the end change --queue 0 and add --scan-time 1 --expiry 1 before the quotation. ***DO NOT TRY THIS UNLESS YOU FULLY UNDERSTAND AS YOU WILL BRICK YOUR UNIT**** Please stop telling people to do anything but change the queue. Artificially lowering the discarded value serves no purpose whatsoever. Decreasing scan time and expiry are for the dark ages of CPU mining - paying any attention to the "discarded work" value is completely pointless and actually harmful. The only thing here that's making a difference to CPU load is decreasing the queue which they have set far too high by default. Please do not decrease it below 1 though. I was having other issues before this mod like wrong hash rates at the gui and more HW errors than I would have liked. While load balancing I was getting a lot of discards at the pool I was using. Maybe it doesn't make much difference, but after this mod things look good at the pools, discards and HW look great, but hash rates seem way off still. I think the firmware is buggy and could be improved. Edit: hash rates look good now on failover. Testing load-balancing now. Results = not hashing well at the pools. sticking to failover until we figure this out. How should we revert back if need be, or what would be ideal parameters. I'm hoping that I could always just re-flash the firmware if need be. Con is obviously much more of an expert than I am but I would drop scan-time and expiry completely, revert queue to the default of 1 (or remove it complete, it defaults to 1)... Perhaps a higher queue value is better for the S3 but 4096 was taking the CPU usage off the charts and starving the system.. |
|
|
|
Observations re S3 (vs S1)
S3 is quite a different beast. S1 was like a soldier. You give it an order to march at higher speed-and it does or "dies" trying-gives you XX.
One of my S3-I give it more juice (225 vs 218.75)-it goes up to 455, then back to the same 420 GH (while keeping all 0000).
Now trying 212.5, but it can do 430GH max on this-we will see.
There must be a controller (probably R47) that limits the performance no matter of what mhz you give it.
Cooling the case with an additional airflow from two fans directed at opposite sides did not help at all-I tried it.
However, i think that experimenting with heat sinks on R47 is a worthwhile endeavor.
I am wondering how the load average impact these, I ask because seeing the system at an average load average of 2.3 and 0% CPU cycles free all of the time I wonder if cgminer is getting resource starved. On the surface it sure seems like it.. |
|
|
|
I'm just looking at this thread and bitmain site. And what i can see, quality went down the drain.i mean, quality in regards of delivery on time, process of any refunds, simple information to community.
Now it seems bitmain asking for btc in advance which is basically preorder.
With s1 there was no issues related to delivery of miners. Now im reading people waiting to get their s3 mining week or more!
I was hesitating to order B1,B2,B3 and it seems i didnt lost a lot. as all batches was delayed and now batch 4 and 5 is simple proeorder with no warranty that will be delivered in time frame given.
I dont know whats the issue is but even labeling boxes as miner means issues for end user.
I am fan of bitmain but at this stage whats the point of ordering when their are not in stock?
Price is nice but again waiting time for B5 will kill any profit if any. We looking at least 14 days to receive any miner. What if customs will delay the process? Whats safe quantity to order? I was thinking to order 10. Any ideas how this will look for customs?
Have you actually looked up anything you are spouting off, almost every one of your points is quite wrong. 1. Delivery times clearly posted on the site for B4 and B5. 2. You are suggesting they violate customs law by changing the labeling to something it is not? 3. Your country's customs helps dictate that, why don't you lookup your countries regulations and figure out what makes the most sense to you since the answer is different for everyone. |
|
|
|
|
Looking around for documentation on BTC Guild JSON API, didn't see much on Google searches aside from existing implementations, those are useful but curious to see if there is a comprehensive doc for the JSON API?
|
|
|
|
Please tell me how you know that for sure, you do not know my background nor my dealing with Spondoolies or any other manufacturer, I am making statements based on the foundry production timelines as the industry isn't magic but a fairly well understood process if you have proper background...
They just announced they get the chips on Tuesday, so is this argument really worth having? You can go from chips to finished pick and place and working miners in like 3 days, even KNC managed that on their first product. Fair enough, RoadStress brought a piss poor attitude with his response so I addressed it, thanks for pointing out the real status of the chips... |
|
|
|
So, when is the first batch SP30 going to be delivered?
Well this month for sure even if there are just 10 days left. I know they are a good crew but without even having the first set of chips in you think it will really be that smooth? How do you know they don't have the first set of chips in hand? You don't. Please tell me how you know that for sure, you do not know my background nor my dealing with Spondoolies or any other manufacturer, I am making statements based on the foundry production timelines as the industry isn't magic but a fairly well understood process if you have proper background... If you so close to them you should know the answer as well, let's assume you are close to them and know the answer, under NDA or not you shouldn't be making the statements above no matter the case because that is extremely irresponsible as you are not a formal representative of the company but you are trying to push your GB.. |
|
|
|
|
Have some 2013 Casascius 1 BTC coins..
If you are serious about a trade maybe we can work something out..
|
|
|
|
So, when is the first batch SP30 going to be delivered?
Well this month for sure even if there are just 10 days left. I know they are a good crew but without even having the first set of chips in you think it will really be that smooth? |
|
|
|
|
Would be helpful if you actually stated what the hardware is..
|
|
|
|
I followed suggestions from another venue about recompiling modified source code. The bar is higher than editing a script and running it currently. The RESULTS for me are less than ideal to date so I don't elaborate here. WIthout cooling and power improvements, not much there to get. If I were helpful like you are, explained monster heatsink in this thread, with pictures, I could start checking for messages, yesterday.  It's in this thread is also a cruel correct answer. It's cryptic tidbit time! Fun with powers of 2. root@Neptune:~# cat /var/run/.waas_curfreq
-1 -1 -1 -1 512 512 528 512 512 512 544 512 512 512 544 512 512 512 512 512 512 512 512 512 False is a possibility too. (BTW I claim it's real) Don't assume nuthin! Thanks to KnCMiner, It's open source, legal yet fun! YMMV  This is interesting if it actually works, you have always been able to set whatever you want but waas itself is closed source in the Nov Jupiters, while you can pass it anything you like it will not actually honor the settings.. I can't imagine they open sourced the code for waas itself for the Neptune but if they did then it's an easy fix.. On my firmware I need to set things manually by flipping bits because it's out of the range of waas, I actually intercept the speed (if anyone has looked at the code) and if waas can handle it I let it, anything over the Octover and November waas ranges automatically gets set by flipping bits.. In any case if they now allow waas to do it directly it will be much easier.. |
|
|
|
I guess I can understand that. Over time I'm confident I'll prove to the community that I'm here to stay and to give away cool merchandise. Check out my S1 raffle and buy a few tickets. .001 a ticket. You could be a winner!
so it's not free - you just want money - scammer!!! you are not giving anything any ...scammer - you just want money - you're just like the rest of the fucking scammers around here.... please go crawl back into the hole you came out of asshole! You are an absolute moron, look-up the definition of a raffle and realize he is being completely upfront... You are one of the reasons the forum has a piss poor reputation when it comes to hinges like this.. |
|
|
|
Does anyone know
If stock November Jupiter is 1 watt per gh
Or 1.3 watt per gh
At wall?
1.3 ... or more if you use the Padrino firmware. I just shut down my last Nov Jupiter 5 minutes ago. 1.3W per Gh if you are using shitty PSUs.. Pull from the wall only as good as your PSU efficiency with the load.. |
|
|
|
If you think KNC is deceitful look at Blackarrow or Hashfast.
So I only committed fraud 10 times, not 100, obviously makes it all better.. |
|
|
|
Yes!
The idea was if we get the big ass cooling tower, bar, and blanket out of the way, we may be able to cool those VRM's a bit better.... what ya think?
I agree.. Since they sheered the aluminum the blankets are going to vary based on the unit, some will work much better than others.. I would like to try replacing the current setup with the same type of bracket on the old Neptunes, possibly some small VRM heatsinks (with 48A the heat dissipation is pretty insane) and a higher CFM fan.. I suspect that will be the easiest option that provides plenty of heat dissipation.. I'm most interested in swapping out the VRMs for the 50A version, I suspect they can really be pushed if that jump is taken... While on the Nov we can drive the VRMs much higher they still don't hit the 48A hard shutdown, in the Neptune the stock config is within a few percent of 48A.. Ah yes. The old Jupiter bar would be great, but that would also mean losing the box totally because the holes are on the wrong sides (in previous posts). No problem there really. The ericcsons they are using in Neptune are auto-shutting down at 48a?... and pushed within a couple amps?. Damn. Theres gotta be a cheaper way than buying 8 new vrms for every pcb.... Hmm... well... we will soon see exactly what those limits are if Tolip has anything to say about it...hehe I'm not sure how hard the limit is enforced but per the datasheet for the VRM it cannot be raised past 48A and the VRM is supposed to shutdown at that number.. I hope it's soft enough that they allow maybe 50A before a hard kill but some testing will tell.. |
|
|
|
Yes!
The idea was if we get the big ass cooling tower, bar, and blanket out of the way, we may be able to cool those VRM's a bit better.... what ya think?
I agree.. Since they sheered the aluminum the blankets are going to vary based on the unit, some will work much better than others.. I would like to try replacing the current setup with the same type of bracket on the old Neptunes, possibly some small VRM heatsinks (with 48A the heat dissipation is pretty insane) and a higher CFM fan.. I suspect that will be the easiest option that provides plenty of heat dissipation.. I'm most interested in swapping out the VRMs for the 50A version, I suspect they can really be pushed if that jump is taken... While on the Nov we can drive the VRMs much higher they still don't hit the 48A hard shutdown, in the Neptune the stock config is within a few percent of 48A.. |
|
|
|
|
Good to see people getting into the Neptunes just like the Jupiter..
Although I think watercooling is great the way the Neptune is put together and the heat one must dissipate means an i30 with a decent fan provides plenty of heat dissipation.. The VRM and temps on the bottom of the board are two of the most concerning and really the place one needs to focus to keep things under control.
I have built over 30 1Th/s 4 board Jupiters so far (6 boards all run 1.5Th/s) and raising the boards a little and swapping out the fan for a fairly low pressure high CFM fan (keeps the noise down with a low pressure fan) is enough to keep air moving quick enough to keep them where they need to be..
On the Neptune side I haven't put my thermal camera on the boards yet since I don't have one but based on the layout it's a similar problem..
The biggest challenge I've seen is the VRM shutdown, with a hardcoded 48A shutdown I don't know how to push past that but I have replaced VRMs on the Jupiters so I might do it on the Neptune and see what happens, if I get one at some point..
|
|
|
|
here is my recent e-mail discussion with bitmine Kerim (Bitmine AG)
Jul 01 10:47
I will ask what this money is for. But I guess it is to cover future costs of the facility in Iceland.
Best regards,
Bitmine AG, Bitmine.ch
WHAT??? Them too? Fuckers! I give them credit for the honesty however that is not relevant to their commitment to their customers with regard to systems that were purchased, which no must be refunded.. A court would have a field day with this so if you do make a move legally please save those comms. |
|
|
|
what option i must put at padrino firmware for have it 900 gh hashing speed?
As of late I've settled on 0x361 in my firmware, Ive have great luck with all boards running at 250Gh/s each and all units I've put together with 6 boards maintain 1.5Th/s. The guide I wrote that has been distributed to many of the donators explains the fan configuration needed to keep them cool, it's a minimal investment for a huge difference in temperate, on the stock fans you can't go more than 750-800Gh/s before things start shutting down for thermal reasons.. |
|
|
|
Can someone explain what this means please...
"Don’t parallel connected different DC input from different PSU into the same Hashing board."
Or if already discussed just tell me and I'll look back through the posts for it.
Thanks
It means don't use two PSUs to power a single board (each board has two PCIe connections).. The voltage differences will throw the board out of whack.. |
|
|
|
Bitmain,
Any chance of getting some pics of the business end of an S3? I would like to see the connectors, etc. so I am ready to plug in when they start shipping.
You guys are just kidding about the July 10 (if not later) date right? You are really planning to box em up and ship on the 5th or 6th RIGHT?? lol
ig
The picture on the site shows the power connectors, 4 PCIe on top but only two are needed... |
|
|
|
|
Show Posts
