I've been using DiabloMiner for months on Windows, but I wanted to try it on mac (10.7) with a 6750M. I downloaded the newest version and cd'd the directory. Using slush,
So I type ./DiabloMiner-OSX.sh -u username -p password -0 api.bitcoin.cz -r 8332 -w 64
It opens and starts to run
Started
Connecting to :http..api2.bitcoin.cz:8332
Using Apple OpenCL 1.1 (Jul 25 2011 time)
Added ATI Radeon HD 6750M.......
But then it will say ERROR: Cannot connect to api2.bitcoin.cz connect time out
I have checked the password and user name several times, even created a new worker.
Is the OpenCL up to date? All I can find are .exe files for OpenCL and SDK upgrades.
Any help would be greatly appreciated.
This isn't a miner bug, are you sure slush's pool isn't actually down? I know the miner is working, and Slush was not down. But how do I know the SDK or OpenCL is up to date for it to run correctly. The only other option is that somehow the port is blocked. You cant control OpenCL on OSX, its up to Apple there. However, the error you pasted only happens when it cant connect. It has nothing to do with the rest of the miner. |
|
|
|
I've been using DiabloMiner for months on Windows, but I wanted to try it on mac (10.7) with a 6750M. I downloaded the newest version and cd'd the directory. Using slush,
So I type ./DiabloMiner-OSX.sh -u username -p password -0 api.bitcoin.cz -r 8332 -w 64
It opens and starts to run
Started
Connecting to :http..api2.bitcoin.cz:8332
Using Apple OpenCL 1.1 (Jul 25 2011 time)
Added ATI Radeon HD 6750M.......
But then it will say ERROR: Cannot connect to api2.bitcoin.cz connect time out
I have checked the password and user name several times, even created a new worker.
Is the OpenCL up to date? All I can find are .exe files for OpenCL and SDK upgrades.
Any help would be greatly appreciated.
This isn't a miner bug, are you sure slush's pool isn't actually down? |
|
|
|
Is there a way to use optimal settings for both VLIW and GCN without running two instances of DiabloMiner?
No, not yet. |
|
|
|
It can set the memory clock to whatever your GPU's firmware is limited to, this is usually far below the minimum displayed in CCC.
It can set the voltage on any card that uses stock VRMs. The 6000 and 7000 series cards have always been limited to 125Mhz below engine clock (IIRC, my 7000's went 150Mhz below engine clock). I've had to flash every 6000/7000 card to drop the memory clock by a significant amount and to drop the voltage at all (in Linux). It's been about 4 months since I've tried AMDOverdriveCtrl though. Apparently I need to give it another go? I have 84 video cards with modified BIOSes. It'd be a godsend to be able to hit low memory clocks and adjust voltages without flashing cards anymore. The 5000's are a different story... a reference board will clock to just about whatever engine/memory/voltage is entered. Yes, as long as you've modified the firmwares, you're fine. |
|
|
|
Use Debian unstable, use whatever is packaged newest by Debian (do NOT use the .run installer provided by AMD), and use AMDOverdriveCtrl to control clocks and voltage.
Correct me if I'm wrong, but AMDOverdriveCtrl cannot change the voltage or lower the memory clock substantially (unless it's been updated since I last used it). It can set the memory clock to whatever your GPU's firmware is limited to, this is usually far below the minimum displayed in CCC. It can set the voltage on any card that uses stock VRMs. |
|
|
|
I have a host with 6970 and 7970.
Until now I have found no way to set GPU clock, mem clock and voltage at the same time.
- MSI Afterburner: I can set GPU clock and voltage, but mem clock can go no lower than 685
- Sapphire Trixx: GPU and mem clock can be set, but voltage is fixed
- ATI tray tools won't run with the 7970.
What to do?
Use Linux. Hmm ... I never thought about mining using Linux. Because of all the driver madness that I was reading the last couple of years. - which Catalyst would you suggest for Linux? - which tool would you recommend to set GPU & mem clocks and voltage? Use Debian unstable, use whatever is packaged newest by Debian (do NOT use the .run installer provided by AMD), and use AMDOverdriveCtrl to control clocks and voltage. |
|
|
|
I have a host with 6970 and 7970.
Until now I have found no way to set GPU clock, mem clock and voltage at the same time.
- MSI Afterburner: I can set GPU clock and voltage, but mem clock can go no lower than 685
- Sapphire Trixx: GPU and mem clock can be set, but voltage is fixed
- ATI tray tools won't run with the 7970.
What to do?
Use Linux. |
|
|
|
So I downloaded the latest version of hte miner and extracted it.
Do I need to do any setup in order ot use it? I keep trying to use the DiabloMiner-Windows application and all it does is open, then instantly close some command line text. How do I stop it from doing this>? (Windows 7 as the OS btw).
Its a command line application. Either run it from the command line, or run it from a .bat file that has the args you want. I gotchya. Thanks for hte clarification. Got it wokring now.  This might be a stupid quesiton, but the mhash number shows two numbers. What is the difference between the first and 2nd number? 15 second average, forever average |
|
|
|
So I downloaded the latest version of hte miner and extracted it.
Do I need to do any setup in order ot use it? I keep trying to use the DiabloMiner-Windows application and all it does is open, then instantly close some command line text. How do I stop it from doing this>? (Windows 7 as the OS btw).
Its a command line application. Either run it from the command line, or run it from a .bat file that has the args you want. |
|
|
|
So are we still running no flags for the best performance on GCN with the current DM? Oh, and 2 BTC sent to help fund further GCN development.  Yes, just make sure you're using 12.2. |
|
|
|
Just get rid of the http:// and you should be all set. THANKS! Can't believe it was something so simple  Sorry again for the noob post! I seem to be getting slightly less MH/s than I did with Phoenix 2, although that was with fine tuned paramaters, whears I am passing Diablo no parameters besides my pool. Great MH/s for auto detect settings! Will try and tweak it and see what I can get from Capeverde 7770! Make sure you're using 12.2. DiabloMiner doesn't autodetect, the default merely happens to work best on GCN. However, no one has tried all options on 7770s yet, -v 2 and -v 4 and -v 2,1 (and 3, and 2,2 and 1,1,1 and 1,1,1,1 and so forth...) probably will be slower for you, but you're welcome to try. Also, do not use -na, 12.2 fixed this. |
|
|
|
Compared to my 5850@960, that'd be 360 and 384 mhash respectively. I'm getting 393. I have hopes for 12.2, but are you sure you're using the newest version of DiabloMiner?
I do have the latest, just updated to be sure and still at 282mhash. This system is an old pentium 4, and just running off the cheap Dell power supply so I can't push the card much without crashing. Anything above 900mhz core seems to result in crashes. I have 2 systems at home with 2X 5830s each, and they do better mhash per card, even at similar clock speeds. I think I'm hitting a limitation in this box due to the old chipset or something. Well, on 12.1, it seems that a 5830 at 900mhz should get 287 or so. Are your systems at home doing that, or are they doing better on 12.2? |
|
|
|
New App fixes it from 12.2 drivers. (898.1)
EDIT: Picked up 5mh/s too.
12.2 seems magical. Updated an old p4 box from 12.1 to 12.2 and gained 18mhash, from 262 to 280. Using -v 2 -w 256 Radeon 5830, 900 core, 300 mem, 1.01v Compared to my 5850@960, that'd be 360 and 384 mhash respectively. I'm getting 393. I have hopes for 12.2, but are you sure you're using the newest version of DiabloMiner? |
|
|
|
So, -na fixes it on GCN, but it incurs an estimate 13% performance loss (at least, if the ops on my 5850 are any indication).
Goddamnit AMD.
The score thus far:
vliw5: 1% slower vs old kernel on 2.1
vliw4: 3-5% faster vs old kernel on 2/42.5
gcn: 1% faster vs old on 2.6
Seriously, goddamnit AMD.
New App fixes it from 12.2 drivers. (898.1) EDIT: Picked up 5mh/s too. Confirmed! Same here too. Diablo what is this -na flag u speak of? I do not have that option. Don't bother with it, 12.2 fixes it. Also, if you don't have -na, you're not using the newest version of DM. |
|
|
|
Radeon users: Catalyst 11.6 + SDK 2.1 seems to be the golden combination for 4xxx and 5xxx miners. Is this referring to the whole Catalyst suite including the OpenCL, Display, and ATI Integrated Drivers? Or just the actual program? Apologies if it's a n00b question. Catalyst didn't used to come with the SDK, it does now. That text is out of date due to the new kernel, its now 12.2 is recommended, use the SDK that comes with it. |
|
|
|
|
So, -na fixes it on GCN, but it incurs an estimate 13% performance loss (at least, if the ops on my 5850 are any indication).
Goddamnit AMD.
The score thus far:
vliw5: 1% slower vs old kernel on 2.1
vliw4: 3-5% faster vs old kernel on 2/42.5
gcn: 1% faster vs old on 2.6
Seriously, goddamnit AMD.
|
|
|
|
|
Update: Remove -vs, -b, add -na for no array mode, set min fps to 0.1, and make loops work better.
|
|
|
|
Diablo what's up with GCN on the new miner. Do I need different flags only getting 30Mhash?
SDK bug that I've rammed into. Haven't quite figured out why its sucking, either. |
|
|
|
But you shouldn't be using -v 4 -w 64. That is not appropriate for the new kernel on vliw5. For me, -v 2 -w 256 is fastest, -v 2,1 -w 256 is slower, -v 2 -w 128 isn't faster (but -w is very sensitive to memory timings, so -w 128 being faster for others does not surprise me).
What kernel do you mean by "the new kernel"? I'm using the zip-package linked in the first post of this thread and this is still the "old kernel", isn't it?! I did not compile DiabloMiner from source so I guess I'm still using your "not optimized for SDK 2.6"-version. Maybe we can clear that confusion first  Okay, I figured out how to do this on Windows. In the .bat file or in cmd.exe or whatever you use, before running DiabloMiner, do SET GPU_DUMP_DEVICE_KERNEL=3. It should cause it to dump the .isa files.
-v4 http://pastebin.de/23309-v1,2 http://pastebin.de/23310-v2 http://pastebin.de/23311Nope, its the new kernel as of the post that you quoted originally that says "Update: Committed the new kernel." Er, 1503 on -v 2? Dude, you're not using the newest copy of DM. 1503 is what the old kernel got on -v 2 on 2.6. And it explains your weird results with -v 2,1... the hash mater was broken at the time of that version for non-power of two -v, I told you the mhash meter was fine because I fixed it in above referenced commit. |
|
|
|
|
Show Posts
