|
I'm trying to figure out the best settings for 290/290x/280x cards, but I'm not really finding any references to speeds in this thread. Can anyone point me in the right direction?
|
|
|
|
First block!  Sent. Congratulations on finding your first block. I hope you keep mining with us, it's a great coin I see going places. That was quick! Yes, I intend to switch what remains of my GPU farm over. Nice to see a coin with something truly different, I'll support it. I'm trying to figure out the best settings for 290/290x/280x cards, but I'm not really finding any references to speeds achieved anywhere. Do you have any links that could help me out? I'm only running it on 4 GPUs right now, 2 290x and 2 290. 290x = 2.43MH/s each @ 950/1375 and 290 = 2.25MH/s each @ 950/1375. Thanks again! |
|
|
|
First block!  Here's my address: ScGJsdQCenik4aPUhCtCMUUPRxJqcLDPaU Thanks for the reward and bringing spreadcoin to my attention! Love the fact that there are no pools. |
|
|
|
Cool, first I've read of Spread. I was wondering what to do with my GPUs, looks like you've answered my question. I'll post back once I've found a block.  |
|
|
|
Can't seem to find any cables on this webshop.... Gotta call them. They actually supply Seasonic, but deal with individuals also. |
|
|
|
|
Impressive. Seems the best S4s can muster is about 4 days before they shit the bed and have to be rebooted.
|
|
|
|
|
A big 2000 fuck yous, KNC.
|
|
|
|
As above, the circuit rating is there to protect the wiring. If you want more, you'd need to replace the cabling. Is there another circuit you could run an extension from? That would be the cheapest option.
The thing is, I'm trying to run it from my detached garage, and it only has 1 outlet =( trying to figure out how to run more than 1 S4. Don't you have a breaker panel in your detached garage? Yes, I have a breaker panel in the garage, and it's just a switch to turn off/on. Can you post a pic of your breaker panel so we can advise you properly? You shouldn't be using a breaker as a switch. |
|
|
|
As above, the circuit rating is there to protect the wiring. If you want more, you'd need to replace the cabling. Is there another circuit you could run an extension from? That would be the cheapest option.
The thing is, I'm trying to run it from my detached garage, and it only has 1 outlet =( trying to figure out how to run more than 1 S4. Don't you have a breaker panel in your detached garage? |
|
|
|
Emdje, any chance of an underclockers version?
I've undervolted my A2 and a few blades are already at 1000MHz but elec costs are now approaching revenue. I need lower frequency to get the voltage lower to extend its life a bit more. If you could add 50MHz or even 100MHz steps down to 700 or 800, that would be awesome
Mind sharing how you were able to lower voltage on the blades? |
|
|
|
just add this line at the end of /config/cgminer.conf: "queue" : "1"
and if You want to set queue from shell use: /usr/bin/cgminer-api "setconfig|queue,1" (You can also let ssh do it remotely)
I did not find any difference between queue 0 and 1 in results and I do not use --lowmem
I'm guessing adding it to cgminer.conf would make the setting persistent across reboots? Definitely going to do that if so. Files changed in /config are permanent across reboots. In the S5 there is a file /config/user_setting which has just I'm not sure if the S4 is the same but if it is, that's all you need to modify, to say queue 1 Ok thanks, good to know. You suggest setting queue to 1 instead of 0? I keep seeing people say queue 0 for p2pool, but if you say 1 is best that's what I'll set. I don't mean to turn this thread into an S4 thread, but while you're here.. I noticed you compiled cgminer 4.9 for S5, any chance you'll do the same for the S4? Yes. As far as I know it is persistent accross reboots. Thanks again for bringing that up, you've just saved me a lot of annoyance.  |
|
|
|
Not sure I'd say perfectly? The still default to 8192 queue size and large amounts of stales. I got mine down to about 3.4% stales, which is almost twice as bad as my SP20s at 1.8% stale. Thanks for the ck firmware link, didn't know about that, will have to try it. M Definitely give the firmware a try, you'll get better results. You'll want to follow this to set queue to 0: https://bitcointalk.org/index.php?topic=796839.msg9243760#msg9243760I also add --scan-time 1 --expiry 1 along with lowering queue to 0 and adding --lowmem. Quite a pain in the ass to do every time the machine goes down, but worth it IMO. CK has stated a few times that the --scan-time and --expiry parameters are useless, so you really don't need to bother with them. I hadn't tried --lowmem before, so I can't tell what value it adds if any. The biggest bang for the buck is setting --queue to 0, instead of their default 8192. Good to know, guess I'll stop adding them. lowmem seems to help a little I think, give it a try. CK seems to think it's useful for S4s. just add this line at the end of /config/cgminer.conf: "queue" : "1" and if You want to set queue from shell use: /usr/bin/cgminer-api "setconfig|queue,1" (You can also let ssh do it remotely) I did not find any difference between queue 0 and 1 in results and I do not use --lowmem I'm guessing adding it to cgminer.conf would make the setting persistent across reboots? Definitely going to do that if so. |
|
|
|
Don't take this the wrong way, but you should have asked for advise before ordering that if you don't know anything about PSUs. Return it and order something made by quality manufacturers like Seasonic, Superflower, Flextronics, or Delta. Most brands like Corsair, XFX, EVGA, Silverstone, etc just slap their names on PSUs made by the previously mentioned manufacturers. It's hard to tell what's what, so I suggest browsing through www.jonnyguru.com for the best and most in depth psu reviews on the net. Look up "gutless wonder" on that site. That's what you just bought, unfortunately. I'd be surprised if that PSU can't put out half of it's rated power continuously without dying. I give it 2 days before it crops out on you running a single stock S3. PSUs used for mining are put under heavy stress, 24/7. You can't skimp out. |
|
|
|
For remote access, a cooperating network interface is required: Intel ethernet adapters, Intel WiFi adapters, and certain 3G modems are supported. If you can, replace Intel-made network interfaces with ones made by a different manufacturer, that do not support AMT. Apparently for the remote control to work, you also need to have Intel network card, so not using any Intel network hardware should keep you safe from remote attack. do you know the reason why it has to be an pci intel network card? most motherboards are already coming with onboard lan, shouldnt that be the same? High end motherboards usually come equipped with Intel NICs since they're the best, performance wise. If it isn't Intel you're fine I imagine. Wish I wouldn't have upgraded to X99. |
|
|
|
I didn't finish reading everything. Can I say I am safe if I use an Intel CPU, non-Intel motherboard and a non-Intel network card? I do not think Intel is after my bitcoin, only hackers are.
Your non Intel branded motherboard is using an Intel chipset, unless it's a dinosaur. |
|
|
|
Not sure I'd say perfectly? The still default to 8192 queue size and large amounts of stales. I got mine down to about 3.4% stales, which is almost twice as bad as my SP20s at 1.8% stale. Thanks for the ck firmware link, didn't know about that, will have to try it. M Definitely give the firmware a try, you'll get better results. You'll want to follow this to set queue to 0: https://bitcointalk.org/index.php?topic=796839.msg9243760#msg9243760I also add --scan-time 1 --expiry 1 along with lowering queue to 0 and adding --lowmem. Quite a pain in the ass to do every time the machine goes down, but worth it IMO. CK has stated a few times that the --scan-time and --expiry parameters are useless, so you really don't need to bother with them. I hadn't tried --lowmem before, so I can't tell what value it adds if any. The biggest bang for the buck is setting --queue to 0, instead of their default 8192. Good to know, guess I'll stop adding them. lowmem seems to help a little I think, give it a try. CK seems to think it's useful for S4s. |
|
|
|
Not sure I'd say perfectly? The still default to 8192 queue size and large amounts of stales. I got mine down to about 3.4% stales, which is almost twice as bad as my SP20s at 1.8% stale. Thanks for the ck firmware link, didn't know about that, will have to try it. M Definitely give the firmware a try, you'll get better results. You'll want to follow this to set queue to 0: https://bitcointalk.org/index.php?topic=796839.msg9243760#msg9243760I also add --scan-time 1 --expiry 1 along with lowering queue to 0 and adding --lowmem. Quite a pain in the ass to do every time the machine goes down, but worth it IMO. |
|
|
|
They are selling about $325-350 per cube (600 GH):
Maybe the only people buying these are those with faulty cubes from their 5-Cube Neptune Set because you still need a main Controller board.
You can run 6 cubes, removing the LCD frees a port. |
|
|
|
Thanks for the info, guys. To open it up to the public make sure ports 9332 and 9333 are open to the public and map to your p2pool server on your LAN... Should 8333 be opened also to provide better node connectivity? I currently have 8333 and 9333 open. Any security precautions to take into consideration? Edit: Opened up 9332, and allowed responding to pings. http://69.157.250.149:9332/static/Would you fellas mind pinging my server and posting your results? Specifying your general location would be appreciated, too. The server is located in Montreal, Canada. I just checked out your node... 5 S4s on it, 4 of which are reporting 2TH/s or greater. Looks like whatever firmware you're running is working out well on p2pool. Guess Bitmain finally got around to fixing that, huh? I'm traveling for work this week (currently in Cleveland, OH). Ping to your server from here: round-trip min/avg/max/stddev = 48.655/56.074/85.242/7.561 ms Have you checked out Matt's relay network? https://bitcointalk.org/index.php?topic=766190.0Yep, they work perfectly with p2pool. Bitmain addressed the issue with the firmware they released on Oct. 16th, more or less. For slightly better results, it's best to use ck's firmware found here: https://bitcointalk.org/index.php?topic=796839.msg9242449#msg9242449That 5th S4 has a half dead hashing board, need to get it RMAed soon. Thanks for the ping results. As for the relay server, I've got that running too. I was expecting it to be complicated to set up, but thankfully it was easy as pie.  |
|
|
|
|
Show Posts
