Quote from: smaxz on November 19, 2016, 01:39:30 PM

Quote from: bardacuda on November 18, 2016, 08:06:05 PM

Is Claymore's miner any faster if not dual mining?

no, if ANY gains are noticed they are negated by the "donation" mining deductions.

but then again i'm running an older genoil version before some features i enjoy seeing were removed for the sake of esthetics.

Quote from: Amph on November 19, 2016, 02:33:28 PM

same setting(same oc) and i only get 178MH instead of 176, but you need to remove 1% fee, and you have about the same profit if not worse in the end

Ok, thanks!

Quote from: Lucide on November 19, 2016, 06:09:20 PM

Hi ,
I am just trying ethminer/genoil for the first time and run into some issues:

Allocating/mapping DAG buffer failed with clCreateBuffer(-61). GPU can't Allocate THE DAG in a single chunk. Bailing.
clEnqueueWriteBuffer(-38)

any help with that ?
thanks

It's been a while since I mined ETH, but I know the DAG was supposed to bump 2GB cards out around this time. Make sure you set your environment variables. Use 'setx' to make them permanent, or 'set' to make them only for the current session. I think if you use 'set' you have to use '=' before the value instead of a space but don't quote me on that. So once you open up the command prompt (or in your batch file) you'd type in this:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

You may have to reboot first for it to take effect. If you type:

ethminer --list-devices

You should be able to see how much available memory you have on each card. (Apparently you have to add -G to that command now for AMD cards or -U for nVidia). If your available memory (CL_DEVICE_MAX_MEM_ALLOC_SIZE) is less than the size of the DAG, then you can't mine on that card. In my case I see this:

Code:

c:\Program Files\Ethereum\ethminer-0.9.41-genoil-1.1.7>ethminer --list-devices -G
Genoil's ethminer 0.9.41-genoil-1.1.7
=====================================================================
Forked from github.com/ethereum/cpp-ethereum
CUDA kernel ported from Tim Hughes' OpenCL kernel
With contributions from nicehash, nerdralph, RoBiK and sp_

Please consider a donation to:
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d

Listing OpenCL devices.
FORMAT: [deviceID] deviceName
[0] Hawaii
   CL_DEVICE_TYPE: GPU
   CL_DEVICE_GLOBAL_MEM_SIZE: 4294967296
   CL_DEVICE_MAX_MEM_ALLOC_SIZE: 4024925276
   CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
[1] Hawaii
   CL_DEVICE_TYPE: GPU
   CL_DEVICE_GLOBAL_MEM_SIZE: 4294967296
   CL_DEVICE_MAX_MEM_ALLOC_SIZE: 4024925276
   CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
[2] Hawaii
   CL_DEVICE_TYPE: GPU
   CL_DEVICE_GLOBAL_MEM_SIZE: 4294967296
   CL_DEVICE_MAX_MEM_ALLOC_SIZE: 4024925276
   CL_DEVICE_MAX_WORK_GROUP_SIZE: 256
[3] Pitcairn
   CL_DEVICE_TYPE: GPU
   CL_DEVICE_GLOBAL_MEM_SIZE: 2147483648
   CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1878490204
   CL_DEVICE_MAX_WORK_GROUP_SIZE: 256

So if the DAG is larger than 1.75GB (or 1878490204 bytes), then I won't be able to mine on my Pitcairn card. There was supposed to be some kind of 'chunking' implemented to break the DAG into smaller pieces so you could use the full 2GB, but I don't know if that happened or not.