Topic: DiabloMiner GPU Miner - page 55. (Read 866596 times)

If it crashes after 2 hours of OC, you might be OCing too far.

Im surprised any of the 30s do anything reasonable at all.

Most people find -v 2, 3, and 19 to be the best with some -w setting tuning it.

It doesnt nonce steal because it costs nothing to get more... if you're pool mining and your network has a lot of lag this can screw stuff up, but it looks like you were solo mining, which leads me to believe low -f values on Windows are screwing over bitcoin due to Window's craptastic scheduler.

Also, benchmarking on low -f values are difficult. Due to Windows' broken clock implementation, the first number (the 15 second avg) reports rather random values. The only way to stop that is to run for at least 5 minutes and use the second number (the forever average) only.

Other than that, interesting table.

I got yesterday a MSI 6950 rev.1 I was difficult to find a unlockable 6950 but still there are some models out there.
So as it was going to be my main miner for some time (still have a 5770 but I can have both on my computer due to the PSU) I made a real table of doom with every vector option and most of the worksizes for the best -vs most of the measures are no more than 5 minutes enough to see the possible outcome with more fine tunning.
I remeasured the best during the whole process, stock -> unlock shaders -> be aggresive -> OC
Catallist 11.5 SDK 2.4 Windows 7 Ultimate 5Gb DDR2-800

V	W	Config 1	Config 2	Config 3	Config 4
1	64	290
1	128	290
1	192	291
1	256	287
2	64	308	338		370
2	128	305	337		364
2	192	308	307		340
2	256	265	282
3	64	263
3	128	256	307
3	192	305	339	347	373
3	256	264
4	64	285
4	128	242
4	192	187
4	256	241
5	64	236
5	128	240
5	192	178
5	256	240
6	64	242
6	128	238
6	192	176
6	256	242
17	64	291
17	128	291
17	192	291
17	256	270
18	64	303	330		355
18	128	274
18	192	274
18	256	232
19	64	278
19	128				259
19	192				195
20	64	115
21	64	177
22	64	doesn't work
23	64	doesn't work
33	64	287
34	64	303	330		357
34	128	360
34	192	363
34	256	249
35	64	278
36	64	262
37	64	290 22% fail
38	64	180
39	64	183
40	64	182
41	64	106
42	64	116
43	64	119

Config 1 - Stock -f 60 -dd 800/1250@1100
Config 2 - Unlocked shaders -f 60 -dd 800/1250@1100
Config 3 - Unlocked shaders -f 5 -dd 800/1250@1100
Config 4 - Unlocked shaders -f 15 -g 4 -dd 900/1200@1129

I have been able to reach 408Mhs being more aggresive on the OC and -f but after 2 hours miner crashed

Also with this card I can not see flash videos (I hade no problems with 5770 and SDK 2.1) becouse the miner also crashes.

From the data I am unable to reach to any conclussions as with some config OC or unlicking doesn't improve a bit, -v 34 is a good number, -v 37 just gives 22% of HW errors... Anyway my best setup is -v 3 -w 192 similar to -v2 -w 64 but a hell more stable

There is a significative drop in MHs when the nonces are exhausted, it seems a thread just sits waiting while we must have some unused nonces from other threads, and also the spureus errors but ina lesser extent.

Not sure if this info will be valuable for someone else but here it is for reference.

What, seriously? Thats bad.

I had the same problem when setting up the miner. There seems to be a problem with the most recent version of bitcoin (0.3.22-beta). Try version 0.3.21-beta and it should work - given that the rest of your setup is okay.

-D 0 isn't valid, thats why. It starts at 1, and you shouldn't be using -D anyhow unless you have a very specific reason to.

I'm getting the same kind of issue with Window 7 64 bit.

