GUI mining - updated Dec 3 with 7970 bugfix, also supports Stratum!

[Chimel]

I have a 8800 (GTX) like nickman, but it connects fine.
I was wondering however if a 26MH/s rate was normal for this video card, when I see recent cards going at 400MH/s.
A bit off-topic, but is there a reference chart listing the MH/s rate for different GPUs?

It does not look like guiminer is actually using the card at all, there's no CPU/memory usage, as expected for a GPU app, but there's also no more heat than usual (the GPU fan usually starts rotating faster and making more noise if the GPU is heavily used.)
Is there a way to increase the GPU usage in guiminer? I couldn't find any setting in the UI.
I thought maybe the default miner was wrong, so I created a second CUDA miner, but it only went from 26MH/s for the unique default miner to 1MH/s for default and 25MH/s for CUDA.

Is there a help site to learn more about guiminer, aside from this (long) thread? Like all the switches that are mentioned here.
And another noob question: I am not using a dedicated mining machine, it's my main desktop machine, but I noticed the MH/s rate is the same when I am not using the machine. It would be great to max out the GPU automatically when the computer is idle.

I am just getting started on the whole bitcoin thing, so I appreciate a lot the GUI approach.
It might benefit from a little more UI simplification or integrated help for the bitcoin newcomers.
For instance, a real setup. Guiminer currently does not run if you copy the folder to Program Files because of the Windows permissions. It's also not listed in Add/Remove Programs Control Panel.
Solo mining is unnecessarily complex too, it should probably launch the bitcoin client as server automatically, as it's not clear it's a required step. Not even sure why a password is required for solo mining.
Sorry, I know it's done on your own time, I am not making requests, it's just directions if you intend to go that way.
I have installed the latest version, so I don't know how updates work, if they are automated or not, but I suggest to track the MH/s rate before and after the updates, to offer a revert to previous version option in case the update affects negatively the MH/s rate. That'd be cool!

Now on to some GPU hunt...

[1714050601]

1714050601

[1714050601]

1714050601

[1714050601]

1714050601

[shivansps]

there nothing wrong there CUDA init takes a very long time.

[petercyr]

@Chimel Nvidia cards don't do really well for bitcoin mining.

Here's the cart -> https://en.bitcoin.it/wiki/Mining_hardware_comparison

[Chimel]

Thanks, @petercyr, I knew there'd be such a chart somewhere!
Wow, it looks like the miner apps are not optimizing CUDA at all, just for Stream.
Top of the line Nvidia GPUs have similar or better performance than Radeon for gaming, yet 4 times less for mining.
I guess my new machine will be a Radeon 6xxx series...

[neijek.bit]

I tried using search, but I did not quite find the "resolution" to this problem... so i figured I would ask.

First of all, thank you so much, as soon as a few bitcoins are in my wallet I will donate for sure... meanwhile though if you have an idea as to what might be causing this I would so appreciate a reply.

If i start the latest version of the miner (not the new beta from today but the latest release).. and i set it up to do CUDA mining within my mining group .. i'm getting a nice and constant 45m/s which based on my card (nvidia450gts with slight over clock and no extra "flags" used) i gather is "ok".

BUT

If i "stop" mining, then use my pc a little (say watch a movie via vlc.. or run a game client) then i close everything and go back to "start mining" it will top out around 19m/s and stay there.. reguardless of what I do. Only way to get it back to the "right" 45~m/s range is to re-start my pc, then it will go at 45 for days with no issues...

Any ideas?

If you need more info ler me know, but I have win7 installed, latest version whql drivers for the card and .. thats about all i think is important no?

Thanks...



--- EDIT:

I'm including the logs where you can see that right after "starting" and then "stopping" if i start the cuda miner again the video card slows down drastically (about half as fast).

Code:

