 Show Posts
|
|
Pages: [1]
|
Depends upon the quality of the PSU. Weak 600W will be same as 300W quality. Weak: All is counted as total. Corsair, Enermax atleast count ONLY 12V rail outputs to the marketed total. 2x6770 sucks about 220W, my CPU (even tho it's extreme series) prob around 130W, and rest prob 50W. and GPUs and rest don't enjoy even solely 12V. In any case, they are now running stable on the *same* system, in crossfire. Kind of, still reports 2 adapters, yet i got crossfire enabled. Whatever, is not crashing anymore. (Not needed for gaming). Next week 2x5970 arrives anyway and got to upgrade PSU, hopefully some store will have 1kW enermax in stock  Oh and quality differs: 550W cheapo PSU was not able to power up a system which a really old Enermax 350W was happy to powerup I think that system required something like 450W and the really old, too small Enermax didn't have problems with that  Running in crossfire will cut your hash rate by 15 to 30%. Run both cards independently and make sure you either have a second monitor, or a dummy plug ooked to the second card. |
|
|
|
|
You probably need to experiment with -v and -w commands to find out what works best with your setup.
|
|
|
|
If you have a monitor always plugged into the second card as well, you don't need a dummy plug. Updated to cat 11.6 and had to change some settings around. Seems that optimum now for my cards is -v 18 -w 128 and I'm still getting ~450Mh/s with both cores oc'd to 875MHz (stock 775), memory at 500MHz. Temps are at 60c on both cards with the side of the case off and a house fan blowing into the case. I had to move the bottom card down to the lower pci-e x8 slot (no performance loss) to achieve this. Top card was running at about 80c when they were close. I guess that's about all I'm going to get. I noticed no difference in performance with the crossfire cable off or on, but, it's off because that's what you recommend. Seems that my usage fluctuation problems have been taken care of after I unplugged all the unnecessary components (pc was originally designed for gaming). Both cards have been pegged at full load for over two hours now. So I think I'm ready to let her sit and look for a while. Again, thanks for the great miner and all the help, diabloD3. |
|
|
|
|
Yeah I get ~450 Mh/s with 2 6850's.
|
|
|
|
BTW, yes, 0 accepts and 0 rejects are valid for solo mining. At the current difficulty it will take you about 14 weeks on average to find a block, which then accepts will turn to 1.
Disconnect your crossfire cable if you have crossfire disabled. If you're solo mining, the only thing you need to give to DiabloMiner is -u and -p, -o and -r are already set correctly by default for local solo mining.
From your description in the other thread, it almost sounds like its failing to connect to Bitcoin (which eventually will timeout) during startup.
Also, are you using a dummy plug on your second GPU? With crossfire off, Windows turns cards off, even if they're in use, when there is no monitor plugged in. I got the bitcoin client working. It's at 48 connections and your miner is hashing. That's about all I know what to look for to be able to tell if it's working. The command I use to connect is diablominer-windows.exe -u XXXX -p XXXX -v 19 -w 192. I have a monitor hooked up to the second card. As I said in the other thread, if I disconnect the crossfire cable I get bad core usage fluctuations according to msi afterburner. It's more stable with it connected. Crossfire is disabled in catalyst control center as well. All along I've had full load on both cards, other than fluctuations. Do I need a dummy plug? To my understanding a dummy plug is only used if you don't have a monitor hooked up. I can view the desktop on my 2nd monitor as well. Thanks again for all the help. |
|
|
|
My math gives about 469 combined for two 6850s if you can find the right settings, but its more likely to be in the 450s because you're on SDK 2.4. A 6870 is about as fast as a 5850 at their respective stock clocks, a 6850 is about 1/3rd slower than a 6870 at their respective stock clocks, and a 5850 is about 1/4th slower than a 5870.
So 450s for two overclocked 6850s is in the right ballpark if a overclocked 5870 is doing 450.
Thanks for the info man. I needed some closure lol. I think my main problem is the power supply in my computer under volting causing fluctuation performance (600w coolermaster). I'm going to try unplugging my 2 dvd burners and my second hdd to see what happens. So do you recommend reverting to an earlier revision of sdk? |
|
|
|
I'm pushing ~450mh/s on 2 6850's oc'd to 875 on the cores. Does that sound right? Based on what I've read on this forum, people with single 5870's push the same thing. So, in theory, I should be pushing at least 650 and at most 800. I'm running one of your recommended settings -v 19 -w 192 after hours of fishing for the sweet spot. I made a post in the newbie section, http://forum.bitcoin.org/index.php?topic=18632.0, because I was unable to post here. There's more info on the way I have things set up, in that thread. Another question I have is, is it safe to assume that your program reporting accept: 0 reject: 0 hw error: 0 is normal on solo mining? I'm guessing that it wont start processing a block until it finds one, so those numbers will remain at zero, right? I know, I'm a nub, but, you gotta crawl before you walk, lol. |
|
|
|
Thanks for the info, man. Definitely helped to bring things into perspective. Yeah, the market got flooded with the 25k btc that were stolen causing the value to drop, causing people not to trade, causing the difficulty to go up. It's a snowball. I myself have a pretty good feeling that people will buy them up and hold on to them, increasing the rarity/value. The difficulty will drop. Patience is a virtue, lol. Statistics over a two year time period don't lie. I'm now riding the roller coaster. I can wait, haha. Check out http://bitcoincharts.com/markets/ if you haven't already. |
|
|
|
If you didn't get to 1 coin in 4 days, you're looking at an AVERAGE of more than a month to find a block your, that doesn't include the difficulty increasing.
Yeah, sorry, I failed to mention that I started 4 days ago and I've had the miner off and on trying to optimize it, so my contributions kept resetting. If I'd left the miner on I'd probably be a lot further ahead. I'm pushing ~450 mh/s (which I thought was a bit low for my cards, hence my "cry for help" thread). |
|
|
|
Can a mod please move this to the tech support section? Or, someone report this to get moved? I'm a jr. member now . Maybe someone can help me out over there. |
|
|
|
|
The bitcoin client is used for solo mining. You view your payouts on the website of the pool you belong to. I was mining for mining.bitcoin.cz and their site has a payout threshold of 1 coin by default. So, I was getting fractions of a coin based on the pool's size and when someone in the pool found a block. mining.bitcoin.cz has about 2500 workers fishing last time I checked. I ran for about 4 days and never hit a 1 coin payout. So, yeah, lol, do the math.
If your miner is running as it should, track your payouts on mining.bitcoin.cz. I'm running solo now, mainly because the anticipation of possibly finding a block and getting 50 coins is more gratifying to me than seeing a payout of 1000th's of a coin on every block that is found by the pool.
|
|
|
|
|
Yeah. Read up, lol. I got bad hash rate fluctuation. GPU usage per card would drop to 0% 30% 75% 20% etc. etc. every few seconds, and would stay at that percentage for a couple seconds, then go up without the crossfire cable. With the crossfire cable, gpu usage percentage stays at 99% and (with the clock on both gpu's at 875), I'm now averaging ~ 450mh/s.
|
|
|
|
|
Anyone have any other ideas?
|
|
|
|
|
Thanks for the reply! Was wondering when I would get noticed, lol.
6850's are single core cards. Whenever I start diablominer, it says it's connected to both cores (2 cards = 2 cores). Is there an argument that is used to specify if you want 1 instance of diablominer on a single core? If I start multiple instances of diablominer it cuts my hash rate in half in both instances. I've tried different -v and -w value combinations and still -v 19 -w 192 works the best. I tried removing the crossfire cable and I got pretty much the same hash rate, but bad fluctuation.
To my knowledge, having one instance of the miner running is addressing both cores because I get full load on both of them at all times.
|
|
|
|
|
I figured out the bitcoin client problem. I just had to download the latest revision. I'm still only hashing at ~400 Mega hashes/sec. Some help would be nice...
|
|
|
|
|
Anyone? I don't like to bump, but, could this get moved to a section where it might possibly get some attention?
|
|
|
|
|
I've been battling with learning how this works for about 4 days now. I've managed to get diablominer to work for me using the api.bitcoin.cz pool. I'm not too sure on what I'm seeing at the bottom of the screen. I average around 400 mhash's, at least I think.
I'm assuming that mhash 401.1/402.8 means that 401.1 is realtime because it fluctuates and 402.8 stays the same meaning it's an average. At first I thought that those were the numbers both cards were pushing.
Anyway, I'm running 2 6850's. Crossfire is disabled. Catalyst 11.5b and sdk app 2.4. There are monitors hooked up to both cards. There's a crossfire cable in place. Both gpu's report full load according to msi afterburner. Diablominer reports that it's connected to both cores (barts 1 and 2). I start the program by going to the c drive and shift right clicking the diablominer folder to open a cmd with the path already specified. Then I type out the start command diablominer-windows.exe -u xxxxx -p xxxxx -o api.bitcoin.cz -r 8332 -v 19 -w 192.
All is well and good except for the fact that I read on here that people with single 5870's are pushing around the same hash rate as me.
I've also read on here that people are starting their miners in java directly, but, according to the original diablo3 post, I'm doing it the right way.
So, which way is the right way? Why are my 2 card's producing the same hash rate as a single card?
Another thing is that I've been 100% unsuccessful at solo mining. I have the bitcoin daemon. I start it with the -server command. It starts. I have the config created and it's right (i've tried about 4 different suggestions). When I start diablominer, it gets as far as connecting to the first gpu core and stops.
So, yeah, lol. I'm at a loss here. Any help would be greatly appreciated.
|
|
|
|
|
I've been working on learning bitcoin mining for about 4 days now. I've been able to successfully get diablominer working on the api.bitcoin.cz pool at about 400mhs on 2 6850's, which I think is kinda low because I see people with single 5870's pushing that. Not trying to turn this into a help question lol. Mainly I need help with understanding what I'm looking at and command line parameters. I'm a fast learner and I know what I'm doing most of the time. I've just hit a road block and need help to get around it. Thanks. Ken.
|
|
|
|
|