If I run Diablo-Windows.exe with no params, it will start hashing using the GPU, but can't connect to bitcoin. 
If I use the -u -p params (Diablo-Windows.exe -u uid -p pwd) it just sits there after adding the GPU
Added GeForce GTX 580 (#1) (16 CU, local work size of 1024)

Figured it out:

Made a small bash script called 'run' that does:
./DiabloMiner-OSX.sh --url ...

I created an AppleScript that does:
do shell script "/Users/user/DiabloMiner/run"

I saved it as an 'Application' with 'Run only' checked.

I then downloaded iBackground Scripts and used it to launch the AppleScript. Once that's done, I added the AppleScript file to the Login Items for the user. Seems to be working fine. Shitty video card/OS, as it's getting ~50MH/s

Is it possible to have DiabloMiner running on a Mac in the background? Meaning, it doesn't display a terminal window when running, I just want it to run silently. I have added it to my user's Login Items, but it pops up that Terminal window.

Diablo,

In a previous post you did slash the average hash/s function on deepbit. I am a bit puzzled though: I manage close to 800Mh/s according to dm's output. However, whenever I look at deepbit, I see roughly dm/2. This is fully reflected in the share I receive. Using poclbm, I only managed about 90% of dm's rate, however, the values on deepbit and my share nearly doubled...

It gives me the same result each time I run it.

It appears in my process list but I never see any CPU consumption at all and GPU Caps doesn't show anything changing as I launch it.  I'm on Windows Vista Ultimate 64 SP2, if there are any known issues.

If I run it with -D 0, it doesn't write this line to the terminal:

[6/9/11 10:12:49 AM] Added GeForce 9600 GSO (#1) (12 CU, local work size of 512)

and instead writes "waiting..." and then replaces that with "0/0 khash/sec"

Is there any diagnostic info that I can provide that would tell you what's going wrong?

Yes, the terminal is that.

It almost sounds like the miner locked up.

So, if the last thing to appear in the terminal is
and it appeared five hours ago.  Then what should I be looking to correct?

And just to be sure, the terminal is the command line window, right?

I did not formally learn to program, I learned how to program by doing it day in and day out for over a decade (which, honestly, is the only way to learn how to program, no college degree is magically going to make you know how to).

I do not have a job that reflects my skill set.

If the miner is functioning correctly, it should be at the bottom of the terminal.

Diablo,

Sort of a personal question. Where did you learn to program? Did you get a CS/CE degree? Do you have a good job and if so what is it and do you enjoy it?

Where is that?

The hash meter is the thing that says xxxx/xxxx khash/sec.

The Bitcoin client no longer mines because its pointless.

The hash meter?

Also, am I correct in thinking that if a block is found, it will show up in the Bitcoin client?  And a year ago, the Bitcoin client showed hash rate in the lower left corner of the gui, but it doesn't now.  Does that mean anything or just that it doesn't mine anymore?

Don't use -D unless you specifically want to NOT use certain GPUs in a multi-GPU setup.

You will not get any additional log output unless you find a block, or there is an error of some kind. The hash meter is pretty much it.

Is there a document somewhere that shows me what I should expect to be seeing upon first running DiabloMiner?  Maybe it's doing what it's supposed to but the stuff I'm reading in this thread makes it seem like I should be getting more feedback in the cmd window.

I'm running with: DiabloMiner-Windows.exe -u uid -p pw (and then several different attempts to include -D with: 0; 1; 2; 1,2)

And I get stuff like:

[6/9/11 10:12:48 AM] Started
[6/9/11 10:12:48 AM] Connecting to: http://127.0.0.1:8332/
[6/9/11 10:12:48 AM] Using NVIDIA CUDA OpenCL 1.0 CUDA 3.1.1
[6/9/11 10:12:49 AM] Added GeForce 9600 GSO (#1) (12 CU, local work size of 512)

And then nothing else for at least fifteen minutes (so far).  Is it just doing work and I'll see more when it has something to report?  Or is waiting a waste of time because I made some simple mistake?

I'm also running GPU Caps as suggested in your wiki instructions and it shows a GPU load of 0.0% near the bottom of the main GPU tab, but I don't really know how I should be usign that tool to check in.