2011-06-12 02:42:45: Running command: C:\Users\hidden\Downloads\guiminer\miners\puddinpop\rpcminer-cuda.exe -user=hidden -password=hidden -url=http://hidden 
2011-06-12 02:42:45: Listener for "hidden" started
2011-06-12 02:42:46: Listener for "hidden": Client will start 1 miner threads
2011-06-12 02:42:46: Listener for "hidden": Work will be refreshed every 4000 ms
2011-06-12 02:42:46: Listener for "hidden": 1 CUDA GPU devices found
2011-06-12 02:42:46: Listener for "hidden": Setting CUDA device to first device found
2011-06-12 02:42:46: Listener for "hidden": Loading module bitcoinminercuda_20.cubin
2011-06-12 02:42:46: Listener for "hidden": CUDA initialized
2011-06-12 02:42:46: Listener for "hidden": Done allocating CUDA resources for (16,16)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (16,16) 476ms  prev best=9223372036854775807ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (16,32)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (16,32) 231ms  prev best=476ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (16,64)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (16,64) 120ms  prev best=231ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (16,128)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (16,128) 102ms  prev best=120ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (16,256)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (16,256) 98ms  prev best=102ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (32,16)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (32,16) 281ms  prev best=98ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (32,32)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (32,32) 120ms  prev best=98ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (32,64)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (32,64) 103ms  prev best=98ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (32,128)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (32,128) 100ms  prev best=98ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (32,256)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (32,256) 95ms  prev best=98ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (64,16)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (64,16) 277ms  prev best=95ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (64,32)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (64,32) 118ms  prev best=95ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (64,64)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (64,64) 101ms  prev best=95ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (64,128)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (64,128) 97ms  prev best=95ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (64,256)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (64,256) 94ms  prev best=95ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (128,16)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (128,16) 273ms  prev best=94ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (128,32)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (128,32) 117ms  prev best=94ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (128,64)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (128,64) 98ms  prev best=94ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (128,128)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (128,128) 96ms  prev best=94ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (128,256)
2011-06-12 02:42:56: Listener for "hidden": Finding best configuration step end (128,256) 93ms  prev best=94ms
2011-06-12 02:42:56: Listener for "hidden": Done allocating CUDA resources for (128,256)
2011-06-12 05:59:46: Listener for "hidden": Server sent: {"id":1,"error":null,"result":false}
2011-06-12 06:23:43: Listener for "hidden": Server sent: {"id":1,"error":null,"result":false}
2011-06-12 08:13:40: Listener for "hidden": Server sent: {"id":1,"error":null,"result":false}
2011-06-12 09:26:34: Listener for "hidden": Server sent: {"id":1,"error":null,"result":false}
2011-06-12 10:06:10: Listener for "hidden": Server sent: {"id":1,"error":null,"result":false}
2011-06-12 11:01:22: Listener for "hidden" shutting down
2011-06-12 11:04:03: Running command: C:\Users\hidden\Downloads\guiminer\miners\puddinpop\rpcminer-cuda.exe -user=hidden -password=italiano2005! -url=http://hidden
2011-06-12 11:04:03: Listener for "hidden" started
2011-06-12 11:04:04: Listener for "hidden": Client will start 1 miner threads
2011-06-12 11:04:04: Listener for "hidden": Work will be refreshed every 4000 ms
2011-06-12 11:04:04: Listener for "hidden": 1 CUDA GPU devices found
2011-06-12 11:04:04: Listener for "hidden": Setting CUDA device to first device found
2011-06-12 11:04:04: Listener for "hidden": Loading module bitcoinminercuda_20.cubin
2011-06-12 11:04:04: Listener for "hidden": CUDA initialized
2011-06-12 11:04:04: Listener for "hidden": Done allocating CUDA resources for (16,16)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (16,16) 1038ms  prev best=9223372036854775807ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (16,32)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (16,32) 507ms  prev best=1038ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (16,64)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (16,64) 264ms  prev best=507ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (16,128)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (16,128) 241ms  prev best=264ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (16,256)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (16,256) 221ms  prev best=241ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (32,16)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (32,16) 926ms  prev best=221ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (32,32)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (32,32) 264ms  prev best=221ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (32,64)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (32,64) 238ms  prev best=221ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (32,128)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (32,128) 224ms  prev best=221ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (32,256)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (32,256) 216ms  prev best=221ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (64,16)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (64,16) 913ms  prev best=216ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (64,32)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (64,32) 261ms  prev best=216ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (64,64)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (64,64) 237ms  prev best=216ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (64,128)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (64,128) 220ms  prev best=216ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (64,256)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (64,256) 214ms  prev best=216ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (128,16)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (128,16) 898ms  prev best=214ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (128,32)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (128,32) 259ms  prev best=214ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (128,64)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (128,64) 234ms  prev best=214ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (128,128)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (128,128) 217ms  prev best=214ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (128,256)
2011-06-12 11:04:14: Listener for "hidden": Finding best configuration step end (128,256) 212ms  prev best=214ms
2011-06-12 11:04:14: Listener for "hidden": Done allocating CUDA resources for (128,256)
2011-06-12 11:04:43: Listener for "hidden" shutting down

