I'm not a troll, but is there still profit in Cryptonight mining?
I used to do Cryptonight mining with my powerful xeon processors in January - February but stopped in March as profits < electricity (I'm paying EUR 0.13 kWh).
AMD R9 Fury also is not covering electricity costs with Crypto on Nicehash.
So am I missing something? Is crypto mining still viable?
Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 362. (Read 237263 times)
March 25, 2018, 01:53:55 PM
March 25, 2018, 01:52:19 PM
Same error but it says Thread 0 now which indicates it is actually the HD 6950.
Oh well I guess that card is going to have to be on neoscrypt now.
xmr-stak suffers the same problems and all he offered was some patches you could add an compile yourself but no binaries.
https://github.com/fireice-uk/xmr-stak-amd/issues/22
Oh well I guess that card is going to have to be on neoscrypt now.
xmr-stak suffers the same problems and all he offered was some patches you could add an compile yourself but no binaries.
https://github.com/fireice-uk/xmr-stak-amd/issues/22
March 25, 2018, 10:29:58 AM
Ok, guys download V1.1.1 and let's try to solve misteries 
https://mega.nz/#F!qVIgxAwB!kKmgCDICmQwbdVvMb-tAag
https://mega.nz/#F!qVIgxAwB!kKmgCDICmQwbdVvMb-tAag
March 25, 2018, 08:57:23 AM
HD 6950 gets 200h/sec on monero in claymore 9.7
R9 270X gets 430h/sec on monero in claymore 9.7
shows a hashrate in the console but I doubt the results are valid
[2018-03-25 05:54:29] Pool accepted result 0x0000A903
[2018-03-25 05:54:30] Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDR
angeKernel for kernel 3.
[2018-03-25 05:54:31] GPU0[T0]: 419.0 H/S
[2018-03-25 05:54:31] GPU1[T1]: 852.0 H/S
[2018-03-25 05:54:31] Total: 1271.0 H/S
it appears that the error is coming from the R9 270X and not the HD 6900... if kernel 3 means BUS_ID 3
R9 270X gets 430h/sec on monero in claymore 9.7
shows a hashrate in the console but I doubt the results are valid
[2018-03-25 05:54:29] Pool accepted result 0x0000A903
[2018-03-25 05:54:30] Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDR
angeKernel for kernel 3.
[2018-03-25 05:54:31] GPU0[T0]: 419.0 H/S
[2018-03-25 05:54:31] GPU1[T1]: 852.0 H/S
[2018-03-25 05:54:31] Total: 1271.0 H/S
it appears that the error is coming from the R9 270X and not the HD 6900... if kernel 3 means BUS_ID 3
No, kernel 3 has nothing to do with gpu id or bus id 3.
I will do a little more useful error messages so we can find out what is causing the problem.
March 25, 2018, 08:50:15 AM
Thanks! Good job!
What about setting over/underclocking and under/overvoltaging? Maybe you add parameters to set clocks and voltages?
Temperature and fan control didn't work for R9 270X 4Gb.
Miner didn't work if i use gpu_conf section and left only gpu id#2 (270X).
Wrote "Error CL_INVALID_DEVICE when calling clCreateContext."
If I set gpu0 or gpu1 or all 3 cards miner starts to mine.
What about setting over/underclocking and under/overvoltaging? Maybe you add parameters to set clocks and voltages?
Temperature and fan control didn't work for R9 270X 4Gb.
Miner didn't work if i use gpu_conf section and left only gpu id#2 (270X).
Wrote "Error CL_INVALID_DEVICE when calling clCreateContext."
If I set gpu0 or gpu1 or all 3 cards miner starts to mine.
I can add gpu/mem clock parameters, that's not a problem, voltages we will see
can you put a screenshot how it looks when all three cards work, but 270x does not report temp/fans rpm ?
ScreenShot
How I can launch only on 270X?
Looks like it thinks your 270x gpu id is 47, not 2 LOL, now this is really strange.
Did you try leaving out the gpu_conf array and let the miner detect every card ?
Ex. set intensity:0 and leave double_threads off for testing.
March 25, 2018, 08:43:37 AM
/* This is just an example, edit it and remove comment lines (the slash and star) !! */
"gpu_conf" :
[
{ "id" : 0, "intensity" : 13, "double_threads" : true},
{ "id" : 1, "intensity" : 13, "double_threads" : true},
{ "id" : 2, "intensity" : 13, "double_threads" : true},
{ "id" : 3, "intensity" : 13, "double_threads" : true},
{ "id" : 4, "intensity" : 13, "double_threads" : true},
{ "id" : 5, "intensity" : 12, "double_threads" : true},
]
/* Make sure not to delete this last blank line */
this is how the end of the config looks like
"gpu_conf" :
[
{ "id" : 0, "intensity" : 13, "double_threads" : true},
{ "id" : 1, "intensity" : 13, "double_threads" : true},
{ "id" : 2, "intensity" : 13, "double_threads" : true},
{ "id" : 3, "intensity" : 13, "double_threads" : true},
{ "id" : 4, "intensity" : 13, "double_threads" : true},
{ "id" : 5, "intensity" : 12, "double_threads" : true},
]
/* Make sure not to delete this last blank line */
this is how the end of the config looks like
Try download this example config and run it :
https://mega.nz/#F!yJxTTZpK!ZA6WVs3kIfcw_slX3dgw1Q
March 25, 2018, 08:23:16 AM
- Low DevFee (0.85%) -> every ~2 hours 1 minute mining for the dev
- Non-agressive DevFee mining -> if miner can't connect to DevFee pool, no problem, switching back to user pool ASAP
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Smart move why can't the rest do it this way, more will use it with less complaints . if anyone complains about this fee an the way it works they are ass holes .
I can see complaining about the 2 % fee it makes the DEV the ass holes imo.....an they Usually are .......
- Non-agressive DevFee mining -> if miner can't connect to DevFee pool, no problem, switching back to user pool ASAP
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Smart move why can't the rest do it this way, more will use it with less complaints . if anyone complains about this fee an the way it works they are ass holes .
I can see complaining about the 2 % fee it makes the DEV the ass holes imo.....an they Usually are .......
March 25, 2018, 06:38:40 AM
HD 6950 gets 200h/sec on monero in claymore 9.7
R9 270X gets 430h/sec on monero in claymore 9.7
shows a hashrate in the console but I doubt the results are valid
[2018-03-25 05:54:29] Pool accepted result 0x0000A903
[2018-03-25 05:54:30] Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDR
angeKernel for kernel 3.
[2018-03-25 05:54:31] GPU0[T0]: 419.0 H/S
[2018-03-25 05:54:31] GPU1[T1]: 852.0 H/S
[2018-03-25 05:54:31] Total: 1271.0 H/S
it appears that the error is coming from the R9 270X and not the HD 6900... if kernel 3 means BUS_ID 3
270X on Claymore 11.2 gives 500+ h/s. R9 270X gets 430h/sec on monero in claymore 9.7
shows a hashrate in the console but I doubt the results are valid
[2018-03-25 05:54:29] Pool accepted result 0x0000A903
[2018-03-25 05:54:30] Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDR
angeKernel for kernel 3.
[2018-03-25 05:54:31] GPU0[T0]: 419.0 H/S
[2018-03-25 05:54:31] GPU1[T1]: 852.0 H/S
[2018-03-25 05:54:31] Total: 1271.0 H/S
it appears that the error is coming from the R9 270X and not the HD 6900... if kernel 3 means BUS_ID 3
March 25, 2018, 05:49:01 AM
HD 6950 gets 200h/sec on monero in claymore 9.7
R9 270X gets 430h/sec on monero in claymore 9.7
shows a hashrate in the console but I doubt the results are valid
[2018-03-25 05:54:29] Pool accepted result 0x0000A903
[2018-03-25 05:54:30] Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDR
angeKernel for kernel 3.
[2018-03-25 05:54:31] GPU0[T0]: 419.0 H/S
[2018-03-25 05:54:31] GPU1[T1]: 852.0 H/S
[2018-03-25 05:54:31] Total: 1271.0 H/S
it appears that the error is coming from the R9 270X and not the HD 6900... if kernel 3 means BUS_ID 3
R9 270X gets 430h/sec on monero in claymore 9.7
shows a hashrate in the console but I doubt the results are valid
[2018-03-25 05:54:29] Pool accepted result 0x0000A903
[2018-03-25 05:54:30] Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDR
angeKernel for kernel 3.
[2018-03-25 05:54:31] GPU0[T0]: 419.0 H/S
[2018-03-25 05:54:31] GPU1[T1]: 852.0 H/S
[2018-03-25 05:54:31] Total: 1271.0 H/S
it appears that the error is coming from the R9 270X and not the HD 6900... if kernel 3 means BUS_ID 3
March 25, 2018, 05:41:31 AM
I guess it only works with GCN or newer cards like almost every other miner created
[2018-03-25 05:08:15] Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDRangeKernel for kernel 4.
scrolling...
I think, that pre-GCN cards is not suitable for mining at all. Thats why it's needless to say...[2018-03-25 05:08:15] Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDRangeKernel for kernel 4.
scrolling...
Your error may be because of lack of vmemory. Try to lower intensity.
March 25, 2018, 05:40:02 AM
/* This is just an example, edit it and remove comment lines (the slash and star) !! */
"gpu_conf" :
[
{ "id" : 0, "intensity" : 13, "double_threads" : true},
{ "id" : 1, "intensity" : 13, "double_threads" : true},
{ "id" : 2, "intensity" : 13, "double_threads" : true},
{ "id" : 3, "intensity" : 13, "double_threads" : true},
{ "id" : 4, "intensity" : 13, "double_threads" : true},
{ "id" : 5, "intensity" : 12, "double_threads" : true},
]
/* Make sure not to delete this last blank line */
this is how the end of the config looks like
"gpu_conf" :
[
{ "id" : 0, "intensity" : 13, "double_threads" : true},
{ "id" : 1, "intensity" : 13, "double_threads" : true},
{ "id" : 2, "intensity" : 13, "double_threads" : true},
{ "id" : 3, "intensity" : 13, "double_threads" : true},
{ "id" : 4, "intensity" : 13, "double_threads" : true},
{ "id" : 5, "intensity" : 12, "double_threads" : true},
]
/* Make sure not to delete this last blank line */
this is how the end of the config looks like
For whom this post?
March 25, 2018, 05:08:45 AM
I guess it only works with GCN or newer cards like almost every other miner created
[2018-03-25 05:08:15] Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDRangeKernel for kernel 4.
scrolling...
[2018-03-25 05:08:15] Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDRangeKernel for kernel 4.
scrolling...
March 25, 2018, 04:58:01 AM
/* This is just an example, edit it and remove comment lines (the slash and star) !! */
"gpu_conf" :
[
{ "id" : 0, "intensity" : 13, "double_threads" : true},
{ "id" : 1, "intensity" : 13, "double_threads" : true},
{ "id" : 2, "intensity" : 13, "double_threads" : true},
{ "id" : 3, "intensity" : 13, "double_threads" : true},
{ "id" : 4, "intensity" : 13, "double_threads" : true},
{ "id" : 5, "intensity" : 12, "double_threads" : true},
]
/* Make sure not to delete this last blank line */
this is how the end of the config looks like
"gpu_conf" :
[
{ "id" : 0, "intensity" : 13, "double_threads" : true},
{ "id" : 1, "intensity" : 13, "double_threads" : true},
{ "id" : 2, "intensity" : 13, "double_threads" : true},
{ "id" : 3, "intensity" : 13, "double_threads" : true},
{ "id" : 4, "intensity" : 13, "double_threads" : true},
{ "id" : 5, "intensity" : 12, "double_threads" : true},
]
/* Make sure not to delete this last blank line */
this is how the end of the config looks like
March 25, 2018, 04:33:27 AM
Thanks! Good job!
What about setting over/underclocking and under/overvoltaging? Maybe you add parameters to set clocks and voltages?
Temperature and fan control didn't work for R9 270X 4Gb.
Miner didn't work if i use gpu_conf section and left only gpu id#2 (270X).
Wrote "Error CL_INVALID_DEVICE when calling clCreateContext."
If I set gpu0 or gpu1 or all 3 cards miner starts to mine.
What about setting over/underclocking and under/overvoltaging? Maybe you add parameters to set clocks and voltages?
Temperature and fan control didn't work for R9 270X 4Gb.
Miner didn't work if i use gpu_conf section and left only gpu id#2 (270X).
Wrote "Error CL_INVALID_DEVICE when calling clCreateContext."
If I set gpu0 or gpu1 or all 3 cards miner starts to mine.
I can add gpu/mem clock parameters, that's not a problem, voltages we will see
can you put a screenshot how it looks when all three cards work, but 270x does not report temp/fans rpm ?
ScreenShot
How I can launch only on 270X?
March 25, 2018, 02:33:02 AM
Thanks! Good job!
What about setting over/underclocking and under/overvoltaging? Maybe you add parameters to set clocks and voltages?
Temperature and fan control didn't work for R9 270X 4Gb.
Miner didn't work if i use gpu_conf section and left only gpu id#2 (270X).
Wrote "Error CL_INVALID_DEVICE when calling clCreateContext."
If I set gpu0 or gpu1 or all 3 cards miner starts to mine.
What about setting over/underclocking and under/overvoltaging? Maybe you add parameters to set clocks and voltages?
Temperature and fan control didn't work for R9 270X 4Gb.
Miner didn't work if i use gpu_conf section and left only gpu id#2 (270X).
Wrote "Error CL_INVALID_DEVICE when calling clCreateContext."
If I set gpu0 or gpu1 or all 3 cards miner starts to mine.
I can add gpu/mem clock parameters, that's not a problem, voltages we will see
can you put a screenshot how it looks when all three cards work, but 270x does not report temp/fans rpm ?
March 24, 2018, 03:04:16 PM
Thanks! Good job!
What about setting over/underclocking and under/overvoltaging? Maybe you add parameters to set clocks and voltages?
Temperature and fan control didn't work for R9 270X 4Gb.
Miner didn't work if i use gpu_conf section and left only gpu id#2 (270X).
Wrote "Error CL_INVALID_DEVICE when calling clCreateContext."
If I set gpu0 or gpu1 or all 3 cards miner starts to mine.
What about setting over/underclocking and under/overvoltaging? Maybe you add parameters to set clocks and voltages?
Temperature and fan control didn't work for R9 270X 4Gb.
Miner didn't work if i use gpu_conf section and left only gpu id#2 (270X).
Wrote "Error CL_INVALID_DEVICE when calling clCreateContext."
If I set gpu0 or gpu1 or all 3 cards miner starts to mine.
March 24, 2018, 02:37:07 PM
Good job doktor83
I'll try it and comment, thank you.
I'll try it and comment, thank you.
March 24, 2018, 02:34:22 PM
leave a blank line at the end of the config file
i will fix this , just always forget.
i will fix this , just always forget.
March 24, 2018, 02:22:43 PM
That's exactly what I thought. BUT! the miner issues an error if I enable this option. Swears at the syntax error in the config file.
Error in config.txt (ParseError)
Error in config.txt (ParseError)
March 24, 2018, 01:53:57 PM
Hey. There is an error. I tried to run 6 cards RX550 2Gb. With intensity 12 all cards are launched. But the result is noticeably lower than on GG. At an intensity of 13, only 5 cards are mined. The result is close to GG. 6th can not mine. Launched in 2 threads.
https://drive.google.com/open?id=12uE_WPV4Q10T2a6Ee_NyJSfSXvYbt28I
On gg I get 495-500 h / s
https://drive.google.com/open?id=12uE_WPV4Q10T2a6Ee_NyJSfSXvYbt28I
On gg I get 495-500 h / s
That one card can't handle intensity 13, so set every gpu :
"gpu_conf" :
[
{ "id" : 0, "intensity" : 13, "double_threads" : true},
{ "id" : 1, "intensity" : 13, "double_threads" : true},
{ "id" : 2, "intensity" : 13, "double_threads" : true},
{ "id" : 3, "intensity" : 13, "double_threads" : true},
{ "id" : 4, "intensity" : 13, "double_threads" : true},
{ "id" : 5, "intensity" : 12, "double_threads" : true},
]
Jump to: