DiabloMiner GPU Miner - page 51. | Bitcointalksearch.org

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: iopq on June 25, 2011, 08:45:39 PM

Quote from: DiabloD3 on June 25, 2011, 10:03:26 AM

Uodate: Behold, the frankenkernel. A mix of DiabloKernel and phatk.

Before this, I got 369 mhash on my 5850@918 on SDK 2.1, and 352 on 2.4 post-11.4 (thanks AMD!)

Now I get 369 on 2.1 AND 2.4.

AMD, you can't hide. I am coming for you.

oh hey it started working for me now
not as fast as poclbm, though

Use -v 2 with either -w 128 or 256. -v 3/19 settings don't seem to be optimum anymore.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: gmaxwell on June 25, 2011, 05:06:30 PM

Quote from: DiabloD3 on June 25, 2011, 10:03:26 AM

Uodate: Behold, the frankenkernel. A mix of DiabloKernel and phatk.
Before this, I got 369 mhash on my 5850@918 on SDK 2.1, and 352 on 2.4 post-11.4 (thanks AMD!)
Now I get 369 on 2.1 AND 2.4.
AMD, you can't hide. I am coming for you.

Congrats, you're finally as fast as phoenix / phatk for me— actually about 0.4% faster it looks like. (Only tested it on the 5850s with SDK 2.4 so far)

I seemed to be getting high stales with -f0, -f1 was fine but it could have just been bad luck. There didn't appear to be much if any hashrate difference, so I just left it at 1%.

Still need the ability to loadshare (ideally) or fail over between multiple pools. But it's looking pretty good. Good work.

Don't use -f 0. I need to add an error message for that, as far as I can tell, instead of dividing by zero, it just steadily increases the worksize to maximum of 2^32 (or about 0.1 fps give or take).

Loadshare might be halfway easily to implement. Not sure.

kripz

full member

Activity: 182

Merit: 100

Quote from: kripz on June 24, 2011, 05:50:54 AM

Quote

