GPU rejecting DAG because of size - My cards have enough space

hangabers

Finally got my ethminer to recognize and mine on both my R9 290Ss. 25mh each. So happy days...
Now they won't, but at least ethminer still sees both my cards....

Lets back track for a second...
I had set my GPUs into crossfire after banging my head for days trying everything for both to even be seen. Second card was always just a ghost untill crossfire was enabled.. Also crossfire never seemed to effect my expected hashrate..
So then I tried to remove crossfire, and back to the beginning I was with only lspci seeing both cards and nothing else.

Set them back to crossfire mode for OpenCL to recognize I have them both attached, and sure enough ethminer sees them too.
But.. Ethminer will sometimes benchmark correct scores, but normally will do one of two things.. Mine 00MH then hang, or bail because it thinks the memory size is too small for the DAG. Sometimes it doesn't like Geth's DAG file and will create it's own on each card.

Side note: Catalyst always sees my second cards and lists them correctly in terminal, but the GUI calls my second card [unidentified]R9 200 card... No matter what the circumstances.

I have reason to believe that problems occur because both GPUs are identical and no PCI ID gets assigned in OpenCl unless catalyst forces identification when crossfire is enabled. But it could also be environment settings, but I've tried export DISPLAY=0 , export GPU_MAX_ALLOC_PERCENT=98. It could also be that the motherboard has an unsupported APU chipset (HD 3300) that isn't used because there is no driver attached; so the AMD processor gets defined as an OpenCL platform in device position 1 (the position my second GPU takes in crossfire). I also wonder if it is the GPU BIOSs, both cards hold the same ID (I assume) and the cards have no Uber or Slow setting (factory overclocked with unlocked voltage). Apparently both switch positions yield the same BIOS settings.

Ubuntu 14.04.3
Catalyst 15.07 (I think) (sudo apt-get install fglrx fglrx-updates fglrx-dev-updates)


Installed all the dependencies

Tied the AMDAPPSDK folders and libraries in /opt as stated in the frontier manual

For what it's worth I have installed the ./print-devices MIT program (very helpful)
And not sure if it is an issue, I installed Steam
Nothing seemed to get catalyst to properly identify the second card even in crossfire. multi-head setups failed, --initial=all didin't seem to do anything, force Xinerama, --initial=0,2.. only crossfire


