is it super duper faster yet?
Sure, its pretty close to as fast as its going to get.
Topic: DiabloMiner GPU Miner - page 19. (Read 866596 times)
is it super duper faster yet?
Sure, its pretty close to as fast as its going to get.
is it super duper faster yet?
I've been using a few months old version which would keep having kernel queue errors on my Nvidia GPU. But I upgraded to a 6870 and the kernel queue errors went away... or so it seemed. I got one last night. Very frustrating because I'm trying to mine and I don't want my freaking miner to stop working.
So I upgraded to the most recent build but it dropped by hash rate by 100Mhash/s. WTF? I fiddled with other configurations but the highest I could get was a drop of 40Mhash/s instead. So I reverted to the build I had.
Is there some reason why I'm getting these kernel queue errors, and why upgrading the build drops my hash rate so much? I was told kernel queue errors are driver bugs, but I'm wondering if that's true when I keep changing my drivers to newer/older versions looking for a fix and nothing works.
I'd give the version of DM I'm using but I actually can't find the version number in the docs, seriously WTF?
Anyway my config is -w 128 -v 2,1 -f 240 and it gives about 290-310Mhash/s on this GPU, no overclock, if that helps.
So I upgraded to the most recent build but it dropped by hash rate by 100Mhash/s. WTF? I fiddled with other configurations but the highest I could get was a drop of 40Mhash/s instead. So I reverted to the build I had.
Is there some reason why I'm getting these kernel queue errors, and why upgrading the build drops my hash rate so much? I was told kernel queue errors are driver bugs, but I'm wondering if that's true when I keep changing my drivers to newer/older versions looking for a fix and nothing works.
I'd give the version of DM I'm using but I actually can't find the version number in the docs, seriously WTF?
Anyway my config is -w 128 -v 2,1 -f 240 and it gives about 290-310Mhash/s on this GPU, no overclock, if that helps.
You might be facing different issues all at once.
First, DiabloMiner does not have a version number as I don't officially release it. Just follow it via git, github, or subscribe to this thread.
Second, remove -f 240. It'll make your desktop lag, but you don't need nearly as much -f to stop that, AMD drivers are much better built than Nvidia's. -f 30 or -f 60 is what most people use on AMD hardware depending on taste.
Third, 290-310 seems to be about right for a 6870 at stock clocks. And try -v 2 over -v 2,1, sometimes its faster, sometimes its not for vliw5 hardware.
Fourth, makes sure you're running Catalyst 12.3 WITHOUT SDK 2.6, 12.3 ships with the OpenCL runtime and its newer than whats in SDK 2.6.
GCN?
I've been using a few months old version which would keep having kernel queue errors on my Nvidia GPU. But I upgraded to a 6870 and the kernel queue errors went away... or so it seemed. I got one last night. Very frustrating because I'm trying to mine and I don't want my freaking miner to stop working.
So I upgraded to the most recent build but it dropped by hash rate by 100Mhash/s. WTF? I fiddled with other configurations but the highest I could get was a drop of 40Mhash/s instead. So I reverted to the build I had.
Is there some reason why I'm getting these kernel queue errors, and why upgrading the build drops my hash rate so much? I was told kernel queue errors are driver bugs, but I'm wondering if that's true when I keep changing my drivers to newer/older versions looking for a fix and nothing works.
I'd give the version of DM I'm using but I actually can't find the version number in the docs, seriously WTF?
Anyway my config is -w 128 -v 2,1 -f 240 and it gives about 290-310Mhash/s on this GPU, no overclock, if that helps.
So I upgraded to the most recent build but it dropped by hash rate by 100Mhash/s. WTF? I fiddled with other configurations but the highest I could get was a drop of 40Mhash/s instead. So I reverted to the build I had.
Is there some reason why I'm getting these kernel queue errors, and why upgrading the build drops my hash rate so much? I was told kernel queue errors are driver bugs, but I'm wondering if that's true when I keep changing my drivers to newer/older versions looking for a fix and nothing works.
I'd give the version of DM I'm using but I actually can't find the version number in the docs, seriously WTF?
Anyway my config is -w 128 -v 2,1 -f 240 and it gives about 290-310Mhash/s on this GPU, no overclock, if that helps.
Why? It already allows nearly unlimited pools. I think you made a different mistake, such as not providing comma separated -u and -p as well.
Yep, something in config has been wrong. I rewrited its, and failover now working. Thanks!
Yeah, I think its 8332. Also, forget what I said, I forgot I removed the code that ignores port 80, it should in fact work.
Ok. Can you improve selecting different port in multipool configuration?
Why? It already allows nearly unlimited pools. I think you made a different mistake, such as not providing comma separated -u and -p as well.
Yeah, I think its 8332. Also, forget what I said, I forgot I removed the code that ignores port 80, it should in fact work.
Ok. Can you improve selecting different port in multipool configuration?
DiabloMiner automatically rewrites 80 to the default port to prevent user error.
I'm confused. Default port is 8332 ? With option -r 8332,8332 miner never connected to pool.metabank.ru, and switching to pit.deepbit.net automatically. Possible my miner is older verion.
In network monitor connections on port 80 is established:
Yeah, I think its 8332. Also, forget what I said, I forgot I removed the code that ignores port 80, it should in fact work.
DiabloMiner automatically rewrites 80 to the default port to prevent user error.
I'm confused. Default port is 8332 ? With option -r 8332,8332 miner never connected to pool.metabank.ru, and switching to pit.deepbit.net automatically. Possible my miner is older verion.
In network monitor connections on port 80 is established:
You can't use port 80 with DiabloMiner. Also, it will still emit the error, but it still switches to the next.
Why can't use? My rigs normally works with pool.metabank.ru and sends block to port 80 without errors. Problem only with switch to port 8332 of secondary pool.
DiabloMiner automatically rewrites 80 to the default port to prevent user error.
You can't use port 80 with DiabloMiner. Also, it will still emit the error, but it still switches to the next.
Why can't use? My rigs normally works with pool.metabank.ru and sends block to port 80 without errors. Problem only with switch to port 8332 of secondary pool.
That is detailed in the op post: just use commas in the arguments.
Tested with sample:
Code:
-o pool.metabank.ru,pit.deepbit.net -r 80,8332
With different ports, secondary not worked if primary fails. Error is "Read timeout"
You can't use port 80 with DiabloMiner. Also, it will still emit the error, but it still switches to the next.
That is detailed in the op post: just use commas in the arguments.
Tested with sample:
Code:
-o pool.metabank.ru,pit.deepbit.net -r 80,8332
With different ports, secondary not worked if primary fails. Error is "Read timeout"
Hi! How set secondary pool in failover configuration? Can miner works with several pools simultaneously?
That is detailed in the op post: just use commas in the arguments.
Hi! How set secondary pool in failover configuration? Can miner works with several pools simultaneously?
Ah-ha! So that explains why the setting doesn't seem to make a difference for me! Thanks for the explanation. 
Hi, folks. I'm experimenting with using my 6770 for mining using DiabloMiner. I love how easy this software is to set up, but there's one commandline switch I don't understand...
What does the -g switch do?
I'm getting a respectable 185-190 MH with my current configuration, but I'd like to improve my efficiency and keep the other miners in the pool happy. Will setting -g higher (or lower?) help me achieve that? (FYI, I have a good Internet connection and no issues connecting to the server for the pool.)
What does the -g switch do?
I'm getting a respectable 185-190 MH with my current configuration, but I'd like to improve my efficiency and keep the other miners in the pool happy. Will setting -g higher (or lower?) help me achieve that? (FYI, I have a good Internet connection and no issues connecting to the server for the pool.)
-g sets how often it pulls new work; however, it is completely ignored on any pool that does long poll and/or sets an expiry time. The default value of -g is whats recommended for solo miners.
Hi, folks. I'm experimenting with using my 6770 for mining using DiabloMiner. I love how easy this software is to set up, but there's one commandline switch I don't understand...
What does the -g switch do?
I'm getting a respectable 185-190 MH with my current configuration, but I'd like to improve my efficiency and keep the other miners in the pool happy. Will setting -g higher (or lower?) help me achieve that? (FYI, I have a good Internet connection and no issues connecting to the server for the pool.)
What does the -g switch do?
I'm getting a respectable 185-190 MH with my current configuration, but I'd like to improve my efficiency and keep the other miners in the pool happy. Will setting -g higher (or lower?) help me achieve that? (FYI, I have a good Internet connection and no issues connecting to the server for the pool.)
Jump to: