[ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner

[revelacaogr]

.bat example X11...

set GPU_MAX_ALLOC_PERCENT 100
set GPU_USE_SYNC_OBJECTS 1
Color 1E
sgminer -k darkcoin-mod  -o  stratum+tcp://stratum1.suchpool.pw:3328 -u ...... -p ... --no-submit-stale --worksize 64 --hamsi-expand-big 4  --xintensity 128 --thread-concurrency 8192  --gpu-threads 4  --difficulty-multiplier 2

[1714763206]

1714763206

[1714763206]

1714763206

[1714763206]

1714763206

[enginera]

.bat example X11...

set GPU_MAX_ALLOC_PERCENT 100
set GPU_USE_SYNC_OBJECTS 1
Color 1E
sgminer -k darkcoin-mod  -o  stratum+tcp://stratum1.suchpool.pw:3328 -u ...... -p ... --no-submit-stale --worksize 64 --hamsi-expand-big 4  --xintensity 128 --thread-concurrency 8192  --gpu-threads 4  --difficulty-multiplier 2

Color worked yes But that's all.
sgminer.exe -k darkcoin.cl worked. the problem is --difficulty-multiplier part.
https://i.imgur.com/f5A1LgY.jpg

[revelacaogr]

use only these:

set GPU_MAX_ALLOC_PERCENT 100
set GPU_USE_SYNC_OBJECTS 1
Color 1E
sgminer -k darkcoin-mod  -o  stratum+tcp://stratum1.suchpool.pw:3328 -u ...... -p ... --no-submit-stale --worksize 64   --i18

[badman74]

.bat example X11...

set GPU_MAX_ALLOC_PERCENT 100
set GPU_USE_SYNC_OBJECTS 1
Color 1E
sgminer -k darkcoin-mod  -o  stratum+tcp://stratum1.suchpool.pw:3328 -u ...... -p ... --no-submit-stale --worksize 64 --hamsi-expand-big 4  --xintensity 128 --thread-concurrency 8192  --gpu-threads 4  --difficulty-multiplier 2

Color worked yes But that's all.
sgminer.exe -k darkcoin.cl worked. the problem is --difficulty-multiplier part.

try the sgminer version from my sig
and -k darkcoin.cl does NOT work as it is actually just loading the default scrypt kernel
-k darkcon or -k darkcoin-mod would work if something wasn't wrong with your darkcoin kernel

[enginera]

i switch to dgore.suprnova pool.
it seems working
https://i.imgur.com/DEMfK7V.jpg

But my worker info not updating at suprnova website.

Anyway.. I give.. renting rig is better

Thank you for your helps

[splat44]

I am mining doge on ypool (see following):



Can anyone explain all those server interruptions and difficulty changed?

As for matter of fact, I earning more litecoin using litecoingpool without interruptions then ypool!

Also the above image applies for LTC mining on ypool.

Again since l have no problems via litecoinpool which cause me to believe earning LTC and DOGE shouldn't be that difficult!

If there no improvement need in my setting then I'll mining doge and will continue with XPM!

[platinum4]

Mining DOGE at 80Kh/s?

[badman74]

Mining DOGE at 80Kh/s?

It looks like his settings need some massive tweaking....

[splat44]

Mining DOGE at 80Kh/s?

It looks like his settings need some massive tweaking....

Are you booth talking about me?
I am using amd R7 240
The only other setting that I have set is "--intensity=14"

What other settings that is needed tweaking?

My card might not be as great but until I get better GPU, this will have to do!

[badman74]

Mining DOGE at 80Kh/s?

It looks like his settings need some massive tweaking....

Are you booth talking about me?
I am using amd R7 240
The only other setting that I have set is "--intensity=14"

What other settings that is needed tweaking?

My card might not be as great but until I get better GPU, this will have to do!

try --worksize 64 --xintensity 64 and see what you get

[splat44]

Mining DOGE at 80Kh/s?

It looks like his settings need some massive tweaking....

Are you booth talking about me?
I am using amd R7 240
The only other setting that I have set is "--intensity=14"

What other settings that is needed tweaking?

My card might not be as great but until I get better GPU, this will have to do!

try --worksize 64 --xintensity 64 and see what you get

So those in addition to what I've set and as below right?:
--intensity 14 --worksize 64 --xintensity 64

What is difference between intensity and xintensity?

[platinum4]

What is difference between intensity and xintensity?

You can't use both in the same instance, it will likely default to intensity.  xintensity is number of shaders x _value of xintensity_

[semajjames]

Does anyone know how two of my rig's can show Nice hash x13 pool as dead when the third rig show's x13 as alive ,,,

all three rigs contain the same gpu's and all three rigs are running on the same password for algo switching

cheers

[JuanHungLo]

Does anyone know how two of my rig's can show Nice hash x13 pool as dead when the third rig show's x13 as alive ,,,

all three rigs contain the same gpu's and all three rigs are running on the same password for algo switching

cheers

Happens to me all the time.  No idea.

[nicehash]

Does anyone know how two of my rig's can show Nice hash x13 pool as dead when the third rig show's x13 as alive ,,,

all three rigs contain the same gpu's and all three rigs are running on the same password for algo switching

cheers

Happens to me all the time.  No idea.

This should not happen. Are all miners at the same location, same public IP? Are you 100% sure you're using VALID bitcoin address as username? Are 100% sure you using exactly the same password factors (try copy paste to make sure).

[MaxDZ8]

What is difference between intensity and xintensity?

You can't use both in the same instance, it will likely default to intensity.  xintensity is number of shaders x _value of xintensity_

Since an user asked me the very same thing I actually had to look at sgminer again. It turns out there are two formulations which are selected on a per-algorithm basis.

Code:

glob_thread_count = clState->compute_shaders * ((cgpu->algorithm.xintensity_shift)?(1UL << (cgpu->algorithm.xintensity_shift + cgpu->xintensity)):cgpu->xintensity);

Which means: it's always shaders * something where something is (usually?) the specified xintensity value (I don't remember the actual xintensity_shift values). Otherwise something will be determined as usual intensity, which could be considered 2^x in layman terms.

Both formulations allow much finer control than regular intensity.

[splat44]

What is difference between intensity and xintensity?

You can't use both in the same instance, it will likely default to intensity.  xintensity is number of shaders x _value of xintensity_

Since an user asked me the very same thing I actually had to look at sgminer again. It turns out there are two formulations which are selected on a per-algorithm basis.

Code:

glob_thread_count = clState->compute_shaders * ((cgpu->algorithm.xintensity_shift)?(1UL << (cgpu->algorithm.xintensity_shift + cgpu->xintensity)):cgpu->xintensity);

Which means: it's always shaders * something where something is (usually?) the specified xintensity value (I don't remember the actual xintensity_shift values). Otherwise something will be determined as usual intensity, which could be considered 2^x in layman terms.

Both formulations allow much finer control than regular intensity.

I am with you so far!
Using --worksize 64 --xintensity 64, then what the expected kh/s number on an AND R7 240 series?

[semajjames]

Does anyone know how two of my rig's can show Nice hash x13 pool as dead when the third rig show's x13 as alive ,,,

all three rigs contain the same gpu's and all three rigs are running on the same password for algo switching

cheers

Happens to me all the time.  No idea.

This should not happen. Are all miners at the same location, same public IP? Are you 100% sure you're using VALID bitcoin address as username? Are 100% sure you using exactly the same password factors (try copy paste to make sure).

Thank's nicehash

All the rig's are on the same public IP and all have the same bitcoin address  with .M1 .M2 .M3 respectively added to the end of the bitcoin address/user name   and yeah all the passwords are copy pasted

the only difference other than specific GPU  settings

is

the two rigs that said X13 was dead contained a X13 profile name :- "name" : "NiceHash_X13_multi",
and
the rig that said X13 was alive contained a X13 profile name  :-          "name" : "NiceHash_x13",

I can't think that this would cause a problem

[Aknoth]

how much is the hashrate with a 290X in myrgroestl now ?

thx

[pallas]

Myr-groestl is about 1.5x faster than groestlcoin.
Since the 290x can go up to 35 mh/s in groestlcoin, I believe it should reach at least 50 mh/s in myr-groestl.
That's using the asm kernel or the latest, unfinished opencl (Hawaii only) kernel.