[Kiv]

The GUI itself actually works fine on Linux if you run the Python source code from GitHub. The only problem is figuring out how to get it set up properly with the OpenCL drivers. When I tried to get it going the first time I had some frustration with installing the wrong drivers, and then PyOpenCL was fussy, etc.

What Linux support needs at this time is for some Linux guru (I don't qualify) to write up a post on how to painlessly get the environment set up. Probably this could borrow heavily from posts on how to get poclbm set up; the only additional requirement the GUI has over poclbm should be the wxPython library.

Kiv are you making the Linux version? 

[BombaUcigasa]

I have a 8800 (GTX) like nickman, but it connects fine.
I was wondering however if a 26MH/s rate was normal for this video card, when I see recent cards going at 400MH/s.

If it's any consolation you can overclock everything by 15% and get up to 30MH/s...

[the_joey_o]

I'm sure I'm doing something really obviously wrong here, but I have no idea what it is. Whenever I click the "Start mining!" button, it doesn't start mining. Both my GPU and my CPU are showing up in the Device drop down menu. I have an AMD Phenom II X4 CPU & an AMD Radeon HD 5770 GPU. Here's what my console is showing (I tried running it with flags and without):

Code:

2011-06-11 19:13:58: Running command: poclbm.exe --user=###.### --pass=### -o mining.bitcoin.cz -p 8332 --device=0 --platform=0 --verbose -v -w128
2011-06-11 19:15:03: Running command: poclbm.exe --user=###.### --pass=### -o mining.bitcoin.cz -p 8332 --device=0 --platform=0 --verbose 

[Kiv]

That's extremely strange. Mine has the exact same console output and works fine. If the devices are shown in the Device drop down, the drivers are clearly installed correctly and I'm not sure what the issue could be.

I'm not sure if the two output lines you showed are for the same miner or two different ones, but is device 0 the one you mean to be using?

All I can think for you to do is try opening a command prompt and running the same command as you see in the console (in other words launching poclbm directly) and see if you get anything more descriptive in the command prompt output.

I'm sure I'm doing something really obviously wrong here, but I have no idea what it is. Whenever I click the "Start mining!" button, it doesn't start mining. Both my GPU and my CPU are showing up in the Device drop down menu. I have an AMD Phenom II X4 CPU & an AMD Radeon HD 5770 GPU. Here's what my console is showing (I tried running it with flags and without):

Code:

2011-06-11 19:13:58: Running command: poclbm.exe --user=###.### --pass=### -o mining.bitcoin.cz -p 8332 --device=0 --platform=0 --verbose -v -w128
2011-06-11 19:15:03: Running command: poclbm.exe --user=###.### --pass=### -o mining.bitcoin.cz -p 8332 --device=0 --platform=0 --verbose 

[the_joey_o]

That's extremely strange. Mine has the exact same console output and works fine. If the devices are shown in the Device drop down, the drivers are clearly installed correctly and I'm not sure what the issue could be.

I'm not sure if the two output lines you showed are for the same miner or two different ones, but is device 0 the one you mean to be using?

All I can think for you to do is try opening a command prompt and running the same command as you see in the console (in other words launching poclbm directly) and see if you get anything more descriptive in the command prompt output.

I'm sure I'm doing something really obviously wrong here, but I have no idea what it is. Whenever I click the "Start mining!" button, it doesn't start mining. Both my GPU and my CPU are showing up in the Device drop down menu. I have an AMD Phenom II X4 CPU & an AMD Radeon HD 5770 GPU. Here's what my console is showing (I tried running it with flags and without):

Code:

2011-06-11 19:13:58: Running command: poclbm.exe --user=###.### --pass=### -o mining.bitcoin.cz -p 8332 --device=0 --platform=0 --verbose -v -w128
2011-06-11 19:15:03: Running command: poclbm.exe --user=###.### --pass=### -o mining.bitcoin.cz -p 8332 --device=0 --platform=0 --verbose 

I restarted my machine and ran CCleaner and suddenly it works! And it works at about 2.5X what I was getting before I tried your miner! I ran CCleaner simply because I've been meaning to, not because I thought it would fix this. And, I don't know if it or the restart was what fixed this issue. But, hey! I'm running faster than I ever have! Thanks so much!
--Edit--
I forgot to add in the extra flags. I'm now getting triple the Mhash/s rate I was getting before!

[LegitBit]

It also has a test version of CPU affinity built in, so if that's a feature you were waiting for you can test that out too for me

Awesome. 0.02 BTC going your way.

[becoin]

When I try to start guiminer mining, I get "Problems communicating with bitcoin RPC" in the status bar and the miner doesn't start. I already checked that my bitcoin.conf contains the correct username and password. I am using:

GUIMiner version: v2011-06-09
Operating system: Vista SP2
Video card: nvidia geforce 9200m gs
Server: solo mining on Bitcoin client 0.3.22

Anyone having same config and problem?

[Dobrodav]

Do you trying to mine solo ? Login/pass in bitcoin.conf are just for solo mining.
If you mining solo - use other version of bitcoin client (not 0.3.22) or read through theme about 0.3.22 at forum and tune it up.

When I try to start guiminer mining, I get "Problems communicating with bitcoin RPC" in the status bar and the miner doesn't start. I already checked that my bitcoin.conf contains the correct username and password. I am using:

GUIMiner version: v2011-06-09
Operating system: Vista SP2
Video card: nvidia geforce 9200m gs
Server: solo mining on Bitcoin client 0.3.22

Anyone having same config and problem?

[faille]

I had guiminer to auto load on windows startup and the miners to be autostarted.
This generally resulted in a hardlockup on booting up, so had to turn off the autostart option on the miners.
Is there something I should do to avoid this?
Alternatively, Is there a feature I'm missing to set a delayed autostart for the miners? ie after 1 min from guiminer loading they start up?

[becoin]

Do you trying to mine solo ? Login/pass in bitcoin.conf are just for solo mining.
If you mining solo - use other version of bitcoin client (not 0.3.22) or read through theme about 0.3.22 at forum and tune it up.

Thanks, Dobrodav. Yes, I'm trying to setup solo mining with login/pass in bitcoin.conf. Which version of bitcoin client is best suited for this?

[PGPpfKkx]

proposal to the creator:

make the gui accept backup miners so if one cant connect it has its backup buddy and autostarts it. this way when pools go down we dont loose money!

[LightRider]

Thanks for the new backend support!

[Lightspeed]

I want:

yes another backup pool request

after 10 minutes of no activity / no connection - play an alarm (make it optional, the length of time configurable and the sound/music play mp3 + wav files with 1 default one included in the app)

bottom right total hashrate, as soon as I hit 1Ghash/sec I want to be able to see another 2 decimal places - can you add this? since there is no total column in MH/s it makes it harder to judge risk/rewards for overclocking/total heat output etc (im too lazy to sit there with a calculator)

[Dobrodav]

For now, most suitable version of bitcoin client for windows is  0.3.20.

[stellan0r]

Great work Kiv!

I have two questions for you:

Are you working on a version for Linux already, or do you need to get a better poll result for that?

And second, this was already asked for, can you please put a "idle/disconnect worker" feature in it? Say if have 6 different pools set up and I am always running 2 miners/pools on 1 gpu, now one or two of these go down, I want guiminer to auto-switch to the other miners i have set up in either a random or defined order - and maybe a switch back feature, guiminer checks if the miners can reconnect to pool 1 or 2 after X minutes and quit work with miner/pool 3 or 4 and so on. A way you kind of never stop mining for one of your favorite pools!

Would be totally awesome if this feature would be possible and be build in