[24/06/11 8:49:58 PM] DEBUG: Attempt 77 found on Cypress (#3)
[24/06/11 8:50:02 PM] DEBUG: Attempt 78 found on Cypress (#2)
[24/06/11 8:50:07 PM] DEBUG: Attempt 79 found on Cypress (#2)
[24/06/11 8:50:12 PM] DEBUG: Attempt 80 found on Cypress (#3)
[24/06/11 8:50:13 PM] DEBUG: Attempt 81 found on Cypress (#2)
[24/06/11 8:50:14 PM] DEBUG: Attempt 82 found on Cypress (#3)
[24/06/11 8:50:15 PM] DEBUG: Attempt 83 found on Cypress (#2)
[24/06/11 8:50:18 PM] DEBUG: Attempt 84 found on Cypress (#3)
[24/06/11 8:50:21 PM] DEBUG: Attempt 85 found on Cypress (#1)
[24/06/11 8:50:23 PM] DEBUG: Attempt 86 found on Cypress (#2)
[24/06/11 8:50:33 PM] DEBUG: Attempt 87 found on Cypress (#2)

both updated to latest git

Just updated windows machine

Quote

[24/06/11 8:56:17 PM] DEBUG: Attempt 3 found on Cayman (#2)
[24/06/11 8:56:18 PM] DEBUG: Attempt 4 found on Cayman (#2)
[24/06/11 8:56:20 PM] DEBUG: Attempt 5 found on Cayman (#2)
[24/06/11 8:56:26 PM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 8:56:31 PM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 8:56:32 PM] DEBUG: Attempt 6 found on Cayman (#2)
[24/06/11 8:56:32 PM] DEBUG: Attempt 7 found on Cayman (#2)
[24/06/11 8:56:34 PM] DEBUG: Attempt 8 found on Cayman (#2)
[24/06/11 8:56:38 PM] DEBUG: Attempt 9 found on Cayman (#2)

mhash 364.5/362.8 | a/r/hwe: 0/1/0 | ghash: 30.1 | fps: 30.4

Nothing is being submitted?

EDIT: now how do i go back to the old version?

Nope, it's Diablominer and/or flexible proxy (though i never touched the proxy). It will find a few results, submit one or two and say accepted. After that "Attempt found" but never submit it?

Phoenix works 100% rock solid

iopq

hero member

Activity: 658

Merit: 500

Quote from: DiabloD3 on June 25, 2011, 10:03:26 AM

Uodate: Behold, the frankenkernel. A mix of DiabloKernel and phatk.

Before this, I got 369 mhash on my 5850@918 on SDK 2.1, and 352 on 2.4 post-11.4 (thanks AMD!)

Now I get 369 on 2.1 AND 2.4.

AMD, you can't hide. I am coming for you.

oh hey it started working for me now
not as fast as poclbm, though

gmaxwell

staff

Activity: 4326

Merit: 8951

Quote from: DiabloD3 on June 25, 2011, 10:03:26 AM

Uodate: Behold, the frankenkernel. A mix of DiabloKernel and phatk.
Before this, I got 369 mhash on my 5850@918 on SDK 2.1, and 352 on 2.4 post-11.4 (thanks AMD!)
Now I get 369 on 2.1 AND 2.4.
AMD, you can't hide. I am coming for you.

Congrats, you're finally as fast as phoenix / phatk for me— actually about 0.4% faster it looks like. (Only tested it on the 5850s with SDK 2.4 so far)

I seemed to be getting high stales with -f0, -f1 was fine but it could have just been bad luck. There didn't appear to be much if any hashrate difference, so I just left it at 1%.

Still need the ability to loadshare (ideally) or fail over between multiple pools. But it's looking pretty good. Good work.

DareC

member

Activity: 83

Merit: 10

The new frankenkernel seems to have lost me about 10 mhash/s. I'm on a 6990@910 (mem 625). Using -v 2 -w 128 (increasing -w made things worse, as did fiddling with -v).

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Uodate: Behold, the frankenkernel. A mix of DiabloKernel and phatk.

Before this, I got 369 mhash on my 5850@918 on SDK 2.1, and 352 on 2.4 post-11.4 (thanks AMD!)

Now I get 369 on 2.1 AND 2.4.

AMD, you can't hide. I am coming for you.

iopq

hero member

Activity: 658

Merit: 500

instead of solving shares I'm just getting hardware errors Huh

I'm running an ATI 5750 on windows 7 64-bit with 2.1 ati stream sdk

bacoboy

newbie

Activity: 18

Merit: 0

OK replying to my own post since I found a solution and others may get into this pickle.

Seems that with the 10.6.8 upgrade Apple changed the ATI driver for the 5xxx series enough that Diablominer couldn't see my 5770 anymore.

Clearly the card isn't on the approved tested list from Apple as I found the solution on the hackintosh forums here:
http://tonymacx86.blogspot.com/2011/06/mac-os-x-1068-update.html?showComment=1308885830329#c2474866973888572776

The crux of it is you need to rollback 3 kext directories in your /System/Library/Extensions folder to the 10.6.7 versions. Luckly I was able to pull from a time machine backup so if you haven't upgraded yet, be sure to back these up.
You restore the directories, run repair permissions on the disk via Disk Utility and reboot.

When it came back up Diablominer could see the openCL device again.

Hope this helps one of my mac brothers...

Also, using no modifications (and the latest client) I went from a pretty variable ~104.5Mh/s to a steady 106Mh/s. I'm assuming the improvements are due to the newer client code...

bacoboy

newbie

Activity: 18

Merit: 0

Just upgraded Mac from 10.6.7 to 10.6.8. Went to start Diablominer and got:

[6/24/11 7:40:11 PM] Using Apple OpenCL 1.0 (Dec 23 2010 17:30:26)
[6/24/11 7:40:11 PM] ERROR: OpenCL platform Apple contains no devices

I have an ATI 5770 with the Mac BIOS hack so it worked under 10.6.7.
Been mining for weeks in this setup...

Anybody else having this problem due to the upgrade?
I downloaded the latest zip but still get this.
Reboot also doesn't fix (as I said, it shows up fine in the System Profiler).

Help!

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: Druas on June 24, 2011, 12:05:13 PM

Random question: Does DiabloMiner support MMP?

No.

Druas

member

Activity: 78

Merit: 10

Random question: Does DiabloMiner support MMP?

kripz

full member

Activity: 182

Merit: 100

Quote

[24/06/11 8:49:58 PM] DEBUG: Attempt 77 found on Cypress (#3)
[24/06/11 8:50:02 PM] DEBUG: Attempt 78 found on Cypress (#2)
[24/06/11 8:50:07 PM] DEBUG: Attempt 79 found on Cypress (#2)
[24/06/11 8:50:12 PM] DEBUG: Attempt 80 found on Cypress (#3)
[24/06/11 8:50:13 PM] DEBUG: Attempt 81 found on Cypress (#2)
[24/06/11 8:50:14 PM] DEBUG: Attempt 82 found on Cypress (#3)
[24/06/11 8:50:15 PM] DEBUG: Attempt 83 found on Cypress (#2)
[24/06/11 8:50:18 PM] DEBUG: Attempt 84 found on Cypress (#3)
[24/06/11 8:50:21 PM] DEBUG: Attempt 85 found on Cypress (#1)
[24/06/11 8:50:23 PM] DEBUG: Attempt 86 found on Cypress (#2)
[24/06/11 8:50:33 PM] DEBUG: Attempt 87 found on Cypress (#2)

both updated to latest git

Just updated windows machine

Quote

[24/06/11 8:56:17 PM] DEBUG: Attempt 3 found on Cayman (#2)
[24/06/11 8:56:18 PM] DEBUG: Attempt 4 found on Cayman (#2)
[24/06/11 8:56:20 PM] DEBUG: Attempt 5 found on Cayman (#2)
[24/06/11 8:56:26 PM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 8:56:31 PM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 8:56:32 PM] DEBUG: Attempt 6 found on Cayman (#2)
[24/06/11 8:56:32 PM] DEBUG: Attempt 7 found on Cayman (#2)
[24/06/11 8:56:34 PM] DEBUG: Attempt 8 found on Cayman (#2)
[24/06/11 8:56:38 PM] DEBUG: Attempt 9 found on Cayman (#2)

mhash 364.5/362.8 | a/r/hwe: 0/1/0 | ghash: 30.1 | fps: 30.4

Nothing is being submitted?

EDIT: now how do i go back to the old version?[/s]

m3ta

sr. member

Activity: 435

Merit: 250

Quote from: DiabloD3 on June 24, 2011, 12:30:49 AM

Update: Change execution thread count from 3 to 2. More efficient, no longer need 3 because of fully async getwork.

Stable on OSX.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Update: Change execution thread count from 3 to 2. More efficient, no longer need 3 because of fully async getwork.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Update: Finish async networking, now everything is async. getwork, sendwork, and LP now use 1 thread per miner instance instead of 3 per GPU.

So, no matter how much Eligius lags out, it can't stop mining.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: kripz on June 23, 2011, 08:41:20 AM

xorg wierdness, restarted x and all is well.

Now with all 3 i get alot of force getworks?

Quote

[24/06/11 9:38:27 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:30 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:31 AM] DEBUG: Attempt 120 found on Cypress (#1)
[24/06/11 9:38:31 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:31 AM] DEBUG: Attempt 121 found on Cypress (#3)
[24/06/11 9:38:31 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:32 AM] Accepted block 115 found on Cypress (#1)
[24/06/11 9:38:32 AM] Accepted block 116 found on Cypress (#3)
[24/06/11 9:38:33 AM] DEBUG: Attempt 122 found on Cypress (#2)
[24/06/11 9:38:33 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:33 AM] Accepted block 117 found on Cypress (#2)
[24/06/11 9:38:34 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:36 AM] DEBUG: Attempt 123 found on Cypress (#2)
[24/06/11 9:38:37 AM] Accepted block 118 found on Cypress (#2)
[24/06/11 9:38:39 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:40 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:52 AM] DEBUG: Attempt 124 found on Cypress (#2)
[24/06/11 9:38:53 AM] Accepted block 119 found on Cypress (#2)
[24/06/11 9:38:58 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:39:04 AM] DEBUG: Attempt 125 found on Cypress (#2)
[24/06/11 9:39:05 AM] Accepted block 120 found on Cypress (#2)

Thats normal. At 300 mhash, you can see 3 nonce saturations happen every 45 seconds.

kripz

full member

Activity: 182

Merit: 100

xorg wierdness, restarted x and all is well.

Now with all 3 i get alot of force getworks?

Quote

[24/06/11 9:38:27 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:30 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:31 AM] DEBUG: Attempt 120 found on Cypress (#1)
[24/06/11 9:38:31 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:31 AM] DEBUG: Attempt 121 found on Cypress (#3)
[24/06/11 9:38:31 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:32 AM] Accepted block 115 found on Cypress (#1)
[24/06/11 9:38:32 AM] Accepted block 116 found on Cypress (#3)
[24/06/11 9:38:33 AM] DEBUG: Attempt 122 found on Cypress (#2)
[24/06/11 9:38:33 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:33 AM] Accepted block 117 found on Cypress (#2)
[24/06/11 9:38:34 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:36 AM] DEBUG: Attempt 123 found on Cypress (#2)
[24/06/11 9:38:37 AM] Accepted block 118 found on Cypress (#2)
[24/06/11 9:38:39 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:40 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:38:52 AM] DEBUG: Attempt 124 found on Cypress (#2)
[24/06/11 9:38:53 AM] Accepted block 119 found on Cypress (#2)
[24/06/11 9:38:58 AM] DEBUG: Forcing getwork update due to nonce saturation
[24/06/11 9:39:04 AM] DEBUG: Attempt 125 found on Cypress (#2)
[24/06/11 9:39:05 AM] Accepted block 120 found on Cypress (#2)

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: kripz on June 23, 2011, 07:10:01 AM

using aticonfig to list the adaptors i see all 3, diablo only uses 2 to mine?

If your setup is configured correctly, it will use all 3.

kripz

full member

Activity: 182

Merit: 100

using aticonfig to list the adaptors i see all 3, diablo only uses 2 to mine?

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