-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Way to improve HR on HD6xxx #113
Comments
I was get one mixed rig with HD6970/HD6870/HD6850.
But may be I'm wrong, because this is my first day with this pre CGN devices. This issues was discussed here #75 and here fireice-uk/xmr-stak#472 @xmrig you can comment this? Where is a root of problem - "in fork", in miner settings or driver? Something else? |
hum i do some test, and stable result on xmrig are achieved with memchunk of 2 . |
I just finish my final test, under xmrstak |
У меня 6990 (как две 6970) выдает 796 H/S , вот с такими настройками "index": 1, |
@gritche70 nice results! |
{ "background": false, "colors": true, "donate-level": 1, "log-file": null, "print-time": 60, "retries": 5, "retry-pause": 5, "opencl-platform": 0, "threads": [{ "index": 0,
"index": 1,
"pools": [ "user": "49Fo***********+30000", "keepalive": true, "nicehash": false, "variant": -1 "api": { "access-token": null, "worker-id": null |
@GrigoryMel, man we understood you. |
Что то не так? |
@GrigoryMel, please use english. |
yep, X is just a need for using aticonfig but i do a special firmware on windows with rbe fot my 6970 and 6950 for avoid the need of use it . |
I understand, google translator to help you, I translate you so)) |
Please, tell me what exactly file you use? I try to avoid doing the work that you have already done. |
error: «Unauthenticated», код: -1 Please tell me who faced this mistake? Is there a solution? XmrStark |
I just saw this post and I also have HD 6950 2GB and Windows 7 x64 and I get ~297 h/s CN-V7 but not using xmrig-amd I compiled xmr-stak myself and I didn't modify anything in the code to make it work EDIT: using 14.1 beta driver |
@gritche70 you are sure about driver file? clinfo: Max memory allocation: 134217728
Global memory size: 536870912
Name: Barts
Max memory allocation: 268435456
Global memory size: 1073741824
Name: Barts
Max memory allocation: 268435456
Global memory size: 1073741824
Name: Cayman And jessie with 3.2 lts kernel: root@debian:/# uname -a
Linux debian 3.2.101-0302101-generic #201803192131 SMP Mon Mar 19 21:32:51 UTC 2018 x86_64 GNU/Linux
root@debian:/# modinfo fglrx
filename: /lib/modules/3.2.101-0302101-generic/kernel/drivers/char/drm/fglrx.ko
license: Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY
description: ATI Fire GL
author: Fire GL - ATI Research GmbH, Germany
srcversion: E8BCDA993D9B46458839AD6
depends:
retpoline: Y
vermagic: 3.2.101-0302101-generic SMP mod_unload modversions
parm: firegl:charp |
@Tohelo101 I think you need some "golden" driver too. |
@k0ste yep exactly my setup, try xmr-stack to replace xmrig with this setup and no more prob, i don't know why xmrig have problem with old card |
@gritche70, please post your |
clinfo.log Platform Name: AMD Accelerated Parallel Processing Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_CPU |
okey i installled winows again here is new Platform Name: AMD Accelerated Parallel Processing Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_GPU Device Type: CL_DEVICE_TYPE_CPU |
@Tohelo101 post your xmrig configuration. |
@k0ste here it is |
@Tohelo101 you should define your threads configuration manually.
|
@Tohelo101 you try to do a heavy one ( sumo ) , my intensity is for a V7 ( multiply intensity by 0.6 for heavy one ) |
hum Gpu3 seems stuck, too much overclock or to much heat around it |
@gritche70, please post output from your linux box for this: cat /usr/src/fglrx-*/dkms.conf modinfo fglrx And your |
@k0ste CLEAN="rm -f *.*o" BUILT_MODULE_NAME[0]="fglrx" and with this setup ( debian jessie ), 4 fglrx card 👍 so seems near normal , it's not? |
Yeah, but as I mentioned before - driver what you give me:
Is |
@gritche70 |
@k0ste upset lol, you can use the 2, i also do test all day long, and my setup is constantly moving, nothing is wrote . i search the perfect bet, between Xorg dependencies (13 deny it to work ), kernel version ( i don't want to rest on 2.6.x ), and fglrx ( for memory problem ) . i can just confirm the result, but i don't plan to give a ready to go solution |
@gritche70 ok, may be I got you wrong about "amd-catalyst-13.9-linux-x86.x86_64.zip". I was understand that this driver has no memory problems. But my tests give me otherwise. |
@k0ste there lot of to do, i plan to test 3.18 and 3.19 kernel with patch version of fglrx . |
@gritche70 still no luck with memory on this versions. What's about memory in your clinfo? root@debian:/home/build# clinfo | grep -E '(Max memory allocation:|Global memory size:|Name)'
Platform Name: AMD Accelerated Parallel Processing
Platform Name: AMD Accelerated Parallel Processing
Max memory allocation: 134217728
Global memory size: 536870912
Name: Barts
Max memory allocation: 268435456
Global memory size: 1073741824
Name: Barts
Max memory allocation: 268435456
Global memory size: 1073741824
Name: Barts
Max memory allocation: 536870912
Global memory size: 2117074944
Name: Cayman
Max memory allocation: 1922211840
Global memory size: 1922211840
Name: Intel(R) Celeron(R) CPU J1800 @ 2.41GHz root@debian:/home/build# cat /usr/src/fglrx-*/dkms.conf
PACKAGE_NAME="fglrx"
PACKAGE_VERSION="14.301"
CLEAN="rm -f *.*o"
BUILT_MODULE_NAME[0]="fglrx"
MAKE[0]="cd ${dkms_tree}/fglrx/14.301/build; sh make.sh --nohints --uname_r=$kernelver --norootcheck"
DEST_MODULE_LOCATION[0]="/kernel/drivers/char/drm"
AUTOINSTALL="yes"
PATCH[0]="rt_preempt_28.patch"
PATCH_MATCH[0]="^2.6.28\-[0-9]*\-rt$"
PATCH[1]="rt_preempt_31.patch"
PATCH_MATCH[1]="^2.6.31\-[0-9]*\-rt$" root@debian:/home/build# modinfo fglrx | grep -v alias
filename: /lib/modules/3.10.102-0310102-generic/updates/dkms/fglrx.ko
license: Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY
description: ATI Fire GL
author: Fire GL - ATI Research GmbH, Germany
srcversion: 3104151FDCA4A081C526766
depends: amd_iommu_v2
vermagic: 3.10.102-0310102-generic SMP mod_unload modversions
parm: firegl:charp root@debian:/home/build# uname -a
Linux debian 3.10.102-0310102-generic #201606131145 SMP Mon Jun 13 15:47:15 UTC 2016 x86_64 GNU/Linux |
under the 3.10.102 clinfo | grep -E '(Max memory allocation:|Global memory size:|Name)' cat /usr/src/fglrx-*/dkms.conf the memory reported seems strange, but under xmr-stack i do stellite since 1 week without prob, so |
@gritche70 what version of xmr-stack you use? I was try 2.4.5 - the same issue - can't jump over intensity 256. |
i test a lot, but the one modified by indeed miner is fine 👍 |
At my instance - the same :/ "platform_index": 0,
"gpu_threads_conf" : [
{ "index" : 3,
"intensity" : 257, "worksize" : 8,
"affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
"comp_mode" : true
}
], Indeed xmr-stak 2.4.8: root@debian:/home/build/xmr-aeon-stak-2.4.8/bin# ./xmr-stak --noCPU
[2018-06-18 08:54:15] : Your CPU doesn't support hardware AES. Don't expect high hashrates.
[2018-06-18 08:54:15] : MEMORY ALLOC FAILED: mmap failed
[2018-06-18 08:54:15] : MEMORY ALLOC FAILED: mmap failed
[2018-06-18 08:54:15] : MEMORY ALLOC FAILED: mmap failed
[2018-06-18 08:54:15] : MEMORY ALLOC FAILED: mmap failed
[2018-06-18 08:54:15] : MEMORY ALLOC FAILED: mmap failed
-------------------------------------------------------------------
xmr-stak 2.4.8 4f34bd18
Brought to you by fireice_uk and psychocrypt under GPLv3.
Based on CPU mining code by wolf9466 (heavily optimized by fireice_uk).
Based on OpenCL mining code by wolf9466.
Configurable dev donation level is set to 1.0%
You can use following keys to display reports:
'h' - hashrate
'r' - results
'c' - connection
-----------------------------Compiled by Indeed Miners-----------------------------
88 88b 88 8888b. 888888 888888 8888b. 8b d8 88 88b 88 888888 88''Yb .dP'Y8
88 88Yb88 8I Yb 88__ 88__ 8I Yb 88b d88 88 88Yb88 88__ 88__dP `Ybo.'
88 88 Y88 8I dY 88'' 88'' 8I dY 88YbdP88 88 88 Y88 88'' 88'Yb o.`Y8b
88 88 Y8 8888Y' 888888 888888 8888Y' 88 YY 88 88 88 Y8 888888 88 Yb 8bodP'
-----------------------------------------------------------------------------------
[2018-06-18 08:54:15] : Mining coin: cryptonight_v7
[2018-06-18 08:54:17] : Compiling code and initializing GPUs. This will take a while...
[2018-06-18 08:54:17] : Device 3 work size 8 / 32.
[2018-06-18 08:54:17] : Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer.
[2018-06-18 08:54:17] : WARNING: AMD device not found
[2018-06-18 08:54:17] : WARNING: backend AMD (OpenCL) disabled.
[2018-06-18 08:54:17] : ERROR: No miner backend enabled. |
hum very strange, no prob with it . |
This index ('3') is for 2Gb 6970. |
so the same as me, and ow many card do you use on this motherboard, i don't pass 4 because of bios problem ( every card consume 256 Mo of main memory ) |
I test a 6970 alone yesterday on my running system and surprise, like you no way to mount intensity, |
omg, thanks. I'm not insane. |
under 3.10 yes, under 2.6.32 i need to confirm, but 69xx alone work ( it don't work upper 256 under 3.10) |
I since the last change to V7 , lot of old card have problem to produce more Hash .
We can't set intensity to more than 256, and so it cut the maximum rate near 100 H .
I do some test yesterday to improve the situation, and find, that you have backport some code from xmr-stak ( who have the same HR problem ), but that open the possibility to play with mem_chunk and strided_index parameter .
On my 6950, on V7, i pass from 110 to 142 H / r with that 👍
in src/workers/OclThread.cpp
you can modify the 2 entry :
m_stridedIndex(2),
m_memChunk(2),
the 2 times, compil the result and that fine, same improvement as we had with xmr-stak.
but far from old perf, i search a way to improve intensity
The text was updated successfully, but these errors were encountered: