|
Update: I've added mtrlt's bat script for Windows. No longer do you have to run the whole Java command by hand.
|
|
|
|
Does DiabloMiner support the Long Polling protocol that DeepBit has introduced? If not, do you have any plans to implement it?
I don't see value in the long polling protocol. Its much easier to just use a dedicated Websockets protocol. I plan on introducing this in the future. |
|
|
|
Thanks diablo I guess I will have to make do with the hash rate till amd comes out with the new sdk for 6990. Thanks for your great miner, I am using it for the dual 6990. It hovers around 1ghash/s and its at -f 7777777. Hahah I tested and the numbers seem to slow down the hash rate when its lesser than -f 17 but anything more it hits 1ghash/s constant. Which is nice =)
GPU Max at 93% with powerplay maxed out
It generally maxes out at your OS's kernel's scheduler's timeslice length. Generally, this is 100hz or 1000hz. Higher than -f 1000 makes no sense. Not only that, my miner has an automatic lower limit as to not send too little work to the GPU. The actual -f maximum may be much lower. Wait I dont quite get the part OS kernel scheduler timeslice length. What I do face is a huge drop in hash/s when i go lower than -f 15, at -f 2 its almost 600mhash/s so thats why i up the -f number to go it to run at 1ghash Basically, the GPU babysitting threads go to sleep between OpenCL executions. The OS's kernel can only change threads so fast. Thus, having OpenCL executions that are shorter than the length of one timeslice means the GPU is waiting for the babysitting threads to catch up. However, as I said, the minimum kernel length is tuned to your hardware, it doesn't seem you can ever reach the timeslice length. As for -f 1 looking slower, its because at extremely long execution lengths, it tends to screw over the OS's clock in as that it jumps large periods to catch up to the real world. This is why, when using -f 1, you use the second number my miner outputs and run it for 10 minutes before you trust the number. Linux doesn't suffer this nearly as much as Windows does. |
|
|
|
Thanks diablo I guess I will have to make do with the hash rate till amd comes out with the new sdk for 6990. Thanks for your great miner, I am using it for the dual 6990. It hovers around 1ghash/s and its at -f 7777777. Hahah I tested and the numbers seem to slow down the hash rate when its lesser than -f 17 but anything more it hits 1ghash/s constant. Which is nice =)
GPU Max at 93% with powerplay maxed out
It generally maxes out at your OS's kernel's scheduler's timeslice length. Generally, this is 100hz or 1000hz. Higher than -f 1000 makes no sense. Not only that, my miner has an automatic lower limit as to not send too little work to the GPU. The actual -f maximum may be much lower. |
|
|
|
Hi diablo I have the dummy plugs in both graphics card. And if I were to disable xfire the cards will not be recognised by the diablo software. Same goes with poclbm.
That shouldn't happen. However, leaving Crossfire on could explain your lost speed. |
|
|
|
Hi diablod3 I am facing some issues using this miner with dual 6990. With -f 1 the hash rates drop to a whooping 600000 low. I tested out different flags and found that -f 17 to 20 is the best with the highest at 1ghash/s. This is very stable compared to poclbm which fluctuates from 800mhash to 1.2ghash. I am using 11.3 + 2.4 sdk like u recommend. The preview 11.4 drivers + 2.4 sdk yield the same results. I am using windows 7 64 bit. And the only way to get the software to recognise the dual 6990 is to crossfire them. Any advice u could give me?
Thank you =)
On Windows, due to stupidity on Microsoft's part, you usually need a dummy plug to make cards that don't have monitors plugged in to them turn on (this doesnt apply to Linux, nor Crossfired cards). -f controls the length of a kernel (1/n seconds, where -f 1 is a full second), and you'll only see changes at large multiples or divisors of 60 (ie, 1, 15, 30, 60, 120, 240, etc). -f 1 tends to largely skew the realtime clock used by the OS. So, to test with -f 1, you need to run for about 10 minutes and only rely on the second number (pocblm does not provide a second number, so you can't accurately watch it). That said, the numbers tell me you should get about 1.2 ghash total instead of 1 (or about 17% slower). I suspect a driver bug. Make absolutely sure you've turned off Crossfire and that my miner lists 4 devices. |
|
|
|
You can use bitcoin -server instead of bitcoind. I'm not sure if the OSX binaries build bitcoind.
Pardon my ignorance, but how do I run bitcoin with the -server option? Terminal doesn't recognize it. Do I need to build from source and run that? I don't understand your question. You download the OSX binaries from the Bitcoin website, unzip them, open up Terminal, cd to the directory, and then ./bitcoin -server & exit |
|
|
|
|
Please note: I screwed up testing on SDK 2.4. It does fix the CPU use bug 2.2/2.3 introduced, but I get about 71 mhash/sec on my 4850 out of 76. This puts it at the same speed as 2.3, but without the CPU use.
So, I am still recommending 10.9 through 10.11 + SDK 2.1 for 4xxx/5xxx mining, but I'm recommending 11.3 + SDK 2.4 for 6xxx.
|
|
|
|
so in a terminal you run: ./bitcoind [from the bitcoin directory - skip the GUI; go with the daemon]
i'm assuming your mvn install on DiabloMiner went ok?
Here is my problem: I don't appear to have bitcoind on my computer. Even as a hidden file. I have neither a .bitcoin folder nor a bitcoin/bin folder. Where would it be otherwise on a Mac? I didn't install DiabloMiner, I just ran the shell from Terminal. I don't know what mvn means - ? Thanks again for your help. You can use bitcoin -server instead of bitcoind. I'm not sure if the OSX binaries build bitcoind. |
|
|
|
and then: *******@minty64 ~/DiabloMiner/Diablo-D3-DiabloMiner-d758eef $ ./DiabloMiner-Linux.sh -w 128 -f 1 -u ******* -p ********
?
i'm assuming your mvn install on DiabloMiner went ok?
You shouldn't use -w 128 unless for some strange reason it is, indeed, faster than you. -w 64 is whats recommended by AMD themselves. Also, you only use mvn to build from source. If you download the binary zip, you don't (and can't) use this. |
|
|
|
|
Update: I removed the new constant buffer creation code in exchange for a much simpler double buffering method. This seems to a faster solution than either using single buffers or creating new ones all the time. Also, I added another error check.
|
|
|
|
Is it preferable to run bitcoind or bitcoin -server in the background?
Where can I find bitcoind? It doesn't appear to be included in the zip file for the Mac OS binary.
Thanks.
bitcoind is just bitcoin without the GUI, and it automatically does -server. It doesn't really matter which you run, there are miners equally in both camps. |
|
|
|
Are you absolutely sure you're using SDK 2.4?
I am now. I installed dual 6990s and did a fresh install of Win7, Catalyst 11.4, Stream 2.4, and latest DiabloMiner with '-f 1'. 4 Caymans are found but hashrate is poking along at under 700 mhps. Weird. I believe you should be getting around 1200 mhash/sec with that setup. |
|
|
|
|
Update: Made a small modification that may increase speed for some users. Those suffering from the abnormally low khash bug may be fixed by this.
|
|
|
|
Anybody with Win7 and a 6990 running DiabloMiner? I installed Catalyst 11.4, and while DiabloMiner runs, the GPU activity level barely gets above 80%, and thus my hashrate is poor.
Are you absolutely sure you're using SDK 2.4? |
|
|
|
|
Holy crap! SDK 2.4 on Catalyst 11.3 not only cures the CPU use bug in 2.2/2.3, but also is faster than 2.1.
On my Radeon 4850
2.1 = Upper 75 mhash
2.2 = Around 65
2.3 = Around 70
2.4 = Lower 76
SDK 2.4 requires at least 11.1, so don't try it on earlier.
|
|
|
|
Oh, damn! And it seems I can't mine using Intel cards, too. D'oh!  Thank you anyway. Surprisingly, Intel has FINALLY joined the world the rest of us have been in for the past 2+ years. GMAHD 2000/3000 GPUS (those in the newest i5s/i7s) can run OpenCL... but the fastest ones only go about 5-10 mhash/sec, so it is is still a waste of time. Go figure. |
|
|
|
DiabloD3 -
just thought i'd check in with my compliments.
i'm running Debian testing (LMDE) - i froze updates at march 30 on my mining-only box.
with your miner set at -w 128 -f 1, my two (VisionTek) 5850s (with crossfire connector attached) are putting out 495,200 Mh/s regular as an atomic clock. i'll screw with overclocking after i've scored a couple of blocks - i'm coming up on 'average time' (six days plus some) as i write this. my case is a piece of crap though: less than 1/2" clearance between the second card and the bottom of the case. i'm running it open with a couple extra fans, and the bottom card fluctuates between 72-74.5 degrees. gotta poke a hole in it or get a bigger case if i'm gonna overclock.
my SDK is 2.1, and Catalyst is 11.2. motherboard is an MSI 870A-G54, with a ~90 watt Phenom dual-core (whatever...) and 2 gig RAM.
you sell shit and i'm your customer...
EDIT: oh - and coinage on blockage, of course...
As a suggestion, don't use Catalyst 11.x or 10.12 for mining. It usually leads to abnormally low speeds for no reason. Also, you need to turn crossfire off, and just disconnecting the bridge doesn't turn it off, you need to run aticonfig --initial -f --adapter=all as root and then restart X. Leaving crossfire on can lead to incorrect results (which my miner is supposed to catch and spit out errors for). Also, you should be getting better speed with -w 64 (as this is what is recommended by AMD). Hi all. I'm new here.
I would like to start mining with DiabloMiner.
I'm having troubles to understand how to run it; till now I'm stuck on the NoClassDefFoundError error.
But first of all I'm not sure that my system is able to do GPU mining. I'm running Gentoo Linux with NVidia GeForce 7100 GS; I made some search with no success.
Could you confirm/exclude I can do GPU mining?
thanks!
You can't mine with a Geforce 7xxx, only 8xxx and up. |
|
|
|
I had two complete lock ups of my system (probably due to me using aticonfig to adjust the fan speeds in a cronjob) at 30 hours between each other (100'000 seconds ~= 30 hours). I was wondering whether this is a known bug or one of my cards is dying on me:
Sounds like the cards overheated, the driver tried a GPU restart, and failed.... which GPU restarts on Linux ALWAYS fail, and theres no way to shut it off. Just leave your GPU fans at full speed. |
|
|
|
|
Update: Merged jwadamson's patch that gets rid of the OSX dock icon
|
|
|
|
|
Show Posts
