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?
-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 reported it to GitHub as a GPL violation. Lets see what happens.
|
|
|
|
This is what shows up in my terminal at the moment. Is there a way to utilize both GPUs at the same time? If not, is there way to just use my 9600M GT for mining and not the 9400M? I can't seem to get it to stop using the 9400M. [6/9/11 11:21:04 AM] Added GeForce 9600M GT (#1) (4 CU, local work size of 256)
[6/9/11 11:21:07 AM] Added GeForce 9400M (#2) (2 CU, local work size of 256)
[6/9/11 11:26:03 AM] Block 1 found on GeForce 9400M (#2)
[6/9/11 11:41:27 AM] Block 2 found on GeForce 9400M (#2)
[6/9/11 12:19:45 PM] Block 3 found on GeForce 9400M (#2)
2314/1936 khash/sec You're on one of those hybrid dual Nvidia setups. You can't force one on or the other. Use -D to force it to use the right one (starts at 1). |
|
|
|
If the miner is functioning correctly, it should be at the bottom of the terminal.
So, if the last thing to appear in the terminal is [6/9/11 10:12:49 AM] Added GeForce 9600 GSO (#1) (12 CU, local work size of 512) 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? Yes, the terminal is that. It almost sounds like the miner locked up. |
|
|
|
Forgive me if I am totally wrong.. but don't ATI cards have specific tessellation units separate from the shader ALU's?
Tessellation is a math heavy algo, but nVidia cards even surpass ATI's in this case.
Is that because of tessellation requiring more iterations? Math isn't my strong suit, but I figure a probe in that direction might help.
Both ATI and Nvidia have fixed function hardware dedicated to tessellation. Nvidia 5xx performance on tess is about the same as Radeon 5xxx/68xx performance, which both are really inferior to 69xx performance. |
|
|
|
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?
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. |
|
|
|
The hash meter is the thing that says xxxx/xxxx khash/sec.
Where is that? If the miner is functioning correctly, it should be at the bottom of the terminal. |
|
|
|
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?
The hash meter is the thing that says xxxx/xxxx khash/sec. The Bitcoin client no longer mines because its pointless. |
|
|
|
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. 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. |
|
|
|
What is this message I am getting on the easier (not so easier) DIABLOMINER gui interface for Java?
[6/9/11 9:34:19 AM] ERROR: Can't connect to Bitcoin: Bitcoin returned unparsable JSON
I cant find a real GUI for cooperative mining on MacOSX
Sounds like user error. |
|
|
|
A+++ software this is my new favorite miner
i got the same rates as i do on other miners except when this runs i can watch a movie or what ever i want while its going without glitching with other miners my computer glitches so bad the mouse pointer skips around the screen
thank you for the wonderful software
gtx 260 gpu using -platform=0 -w128
tried -w64 only had half the rate as -w128 and -w256 was slower to -w128 is the gtx 260s sweet spot with diablo
Um, platform is not a valid argument for my miner. thats strange cause i didnt include it and it said it didnt find an OpenCL device and i added the -platform=0 and it then said using NVIDIA CUDA OPEN CL i dont know what happened then i guess it was just a problem in windows because if platform is not specified in your code then it couldnt possibly have an effect to the outcome of the softwares reaction maybe it didnt initialize cuda correctly the 1st time and trying again worked Yeah, must be. Seriously, check the code yourself, line 140 and up. No --platform. |
|
|
|
A+++ software this is my new favorite miner
i got the same rates as i do on other miners except when this runs i can watch a movie or what ever i want while its going without glitching with other miners my computer glitches so bad the mouse pointer skips around the screen
thank you for the wonderful software
gtx 260 gpu using -platform=0 -w128
tried -w64 only had half the rate as -w128 and -w256 was slower to -w128 is the gtx 260s sweet spot with diablo
Um, platform is not a valid argument for my miner. |
|
|
|
What the hell is wrong with Nvidia lately. I swear to god I hit every goddamned Nvidia bug.
Dear Nvidia users: BUY AMD CARDS.
Is there any more information I can provide you that may help remedy the situation? --I would love to buy an AMD CARD, Just gotta get mining  . Also, I am not about to buy ATI cards for a 110 computer lab when they all have working GTX's -- not even my lab, either. I appreaciate your work on this program, it's sweet. You're not the only one to tell me of similar bugs. I have another guy who is getting tons of "this nonce was already submitted" errors on Deepbit, which makes zero sense because the nonce counter is happily rotating. It makes no sense why its triggering unless nvidia has a very broken OpenCL impl. Which, well, we know that already. |
|
|
|
One block solved in 2 hours, 15 mins? Could be just bad luck, but it seems a bit suspect.
The entire network once waited about 6 hours. Doesn't seem abnormal to me. |
|
|
|
|
What the hell is wrong with Nvidia lately. I swear to god I hit every goddamned Nvidia bug.
Dear Nvidia users: BUY AMD CARDS.
|
|
|
|
Hrm, update to the newest one, but I don't think any of the updates effect Nvidia users.
I wonder if its just yet another Nvidia driver bug.
I don't know what's going on. Ubuntu says that the Nvidia proprietary driver is "activated but not currently in use" whatever that means. Unity works. ::shrug:: Sounds like your install is broken. Take it up with Ubuntu. |
|
|
|
If it happens infrequently, ignore it. All hardware does now and then (maybe 1 or 2 in 1000 blocks or so). However, if it does it frequently, then your card is either overheating (no more than 75c for a Geforce), or you have it overclocked too far. I get a bunch after every block as soon as I start mining with my GTX 460, and its temperature is 56C. I've been using -w 256 with a Diablo Miner binary that I d/l'ed on June 1. Hrm, update to the newest one, but I don't think any of the updates effect Nvidia users. I wonder if its just yet another Nvidia driver bug. |
|
|
|
I heard about Bitcoins and want to test a bit of mining.
Now i have some questions about your miner.
My hardware is:
Geforce GTX 285
Core Due 6300, 2 GB RAM, Win 7
I create a bitcoin.conf with rpc user and password and started bitcoin.exe with -server variable. I have also started and it worked with standard settings. It shows me about xxxxx/30000 khash/ in the cmd window of DiabloMiner and about 1000 khash/s in the Bitcoin Gui. Is right or did i something wrong or miss something?
Thanks for help, Mowo
The Bitcoin client only shows its own CPU mining. I recommend you turn CPU mining off in the client, as its a waste of electricity, hardware, and time and usually slows GPU mining down too. Is this ERROR: Invalid block found on GeForce GTX 285 (#1), possible driver or hardware issue
Block 7 found on Geforce GTX 285 (#1) bad or can i ignore it? If it happens infrequently, ignore it. All hardware does now and then (maybe 1 or 2 in 1000 blocks or so). However, if it does it frequently, then your card is either overheating (no more than 75c for a Geforce), or you have it overclocked too far. |
|
|
|
I'm on a macbook air and i can't seem to get more than 700 khash/sec
any suggestions?
./DiabloMiner-OSX.sh ... -w 64
[6/4/11 12:24:51 PM] Started
[6/4/11 12:24:51 PM] Connecting to: http://..../
[6/4/11 12:24:51 PM] Using Apple OpenCL 1.0 (Dec 23 2010 17:30:26)
[6/4/11 12:24:51 PM] Added GeForce 320M (#1) (6 CU, local work size of 64)
442/619 khash/sec
You should get about 6 mhash. Try a higher -w value, Apple's OpenCL implementation is extremely buggy. Thanks. Whenever I try a -w setting of 256 or higher, the miner seems to have trouble (lots of OpenCL errors),and still is in that sub 800 khash range I can imagine higher, its not valid for most GeForces (or any Radeon for that matter). What does local work size say when you don't use -w? That is your maximum. I get 6.5 khps on my mac air 11", OSX 10.6.7, GeForce 320M. I leave DM vanilla, and it reports a worksize of 512 (!). Never overheats, either, and 3xfaster than my mac pro on DM no flags. But then the desktop on the air is completely unusable and on the pro there's no lag. You can always try -f 120 or 180 or 240. The -w 64 trick sadly only works on real nvidia drivers, not osx's own opencl implementation. |
|
|
|
|
Show Posts