Lastly..
Yes I set ethminer to --no-precompute (still would make a DAG if it didn't like the Geth made DAG)
Yes I targeted the --opencl-device # to the specific GPU in separate terminal windows
Yes the --rpc flag was set, and yes startautoDAG was set to true

thefrog

Do you have enough RAM ?
Example: I have a system with 3 GPU (3gb each). With RAM of 4 GB, I get the same message you get and cards never start mining.
With 8 GB RAM, everything works perfectly (around 26MHs/Card).

hangabers

I have 8GB RAM DDR3 on my mobo and 4GB RAM DDR5 per card.
but it seems ethminer -G -t 2 now works. Doesn't like Geth's DAG? I donno

hangabers

it also took a while for ethminer to really start running, created a DAG file, then couldn't find it, then found both cards and started mining and creating a new DAG...

hangabers

$ ethminer -G --opencl-device 1 --no-precompute [OPENCL]:Found suitable OpenCL device [Hawaii] with 3221225472 bytes of GPU memory miner 10:55:27|ethminer Getting work package... miner 10:55:27|ethminer Grabbing DAG for #f2e59013… DAG 10:56:00|ethminer Generating DAG file. Progress: 0 % Creating DAG. 0% done...DAG 10:56:09|ethminer Generating DAG file. Progress: 1 % Creating DAG. 1% done...DAG 10:56:19|ethminer Generating DAG file. Progress: 2 % Creating DAG. 2% done...DAG 10:56:27|ethminer Generating DAG file. Progress: 3 % Creating DAG. 3% done...DAG 10:56:35|ethminer Generating DAG file. Progress: 4 % Creating DAG. 4% done...DAG 10:56:43|ethminer Generating DAG file. Progress: 5 % Creating DAG. 5% done...DAG 10:56:51|ethminer Generating DAG file. Progress: 6 % Creating DAG. 6% done...DAG 10:56:59|ethminer Generating DAG file. Progress: 7 % Creating DAG. 7% done...DAG 10:57:08|ethminer Generating DAG file. Progress: 8 % Creating DAG. 8% done...DAG 10:57:16|ethminer Generating DAG file. Progress: 9.... .... .... Creating DAG. 97% done...DAG 11:09:16|ethminer Generating DAG file. Progress: 98 % Creating DAG. 98% done...Bus error (core dumped) $ ethminer -G --opencl-device 1 --no-precompute [OPENCL]:Found suitable OpenCL device [Hawaii] with 3221225472 bytes of GPU memory miner 11:10:25|ethminer Getting work package... miner 11:10:25|ethminer Grabbing DAG for #f2e59013… DAG 11:10:51|ethminer Generating DAG file. Progress: 0 % Creating DAG. 0% done...Bus error (core dumped) $ ethminer -G --opencl-device 0 --opencl-device 1 --no-precompute [OPENCL]:Found suitable OpenCL device [Hawaii] with 3221225472 bytes of GPU memory miner 11:11:32|ethminer Getting work package... miner 11:11:32|ethminer Grabbing DAG for #f2e59013… DAG 11:11:57|ethminer Generating DAG file. Progress: 0 % Creating DAG. 0% done...DAG 11:12:04|ethminer Generating DAG file. Progress: 1 % Creating DAG. 1% done...^C $ ethminer -G [OPENCL]:Found suitable OpenCL device [Hawaii] with 3221225472 bytes of GPU memory miner 11:12:40|ethminer Getting work package... miner 11:12:40|ethminer Grabbing DAG for #f2e59013… ^C $ ethminer -G -t2 Invalid argument: -t2 $ ethminer -G -t 2 [OPENCL]:Found suitable OpenCL device [Hawaii] with 3221225472 bytes of GPU memory miner 11:12:59|ethminer Getting work package... miner 11:12:59|ethminer Grabbing DAG for #f2e59013… DAG 11:13:22|ethminer Generating DAG file. Progress: 0 % Creating DAG. 0% done...DAG 11:13:30|ethminer Generating DAG file. Progress: 1 % Creating DAG. 1% done...DAG 11:13:37|ethminer Generating DAG file. Progress: 2 % Creating DAG. 2% done...DAG 11:13:44|ethminer Generating DAG file. Progress: 3 % Creating DAG. 3% done...DAG 11:13:51|ethminer Generating DAG file. Progress: 4 % Creating DAG. 4% done...DAG 11:13:58|ethminer Generating DAG file. Progress: 5 % Creating DAG. 5% done...DAG 11:14:06|ethminer Generating DAG file. Progress: 6 % ... ... ... Creating DAG. 99% done...DAG 11:25:19|ethminer Generating DAG file. Progress: 100 % Creating DAG. 100% done...miner 11:25:19|ethminer Got work package: ℹ 11:25:19|ethminer Loading full DAG of seedhash: #582b0644… miner 11:25:19|ethminer Header-hash: b0b56a75f6fbeb9f9163f130290a5690a05f5ef12809e2953fc632dea1e619a6 miner 11:25:19|ethminer Seedhash: f2e59013a0a379837166b59f871b20a8a0d101d1c355ea85d35329360e69c000 miner 11:25:19|ethminer Target: 000000000027540c840eeba74a4b8f899c5258e18d4e81fdf5db60eb2c287824 ℹ 11:25:19|gpuminer0 workLoop 0 #00000000… #f2e59013… ℹ 11:25:19|gpuminer0 Initialising miner... ℹ 11:25:19|gpuminer1 workLoop 0 #00000000… #f2e59013… ℹ 11:25:19|gpuminer1 Initialising miner... miner 11:25:19|ethminer Mining on PoWhash #b0b56a75… : 0 H/s = 0 hashes / 0.5 s [OPENCL]:Using platform: AMD Accelerated Parallel Processing [OPENCL]:Using device: Hawaii(OpenCL 1.2 AMD-APP (1445.5)) miner 11:25:27|ethminer Got work package: miner 11:25:27|ethminer Header-hash: e0d17637605faf0c8af170e660333d6efbb776ab673a8ccaf78729ed780debae miner 11:25:27|ethminer Seedhash: f2e59013a0a379837166b59f871b20a8a0d101d1c355ea85d35329360e69c000 miner 11:25:27|ethminer Target: 0000000000272310ce2cd255d9abc6a9216da5a1d4a92cd871397b8e70406bf2 [OPENCL]:Using platform: AMD Accelerated Parallel Processing [OPENCL]:Using device: Hawaii(OpenCL 1.2 AMD-APP (1445.5)) [OPENCL]:Printing program log [OPENCL]:LOOP UNROLL: pragma unroll (line 300) Unrolled as requested! LOOP UNROLL: pragma unroll (line 266) Unrolled as requested! LOOP UNROLL: pragma unroll (line 361) Unrolled as requested! LOOP UNROLL: pragma unroll (line 361) Unrolled as requested! [OPENCL]:Creating one big buffer for the DAG [OPENCL]:Loading single big chunk kernels [OPENCL]:Mapping one big chunk. [OPENCL]:Printing program log [OPENCL]:LOOP UNROLL: pragma unroll (line 300) Unrolled as requested! LOOP UNROLL: pragma unroll (line 266) Unrolled as requested! LOOP UNROLL: pragma unroll (line 361) Unrolled as requested! LOOP UNROLL: pragma unroll (line 361) Unrolled as requested! [OPENCL]:Creating one big buffer for the DAG [OPENCL]:Loading single big chunk kernels [OPENCL]:Mapping one big chunk. [OPENCL]:Creating buffer for header. [OPENCL]:Creating mining buffer 0 [OPENCL]:Creating mining buffer 1 ⚡ 11:25:48|ethminer pause 20955 ms ℹ 11:25:48|gpuminer0 workLoop 1 #f2e59013… #f2e59013… [OPENCL]:Creating buffer for header. [OPENCL]:Creating mining buffer 0 [OPENCL]:Creating mining buffer 1 ⚡ 11:26:00|ethminer pause 12271 ms ℹ 11:26:00|gpuminer1 workLoop 1 #f2e59013… #f2e59013… miner 11:26:00|ethminer Mining on PoWhash #e0d17637… : 76888692 H/s = 39059456 hashes / 0.508 s miner 11:26:00|ethminer Got work package: miner 11:26:00|ethminer Header-hash: 9630c900f62f9fb7113e91f57378c5ade3f13682e679c1eef13e5ae5b05e370c miner 11:26:00|ethminer Seedhash: f2e59013a0a379837166b59f871b20a8a0d101d1c355ea85d35329360e69c000 miner 11:26:00|ethminer Target: 0000000000271e2da5047ed8b73eb9da631b42e08ad7eef311ebf437ade51dde ℹ 11:26:01|gpuminer0 workLoop 1 #f2e59013… #f2e59013… ℹ 11:26:01|gpuminer1 workLoop 1 #f2e59013… #f2e59013… miner 11:26:01|ethminer Mining on PoWhash #9630c900… : 32376350 H/s = 16252928 hashes / 0.502 s miner 11:26:02|ethminer Mining on PoWhash #9630c900… : 29812454 H/s = 15204352 hashes / 0.51 s miner 11:26:02|ethminer Mining on PoWhash #9630c900… : 41336079 H/s = 20709376 hashes / 0.501 s DAG 11:26:03|ethminer Generating DAG file. Progress: 0 % miner 11:26:03|ethminer Mining on PoWhash #9630c900… : 36051237 H/s = 18350080 hashes / 0.509 s miner 11:26:03|ethminer Mining on PoWhash #9630c900… : 47754914 H/s = 24641536 hashes / 0.516 s miner 11:26:04|ethminer Mining on PoWhash #9630c900… : 48661461 H/s = 24379392 hashes / 0.501 s miner 11:26:04|ethminer Mining on PoWhash #9630c900… : 51277668 H/s = 25690112 hashes / 0.501 s miner 11:26:05|ethminer Mining on PoWhash #9630c900… : 52116103 H/s = 26214400 hashes / 0.503 s ... ... ... miner 11:38:20|ethminer Target: 000000000026fc0eaed1e0a9cd72b14fc39d269acc913383c4f9a160bdcc6b7c ℹ 11:38:21|gpuminer0 workLoop 1 #f2e59013… #f2e59013… ℹ 11:38:21|gpuminer1 workLoop 1 #f2e59013… #f2e59013… DAG 11:38:21|ethminer Generating DAG file. Progress: 99 % miner 11:38:21|ethminer Mining on PoWhash #6cd99209… : 48234496 H/s = 24117248 hashes / 0.5 s miner 11:38:22|ethminer Mining on PoWhash #6cd99209… : 50231185 H/s = 25165824 hashes / 0.501 s miner 11:38:22|ethminer Mining on PoWhash #6cd99209… : 51277668 H/s = 25690112 hashes / 0.501 s miner 11:38:23|ethminer Mining on PoWhash #6cd99209… : 50131123 H/s = 25165824 hashes / 0.502 s miner 11:38:23|ethminer Mining on PoWhash #6cd99209… : 50131123 H/s = 25165824 hashes / 0.502 s miner 11:38:24|ethminer Mining on PoWhash #6cd99209… : 48138219 H/s = 24117248 hashes / 0.501 s miner 11:38:24|ethminer Mining on PoWhash #6cd99209… : 52324151 H/s = 26214400 hashes / 0.501 s miner 11:38:25|ethminer Mining on PoWhash #6cd99209… : 50871508 H/s = 25690112 hashes / 0.505 s miner 11:38:25|ethminer Mining on PoWhash #6cd99209… : 42820334 H/s = 21495808 hashes / 0.502 s miner 11:38:26|ethminer Mining on PoWhash #6cd99209… : 49086725 H/s = 24641536 hashes / 0.502 s miner 11:38:26|ethminer Mining on PoWhash #6cd99209… : 50452317 H/s = 25427968 hashes / 0.504 s miner 11:38:27|ethminer Mining on PoWhash #6cd99209… : 50552620 H/s = 25427968 hashes / 0.503 s miner 11:38:27|ethminer Mining on PoWhash #6cd99209… : 50031459 H/s = 25165824 hashes / 0.503 s miner 11:38:28|ethminer Mining on PoWhash #6cd99209… : 49932190 H/s = 25165824 hashes / 0.504 s DAG 11:38:28|ethminer Generating DAG file. Progress: 100 % ℹ 11:38:28|ethminer Full DAG loaded miner 11:38:28|ethminer Mining on PoWhash #6cd99209… : 50571086 H/s = 25690112 hashes / 0.508 s

hangabers

as for my OpenCL X Crossfire problems... maybe this is a clue

Loading A Generated Binary Kernel
The steps involved in loading a generated binary OpenCL™ kernel are as follows:

Setup the OpenCL™ platform and create a context with the OpenCL™ devices you plan to use.
Example:
cl_platform_id platform; /* you must find the appropriate platform. */
cl_context_properties cprops[3];
cl_context context;
cprops[0] = CL_CONTEXT_PLATFORM;
cprops[1] = (cl_context_properties)platform;
cprops[2] = (cl_context_properties)NULL;
/* create a context with all of the available devices. */
context = clCreateContextFromType( cprops, CL_DEVICE_TYPE_ALL, NULL, NULL, &err );
For each of the OpenCL™ devices you plan to use, load the appropriate generated binary kernels into individual character buffers. For this example, we assume that you are targeting a single OpenCL™ device and that your generated binary kernel is stored in binary.
Example:
char * binary; /* you must load the appropriatebinary kernel here. */
size_t binary_size; /* you must store the size ofthe binary kernel here. */
Load the generated binary kernels into an OpenCL™ program. If you are loading multiple binary kernels at the same time, the binary kernels in the array must be in the same orderas the matching devices in the device array.
Example:
cl_program program;
program = clCreateProgramWithBinary( context, 1,&device_id, &binary_size, &binary, NULL, &err );
Call clBuildProgram() to setup the necessary internal program state.
Example:
err = clBuildProgram( program, 1, &device_id, NULL, NULL, NULL );
At this point, you can treat the kernels in the OpenCL™ program as you would kernels that were compiled online.
For a sample program that demonstrates this technique, see the clbinaryuse.c file in clbinary.zip.

Notes
It should be noted that while online compilation allows the OpenCL™ runtime to retarget the OpenCL™ C kernel source dynamically to the currently available devices being used in the context, offline compilation, by its very nature, is essentially taking a snapshot of the generated binary kernel for a particular GPU. Developers are highly encouraged to not only generate separate binary kernels for each supported GPU, but to also test their binary kernels to ensure they function properly across the range of devices they wish to support.
The bitness of the generated binary kernel must match the bitness of the OpenCL™ runtime. Attempting to generate or load a binary kernel of a bitness that does not match the OpenCL™ runtime may result in undefined behavior. It is the application’s responsibility to perform the necessary bitness checks.
Currently, even if the binary kernel does not have intermediate kernel representations removed, the OpenCL™ runtime will not attempt to perform a full or partial recompilation. Each generated binary kernel is supported only on the OpenCL™ device it was originally generated for. Attempting to load a binary kernel onto an OpenCL™ device for which it was not originally generated for may result in undefined behavior. It is the application’s responsibility to ensure that binary kernels are only loaded ontocompatible OpenCL™ devices.
Currently, a binary kernel may only contain the ISV for a single OpenCL™ device. If support for several OpenCL™ devices is necessary, you must generate, store and load multiple binary kernels.

developer.amd.com/knowledge-base/

hangabers

Annnd now this..?? Removed old DAGs, tried one more time to get Geth to AutoDAG hoping ethminer likes it..

I0831 12:11:56.750569 4222 ethash.go:230] Still generating DAG: 100% I0831 12:11:56.755082 4222 ethash.go:219] Done generating DAG for epoch 6, it took 11m20.855280496s I0831 12:12:02.296831 4222 ethash.go:230] Still generating DAG: 54% I0831 12:12:09.952380 4222 ethash.go:230] Still generating DAG: 55

Two DAG files being created?

gorgamin

Wow ethminer is a buggy POS.