|
Interested in the last rig. Price shipping to saskatchewan in BTC or PP USD?
|
|
|
|
Hi,
I have 5 5970s I am considering selling. 1 with an extended warranty from memory express in canada.
They are all reference cards.
I also have two OCZ 1250 watt PSUs and two 890FXA-GD70 mbs loaded with a cpu and 1gb of ram.
They are located in western canada for shipping purposes.
Interested. How much for 2x 5970s, a board and a psu to Saskatchewan? |
|
|
|
every 18 months and start with the memory requirement at 6-8 gigabytes per process
6-8 gigabytes per each hash attempt? Then people who are non-miners and simply want to run the client to send/receive coins won't be able to do it, because verifying each block becomes too difficult for regular computers (that are supposed to multitask and run other apps at the same time). Well, surely any modern computer can still do 1-2 gigs per thread right? That still makes it gpu proof and adds to asiç cost |
|
|
|
I heard that Litecoin Scrypt can become more memory intensive by just changing a variable, is that right?
So what? You can make an ASIC that drives a DIMM socket or even a whole bank of DIMM sockets. It really isn't a rocket science. Same with FPGAs. The only wrinkle is that the current favorite: Spartan-6 has a MCB (Memory Control Block) that is designed to work with single memory chips, not the multiple chip memory modules. So the DIMM memory access logic would have to be soft-synthesized instead of the using hard MCB macro. The spartan memory controller is sloooooooow... for fast scrypt performance you need a lot of internal memory bandwidth. If you had quad channel DDR3 clocked at over 1600MHz you might be competitive, but a quad channel controller is expensive too The really easy way to make a coin that is asic and gpu proof is to simply double the memory requirements of the scrypt algorithm every 18 months and start with the memory requirement at 6-8 gigabytes per process (adjust the values in the paper above). gpus will never be able to mine it, and asics will require lots of ram to mine effectively. i'm hoping someone will implement this soon so I can stop mining litecoin and mine this instead. for whatever reason artforz decided against massive ram requirements (he thought cpu cache would be faster than gpu memory access, but if you look at the bandwidth obviously it is not), but there's still room for a scrypt based coin that gets exponentially more memory hard over time. |
|
|
|
Actually I think I did a not too shabby job with the difficulty as you can see we went from 256 to 3000 in less than 3 days and block generation adjusted beautifully.
Otherwise you'd been seeing lots of blocks coming in seconds apart.
No, you did a shabby job. You'll understand why later. May your coin serve as a warning to the community.  That is, if PPCoin hasn't already failed for some other reason at 3 non-coinbase transactions, as the error message may indicate. this sounds bad the testnet is your friend guys |
|
|
|
|
it's sad they're refusing to discuss the protocol openly. bitcoin's market cap will be in the billions by the time this thing is released
|
|
|
|
The common denominator there is all those PSU's are crap or underpowered. No offense.
The Antecs are great budget PSU's for casual rigs but high temps and high draw will shorten their life up a lot.
Number one thing you need when mining is good power supply. I've stuck with PC Power and Cooling and their seven year warranty and they'd yet to have to help me because they are all still working as advertised.
Just disconnect the fan from the PSU controller and connect it directly to the 12v so it's always spinning at 1500+RPM... I find heat to be a big killer |
|
|
|
|
you might wanna make it wait for 6 confirmations before you send out the return for rewards, it seems pretty dangerous to have it wait for 0 confirmations to send it.
edit: I see you changed that right after I mentioned it, haha.
|
|
|
|
btc, cash and ltc withdrawal frozen it's light out for btc-e i guess  |
|
|
|
|
bitinstant has removed btc-e payment options
|
|
|
|
very....wish i sold at my LTC at .2
I pulled everything I had off the exchange... This is more than likely a hacking and I doubt anyone is going to get anything back if that is the case  |
|
|
|
|
Someone just bought all the BTC and LTC available with millions of USD
epic?
|
|
|
|
|
pool works very good, no longer getting 9% stale thanks to higher share difficulty. i don't know why everyone isn't on this pool.
|
|
|
|
At the present price LTC represents an ~50% increase in mining profitability over BTC using AMD cards. The entire month of July has been a straight upward save for the panic sell surrounding BCX, a nearly linear trend for the price of LTC against BTC. How long do you guys think this can keep up? If the current rate of increase continues, we'll be at 0.02BTC/LTC in a month and a half. See http://www.cryptotron.com/ , when it comes back up. |
|
|
|
Yeah, that's what I expected... with reaper and --thread-concurrency of 7168, 8960, or 16000 and number of threads 1 (intensity 19) or 4/5 (intensity 13) should give you at least 400kh/s with a lookup gap of 2 and a worksize of 128 or 256
reaper chrash, chrash, chrash, chrash, chrash, chrash ...... whit : --------------------------------- worksize 256 aggression 19 threads_per_gpu 1 lookup_gap 5gpu_thread_concurrency 7168 --------------------------------- run normal but < 250kH/s something is very wrong, lookup_gap 2 should work fine. might want to try uninstalling 12.6 drivers and reinstalling them, and also uninstalling app sdk 2.6 and installing 2.7. other than that i do not know, something is broken. |
|
|
|
try --shaders 2048 and --thread-concurrency 10240
I'm starting to think something is wrong with your cgminer build though, these should not give 0 memory values
-------------------------------------------------------------------------------- [2012-07-28 22:57:09] Started cgminer 2.5.0 [2012-07-28 22:57:09] Probing for an alive pool [2012-07-28 22:57:10] Long-polling activated for http://ltc.xurious.com:9332/LP [2012-07-28 22:57:23] LONGPOLL from pool 0 detected new block [2012-07-28 22:57:33] Pool 0 http://ltc.xurious.com:9332 alive [2012-07-28 22:57:33] Error -5: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel) [2012-07-28 22:57:33] GPU 0 failure, disabling! [2012-07-28 22:57:33] Thread 0 being disabled -------------------------------------------------------------------------------- Yeah, that's what I expected... with reaper and --thread-concurrency of 7168, 8960, or 16000 and number of threads 1 (intensity 19) or 4/5 (intensity 13) should give you at least 400kh/s with a lookup gap of 2 and a worksize of 128 or 256 |
|
|
|
same whit --thread-concurrency 10240 .... try --shaders 2048 and --thread-concurrency 10240 I'm starting to think something is wrong with your cgminer build though, these should not give 0 memory values |
|
|
|
Use cgminer and these settings
--scrypt -I 19 --shaders 1792 --thread-concurrency 8960 -g 1
Should get 500+ kh/s
also try --thread-concurrency of 17920, may be a little faster
for the 7xxx series you must always use -g 1 to achieve high intensities
---------------------------------------------------------------------------------------- [2012-07-28 22:42:05] Started cgminer 2.5.0 [2012-07-28 22:42:06] Probing for an alive pool [2012-07-28 22:42:06] Long-polling activated for http://ltc.xurious.com:9332/LP [2012-07-28 22:42:28] Maximum buffer memory device 0 supports says 536870912, your scrypt settings come to 0 [2012-07-28 22:42:28] Error -61: clCreateBuffer (padbuffer8), decrease CT or increase LG [2012-07-28 22:42:28] Failed to init GPU thread 0, disabling device 0 [2012-07-28 22:42:28] Restarting the GPU from the menu will not fix this. [2012-07-28 22:42:28] Try restarting cgminer. Press enter to continue: ---------------------------------------------------------------------------------------- same for --thread-concurrency 8960 and 17920 Hum, that's strange, that's 5x the number of SPUs which should work. You can try the 7970 setting of --thread-concurrency 10240, I don't know why that wouldn't work. That is the normal error for incorrect buffer sizes though. I wonder why it doesn't work? Also --lookup-gap should always be 2, but that's the default |
|
|
|
i try use reaper v13 beta 4 x64 with that settings :
worksize 64
aggression 20
threads_per_gpu 1
lookup_gap 5
gpu_thread_concurrency 8192
its work , but only 240~220 kH/s for HD7950OC i think is too little.
my old HD6950 reached ~360 kH/s
but i stil lito to use cgminer
i try same worksize , thread_concurrency and lookup_gap but again fail.
Use cgminer and these settings --scrypt -I 19 --shaders 1792 --thread-concurrency 8960 -g 1 Should get 500+ kh/s also try --thread-concurrency of 17920, may be a little faster for the 7xxx series you must always use -g 1 to achieve high intensities |
|
|
|
|
dropped all mobo voltages by 20%, nb and ht by 100%, cpu to 0.9v and 1400mhz. now at 68w idle, mining at 150w versus 165w with no performance hit. Ddr3 is also at 800mhz/1.1v
|
|
|
|
|
Show Posts
