|
The timings stilt has posted are as tight as they can pretty much get for 200 based cards. Im more involved with 300/400 based cards. Either way the gains you'll get from copying lower memory straps into higher clocked straps will get you most of the way there. Any individual timing tweaks I would do would just increase stability and maybe get a few % extra hashrate.
|
|
|
|
They merged with another company and became this: http://www.sfards.com/Their new dual sha256/scrypt 28nm chip was a massive flop though...the chip had massive design issues out the door and they never recovered as far as I know. |
|
|
|
I suspect the situation is a LOT more complex than you believe, due to interaction of multiple compute units trying to access memory at the same time, wait state timings on the actual memory, etc.
GDDR5 RAS/CAS timings has nothing to do with the bandwidth of the data xfer. Of course it does...if a memory controller has to wait more clock cycles before it can read or write to a memory bank, its effective I/O bandwidth is reduced. Try reading a GDDR5 datasheet. Every mfr supports at least 8 concurrent open pages. 2 bursts (4 clocks) from the same page are required to max the I/O bandwidth due to the 1:1 command:burst ratio. In the context of the Hawaii cards with a memory clock of 1250 or 1300Mhz, faster page activation times than stock make no difference in the data xfer rate. When the time for 16 burst xfers is less than the time to activate a page, only then will page activate timing impact bandwidth for the minimum 64-byte xfers. You'll run into that issue with an Rx 470 at 1750Mhz, but not on a R9 290 at 1250. I have read almost the entire Hynix GDDR5 data sheet, and am probably one of only a handful of people that have decoded the entire memory strap region of the ATOM bios. Of course timings wouldnt matter for slower clocks...but no one on these forums run their memory clocks at 1250 or 1750  |
|
|
|
I suspect the situation is a LOT more complex than you believe, due to interaction of multiple compute units trying to access memory at the same time, wait state timings on the actual memory, etc.
GDDR5 RAS/CAS timings has nothing to do with the bandwidth of the data xfer. Of course it does...if a memory controller has to wait more clock cycles before it can read or write to a memory bank, its effective I/O bandwidth is reduced. |
|
|
|
don't need to rush, you are already 40-50% behind claymore  That's even more a reason why I would want to be able to rush and beat him! that guy is playing with us, i bet he already had prepared a fully optimized private miner that he sold to big farms, and now he is giving us little by little... His V6 gives : r9 270 : 70-72 sol r9 380 : 90-95 sol lol all these guys are screwing with us...there were 100H/S private miners to big GPU farms out on day 1...changes made to increase hashes from 40-100H/s on 470s were trivial. The public miners were obviously gimped on purpose. Its actually quite brilliant on what all these guys are doing (with the exception of @mrb I give him HUGE props for creating a public open source miner). They are making huge increments in hashrate, which then enables them to keep increasing their fees, and we all love it (hey why not pay 20-30% fee when my hashrate is doubled...right?) Greed of bitcoin mining game has finally reached GPU miners. What everyone does not realize is that the only winners are these developers and farms...through these brilliant means they are keeping their share of the mining "pie" the same, while everyone else is fighting over the same scraps...dont forget just because your hashrate doubles means nothing...so does everyone else hashrate. We are actually earning LESS because through this smoke and mirror tactics devs/pools/farms are able to earn more from our expense (and equipment and power costs), AND we are HAPPY with it. Don't fall for it...I think the best course would be to 100% support mrbs efforts...tip him and the devs working with him what they deserve in donations so that open source miner can quickly catch up to Claymours/optiminers. |
|
|
|
|
Nice work guys...currently this performs better on my 470/480s than even claymours miner on windows side. Sucks that he will simply rip off your code again and further optimize his windows miner, while continuing to say "FU" to all his linux customers that supported him for the past year.
Do you guys have a centralized donation address for this project? Ill donate whatever fees claymour would have made to you guys.
|
|
|
|
Does anybody else have problem with flypool getting half of the shares ?  They obviously doubled their difficulty, since hashrate per device has roughly doubled as well. Your earning the same, each share you submit is just "worth" more now. |
|
|
|
new vesrion with 45 sols per gtx 1070 can be runned on windows(10 x64) ?
+1 Is it so hard to add windows support ?  Sorry I am still not, at the moment, working on Windows. But optimizations and various improvements. Yea, not exactly sure why windows users are coming on here and demanding a windows version. Linux users got screwed over by this whole shit, and I have rigs that can't be booted under windows and require linux. Be happy with your claymour 100h/s miner. @mbr id rather you get close to clamour performance, charge a devfee to get that done, and then worry about windows. |
|
|
|
|
Thats literally the 460/470/480 line rebranded and doubled in price.
|
|
|
|
@mrb Keep getting this error with your miner: Task exception was never retrieved
future: <Task finished coro=<Silentarmy.show_stats() done, defined at ./silentarmy:183> exception=KeyError('1.0',)>
Traceback (most recent call last):
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "./silentarmy", line 228, in show_stats
rate_gpus = sorted(gpus(last_sols, last_times, period_gpu))
File "./silentarmy", line 193, in gpus
sols[devid] = last_sols[0][devid] - last_sols[idx][devid]
KeyError: '1.0' |
|
|
|
Hello,
I bought this little device for around $20 second hand. I am completely new and noob in crypto mining. I have some questions, probably stupid, but I have nowhere else to ask.
1. There is a link in the first post about Driver Repo, a link with some files to download. Do I have to download any of this and install. If so, what to install? (I am using Win10)
2. In one of the post here, I think the constructor of this device said "People use this mostly as cheap little lottery miners. They cost next to nothing to run, and you have a chance of making about $100 if you get lucky". What did he mean? Where to sign up for it?
3. From what I understand, the device will run with no problem with no fan under 144MHz, if I would like to overclock it in need a fan. Is something like ARCTIC Breeze Mobile will be OK?
4. Is there a possibility to overheat it do death? Does it have some kind of safe feature like in desktop computers where you can't easily "burn" your processor?
5. I understand frequency setting which I can change in the Start_Moonlander.bat file, bot how is it connected with voltage adjustment? Is there any table or chart, for example if frequency is set to X turn voltage to Y?
I apologize for my ignorance and I hope someone would be so kind to answer my questions.
1) Yes you need to download the silicon labs COM drivers for windows 10, as well as the actual bfgminer driver to run these 2)I mean you can run these on a solo pool, where the pool pays you out for the entire block if your miner is the one that actually happens to find the right solution (the current block reward for litecoin is 25 LTC, so that roughly equals about 100 bucks). Nicehash has a nice solo pool https://solo.nicehash.com/3)Yes, as long as some airflow is blowing over the fan blades even high end clock speeds will be fine 4) Yes...there is no internal temp on this asic...it will most likely just crash before it fries itself, but damage is still a possibility especially if it runs at over 90C for any lengthy period of time. 5)You just have to play with it...you can run bfgminer in -benchmark mode which will return many shares/s...which will allow you to see your hardware error rate in real time. You can then manually change the voltage with the pot as you watch the error rate. Just turn the voltage down untill you see lots of errors, then slowly turn it up. Once it reach nearly zero errors you know you have found the sweet spot for that frequency. |
|
|
|
|
you planing on releasing linux binaries?
|
|
|
|
|
Yea these will drop down to about 800 each in 1-2 months...not sure how you get your power draw 4x worse than planned...
|
|
|
|
|
Post like this are pointless...I have my 470s running at 31mh but it does not mean its stable. Run this for more than 24 hours without it crashing a dozen times.
|
|
|
|
|
Hey sorry have been pretty busy lately....just pm me on here and ill get up to date to all the PMs I got. Bfgminer port is open source and is included in luke's official repo so its just a matter of downloading it. Like others said you do need to flash the boards with new firmware, and ill PM you the flash file you need for that. The instructions for it are detailed in the litecointalk thread.
|
|
|
|
|
yes...those pads are for a capacitor and they are shorted by that solder splash...thats a bad boo boo. Thats why you have to once over these cheap chinese risers.
|
|
|
|
Claymore...you should bundle the shared linux libraries your miner depends on (ex libcurl.so.4), that way we dont have to install all the ethereum crap just for a mining machine. |
|
|
|
I can save you a whole set of PSU/MOBO and run an extra GPU (i.e. 8 GPUs per system) WITH a server rack case for that price |
|
|
|
|
That wont work...the risers use, and need the 5v input from the molex.
|
|
|
|
|
Show Posts
