Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: JaredKaragen on April 05, 2018, 08:55:13 PM



Title: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-18)
Post by: JaredKaragen on April 05, 2018, 08:55:13 PM
Followed all instructions on the XMR-stak github to compile.... kinda.  Notes are below.

Huge thanks to Fireice-UK for making this source public.  Without it;  this release would not be here.  If you like it;  I suggest you donate to him directly rather than the devfee as it costs you more than just the donation time of hashrate in the real scope of things.


Compiled using Cuda 10.  
DevFee set to zero.  
Build version number stayed the same, build name was changed (added -JK).  
No major modifications aside from "built by notes", and changing the donate address to '127.0.0.1' for quick timeouts if there is any code trickery I did not catch.  CLi.cpp file was modified to add built by notes, as well as remove excessive fluff.

No donations or whatever required.  Just enjoy.  I know a bunch of you (like me) would like the zero devfee build, but either can't or are too lazy to compile it yourself.   Here you go you lazy ones ;)  If you do feel like taking the time to donate to me for my time, you can find the donation address in the "miner batch" post that is linked in my signature just message me...  But I highly suggest throwing a donation to fireice-uk first... without him, this release would not be possible.

***I literally cut/paste the source and built it 100% as per instruction aside from the edits mentioned above.***

MS Visual C++ Runtime:
 Download here (https://go.microsoft.com/fwlink/?LinkId=746572)

Current Version:
Download XMR-Stak-2.10.7-JK (VS2019 Build) here (https://mega.nz/#!VXAiBawA!jy-pyxCvXKlAeqMgtX97Uw8_ETX6khYfCBoIrBcU6_I)
Download XMR-Stak-2.10.7-JK here (https://mega.nz/#!MeB2xQCL!_UR8vcDexBez_nxku65feRVGFnLA7g6HMCI7YSg0LaQ)

Previous versions:
Download XMR-Stak-2.10.6-JK here (https://mega.nz/#!gKJymAIJ!uL27cctUIc8s-y76SywFTGNU-Q70f1MH4dingJBMWdg)
Download XMR-Stak-2.10.5-JK here (https://mega.nz/#!xX4TlYBR!39Qz9TjOwPFyUOzSHHIfG88bL1yvmK7LT3aoAEsL9qM) (NOTE: suggested to delete old .txt files and let them get rebuilt due to some changes)
Download XMR-Stak-2.10.3-JK here (https://mega.nz/#!kSYyBKxJ!hg6-BZGBm-Gi0UapKRYlYba2wkTLrqtKZMktymbYpLU)
Download XMR-Stak-2.10.2-JK here (https://mega.nz/#!sCRT2CKI!KR6dcrAeQxSNRwO5AQK7rfx4Zbt_GSAamLjZ3JPN4bc)
Download XMR-Stak-2.10.1-JK here (https://mega.nz/#!pKJFlIiK!qyES-LEvOPeztLDrUMCjv4_cXhLYxjkSJ6UnWn3YQv4)
Download XMR-Stak-2.10.0-JK here (https://mega.nz/#!Ne4wRAJC!6XYCwS7X2Bdf19KN1_R8SBdJCHdSkxIBgPQWnq50V_I)
Download XMR-Stak-2.9.0-JK here (https://mega.nz/#!JKpyDCRQ!4OOBWlXmQNrL8x8zfWlhGbTY2UE8nZO25Gv1PL8Noa4)
Download XMR-Stak-2.8.3-JK here (https://mega.nz/#!1DAjyCpa!wxlP39HE_pjXs0HKax_h1A4LzGdkH8a5g82wrPrR16w)
Download XMR-Stak-2.8.2-JK here (https://mega.nz/#!QO5jFYaa!ytrtAEG-hd-NsVeHBS6b2WSsy5dmPt7BAgicNI4Crgo)
Download XMR-Stak-2.7.1-JK here (https://mega.nz/#!cbJSyIpQ!yFGGR87Q6K3DW_60LrFNL46fyEBUYQlOgmGRktvJ64k)
Download XMR-Stak-2.6.0-JK here (https://mega.nz/#!tTYgWAQD!qjv1f3CaHf2KM-Fhl7iAVrPhs1zVPbp2iWfJg4qv5h4)
Download XMR-Stak-2.5.2-JK here (https://mega.nz/#!9WIF0CzC!vxjCH_SxneGBIIH2It_FlTa7xtaEvlDaejZahNfpcaU)
Download XMR-Stak-2.5.1-JK here (https://mega.nz/#!5fB3DSpD!A9Qfwqqk7TV062h16dCDD_T_C7Nb2AFpq0v09ct9c-o)
Download XMR-Stak-2.4.4-JK here (https://mega.nz/#!ASonXAgQ!2LWANRy_UEMsgovLxbOUtd3pJFy46GciG6dDGGni1dY)
Download XMR-Stak-2.4.2-JK here (https://mega.nz/#!BD5DhCoa!WyweiRSEjb_gIDrDBEB4Fo_HmCKyK1bjwL_lB9Z2eT8)

If you are getting slower hashrates on older cards, try these DLL files.  They are from a different release of xmr-stak, thus not compiled by me.  But, another user has reported that replacing the DLL's with these has increased performance.  Your mileage may vary:  https://mega.nz/#!oGY0iIxa!X1tlll_HR5LWTa1aT3jBQIZAR3Bv91_Bgll8huVl84w (https://mega.nz/#!oGY0iIxa!X1tlll_HR5LWTa1aT3jBQIZAR3Bv91_Bgll8huVl84w)  This was applicable on 2.4.x only.

*update*
2019-08-18: Compiled and uploaded 2.10.7 under VS2019
2019-08-12: Compiled and uploaded 2.10.7
2019-07-23: Compiled and uploaded 2.10.6
2019-06-15: Compiled and uploaded 2.10.5
2019-03-28: Compiled and uploaded 2.10.3
2019-03-16: Compiled and uploaded 2.10.2
2019-03-12: Compiled and uploaded 2.10.1
2019-03-07: Compiled tested and uploaded 2.10.0
2019-03-04: Compiled and uploaded 2.9.0
2019-02-16: Compiled and uploaded 2.8.3
2019-02-15: Compiled and uploaded 2.8.2
2018-12-10: Compiled and uploaded 2.7.1
2018-11-23: Compiled and uploaded 2.6.0
2018-10-29: Compiled and uploaded 2.5.2
2018-10-18: Compiled tested and uploaded 2.5.1
2018-06-03: Compiled and uploaded 2.4.4
2018-05-30: Added vc redistributable install link
2018-05-29: Compiled and uploaded 2.4.3/quickly removed partially built binary
2018-04-10: Alternate .dll files from original dev's older release available, download link added.  May give better or worse hashrates.
2018-04-06: Fixed issue with not launching properly.  Added original usage docs from source.

Just run xmr-stak.exe and fill out the questions.  from there after, just run xmr-stak.exe and theres no need to put any commands after.
See my below replies for notes on disabling CPU and GPU's individually.  I can help if you need assistance with your configuration.

Please see all of the build and usage notes on the original github: By clicking here (https://github.com/fireice-uk/xmr-stak/blob/master/README.md).



If you are looking for XTL-stak, that's right here (https://bitcointalk.org/index.php?topic=4416202).


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: tbearhere on April 06, 2018, 06:12:58 PM
Hi JaredKaragen....how you been? :)
Thx for your mining app.

EDIT: There is no read me file....I'll try using

:start
rem for 750ti -l 8x30
set xmrAddress=addy
set poolPassword=x
set poolUrl=stratum+tcp://poolxxx:1234
set launchParam=-l 8x30
rem greater value means more interactivity of your system but lower hash rate
set bFactor=10
rem time between a kernel start
set bSleep=100
xmrMiner_xmr-stak.exe --url=%poolUrl% -u %xmrAddress% -p %poolPassword% %launchParam% --bfactor=%bFactor% --bsleep=%bSleep%
goto start

Hope this works. :)




Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: Dentidan on April 06, 2018, 06:36:20 PM
Is that program faster than the Claymore miner for the R9 290 or 390?


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 06, 2018, 10:25:38 PM
Just run xmr-stak.exe and answer questions it asks.  It will configure all devices it finds.  There are flags in the xmr-stak docs that can allow you to disable one or the other type of hardware such as cpu.

I'll have to re-compress the archive with the xmr-stak originals; yes, I did not include them.  I'll try to get on that asap.

I'll post again shortly, as well as update original post's download link.

A big storm is coming through Cali and it's messing with my connection.  Please bear with me.




Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 06, 2018, 10:49:17 PM
Is that program faster than the Claymore miner for the R9 290 or 390?

I am unsure.  presently I only have an Rx560 to test and it sees an average of 350H/sec...  which seems on par with recent releases; I started it up ~8 hours ago, so the hashrate average is a real average.

Hi JaredKaragen....how you been? :)
Thx for your mining app.

EDIT: There is no read me file....I'll try using

I've... been... busy... to say the least.   Still staying afloat and feeding myself.... tis what counts ;)

xmr-stak is a bit different than ccminer.  I have the original post updated, as well as the new link to the replacement files.  There was corruption in one of the DLL's apparently from my thumbdrive.   I noticed it when installing onto one of my machines that normally doesn't run XMR just a minute ago.   Double checked this version.  Worked like it should....  sorry for the issues.


there's flags you can use at launch if you run xmr-stak --help from a command prompt/powershell.  don't quote me (been up over 24 hours now) but its something to the tune of --disablenvidia --disablecpu, etc....

or if you know code somewhat well; and don't want to look up what the flags are for at launch; you can go into the text files generated in the xmr stak folder; and edit the files you wish to do;  if you want to disable a specific nvidia GPU;  just go in and comment out the details for the GPU like this:
Code:
/*
 * GPU configuration. You should play around with threads and blocks as the fastest settings will vary.
 * index         - GPU index number usually starts from 0.
 * threads       - Number of GPU threads (nothing to do with CPU threads).
 * blocks        - Number of GPU blocks (nothing to do with CPU threads).
 * bfactor       - Enables running the Cryptonight kernel in smaller pieces.
 *                 Increase if you want to reduce GPU lag. Recommended setting on GUI systems - 8
 * bsleep        - Insert a delay of X microseconds between kernel launches.
 *                 Increase if you want to reduce GPU lag. Recommended setting on GUI systems - 100
 * affine_to_cpu - This will affine the thread to a CPU. This can make a GPU miner play along nicer with a CPU miner.
 * sync_mode     - method used to synchronize the device
 *                 documentation: http://docs.nvidia.com/cuda/cuda-runtime-api/group__CUDART__DEVICE.html#group__CUDART__DEVICE_1g69e73c7dda3fc05306ae7c811a690fac
 *                 0 = cudaDeviceScheduleAuto
 *                 1 = cudaDeviceScheduleSpin - create a high load on one cpu thread per gpu
 *                 2 = cudaDeviceScheduleYield
 *                 3 = cudaDeviceScheduleBlockingSync (default)
 *
 * On the first run the miner will look at your system and suggest a basic configuration that will work,
 * you can try to tweak it from there to get the best performance.
 *
 * A filled out configuration should look like this:
 * "gpu_threads_conf" :
 * [
 *     { "index" : 0, "threads" : 17, "blocks" : 60, "bfactor" : 0, "bsleep" :  0,
 *       "affine_to_cpu" : false, "sync_mode" : 3,
 *     },
 * ],
 * If you do not wish to mine with your nVidia GPU(s) then use:
 * "gpu_threads_conf" :
 * null,
 */

"gpu_threads_conf" :
[
/*  // gpu: GeForce GTX 1070 architecture: 61
  //      memory: 6789/8192 MiB
  //      smx: 15
  { "index" : 0,
    "threads" : 28, "blocks" : 45,
    "bfactor" : 6, "bsleep" :  25,
    "affine_to_cpu" : false, "sync_mode" : 3,
  },
*/
  // gpu: GeForce GTX 980 architecture: 52
  //      memory: 3370/4096 MiB
  //      smx: 16
  { "index" : 1,
    "threads" : 12, "blocks" : 48,
    "bfactor" : 6, "bsleep" :  25,
    "affine_to_cpu" : false, "sync_mode" : 3,
  },

],


notice the /* at the beginning of one GPU section, and the */ closing it;  so my XR stak would now only mine with my second GPU (the 980).

or another example if you dont want to mine on your CPU (cpu.txt):

This:
Code:
"cpu_threads_conf" :
[
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },

],

Becomes this:
Code:
"cpu_threads_conf" :
[
   /* { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },
  */
  //  or you can comment out a line one at a time like this line
],

on my machines, I just put a link to the xmr-stak.exe into the system startup folder....   the text/json config files make it so you dont need to launch the miner with the same details every time like ccminer does.


FYI this works on old GTX4xx cards up to the current pascal cards.  only tested with an RX560 as per above, but im sure its got a lot of backwards compatibility considering how many devices it can handle presently.


If you add more gpus to the system or change the processor, etc... just delete the text/json file pertaining (pool/cpu/amd/nvidia) and it will just re-check or re-ask questions it needs to next time you launch it.  If all of your systems are similar, you can copy/paste the JSON configs, and just go into each miner's pool.txt config and change the worker name.


if you are using nanopool, be sure to follow their instructions for connecting with a worker name;  don't reply on the worker name it asked for you separate,  Im not sure exactly yet wht this version asks you if its already included in the username.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: Documan on April 07, 2018, 07:32:49 AM
I wonder if it works with RX 550 cards. The claymore miner does not work with that.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: RIGED on April 07, 2018, 09:16:00 AM
will give it a whirl,
using Cast XMR with 1.5% fee seems stupid when you can keep that fee by using your compiled Stak

we are also doing things check it out, https://vegatoken.org/

thx again


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: Iamtutut on April 07, 2018, 01:28:39 PM
Thanks for the release !


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: Sgsg666 on April 07, 2018, 05:01:58 PM
Yay! Thanks this is awesome!
Other cryptonight miners you might want to configure:

https://bitcointalk.org/index.php?topic=3058014.0
https://github.com/xmrig/xmrig
https://github.com/Bendr0id/xmrigCC


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 07, 2018, 06:09:39 PM
Yay! Thanks this is awesome!
Other cryptonight miners you might want to configure:

https://bitcointalk.org/index.php?topic=3058014.0
https://github.com/xmrig/xmrig
https://github.com/Bendr0id/xmrigCC


is there a reason to recompile more than one XMR app?   I mean;  I just wanted to provide a legitimate outlet to a no devfee miner for my miner batch/packages I am assembling.  I liked XMR-stak because it incorporated Nvidia as well as AMD cards;  as well as supporting all my pre-CUDA7 devices. (470, 550, 550ti, 650, 650ti, etc etc.)

Something I am mainly on the look out for is:  an all-around good version of SGMiner that handles everything from X11->X16R and everything in between for AMD cards.   I don't have my hands on a stable and reliable "AMD 'other algo' miner" as of yet.  Same for equihash and ETH miners.  ETH is bottom of my list as it is its own animal; and not a coin/platform I ever believed in.  I only use ETH on exchanges for selling otherwise unsellable coins at a profit.   If I can not make a profit on DOGE markets;  usually I can squeeze a profit out of going from ALT->ETH->BTC.  Since ETH doesn't scale as small as DOGE, its easier to pinch out a modest profit.

I already have the nvidia side almost handled;  I just want to find a few more no fee sources like for equihash and possibly one for ETH.

I wonder if it works with RX 550 cards. The claymore miner does not work with that.

I've already tested with a rx560, so I don't see why it wouldn't work;  the algo isn't super dependent on memory size AFAIK.



Side note:  With this new no-devfee recompiled version;  it has been maintaining a more steady hashrate report at the pool.  fewer wild swings, etc. as well as a better monthly income as per nanopool's estimate.   I think it is due in part to the miner app disconnecting;  and reconnecting to the pool and getting auto-diff reset when a block change happens during devfee mining.   The first few lower diff shares tend to get a fake hashrate bump etc.   I see it now.   Devfee mining really hurt the miners profits in the end....   Maybe you guys will see it eventually.

I wish people treated mining apps as people treated software in the early 90's on BBS's......  We would be a better society as a whole.

FYI: sorry for the damaged first upload.  I had no clue until something was mentioned.   If anyone had downloaded when I first uploaded;  I suggest replacing it with the current posted version at the top of this thread.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: RIGED on April 09, 2018, 02:34:56 AM
thnx!!

I couldn't get it to run two threads on the vega64
could you please post the code for 6 gpus if you know

thnx again for the effort


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 09, 2018, 02:39:56 AM
thnx!!

I couldn't get it to run two threads on the vega64
could you please post the code for 6 gpus if you know

thnx again for the effort
Not sure what you mean.

If you have multiple GPU, you will see a config file like this for nvidia:
Code:
"gpu_threads_conf" :
[
  // gpu: GeForce GTX 1070 architecture: 61
  //      memory: 6789/8192 MiB
  //      smx: 15
  { "index" : 0,
    "threads" : 28, "blocks" : 45,
    "bfactor" : 8, "bsleep" :  100,
    "affine_to_cpu" : false, "sync_mode" : 3,
  },
  // gpu: GeForce GTX 980 architecture: 52
  //      memory: 3370/4096 MiB
  //      smx: 16
  { "index" : 1,
    "threads" : 12, "blocks" : 48,
    "bfactor" : 6, "bsleep" :  25,
    "affine_to_cpu" : false, "sync_mode" : 3,
  },

],

You can see each GPU listed with it's configs.   There are notes that I did not cut and paste about modifying 'bfactor' and 'bsleep' to 8 and 100 respectively.  This has helped me in my issues in the past.  the AMD file should contain a similar description of its settings.  I am thinking this is probably your issue?  You should see all system GPU's listed in the AMD.txt file.

I don't have any vegas on hand to test with or anything, so I can't get a config from a vega to show a prime example as the app creates the configs itself... so give it a shot;  assuming I understood your initial question properly ;)

Also;  if you add more GPU's to the system, or remove some, or change the CPU, delete the appropriate file (amd.txt, cpu.txt or nvidia.txt) and re-run xmr-stak.exe.  it will re-assess the system and rebuild the configs for the current hardware set.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: minahan24 on April 09, 2018, 02:56:56 AM
OP, what settings do I need to tweak to increase my speed. I have 6x rx570 and I've run SRBMiner and getting 5700h/s, while I'm only getting 4000h/s with this miner. Maybe you can point me to the settings I need to play around.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 09, 2018, 03:12:52 AM
OP, what settings do I need to tweak to increase my speed. I have 6x rx570 and I've run SRBMiner and getting 5700h/s, while I'm only getting 4000h/s with this miner. Maybe you can point me to the settings I need to play around.

I believe it has something to do with the threads and blocks variables;  the .txt file should have an explanation of each one and what it does.

does SRBMiner apply an overclock to the cards when it launches?  that may be the difference in hashrate.


Im not sure is xmr-stak is the quickest miner app overall TBH... but, I do know so far it has a wide range of compatibility with devices compared to most other apps i've tried.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: minahan24 on April 09, 2018, 03:20:36 AM
OP, what settings do I need to tweak to increase my speed. I have 6x rx570 and I've run SRBMiner and getting 5700h/s, while I'm only getting 4000h/s with this miner. Maybe you can point me to the settings I need to play around.

I believe it has something to do with the threads and blocks variables;  the .txt file should have an explanation of each one and what it does.

does SRBMiner apply an overclock to the cards when it launches?  that may be the difference in hashrate.


Im not sure is xmr-stak is the quickest miner app overall TBH... but, I do know so far it has a wide range of compatibility with devices compared to most other apps i've tried.

The SRBMiner doesnt apply any overclock, I have to manually apply it myself. But I'm using the same overclock I've used on the SRBMiner on this miner but getting lower speed so I think I need to play around with the settings. I will update.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: RIGED on April 09, 2018, 05:07:06 AM
thnx!!

I couldn't get it to run two threads on the vega64
could you please post the code for 6 gpus if you know

thnx again for the effort
Not sure what you mean.

If you have multiple GPU, you will see a config file like this for nvidia:

You can see each GPU listed with it's configs.   There are notes that I did not cut and paste about modifying 'bfactor' and 'bsleep' to 8 and 100 respectively.  This has helped me in my issues in the past.  the AMD file should contain a similar description of its settings.  I am thinking this is probably your issue?  You should see all system GPU's listed in the AMD.txt file.

I don't have any vegas on hand to test with or anything, so I can't get a config from a vega to show a prime example as the app creates the configs itself... so give it a shot;  assuming I understood your initial question properly ;)

Also;  if you add more GPU's to the system, or remove some, or change the CPU, delete the appropriate file (amd.txt, cpu.txt or nvidia.txt) and re-run xmr-stak.exe.  it will re-assess the system and rebuild the configs for the current hardware set.

thnx,
 the vega  can run two simultaneous threads reaching 2000H/s but need a double string input in the amd.txt and for the life of me I cant get the coding correct (spacing? a comma? idunno) I'm sure I will get right by the end of the day by trial and error
I will come back and post it here


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 09, 2018, 05:32:54 AM

thnx,
 the vega  can run two simultaneous threads reaching 2000H/s but need a double string input in the amd.txt and for the life of me I cant get the coding correct (spacing? a comma? idunno) I'm sure I will get right by the end of the day by trial and error
I will come back and post it here

When you do;  generate a fresh amd.txt by deleting it and running xmr-stak again.  Post it here with the #code posting ability
Code:
like this

Ill have a peek and give some input =)

Ill be able to put the Rx560 I have back on xmr-stak off my other tests to generate a amd.txt and see what i see on my end as well.  Im pretty sure the vega driver supports the version of openCL I compiled it with.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 09, 2018, 05:49:46 AM
[cuda] error gpu 0 something something :365

1080ti on windows 10 64 bit. 21gb virtual memory
edit nvidia.txt

see notes at beginning of file about adjusting bfactor and bsleep.  probably happening cause you have a monitor plugged into GPU #0.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: Xapodat on April 09, 2018, 08:46:37 AM
This miner does not work so well on old cards like HD 7970. I only get about 400H/s. Anybody has similar result?


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: RIGED on April 09, 2018, 12:15:03 PM

thnx,
 the vega  can run two simultaneous threads reaching 2000H/s but need a double string input in the amd.txt and for the life of me I cant get the coding correct (spacing? a comma? idunno) I'm sure I will get right by the end of the day by trial and error
I will come back and post it here

When you do;  generate a fresh amd.txt by deleting it and running xmr-stak again.  Post it here with the #code posting ability
Code:
like this

Ill have a peek and give some input =)

Ill be able to put the Rx560 I have back on xmr-stak off my other tests to generate a amd.txt and see what i see on my end as well.  Im pretty sure the vega driver supports the version of openCL I compiled it with.

got it work with max intensity set at 1012
but only one thread

Code:
"gpu_threads_conf" : [
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 0,
    "intensity" : 1012, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 1,
    "intensity" : 1012, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 2,
    "intensity" : 1012, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 3,
    "intensity" : 1012, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 4,
    "intensity" : 1012, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 5,
    "intensity" : 1012, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },

],

/*
 * Platform index. This will be 0 unless you have different OpenCL platform - eg. AMD and Intel.
 */
"platform_index" : 1,

giving about the same hash results as the best I can get it with a double thread per card (yea it was the intensities that were giving the buffer error message)

Code:
"gpu_threads_conf" : [
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 0,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 0,
    "intensity" : 800, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 1,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 1,
    "intensity" : 800, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 2,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 2,
    "intensity" : 800, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 3,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 3,
    "intensity" : 800, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 4,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 4,
    "intensity" : 800, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: gfx901 memory:3920
  // compute units: 64
  { "index" : 5,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 5,
    "intensity" : 800, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },

],

/*
 * Platform index. This will be 0 unless you have different OpenCL platform - eg. AMD and Intel.
 */
"platform_index" : 1,


still playing around with the intensities on the dual thread amd.txt file but it seems the new heavy algo is very demanding on the GPUs as i cant get anywhere near the previous algo 2000H/s

good to be on Cryptonight again

many thanx JK!!


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: RaidoP2 on April 09, 2018, 12:49:20 PM
Thanks for compiling this! Has anyone tried with R9 380 or R9 380x cards? What are the best settings?


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 09, 2018, 07:10:12 PM
Thanks for compiling this! Has anyone tried with R9 380 or R9 380x cards? What are the best settings?

Not sure about AMD, I only have an RX560 on hand for testing.   Outside input is greatly appreciated, but since it seems to support the old HD cards, so I think the other R series cards should be supported.




Ill have to go over the code... I am still figuring out how the dev wrote the app; but I think ive figured out how the containers work and the different functions of the app work;   If I can understand how to create a second thread for vegas;  than im sure hashrate would possibly bump up.   Don't get your hopes up on this;  it is pretty complicated and im trying to better understand the code....

My grand idea in the end is to be able to incorporate all of the open source miner apps into one.   Not expecting this to happen, but it is a goal.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: cpryd on April 10, 2018, 04:32:38 PM
Why not read the manual:

Code:
"gpu_thread_num" : 2,
"gpu_threads_conf" : [
  // gpu: gfx901 memory:3920
  // compute units: 56
  { "index" : 0, "intensity" : 1932, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : false
  },
  { "index" : 0, "intensity" : 1932, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : false
  },

],


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 10, 2018, 09:42:02 PM
Why not read the manual:

Code:
"gpu_thread_num" : 2,
"gpu_threads_conf" : [
  // gpu: gfx901 memory:3920
  // compute units: 56
  { "index" : 0, "intensity" : 1932, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : false
  },
  { "index" : 0, "intensity" : 1932, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : false
  },

],

That looks like it should work at first glance;  but if I were to fix it, I would be adding it to be automatically assigned multiple threads when it senses a vega... assuming I can understand the code to that point to make such a change.


A similar issue arises with i3-6100/i3-7100 CPU's.  Its  a 2 core 4 thread, but the app only detects and sets it up as a 2 core 2 thread for some reason.   my i7-920, and many other CPU's detect and assign all threads fine.  not sure what causes this.  *edit* normal behavior as this is HyperThreading taking effect.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 10, 2018, 11:00:35 PM
Updated original post with a download for alternate AMD and nvidia DLL's.  They have given better performance on some older AMD cards, so if you had low results, might wanna give them a try.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: rs1x on April 11, 2018, 12:29:26 AM
nice work @JaredKaragen


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: RIGED on April 11, 2018, 04:29:25 PM
can you please post the code and placement of the command to stop cpu mining

I find it in the cpu.txt file but cant figure out which * to remove and where to place null (with "null" or without) comma , at the end or not
lol its all very confusing trying to understand the script backwards :o


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: Shnikes101 on April 11, 2018, 04:57:58 PM
can you please post the code and placement of the command to stop cpu mining

I find it in the cpu.txt file but cant figure out which * to remove and where to place null (with "null" or without) comma , at the end or not
lol its all very confusing trying to understand the script backwards :o

He did so on post #5. You could also remove everything between the [ ] or use null.


or another example if you dont want to mine on your CPU (cpu.txt):

This:
Code:
"cpu_threads_conf" :
[
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },

],

Becomes this:
Code:
"cpu_threads_conf" :
[
   /* { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
    { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },
  */
  //  or you can comment out a line one at a time like this line
],

Not sure why you closed the last thread. Wouldn't call my post useless spam.
As you mentioned, the instructions to compile and change the DevFee are clearly outlined on github.
There is always a risk in downloading unknown files. The safest option if you want to change the DevFee is to compile the program yourself - I'd encourage people to at least try.
Jared seems like a nice enough guy and I'm sure would help users out if they have issues but again, safest option is to compile yourself. Trust the code - beware of people.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: livada on April 11, 2018, 10:57:07 PM
NICE JOB :)

Do you add other coin in?

TRTL not work (light) i try with criptonight_lite but reject
XHV not work (heavy) i try with sumo but reject


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 11, 2018, 11:44:15 PM
NICE JOB :)

Do you add other coin in?

TRTL not work (light) i try with criptonight_lite but reject
XHV not work (heavy) i try with sumo but reject

I dont think so;  it was the first xmr-stak release for the cryptonight7 fork.   I didn't look into any of the other algos, my only focus was a zero devfee XMR miner; cause most of em have fees and negatives with switching to a dev pool.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 11, 2018, 11:49:17 PM
Not sure why you closed the last thread. Wouldn't call my post useless spam.
As you mentioned, the instructions to compile and change the DevFee are clearly outlined on github.
There is always a risk in downloading unknown files. The safest option if you want to change the DevFee is to compile the program yourself - I'd encourage people to at least try.
Jared seems like a nice enough guy and I'm sure would help users out if they have issues but again, safest option is to compile yourself. Trust the code - beware of people.

I wanted to have mod control of my thread;  repeats of the same crap are just annoying and useless as the second reply was.

Of course, with anything precompiled, it's at your own risk or your own ability to research the source (provider) or the material (app to download) =)


And to make it clear for commenting things:
Code:
This text is not commented out 
/* But everything between these symbols is commented out */
as well as this text or code is not commented out // But everything after the two '//' is commented out for this line only.
not this line, this line is not commented out

Hopefully that helps serve as a primer for people that don't understand C code type comment fundamentals.



Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: cryptonist on April 19, 2018, 03:32:34 AM
Followed all instructions on the XMR-stak github to compile.  This is the new Monero7 fork fix.  *edit* 4/6/18 4:05PM PST  Mining fine.  Fork-compatibility assured.

Can you please update and reshare using latest release? There was an update a few hours back. Thanks for the great work, bro.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 20, 2018, 12:33:46 AM
Followed all instructions on the XMR-stak github to compile.  This is the new Monero7 fork fix.  *edit* 4/6/18 4:05PM PST  Mining fine.  Fork-compatibility assured.

Can you please update and reshare using latest release? There was an update a few hours back. Thanks for the great work, bro.

Yeah, Ill be working till late (another 4-5 hours) then when I get home, hopefully Ill be able to recompile the binary from the new source for you guys.


Stay tuned for an update.  if not tonight or tomorrow, this weekend for sure.




Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: whoismoses on April 20, 2018, 02:17:04 AM
Can you please update and reshare using latest release? There was an update a few hours back. Thanks for the great work, bro.

and people wonder why other miners are closed source.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: MagicSmoker on April 20, 2018, 07:33:47 PM
Thanks for compiling this! Has anyone tried with R9 380 or R9 380x cards? What are the best settings?

Not sure about AMD, I only have an RX560 on hand for testing.   Outside input is greatly appreciated, but since it seems to support the old HD cards, so I think the other R series cards should be supported.
...

Thanks for doing this! And I can help with the recommended settings for an RX 560 with 16 Compute Units (ie - not the RX 560D, which has 14 CU). I get the best results with two threads per GPU, intensity of 416, worksize of 8, affine to cpu false and strided index 1. So, for example, the relevant section from my amd.txt file looks like the following:

Code:
"gpu_threads_conf" : [
  // gpu: Baffin memory:1395
  // compute units: 16

  { "index" : 0, "intensity" : 416, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },
  { "index" : 0, "intensity" : 416, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },

],

I have 4 cards on that rig and the above section is repeated for each of them except index is incremented by 1 (ie - "index" : 1 for the 2nd GPU; etc.).

When everything is humming I get right around 500 H/s for each GPU using the Adrenalin 18.2.3 drivers on Win 10.

EDIT - oops, I just noticed that you have the RX 560, and the person you were responding to was looking for help with settings for older cards... alas, I can't help with that, either. I'll leave my post as is in case someone else is looking to tweak their RX 560.





Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: columbiamining on April 21, 2018, 01:59:25 PM
@JaredKaragen

Would love to see this compiled from the new 2.4.3. Looking forward to it!


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: cvsea on April 21, 2018, 04:12:54 PM
Does anybody know why there are a lot of "job not found" rejected shares when mining at nicehash?
They are driving me crazy.

Thanks for this thread, inspired me to compile it myself (took a while but it worked).
For all you do-it-yourselfers out there, I used this tutorial:

https://www.youtube.com/watch?v=VgK8dhKmxc0



Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: lncm on April 21, 2018, 06:02:43 PM
@JaredKaragen

Would love to see this compiled from the new 2.4.3. Looking forward to it!

Me too.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: lncm on April 21, 2018, 06:06:56 PM
Can you please update and reshare using latest release? There was an update a few hours back. Thanks for the great work, bro.

and people wonder why other miners are closed source.

Devs give the option and even teach how to do, what file to edit.

I can compile XMR-Stak myself, and I do it for my AMD machine, disabling CUDA backend.

But I need now a 2.4.3 Nvidia working version, and really could use a pre-compiled one because I would need to install a few gigs on that PC, namely MS Visual Studio and Nvidia CUDA.

For someone who has done it, it's a 5 minute task.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 23, 2018, 09:41:07 PM
Can you please update and reshare using latest release? There was an update a few hours back. Thanks for the great work, bro.

and people wonder why other miners are closed source.

Devs give the option and even teach how to do, what file to edit.

I can compile XMR-Stak myself, and I do it for my AMD machine, disabling CUDA backend.

But I need now a 2.4.3 Nvidia working version, and really could use a pre-compiled one because I would need to install a few gigs on that PC, namely MS Visual Studio and Nvidia CUDA.

For someone who has done it, it's a 5 minute task.

I can do it;  when I am well enough.   

I am in no state to be trying this right now;  I've been on Carisoprodol all weekend.... I am in no state until I come back to reality in another day or two as today is my last day of doses.... sorry guys....


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on April 30, 2018, 10:33:09 PM
Just an update guys.

Can't compile this.   MS Visual Studio broke my compiler to no fault of my own.  I can't get an acceptable version for the version of CUDA I have installed.

Funny;  it happened before I even tried to update VS or the CUDA toolkit.

When I can get MSVS2017 and CUDA9.1 to play again;  Ill have a re-compiled updated version.

Until then;  you will have to just be upset at microsoft for their typical BS.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: onionpealer on May 01, 2018, 08:10:41 PM
Just an update guys.

Can't compile this.   MS Visual Studio broke my compiler to no fault of my own.  I can't get an acceptable version for the version of CUDA I have installed.

Funny;  it happened before I even tried to update VS or the CUDA toolkit.

When I can get MSVS2017 and CUDA9.1 to play again;  Ill have a re-compiled updated version.

Until then;  you will have to just be upset at microsoft for their typical BS.

Good luck in getting it working again. I installed MSVS2017 and thought I'd have a go at compiling XMrig to get rig of the dev fee but it's not been working out too well, at least every time I have a go I'm getting further down the line - wish I knew what I was doing :)


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: Vettech on May 26, 2018, 12:01:25 PM
Any updates to this?


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on May 27, 2018, 02:23:11 AM
Any updates to this?

not yet.   Hopefully soon Ill be able to reinstall VS2017 and the cuda toolkits.... give it another attempt.

There are a few programs im waiting to be able to compile....


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: dcrowson on May 27, 2018, 04:19:14 AM
I compiled 2.4.3 from the source just using the compile instructions after changing it to 0%. It was fairly straight forward. I'm more than willing to give out a link.

I appreciate the original poster giving access to his previous version.

Dan


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: Vettech on May 27, 2018, 07:56:07 PM
I compiled 2.4.3 from the source just using the compile instructions after changing it to 0%. It was fairly straight forward. I'm more than willing to give out a link.

I appreciate the original poster giving access to his previous version.

Dan

Feel free to post it. Let's check out your work; lol, jk. I would attempt to compile myself if I weren't so dang busy. Trying to get there, one step at a time.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: RIGED on May 28, 2018, 12:42:56 PM
Hi JK,

just wanted to say thank you again
have referred many to your thread here
hope you are feeling better

all the best
 


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on May 29, 2018, 01:33:45 AM
Hi JK,

just wanted to say thank you again
have referred many to your thread here
hope you are feeling better

all the best
 

Thanks again.   Ill be trying to reinstall VS2017 right now as well as the cuda SDK.... we will see how it goes....



Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on May 29, 2018, 02:32:10 AM
Success.

See first post;  Version 2.4.3 is now compiled and available.

Tested on my laptop with the CPU;  but no reason to believe there is any problems with cuda/openCL.

Enjoy guys.


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: Guy Montag on May 29, 2018, 06:29:54 AM
Thanks for the release  :D


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: Poyu on May 30, 2018, 04:50:37 AM
Success.

See first post;  Version 2.4.3 is now compiled and available.

Tested on my laptop with the CPU;  but no reason to believe there is any problems with cuda/openCL.

Enjoy guys.

Hi,

Does your last version supports the last fork of Electroneum?

Thanks for doing this!


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: JaredKaragen on May 30, 2018, 05:11:19 AM
Success.

See first post;  Version 2.4.3 is now compiled and available.

Tested on my laptop with the CPU;  but no reason to believe there is any problems with cuda/openCL.

Enjoy guys.

Hi,

Does your last version supports the last fork of Electroneum?

Thanks for doing this!

yep, looks like electronium is supported.  give it a try.

Ive only tested with CN7 myself, but this should be exactly the same as the github precompile, aside from the zero devfee change and dev pool address change to localhost (127.0.0.1).   If theres an error in electronium;  it must exist in the main precompile found on github as well.


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: Vettech on May 30, 2018, 09:52:58 AM
We shall see soon enough. I'm still waiting for Electronero MainNet to be released. Should be today, 30 May around 9am GMT according to their website. Thanks for getting this out just in time. I appreciate all your hard work JK. Glad you're feelin better. Happy Mining!


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: Truthchanter on May 30, 2018, 01:42:40 PM
I get some errors when I try to start this.. the normal dev fee release works fine though


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: JaredKaragen on May 30, 2018, 03:35:21 PM
I get some errors when I try to start this.. the normal dev fee release works fine though
Screenshots or detailed list of the problem may help me resolve your issue.

It ran perfectly fine on my Lenovo laptop...


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: s0ftcorn on May 30, 2018, 09:41:28 PM
Im getting errors about missing DLLs:

VCRUNTIME140D.dll
ucrtbased.dll
MSVCP140D.dll

I have basically all MS VC++ redistributables installed (from 2005 thru 2017). But since there is a D in the end of the file, i have the suspicion that these are debug-dlls. Any idea?


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: onionpealer on May 31, 2018, 12:03:19 AM
Im getting errors about missing DLLs:

VCRUNTIME140D.dll
ucrtbased.dll
MSVCP140D.dll

I have basically all MS VC++ redistributables installed (from 2005 thru 2017). But since there is a D in the end of the file, i have the suspicion that these are debug-dlls. Any idea?

I got something like this when I tried to compile XMrig, think it was missing a different dll, still working on it...


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: JaredKaragen on May 31, 2018, 12:30:09 AM
It's definitely a msvc lib install needed


The redistributable should be included with the 2.4.2 release.  If not, reply here and I'll upload it to mega for you guys to download...


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: s0ftcorn on May 31, 2018, 12:46:28 AM
It's definitely a msvc lib install needed


The redistributable should be included with the 2.4.2 release.  If not, reply here and I'll upload it to mega for you guys to download...

The 2.4.2 release works fine. But even if i use the dlls from the 2.4.2 release the 2.4.3 release doesnt work.


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: JaredKaragen on May 31, 2018, 01:03:51 AM
No, msvc redis is a whole slurry of system dll files that don't belong in the program folder.....

This is why it's a system package from Microsoft....

When I finally make it home I'll try on 3 more machines to see if it's a singular fault, or if it's a universal fault to people without some msvc version installed.


*edit*
So it turns out I built as a debug release and it didn't build in the MSVC140 libraries into the executable like it did for earlier releases.

I am booting up the laptop with the compiler and attempting a final release recompile.

Stay tuned.

*edit again*

Gotta completely flush out all toolkits and compilers from my laptop, and try over again.

Very strange things are happening now.   Im going to pull the release.

It worked fine on CPU only apparently.  Something is miffed with the cuda and openCL integrations to the compiler for some reason.   The released binary was only partially built;  even though I can compile the solution for the binary by itself and get zero errors.


Hopefully Ill have more for you guys soon... but I need to get at a high speed internet link to do the reinstalls (again), and I have been working 10+ hour days at my day job... so Ill try to get on it shortly.


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: Truthchanter on May 31, 2018, 05:45:12 PM
Im getting errors about missing DLLs:

VCRUNTIME140D.dll
ucrtbased.dll
MSVCP140D.dll

I have basically all MS VC++ redistributables installed (from 2005 thru 2017). But since there is a D in the end of the file, i have the suspicion that these are debug-dlls. Any idea?

Yeah this is the same errors I got


Good luck JK!


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: JaredKaragen on May 31, 2018, 10:27:02 PM
Im getting errors about missing DLLs:

VCRUNTIME140D.dll
ucrtbased.dll
MSVCP140D.dll

I have basically all MS VC++ redistributables installed (from 2005 thru 2017). But since there is a D in the end of the file, i have the suspicion that these are debug-dlls. Any idea?

Yeah this is the same errors I got


Good luck JK!

Yep, ill keep you guys posted.

Turns out the binary was only partially built;   if it ever tried to do anything with cuda/openCL, it would crash due to not being fully built.   My mistake..... but it did mine just fine on my lenovo laptop with integrated graphics.


So, for now, ill only have the 2.4.2 release available.  Gotta get the libraries working again.


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfee
Post by: gustavoghpf on June 01, 2018, 06:33:59 AM
Version 2.4.4 is out, could you try to compile this?


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfee
Post by: balrogbr on June 01, 2018, 03:23:39 PM
Hello, the stellite will make a hardfork, could you add the support to it? would be sensational and so I would not have to leave that miner I think is very good!


https://github.com/stellitecoin/xtl-stak


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfee
Post by: JaredKaragen on June 04, 2018, 04:09:01 AM
Version 2.4.4 is out, could you try to compile this?

Compiled.

Notes and link on first post.  For version changes, see xmr-stak github page.

Hello, the stellite will make a hardfork, could you add the support to it? would be sensational and so I would not have to leave that miner I think is very good!


https://github.com/stellitecoin/xtl-stak
I am downloading the source now before I head home.

Assuming it compiles the same as XMR stak; and the source is configured similarly, I should be able to easily change the devfee level and update the appropriate parts of the source and upload a binary later tonight;  assuming I have time to try and compile once I get home.


Looks like I should be able to do that for you, and Ill post a note here with a link to the thread for XTL-stak when I get it compiled and uploaded.


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfee
Post by: JaredKaragen on June 04, 2018, 06:57:51 AM
Hello, the stellite will make a hardfork, could you add the support to it? would be sensational and so I would not have to leave that miner I think is very good!


https://github.com/stellitecoin/xtl-stak

source downloaded and compiled.

They give a .zip that says 2.4.4; but the code says its still 2.4.3;  I updated it and hopefully it was a typo they forgot to update.

Give it a shot: Visit the XTL-stak thread here (https://bitcointalk.org/index.php?topic=4416202).


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: dudezt on June 06, 2018, 02:02:56 PM
I'm getting only rejected results on my laptop (i5 6300HQ + GTX 960M 4gb)

What's happening?


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: lncm on June 06, 2018, 04:00:44 PM
I'm getting only rejected results on my laptop (i5 6300HQ + GTX 960M 4gb)

What's happening?

You have selected the wrong algo, for sure.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 06, 2018, 07:32:57 PM
I'm getting only rejected results on my laptop (i5 6300HQ + GTX 960M 4gb)

What's happening?

You have selected the wrong algo, for sure.

Yep.   Tested CN7 here at home... no issues. 

Check your configuration


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: dudezt on June 06, 2018, 08:30:58 PM
I'm getting only rejected results on my laptop (i5 6300HQ + GTX 960M 4gb)

What's happening?

You have selected the wrong algo, for sure.

So it means the miner is using CN for electroneum instead of CN7? How do I change this?


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 06, 2018, 10:01:47 PM
Did you choose electroneum when doing the initial config on first run?


If you are upgrading, delete config.txt, pools.txt, etc.  start fresh.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: tbearhere on June 07, 2018, 12:00:04 AM
@JaredKaragen or anyone.
Looking at the OP it really doesn't show how to put call cpu conf ...call coin conf... call gpu conf... call emr-stak call pool  so I can make a bat file for each algo without disturbing the other coins settings. Very confusing. It could have been made like ccminer so easy to use. Anyone have a nvidia bat file that does muti coins from one folder that the miner is in?
Any help plz.  thx  :)  


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 07, 2018, 03:10:31 AM
@JaredKaragen or anyone.
Looking at the OP it really doesn't show how to put call cpu conf ...call coin conf... call gpu conf... call emr-stak call pool  so I can make a bat file for each algo without disturbing the other coins settings. Very confusing. It could have been made like ccminer so easy to use. Anyone have a nvidia bat file that does muti coins from one folder that the miner is in?
Any help plz.  thx  :)  

Well, I think theres a way to specify a different file for each set of settings,

But, if I understand you correctly, you are looking to be able to call xmr-stak similarly to the way ccminer is called?
XMR-stak is a bunch different than most other miner apps in the way its configured......   I would need to figure out a LOT of this guys code locations and structures to rewrite how it works... and I am probably not gonna have that kind of time anytime soon to be frank.


The main premise that makes XMR-stak nicer than the way you launch ccminer; is:
Once you get the host machine set up, you do your first run of xmr-stak, let it take in configs/settings and bench the devices, and you simply need to only call xmr-stak.exe to launch from then on.  It creates its config .txt files to suit your pools config and devices.

If you want multiple instances for multiple devices;  you need multiple folders per device with a copy of the executables in each...   Bench and first run each as normal;  but comment out the devices in each folder's instance/config .txt to only use the devices you wish to use per-instance....



If I am totally wrong above about what you are trying to achieve, LMK... Ill do my best to help.




Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: dudezt on June 07, 2018, 11:27:32 AM
Did you choose electroneum when doing the initial config on first run?


If you are upgrading, delete config.txt, pools.txt, etc.  start fresh.

Yes, I did. I extracted your compilation in a new file.

Going to try again but it's weird.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: dudezt on June 07, 2018, 12:31:53 PM
yeah, it's not working

hmmm...

EDIT: Just tested the original XMR-stak with devfee and it has the same problem btw


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: tbearhere on June 07, 2018, 04:42:11 PM
@JaredKaragen or anyone.
Looking at the OP it really doesn't show how to put call cpu conf ...call coin conf... call gpu conf... call emr-stak call pool  so I can make a bat file for each algo without disturbing the other coins settings. Very confusing. It could have been made like ccminer so easy to use. Anyone have a nvidia bat file that does muti coins from one folder that the miner is in?
Any help plz.  thx  :)  

Well, I think theres a way to specify a different file for each set of settings,

But, if I understand you correctly, you are looking to be able to call xmr-stak similarly to the way ccminer is called?
XMR-stak is a bunch different than most other miner apps in the way its configured......   I would need to figure out a LOT of this guys code locations and structures to rewrite how it works... and I am probably not gonna have that kind of time anytime soon to be frank.


The main premise that makes XMR-stak nicer than the way you launch ccminer; is:
Once you get the host machine set up, you do your first run of xmr-stak, let it take in configs/settings and bench the devices, and you simply need to only call xmr-stak.exe to launch from then on.  It creates its config .txt files to suit your pools config and devices.

If you want multiple instances for multiple devices;  you need multiple folders per device with a copy of the executables in each...   Bench and first run each as normal;  but comment out the devices in each folder's instance/config .txt to only use the devices you wish to use per-instance....



If I am totally wrong above about what you are trying to achieve, LMK... Ill do my best to help.




Thanks JaredKaragen

What I'm trying to do is have one xmr-stak folder and call from a bat. file the coin I want to mine.
But it generates the txt files for only one coin. So if I'm mining bittube ...then ok. But now I want to mine monero from that xmr-stak folder. It will overwrite the .txt folders for bittube I think.
But there is a call from a batch file like this below and I'm not sure if I can call the different algo's from a command line.

Code:
xmr-stak -c bittube 

Now if I have a second bat. file like this below what would happen?

Code:
xmr-stak -c monero 

This is all I'm trying to do....but these files a regenerated or overwritten I think by xmr-stak.

Code:
Usage: xmr-stak [OPTION]...

  -c, --config FILE     common miner configuration file
  -h, --help            show this help
  --noCPU               disable the CPU miner backend
  --cpu FILE            CPU backend miner config file
  --noAMD               disable the AMD miner backend
  --amd FILE            AMD backend miner config file

The Following options temporary overwrites the config file settings:
  -o, --url URL         pool url and port, e.g. pool.usxmrpool.com:3333
  -u, --user USERNAME   pool user name or wallet address
  -p, --pass PASSWD     pool password, in the most cases x or empty ""

Accounting to this I should be able to do this below except for the algo.

Code:
xmr-stak  -c bittube  --cpu  bittubecpuconf.  -o pool.usxmrpool.com:3333  -u addy  -p x

And name the batfile bittube and then make a shortcut to it to put in my mining coins folder.

Here is someone trying to help out too.
https://bitcointalk.org/index.php?topic=2856278.msg39558852#msg39558852

An example of bittube.
Code:
Usage: bittube-miner [OPTION]...

  -h, --help                 show this help
  -v, --version              show version number
  -V, --version-long         show long version number
  -c, --config FILE          common miner configuration file
  -C, --poolconf FILE        pool configuration file
  --noUAC                    disable the UAC dialog
  --benchmark BLOCKVERSION   ONLY do a 60-second benchmark and exit
  --noCPU                    disable the CPU miner backend
  --cpu FILE                 CPU backend miner config file
  --noAMD                    disable the AMD miner backend
  --noAMDCache               disable the AMD(OpenCL) cache for precompiled binaries
  --openCLVendor VENDOR      use OpenCL driver of VENDOR and devices [AMD,NVIDIA]
                             default: AMD
  --amd FILE                 AMD backend miner config file
  --noNVIDIA                 disable the NVIDIA miner backend
  --nvidia FILE              NVIDIA backend miner config file
  -i --httpd HTTP_PORT       HTTP interface port

The following options can be used for automatic start without a guided config,
If config exists then this pool will be top priority.
  -o, --url URL              pool url and port, e.g. pool.usxmrpool.com:3333
  -O, --tls-url URL          TLS pool url and port, e.g. pool.usxmrpool.com:10443
  -u, --user USERNAME        pool user name or wallet address
  -r, --rigid RIGID          rig identifier for pool-side statistics (needs pool support)
  -p, --pass PASSWD          pool password, in the most cases x or empty ""
  --use-nicehash             the pool should run in nicehash mode
  --currency NAME            currency to mine

Environment variables:

  XMRSTAK_NOWAIT             disable the dialog `Press any key to exit.
                                    for non UAC execution

Supported coin opitons:
        - bittube

Version: bittube-miner 1.1.7 be84883
Brought to by fireice_uk and psychocrypt under GPLv3.
Press any key to exit.
EDIT: Just tried the calls to the conf files that were renamed and no good. I'm just going to put each coin algo in its own separate folder.  Thx


I did this and it works now.  :)
Code:
start xmr-stak --config configbittube.txt --poolconf poolmining.bit.tube.txt --cpu cpubittube.txt --nvidia nvidiabittube.txt 
exit 0


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 08, 2018, 07:34:59 AM
EDIT: Just tried the calls to the conf files that were renamed and no good. I'm just going to put each coin algo in its own separate folder.  Thx


I did this and it works now.  :)
Code:
start xmr-stak --config configbittube.txt --poolconf poolmining.bit.tube.txt --cpu cpubittube.txt --nvidia nvidiabittube.txt 
exit 0


Ahh yeah, I see how it works.

I would have generated all of the different configs for each algo (a pools.txt and config.txt), and named them similarly;  but I would have had my batch just rename them to the proper default filenames and rename them back when the program exits.... probably just copying the file, and each time the loop resets it deletes the default file before loading the proper algo is the smartest "failsafe" way to do it.


Glad you got it sorted though.

yeah, it's not working

hmmm...

EDIT: Just tested the original XMR-stak with devfee and it has the same problem btw

How exactly is it not working?  (Details bazzle..... details please)

What algo/coin, what pool?

Id say if the hard fault exists;  then its out of my control for debugging the problem as its gonna be a problem with the apps code itself.....

since its a universal fault for you between builds; it could be just related to your config or PC....


I have been getting no issues with different algos so far, as you can see, tbearhere has been able to get multiple algos to work fine, so I'd like to at least check myself what you are trying to see if there is some sort of issue i can remedy.



Remember, if need be, always try deleting the .txt files and re-launching the app fresh.  input the configs and different things it wants you to input... see if it still has an issue.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: newmz on June 08, 2018, 11:17:00 AM
First of all thanks to @JaredKaragen  for the no devfee builds: great stuff and so far you are correct when you said they seem to provide a much more stable hash-rate at the pool, I guess because we don't get the devfee switching messing with difficulty, etc.

I am mining Loki with cryptonight-heavy, mostly using 1070s and also 2 1080s while running OhGodAnETHlargementPill so the GDDR5x memory latency doesn't make them hash like a 1060.

I just wanted to share some stuff I have done that may help anyone else in my situation. I posted something elsewhere to see if anyone can tell me how to get past the 2 Gig memory limit we are supposed to be able to do with pascal cards, and if that will even make any difference to hash rates... but that's another story.

One of my rigs has 2 x 1070s and 1 x 1080. The 1070s are set to threads 96, blocks 15 and the 1080 is set to whatever XMR-stack defaulted it to. With OhGodAnETHlargementPill running, all three cards do about 700h/s which is great.

My other rig has 4 x 1070s and 1 x 1080. I set the threads/blocks on the 1070s to the same as above, but I noticed that for some reason - when mining all five GPUs, it would run with the 1080 at around 500h/s, 2 of the 1070s at maybe 560h/s and the other two at the 700h/s I saw on the smaller rig.

I put the virtual memory way up to 54 gig or something, made no difference. I set alternating 1070s at xmr-stak default threads and blocks with the other two at T 96 B 15 and it made it worse.

Eventually I solved this issue by running separate instances of XMR-stak. 1st one running the 1080 and the 1st 2 1070s plus cpu core 0, second one running the remaining two 1070s and cpu core 2. With this setup, now finally all five cards are at 650-700h/s. It took quite a bit of messing with the configs of the second instance to get it to even run, and I have to set it to verbosity 4 and 30secs because pressing h doesn't respond and give me hash-rate.

If anyone else is running a 4 or more GPU rig (especially if you use 1070s/1080s) and you aren't getting full hash rate on all GPUs I suggest trying what I did - it works great.
Like I said, getting the second instance of xmr-stak running on the same machine means changing quite a few things in the configuration.txt so if anyone is interested I will try to remember what I did.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 08, 2018, 08:39:47 PM
Thanks for the good word!

Yeah, I have always believed there's some sort of "sweet spot" when it comes to hashrates...   Too much and it feels negatively impacted (example is a NH rental) and too little you don't feel any love because you get not enough cshares many times to keep your server side calculated hashrate normalized (via shares).....

When on pools, having ~10% of poolhash, seems about right... for some reason.  You feel the luck benefits the most.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: onionpealer on June 10, 2018, 10:39:40 PM

Eventually I solved this issue by running separate instances of XMR-stak. 1st one running the 1080 and the 1st 2 1070s plus cpu core 0, second one running the remaining two 1070s and cpu core 2. With this setup, now finally all five cards are at 650-700h/s. It took quite a bit of messing with the configs of the second instance to get it to even run, and I have to set it to verbosity 4 and 30secs because pressing h doesn't respond and give me hash-rate.

If anyone else is running a 4 or more GPU rig (especially if you use 1070s/1080s) and you aren't getting full hash rate on all GPUs I suggest trying what I did - it works great.
Like I said, getting the second instance of xmr-stak running on the same machine means changing quite a few things in the configuration.txt so if anyone is interested I will try to remember what I did.

Great tip, it should be on a top 10 list. I 'accidentally' found this too with my rig with mis-matched cards, that running different instances of the miner for each card(s) helps a lot.   


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: neemzsoul on June 12, 2018, 03:59:44 PM
Mining loki here - How to active Double Threads for RX 580 8gb? Thanks for the miner


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: zenixchen on June 12, 2018, 11:33:29 PM
Can you help to compile new XMR stak 2.4.5 0% dev for new fork from Masai and Haven ? Thanks a lot


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 13, 2018, 02:11:54 AM
Can you help to compile new XMR stak 2.4.5 0% dev for new fork from Masai and Haven ? Thanks a lot

https://imgur.com/a/EO5Ru0D

CUDA is being a @#$!#@$ again.    Its saying its not a compatible version of the compiler;  yet it is.  I have updated nothing since the last 2.4.4 build.

IDK what gives.  This is the same sort of crap that happened to me last time.

Mining loki here - How to active Double Threads for RX 580 8gb? Thanks for the miner
you will have to go on the xmr-stak github and look through the documentation.   I personally don't understand the json config parameters as to how to create them as multiple threads.... so I would refer you to the original docs.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: MagicSmoker on June 13, 2018, 09:30:38 AM
Mining loki here - How to active Double Threads for RX 580 8gb? Thanks for the miner

You simply duplicate the lines starting with { "index" in the amd.txt file like this:

Code:
"gpu_threads_conf" : [
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 0, "intensity" : 848, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true },
  { "index" : 0, "intensity" : 848, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true },
],

This is for a single RX 570 (4GB) because that's what I have.

The easiest way to do this is to let xmr-stak generate the amd.txt file automatically (which it will do the first time it is run) then edit that file to double up on the index lines. You will likely have to adjust the intensity value to get the best hashrate and stop it from crashing, but the other parameters should be the same as shown above (the default choices for strided_index and mem_chunk may not be ideal).

NB - I'm still running 2.4.2.




Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: btckesh on June 14, 2018, 11:31:25 AM
maybe worth a look when i update my hardware later this year. thanks


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: UpStakeLover on June 15, 2018, 08:20:19 PM
thanks for making this. I tried to follow instructions, but I had trouble with visual studio since I already have a few versions of it installed, the cuda downloader for visual studio integration failed.

Yours worked instantly! 2 ez  ;D


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 15, 2018, 11:58:22 PM
thanks for making this. I tried to follow instructions, but I had trouble with visual studio since I already have a few versions of it installed, the cuda downloader for visual studio integration failed.

Yours worked instantly! 2 ez  ;D
you are welcome.


I have expeirenced a very strange connect error to nanopool on only one of my machines....  Anyone else getting this issue?


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: newmz on June 17, 2018, 03:55:15 AM
thanks for making this. I tried to follow instructions, but I had trouble with visual studio since I already have a few versions of it installed, the cuda downloader for visual studio integration failed.

Yours worked instantly! 2 ez  ;D
you are welcome.


I have expeirenced a very strange connect error to nanopool on only one of my machines....  Anyone else getting this issue?

I'm not sure what the hell happens (because so far I have been asleep each time) but I have some issue which seems to crash three instances of the miner (2.4.4) running on two machines. Last night it was after running great for 16 hours, mining Loki (which has a very low difficulty right now which is good, but has taken a price hit - but I am HODLing anyway).

Did you manage to compile 2.4.5 yet? I was going to try to teach myself how sometime but it's like going back to f'ing school.....


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: newmz on June 17, 2018, 04:07:02 AM

Eventually I solved this issue by running separate instances of XMR-stak. 1st one running the 1080 and the 1st 2 1070s plus cpu core 0, second one running the remaining two 1070s and cpu core 2. With this setup, now finally all five cards are at 650-700h/s. It took quite a bit of messing with the configs of the second instance to get it to even run, and I have to set it to verbosity 4 and 30secs because pressing h doesn't respond and give me hash-rate.

If anyone else is running a 4 or more GPU rig (especially if you use 1070s/1080s) and you aren't getting full hash rate on all GPUs I suggest trying what I did - it works great.
Like I said, getting the second instance of xmr-stak running on the same machine means changing quite a few things in the configuration.txt so if anyone is interested I will try to remember what I did.

Great tip, it should be on a top 10 list. I 'accidentally' found this too with my rig with mis-matched cards, that running different instances of the miner for each card(s) helps a lot.   

so are you running an individual instance for every card? does that give you more stability? I have divided the work up into 1 CPU core & 3 GPUs on one instance and 1 CPU core 2 and 2 GPUs on a second instance, but like I said in my previous post - it all still seems to crash eventually. Sometimes it manages to live for a long time and other times only a few hours, but this is also happening on a second machine with only 3 GPUs (one miner instance). I was beginning to suspect that it's OhGodAnEthLargementPill I am running for better 1080 performance rather than xmr-stak that is the issue, but I don't know. I guess I need to make it keep a log and dig into that.

It seems that the majority of cryptonight miners are more AMD focussed so I guess there is a lack of stability, but unfortunately the only ccminer that does cryptonight hasn't updated to the newer ASIC restistant variations of the algorithm like cryptonight-heavy.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 17, 2018, 06:41:43 AM
thanks for making this. I tried to follow instructions, but I had trouble with visual studio since I already have a few versions of it installed, the cuda downloader for visual studio integration failed.

Yours worked instantly! 2 ez  ;D
you are welcome.


I have expeirenced a very strange connect error to nanopool on only one of my machines....  Anyone else getting this issue?

I'm not sure what the hell happens (because so far I have been asleep each time) but I have some issue which seems to crash three instances of the miner (2.4.4) running on two machines. Last night it was after running great for 16 hours, mining Loki (which has a very low difficulty right now which is good, but has taken a price hit - but I am HODLing anyway).

Did you manage to compile 2.4.5 yet? I was going to try to teach myself how sometime but it's like going back to f'ing school.....

no luck on trying with 2.4.5 yet.  Probably sometime tomorrow since Ill be at a location where I can uninstall and reinstall everything for the third time to try and compile it.

The issue was a fluke;  seems right before the completion of the new windows 18xx update.   I tried running 2.4.2, and it gave the same no connect error.

When I came home later that day my machine had rebooted itself automatically, and 2.4.4 launched no problems again.   It was an odd one.


Go into the CPU config, and remove the CPU threads.... leave it blank brackets {}.   See if stability comes back.   I have a LGA775 machine right now that gets TLS socket errors and reconnects every so often.  The auto emails from nanopool from that machine are quite annoying.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: onionpealer on June 17, 2018, 07:14:49 PM

Eventually I solved this issue by running separate instances of XMR-stak. 1st one running the 1080 and the 1st 2 1070s plus cpu core 0, second one running the remaining two 1070s and cpu core 2. With this setup, now finally all five cards are at 650-700h/s. It took quite a bit of messing with the configs of the second instance to get it to even run, and I have to set it to verbosity 4 and 30secs because pressing h doesn't respond and give me hash-rate.

If anyone else is running a 4 or more GPU rig (especially if you use 1070s/1080s) and you aren't getting full hash rate on all GPUs I suggest trying what I did - it works great.
Like I said, getting the second instance of xmr-stak running on the same machine means changing quite a few things in the configuration.txt so if anyone is interested I will try to remember what I did.

Great tip, it should be on a top 10 list. I 'accidentally' found this too with my rig with mis-matched cards, that running different instances of the miner for each card(s) helps a lot.   

so are you running an individual instance for every card? does that give you more stability? I have divided the work up into 1 CPU core & 3 GPUs on one instance and 1 CPU core 2 and 2 GPUs on a second instance, but like I said in my previous post - it all still seems to crash eventually. Sometimes it manages to live for a long time and other times only a few hours, but this is also happening on a second machine with only 3 GPUs (one miner instance). I was beginning to suspect that it's OhGodAnEthLargementPill I am running for better 1080 performance rather than xmr-stak that is the issue, but I don't know. I guess I need to make it keep a log and dig into that.

It seems that the majority of cryptonight miners are more AMD focussed so I guess there is a lack of stability, but unfortunately the only ccminer that does cryptonight hasn't updated to the newer ASIC restistant variations of the algorithm like cryptonight-heavy.

Well, no, not for every card, only if one card looked like it needed special treatment.
I also ran different instances of a miner if I wanted to spread the risk and mine different coins on the same rig.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: redscream on June 20, 2018, 12:51:30 PM
thanks for making this. I tried to follow instructions, but I had trouble with visual studio since I already have a few versions of it installed, the cuda downloader for visual studio integration failed.

Yours worked instantly! 2 ez  ;D
you are welcome.


I have expeirenced a very strange connect error to nanopool on only one of my machines....  Anyone else getting this issue?

I'm not sure what the hell happens (because so far I have been asleep each time) but I have some issue which seems to crash three instances of the miner (2.4.4) running on two machines. Last night it was after running great for 16 hours, mining Loki (which has a very low difficulty right now which is good, but has taken a price hit - but I am HODLing anyway).

Did you manage to compile 2.4.5 yet? I was going to try to teach myself how sometime but it's like going back to f'ing school.....

no luck on trying with 2.4.5 yet.  Probably sometime tomorrow since Ill be at a location where I can uninstall and reinstall everything for the third time to try and compile it.

The issue was a fluke;  seems right before the completion of the new windows 18xx update.   I tried running 2.4.2, and it gave the same no connect error.

When I came home later that day my machine had rebooted itself automatically, and 2.4.4 launched no problems again.   It was an odd one.


Go into the CPU config, and remove the CPU threads.... leave it blank brackets {}.   See if stability comes back.   I have a LGA775 machine right now that gets TLS socket errors and reconnects every so often.  The auto emails from nanopool from that machine are quite annoying.


I really appreciate if you can compile the latest version 2.4.5. Thanks


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: MagicSmoker on June 20, 2018, 01:10:41 PM

I really appreciate if you can compile the latest version 2.4.5. Thanks

Read post #92, ya lazy newb.



Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 20, 2018, 10:12:00 PM

I really appreciate if you can compile the latest version 2.4.5. Thanks

Read post #92, ya lazy newb.



lol, yeah, ive been under the weather the past week and my life has definitely not been normal.  I am hoping to get into work today and work late to try and make up for lost time.

As soon as I am able to sit down at a high speed internet location, ill attempt another recompile.


I noticed with 2.4.4 my cuda libraries would not be able to use the old gtx 5xx series and older.... no bueno.   I may have to remove cuda 9, and reinstall cuda 7.5 and cuda 8, and see if I can get support back in the 4.4.5 version.    I attempted swapping for my old cuda_backend.dll file that worked; and it crashed the app, so I am assuming that happens because the new algos and functions added to cuda_backend.dll were moved around and changed somehow making the old library foreign language to the new app build.


Ill be walking into uncharted territory, because I believe to compile with cuda 7.5 and 8, Ill need to install VS2015....   so yeah.   fingers crossed I guess.

I just wish this crap would continue working after the first time you reboot the machine.

Not helping that im doing it on a laptop, but I ritually hibernate it now.  just cause.   


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: redscream on June 21, 2018, 12:03:45 AM

I really appreciate if you can compile the latest version 2.4.5. Thanks

Read post #92, ya lazy newb.



lol, yeah, ive been under the weather the past week and my life has definitely not been normal.  I am hoping to get into work today and work late to try and make up for lost time.

As soon as I am able to sit down at a high speed internet location, ill attempt another recompile.


I noticed with 2.4.4 my cuda libraries would not be able to use the old gtx 5xx series and older.... no bueno.   I may have to remove cuda 9, and reinstall cuda 7.5 and cuda 8, and see if I can get support back in the 4.4.5 version.    I attempted swapping for my old cuda_backend.dll file that worked; and it crashed the app, so I am assuming that happens because the new algos and functions added to cuda_backend.dll were moved around and changed somehow making the old library foreign language to the new app build.


Ill be walking into uncharted territory, because I believe to compile with cuda 7.5 and 8, Ill need to install VS2015....   so yeah.   fingers crossed I guess.

I just wish this crap would continue working after the first time you reboot the machine.

Not helping that im doing it on a laptop, but I ritually hibernate it now.  just cause.   

Crossed my fingers... I wish I would help you...  :) hope you will get it fixed... :)


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: stevascha on June 23, 2018, 08:51:11 PM
nice thread here, looking forward 2.4.5 version


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: redscream on June 24, 2018, 12:30:07 AM
nice thread here, looking forward 2.4.5 version

I have complied for amd and running with my vegas on my farm. I will share with you folks tomorrow when I make sure the stability.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: FFI2013 on June 24, 2018, 02:42:12 AM
thanks for making this. I tried to follow instructions, but I had trouble with visual studio since I already have a few versions of it installed, the cuda downloader for visual studio integration failed.

Yours worked instantly! 2 ez  ;D
you are welcome.


I have expeirenced a very strange connect error to nanopool on only one of my machines....  Anyone else getting this issue?

I'm not sure what the hell happens (because so far I have been asleep each time) but I have some issue which seems to crash three instances of the miner (2.4.4) running on two machines. Last night it was after running great for 16 hours, mining Loki (which has a very low difficulty right now which is good, but has taken a price hit - but I am HODLing anyway).

Did you manage to compile 2.4.5 yet? I was going to try to teach myself how sometime but it's like going back to f'ing school.....

no luck on trying with 2.4.5 yet.  Probably sometime tomorrow since Ill be at a location where I can uninstall and reinstall everything for the third time to try and compile it.

The issue was a fluke;  seems right before the completion of the new windows 18xx update.   I tried running 2.4.2, and it gave the same no connect error.

When I came home later that day my machine had rebooted itself automatically, and 2.4.4 launched no problems again.   It was an odd one.


Go into the CPU config, and remove the CPU threads.... leave it blank brackets {}.   See if stability comes back.   I have a LGA775 machine right now that gets TLS socket errors and reconnects every so often.  The auto emails from nanopool from that machine are quite annoying.

I got sick of windows sneaking in updates I had all my rigs running 10 pro with updates totally disabled and somehow they all updated so after playing on google for awhile I was able to find a win 10 pro stripped down with no apps or anything I haven't had one issue since


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: newmz on June 24, 2018, 09:08:23 AM
thanks for making this. I tried to follow instructions, but I had trouble with visual studio since I already have a few versions of it installed, the cuda downloader for visual studio integration failed.

Yours worked instantly! 2 ez  ;D
you are welcome.


I have expeirenced a very strange connect error to nanopool on only one of my machines....  Anyone else getting this issue?

I'm not sure what the hell happens (because so far I have been asleep each time) but I have some issue which seems to crash three instances of the miner (2.4.4) running on two machines. Last night it was after running great for 16 hours, mining Loki (which has a very low difficulty right now which is good, but has taken a price hit - but I am HODLing anyway).

Did you manage to compile 2.4.5 yet? I was going to try to teach myself how sometime but it's like going back to f'ing school.....

no luck on trying with 2.4.5 yet.  Probably sometime tomorrow since Ill be at a location where I can uninstall and reinstall everything for the third time to try and compile it.

The issue was a fluke;  seems right before the completion of the new windows 18xx update.   I tried running 2.4.2, and it gave the same no connect error.

When I came home later that day my machine had rebooted itself automatically, and 2.4.4 launched no problems again.   It was an odd one.


Go into the CPU config, and remove the CPU threads.... leave it blank brackets {}.   See if stability comes back.   I have a LGA775 machine right now that gets TLS socket errors and reconnects every so often.  The auto emails from nanopool from that machine are quite annoying.

I got sick of windows sneaking in updates I had all my rigs running 10 pro with updates totally disabled and somehow they all updated so after playing on google for awhile I was able to find a win 10 pro stripped down with no apps or anything I haven't had one issue since

I was also sick of win 10 updates and all that "telemetry" running. I now use win 8.1 on all my rigs. xmr-stak runs OK for Nvidia GPU mining - I get up to 740h/s per gtx1070 (30 threads, 60 blocks, core 0, memory +750, powerlimit 75%).

@JaredKaragen - did you ever manage to compile 2.4.5? I really need to teach myself all that is necessary to compile for Windows or even maybe run linux.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: tbearhere on June 24, 2018, 10:49:30 AM
@JaredKaragen   Did you ever compile XMR-STAK-2.4.8 ?  Thx


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 24, 2018, 03:55:06 PM
@JaredKaragen   Did you ever compile XMR-STAK-2.4.8 ?  Thx
not yet... I guess its been releasing a lot of updates.

Im gonna hopefully try the VS2015 route later today... but I need sleep... havent slept yet... was a busy day yesterday.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 25, 2018, 08:34:55 PM
snip / original message deleted.

this is not a thread for 4 post users to post a binary...

or harass people for donations.

get that crap out of here.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: DireWolfM14 on June 25, 2018, 09:39:41 PM
@JaredKaragen

Thanks for putting this together.  I still want to compile my own, but it's been years since I've done any coding.  I'm sure I'll get a wild hair on a rainy day come winter.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: lncm on June 26, 2018, 01:23:57 PM
@JaredKaragen

Thanks for putting this together.  I still want to compile my own, but it's been years since I've done any coding.  I'm sure I'll get a wild hair on a rainy day come winter.

I don't do any coding also, and if you follow instructions on XMR-Stak Github, you'll get there.

Worst part is installing Gb's of software - VB Studio, CUDA and AMD OpenCL libraries.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: DireWolfM14 on June 26, 2018, 04:51:08 PM
@JaredKaragen

Thanks for putting this together.  I still want to compile my own, but it's been years since I've done any coding.  I'm sure I'll get a wild hair on a rainy day come winter.

I don't do any coding also, and if you follow instructions on XMR-Stak Github, you'll get there.

Worst part is installing Gb's of software - VB Studio, CUDA and AMD OpenCL libraries.

My workstation's .5tb ssd shouldn't mind, but yeah, mountain biking weather...  nobody got time for that.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 27, 2018, 03:29:32 AM
@JaredKaragen   Did you ever compile XMR-STAK-2.4.8 ?  Thx

2.4.5 is all that fierce-uk has released thus far.....    is it another fork or something?




Update:
Im working on my 5th attempt on compiling 2.4.5.    VS 2017 is uninstalling as I type this, and Ill have to rip out all IDE's and start over by installing fresh... again.

Probably going to DL and install the latest version of the cuda toolkit as well.... hopefully they play nice.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: moonstruck on June 27, 2018, 04:08:29 AM
@JaredKaragen   Did you ever compile XMR-STAK-2.4.8 ?  Thx

2.4.5 is all that fierce-uk has released thus far.....    is it another fork or something?




Update:
Im working on my 5th attempt on compiling 2.4.5.    VS 2017 is uninstalling as I type this, and Ill have to rip out all IDE's and start over by installing fresh... again.

Probably going to DL and install the latest version of the cuda toolkit as well.... hopefully they play nice.

Try CUDA 9.1, you'll slow it down with 9.2 unless you know what you're doing.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on June 27, 2018, 04:23:13 AM
Try CUDA 9.1, you'll slow it down with 9.2 unless you know what you're doing.

Cuda 9 fail.

Right now im working on cuda 8:

Sneak Preview (https://imgur.com/a/zGiu2rk)


Edit***

Fail again.

The dirty results (https://imgur.com/a/H1Ux0iw)


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: gambera on July 17, 2018, 01:06:05 AM
JaredKaragen, great work. Should I assume that you abandoned 2.4.5 or there isn't progress?


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on July 17, 2018, 01:59:12 AM
JaredKaragen, great work. Should I assume that you abandoned 2.4.5 or there isn't progress?

yeah.  for now, ive been focused on work... and every attempt so far at compiling 2.4.5 so far has failed.

I want to wipe the laptop Ive been using to compile, and try reinstalling everything fresh again and see where I can get.

I already have the doctored source to compile that removes all the devfee addresses and sets the devfee factor to zero.  I think the only thing I need to change is the build pull number (there's a giithub reference variable its compiled with that's linked to version,  I haven't changed that yet, but it really doesn't matter int he grand scope of things).

I did compile XTL stak at the same time I did 2.4.4... but it seems to not be a version people are after and Ill be ignoring it from now on.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: gambera on July 17, 2018, 03:13:09 AM
JaredKaragen, great work. Should I assume that you abandoned 2.4.5 or there isn't progress?

yeah.  for now, ive been focused on work... and every attempt so far at compiling 2.4.5 so far has failed.

I want to wipe the laptop Ive been using to compile, and try reinstalling everything fresh again and see where I can get.

I already have the doctored source to compile that removes all the devfee addresses and sets the devfee factor to zero.  I think the only thing I need to change is the build pull number (there's a giithub reference variable its compiled with that's linked to version,  I haven't changed that yet, but it really doesn't matter int he grand scope of things).

I did compile XTL stak at the same time I did 2.4.4... but it seems to not be a version people are after and Ill be ignoring it from now on.


You seem close and thank you for that. I think it's a refreshment to this thread as there wasn't any posts since June 26th or so.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: Mohondoa on July 17, 2018, 03:31:48 AM
Honesly i am not yet try this software. It is seem nice software for mining with no fee. But i still choose claymore with dev fee, because i think dev fee is important for developing the software. Anyway thank for sharing new mining software, and i waiting news for it's speed mining.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: onionpealer on July 19, 2018, 09:15:57 PM
Honesly i am not yet try this software. It is seem nice software for mining with no fee. But i still choose claymore with dev fee, because i think dev fee is important for developing the software. Anyway thank for sharing new mining software, and i waiting news for it's speed mining.

I don't fundamentally begrudge the dev fee for the Claymore miner it's just the way it does it that results in a greater loss of mining than just the fee alone (time spent changing servers adds a significant loss).
Maybe longer periods between collecting dev fee and a lower dev fee (he must be loaded by now) would help.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on July 20, 2018, 02:06:38 AM
I have tried this miner and it all went good. Thank you dev for this great miner. It is more easy and profitable to mine xmr now.
Yep, I thank the dev for releasing the source as well.

I'll be gone for the weekend; hopefully I can pick this back up next week when I'm less busy....


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: onionpealer on July 23, 2018, 10:22:17 PM
thanks for making this. I tried to follow instructions, but I had trouble with visual studio since I already have a few versions of it installed, the cuda downloader for visual studio integration failed.

Yours worked instantly! 2 ez  ;D
you are welcome.


I have expeirenced a very strange connect error to nanopool on only one of my machines....  Anyone else getting this issue?

I'm not sure what the hell happens (because so far I have been asleep each time) but I have some issue which seems to crash three instances of the miner (2.4.4) running on two machines. Last night it was after running great for 16 hours, mining Loki (which has a very low difficulty right now which is good, but has taken a price hit - but I am HODLing anyway).

Did you manage to compile 2.4.5 yet? I was going to try to teach myself how sometime but it's like going back to f'ing school.....

no luck on trying with 2.4.5 yet.  Probably sometime tomorrow since Ill be at a location where I can uninstall and reinstall everything for the third time to try and compile it.

The issue was a fluke;  seems right before the completion of the new windows 18xx update.   I tried running 2.4.2, and it gave the same no connect error.

When I came home later that day my machine had rebooted itself automatically, and 2.4.4 launched no problems again.   It was an odd one.


Go into the CPU config, and remove the CPU threads.... leave it blank brackets {}.   See if stability comes back.   I have a LGA775 machine right now that gets TLS socket errors and reconnects every so often.  The auto emails from nanopool from that machine are quite annoying.

I got sick of windows sneaking in updates I had all my rigs running 10 pro with updates totally disabled and somehow they all updated so after playing on google for awhile I was able to find a win 10 pro stripped down with no apps or anything I haven't had one issue since

Do you have a link to this stripped-down version of Windows 10, I'd like to give it a go and see what happens.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 02, 2018, 02:07:53 PM
I'm using 12 rx 570 nitro+ 8gb per rig and I only got 615H per card, is this hashrate power is okay or there is a way to increase it, I'm using the latest version of xmr-stak I hope somebody here put some help..

Thanks


Title: Re: XMR-stak-JK 2.4.3 Compiled with no devfe3
Post by: john1010 on August 02, 2018, 02:16:48 PM
Im getting errors about missing DLLs:

VCRUNTIME140D.dll
ucrtbased.dll
MSVCP140D.dll

I have basically all MS VC++ redistributables installed (from 2005 thru 2017). But since there is a D in the end of the file, i have the suspicion that these are debug-dlls. Any idea?

I got that same error too and tried installing visual ++c and nothing fix by doing that, I dunno why, I ask my friends about the error and they told me that I must uninstall and install the visual ++c but again, nothing happened.. I discovered that it will need to add more virtual memory to fix that error, I recently setting up the VM with 35K but after I add some VM to 55K and the error fixed.. This miner needs more Virtual memory to run smoothly.. Hope it helps.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: MagicSmoker on August 02, 2018, 02:59:29 PM
I'm using 12 rx 570 nitro+ 8gb per rig and I only got 615H per card, is this hashrate power is okay or there is a way to increase it, I'm using the latest version of xmr-stak I hope somebody here put some help..

Thanks

Each card entry in your amd.txt file should look something like this:

{ "index" : 0, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },
{ "index" : 0, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },

With only the index number incrementing by 1 for each card. This gives 2 threads (why the lines are duplicated) with intensity of 800, etc. So, for example, the 2nd card would have entries like so:

{ "index" : 1, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },
{ "index" : 1, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },

Etc. up to the 12th card, which will have index of 11.



Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 03, 2018, 02:17:32 AM
I'm using 12 rx 570 nitro+ 8gb per rig and I only got 615H per card, is this hashrate power is okay or there is a way to increase it, I'm using the latest version of xmr-stak I hope somebody here put some help..

Thanks

Each card entry in your amd.txt file should look something like this:

{ "index" : 0, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },
{ "index" : 0, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },

With only the index number incrementing by 1 for each card. This gives 2 threads (why the lines are duplicated) with intensity of 800, etc. So, for example, the 2nd card would have entries like so:

{ "index" : 1, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },
{ "index" : 1, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },

Etc. up to the 12th card, which will have index of 11.



I will copy this settings on the AMD config txt? Or only the intensity, worksize and memchunk? sorry totally nood using this miner, since when i was started mining I only using claymore eth base and phoenix miner.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 03, 2018, 03:03:23 AM
I'm using 12 rx 570 nitro+ 8gb per rig and I only got 615H per card, is this hashrate power is okay or there is a way to increase it, I'm using the latest version of xmr-stak I hope somebody here put some help..

Thanks

Each card entry in your amd.txt file should look something like this:

{ "index" : 0, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },
{ "index" : 0, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },

With only the index number incrementing by 1 for each card. This gives 2 threads (why the lines are duplicated) with intensity of 800, etc. So, for example, the 2nd card would have entries like so:

{ "index" : 1, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },
{ "index" : 1, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },

Etc. up to the 12th card, which will have index of 11.



I will copy this settings on the AMD config txt? Or only the intensity, worksize and memchunk? sorry totally nood using this miner, since when i was started mining I only using claymore eth base and phoenix miner.

Update of my result, seems that it increased from 614 - 630/645H Thanks for the help.. Oh by the way what is the hashrate of your card? I am using Sapphire RX 580 8GB and MSI Gaming X 570 4Gb..

Here's the screenshot:

https://s22.postimg.cc/9ai1hkl3l/xcash_hash.png


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 03, 2018, 09:41:36 AM
Calling 1080Ti users of this build:

I just got back from servicing a few of my friend's miners;  as well as disassembling and re-pasting cards to be resold...

At the end of my night;  I loaded xmr-stak 2.4.4 and it would crash when it loads the threads for the nvidia cards....    one card, both cards, either card... same result on the 1080 Ti's.


Here's a big rub:
I updated the video driver.  Clean DDE and install clean via the latest available download.    Same results.
Tried my build of 2.4.2.   Same results.
Tried modifying bfactor/bsleep.  Same results.


Here's the twist:
I was given a 1080 from him as a thanks for all the work today....    brought it home;  works like a champ (not Ti...).  We did not test XMR-stak on the 1080 machines, because they have all been dismantled, cleaned, and re-pasted and re-boxed to re-sell and invest the return in crypto during this low....   so;  in my own eyes, to this day I have seen it work with every card I can throw at it except:  1080Ti, and GTX 2xx series....



So has anyone here had success with their 1080 Ti's?
If so:
What OS, Video driver version, and make/model of card do you have?


FYI; this is a driver crash, leading to a cuda error because the driver crashed.    As mentioned above, changing bfactor/bsleep/threads changed nothing.   Mining other algos (xevan, skien, neoscrypt, etc) works fine.

Thanks.    Hopefully this will help me figure out whats really wrong.  


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: MagicSmoker on August 03, 2018, 04:52:21 PM

Update of my result, seems that it increased from 614 - 630/645H Thanks for the help.. Oh by the way what is the hashrate of your card? I am using Sapphire RX 580 8GB and MSI Gaming X 570 4Gb..
...

This card is on my main desktop so not a dedicated mining rig, but I'm doing about 740H/s on average with an Elpida powersaver ROM, core at 1200, mem at 1900 and no change to power limit.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: Bearier on August 04, 2018, 09:15:06 AM
this miner supports Cryptonight v7 ?
please give the file a start.bat for GTX 1070.
I tormented myself half a day, I can not start it at all. I do not understand what to write there.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 04, 2018, 09:20:30 AM
please give the file a start.bat for GTX 1070.
I tormented myself half a day, I can not start it at all. I do not understand what to write there.

There is no batch file.

You run the app for the first time, answer the questions, and it generates .txt files with the configurations and starts mining right away.

When you go to run it thereafter, you simply launch the .exe to mine.


You can reference the docs or this thread for how to trim and modify each video card's properties/intensities; as well as how to create separate configurations for use with different pools/algos.


But;  if you wish to have the app auto-run at startup (especially in windows 10);  it should be run as administrator;  its folder should be in the root of C for example;  do not use a .lnk to launch it from the startup folder;  you must make a simple batch and the batch file should look something like this (modify it for your config; and this should be one of the only reasons you should need a batch file for xmr-stak):
Code:
@echo off
cd c:\XMR-stak-JK_2.4.4\
start xmr-stak.exe
Be sure this batch file is set to run as administrator.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: Bearier on August 04, 2018, 09:53:07 AM
please give the file a start.bat for GTX 1070.
I tormented myself half a day, I can not start it at all. I do not understand what to write there.

There is no batch file.

You run the app for the first time, answer the questions, and it generates .txt files with the configurations and starts mining right away.

When you go to run it thereafter, you simply launch the .exe to mine.


You can reference the docs or this thread for how to trim and modify each video card's properties/intensities; as well as how to create separate configurations for use with different pools/algos.


But;  if you wish to have the app auto-run at startup (especially in windows 10);  it should be run as administrator;  its folder should be in the root of C for example;  do not use a .lnk to launch it from the startup folder;  you must make a simple batch and the batch file should look something like this (modify it for your config; and this is the only reason you should need a batch file for xmr-stak):
Code:
@echo off
cd c:\XMR-stak-JK_2.4.4\
start xmr-stak.exe
Be sure this batch file is set to run as administrator.

Thanks, I will try. Tell me more, does this miner support Cryptonight v7 ?


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 04, 2018, 10:14:50 AM
yes, this one is current, i am unaware of any algo changes coming up soon.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: Bearier on August 04, 2018, 11:12:15 AM
How to configure the display of statistics in the window of the miner (as in ccminer)?
how to disable support for mining on the CPU?


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 04, 2018, 11:32:08 AM
How to configure the display of statistics in the window of the miner (as in ccminer)?
how to disable support for mining on the CPU?
there is none.

to disable individual devices you should read this thread;  it already explains how to modify the settings and comment out the necessary lines and disable/change different devices in the nvidia.txt, cpu.txt and amd.txt....


What would be better is you should check readme.md, compile.md, etc on the official github:
https://github.com/fireice-uk/xmr-stak     Just scroll down;  there's links there to each subject.  It goes into great detail.

I didn't write the program, I just compiled the source with no devfee.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: Bearier on August 04, 2018, 11:35:43 AM
I'm using windows 7. I'm having errors:
https://i101.fastpic.ru/big/2018/0804/95/a819eae9ae05b4f985e77db743497195.jpg



After this, the system will seriously brake and Afterburner does not work.
It is possible as that to solve it?


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 04, 2018, 12:07:55 PM
I'm using windows 7. I'm having errors:
https://i101.fastpic.ru/big/2018/0804/95/a819eae9ae05b4f985e77db743497195.jpg



After this, the system will seriously brake and Afterburner does not work.
It is possible as that to solve it?
those alerts are likely because it was not run as admin; and because its the first time run on that machine before rebooting. (memory alloc errors)


give it a reboot.  try again.  be sure its run as admin.


as for the rest of the stuff crashing;  check the docs.  individual devices need to have their threads and intensities trimmed.   The auto-configure is just a ballpark setting; and can be wrong out of the box (see the notes on 1080ti issues that are on the github).  Also see the docs about windows and the bfactor/bsleep settings.  They are important.

so far, what I see in your screenshot...   is normal.  VirtualAlloc failed, but after memory pinned, and it moves onto the next thread.


The system seemingly locking up is the miner working... the OS will be come horribly unresponsive.  Its using 99.9% of the GPU resources; and is bottle necking the display port's activity.  The system wont be usable while mining unless you trim down settings in the config txt files.... so do all work/modification with the app not running.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 05, 2018, 05:19:42 AM
Is there a way to adjust the gpu fan speed? I noticed that my gpu got hotter using this miner and the fan speed is only set for 20% and my gpu's temp climbed to 65c, Hope that I can get some help..

Thanks @Dev for this miner for no fee!


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 05, 2018, 06:20:15 AM
Is there a way to adjust the gpu fan speed? I noticed that my gpu got hotter using this miner and the fan speed is only set for 20% and my gpu's temp climbed to 65c, Hope that I can get some help..

Thanks @Dev for this miner for no fee!

Many thanks really go to fierce-UK for making the source freely available so I could compile with no devfee.

what brand of cards?

using nvidiainspector, you can use a command line switch to change fan speed....  maybe that can help automate changing your fans... incorporate into a batch to change settings before then after the app closes....  would be a super simple batch file.

Code:
Nvidiainspector.exe -setFanSpeed:0,100 -setFanSpeed:1,100
makes device 0 have 100% fan speed, and device 1 have 100% fan speed.

AMD?  Not sure of any utilities;  as I leave bios stock and use active cooling in my setups and don't depend on gpu fan speed.


XMR is an intensive algo;  and it does make quite a bit of heat (a prime example is the heat a cpu/laptop will generate when simply syncing and updating the XMR blockchain.....)

Side note:   Monero will be algo-forking again.

As soon as a known good source gets released for the update by the original dev;  Ill pull the source, and attempt setup and compiling it again.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 05, 2018, 11:04:53 AM
Is there a way to adjust the gpu fan speed? I noticed that my gpu got hotter using this miner and the fan speed is only set for 20% and my gpu's temp climbed to 65c, Hope that I can get some help..

Thanks @Dev for this miner for no fee!

Many thanks really go to fierce-UK for making the source freely available so I could compile with no devfee.

what brand of cards?

using nvidiainspector, you can use a command line switch to change fan speed....  maybe that can help automate changing your fans... incorporate into a batch to change settings before then after the app closes....  would be a super simple batch file.

Code:
Nvidiainspector.exe -setFanSpeed:0,100 -setFanSpeed:1,100
makes device 0 have 100% fan speed, and device 1 have 100% fan speed.

AMD?  Not sure of any utilities;  as I leave bios stock and use active cooling in my setups and don't depend on gpu fan speed.


XMR is an intensive algo;  and it does make quite a bit of heat (a prime example is the heat a cpu/laptop will generate when simply syncing and updating the XMR blockchain.....)

Side note:   Monero will be algo-forking again.

As soon as a known good source gets released for the update by the original dev;  Ill pull the source, and attempt setup and compiling it again.

Thanks for your reply, suddenly.. I am using AMD cards and I hope you can update the miner soon, I love your miner and thing I searching now is how to increase my hashrate, I only got 635 each card, All of my card are moded and I got 30-31MH in eth and other ethhash algo, this is my first time to mine monero base coin, totally noob for using it.. And thanks for this thread..  :)  :)


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: obm_dan on August 05, 2018, 01:07:44 PM
Is it possible to differentiate between gpus and cpus in the json api?


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 05, 2018, 03:16:30 PM
Is it possible to differentiate between gpus and cpus in the json api?

yes.

see the .txt files xmr-stak generates.

you can separate them into difference instances of xmr-stak per device if you wish;  see comments earlier in this thread by I believe; tbearhere


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: obm_dan on August 05, 2018, 06:33:23 PM
That helps a lot. Thank you. I was able to find the post where they separate configs.

I was hoping that the api on xmrstak was able to say which ones are cpu and which ones are gpu in api.json. I don’t believe that you can tell though.

Easiest way would be to run them separately. Then you know they’re either all cpu or all gpu. Unless I’m interpreting the api response I correctly.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 06, 2018, 07:00:13 AM
That helps a lot. Thank you. I was able to find the post where they separate configs.

I was hoping that the api on xmrstak was able to say which ones are cpu and which ones are gpu in api.json. I don’t believe that you can tell though.

Easiest way would be to run them separately. Then you know they’re either all cpu or all gpu. Unless I’m interpreting the api response I correctly.

yeah, a few people have said running separate instances is better than running them all together.   I have yet to do my own personal testing on that though.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: impynick on August 06, 2018, 09:02:50 AM
Hello JK,

I just wanted to let you know I actually compiled 2.4.7 and running it with a 1080ti no problem.

I know I dont have any post history but lmk if you would like to check out the miner. You really helped me out by compiling the earlier versions of XMRSTAK and would like to return the favor.

Of course I wont be offended if you decline, but the 1080 ti is working properly on XMR stak 2.4.7 that i compiled. Updated to most recent driver on windows 10 too.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: impynick on August 06, 2018, 11:32:06 PM
My 1080 ti is FE


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 07, 2018, 03:47:41 AM
Hello JK,

I just wanted to let you know I actually compiled 2.4.7 and running it with a 1080ti no problem.

I know I dont have any post history but lmk if you would like to check out the miner. You really helped me out by compiling the earlier versions of XMRSTAK and would like to return the favor.

Of course I wont be offended if you decline, but the 1080 ti is working properly on XMR stak 2.4.7 that i compiled. Updated to most recent driver on windows 10 too.

its not about version;  its about config is my guess......  pm me a mega link to it;  and as well;  include your nvidia.txt with it.

Thanks!


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: Bearier on August 08, 2018, 08:32:10 AM
Hello! Do you have a solution to this problem?
http://i103.fastpic.ru/big/2018/0808/41/de7964c418b2737019282222e62d8941.jpeg


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 08, 2018, 09:31:35 AM

yes, its telling you to modify threads in the nvidia.txt file....  id suggest you visit the fierce-xmrstak gitbhub for extra documentation, but it should be pretty self-explanitory when you open the file.

if you don't know which card is causing the error;  comment out one card at a time in the file, and you'll deduce which needs modified.  At this point; it could be one or all of them.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 09, 2018, 01:38:06 PM
I read some of the xmr stak topic and I saw that they got 800-1000h in their 570 4gb and 8gb cards, I wonder why I only got 600h plus,  I am new to cryptonight algo, since I started mining, I only mined eth and other eth base algo.. can somebody here share some advice below is my settings in amd.txt Is there any way to increase my hashrate.. Thanks in advance to those who are willing to help..  ;)  ;)

HASHRATE REPORT - AMD
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |  655.1 |  654.4 |  654.7 |  1 |  672.9 |  673.0 |  672.9 |
|  2 |  675.8 |  675.5 |  675.4 |  3 |  682.3 |  682.4 |  682.3 |
|  4 |  683.4 |  683.2 |  683.1 |  5 |  677.3 |  677.5 |  677.5 |
|  6 |  633.4 |  633.5 |  633.9 |  7 |  652.2 |  654.4 |  655.0 |
|  8 |  655.4 |  655.1 |  655.4 |  9 |  654.8 |  654.8 |  654.5 |
| 10 |  672.3 |  671.8 |  671.8 | 11 |  652.7 |  654.7 |  654.5 |
Totals (AMD):  7967.6 7970.4 7970.8 H/s
-----------------------------------------------------------------
Totals (ALL):   7967.6 7970.4 7970.8 H/s
Highest:  7977.6 H/s

List of 12 cards accordingly

0. RX 570 4GB
1. RX 570 8GB
2. RX 570 8GB
3. RX 570 8GB
4. RX 570 8GB
5. RX 570 8GB
6. RX 570 8GB
7. RX 570 4GB
8. RX 570 4GB
9. RX 570 4GB
10. RX 570 8GB
11. RX 570 4GB

Code:
// gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 0,
    "intensity" : 896, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 1,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 2,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 3,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 4,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 5,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 6,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 7,
    "intensity" : 896, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 8,
    "intensity" : 896, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 9,
    "intensity" : 896, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 10,
    "intensity" : 1000, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 11,
    "intensity" : 896, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: gambera on August 16, 2018, 03:54:18 AM
I read some of the xmr stak topic and I saw that they got 800-1000h in their 570 4gb and 8gb cards, I wonder why I only got 600h plus,  I am new to cryptonight algo, since I started mining, I only mined eth and other eth base algo.. can somebody here share some advice below is my settings in amd.txt Is there any way to increase my hashrate.. Thanks in advance to those who are willing to help..  ;)  ;)

HASHRATE REPORT - AMD
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |  655.1 |  654.4 |  654.7 |  1 |  672.9 |  673.0 |  672.9 |
|  2 |  675.8 |  675.5 |  675.4 |  3 |  682.3 |  682.4 |  682.3 |
|  4 |  683.4 |  683.2 |  683.1 |  5 |  677.3 |  677.5 |  677.5 |
|  6 |  633.4 |  633.5 |  633.9 |  7 |  652.2 |  654.4 |  655.0 |
|  8 |  655.4 |  655.1 |  655.4 |  9 |  654.8 |  654.8 |  654.5 |
| 10 |  672.3 |  671.8 |  671.8 | 11 |  652.7 |  654.7 |  654.5 |
Totals (AMD):  7967.6 7970.4 7970.8 H/s
-----------------------------------------------------------------
Totals (ALL):   7967.6 7970.4 7970.8 H/s
Highest:  7977.6 H/s

List of 12 cards accordingly

0. RX 570 4GB
1. RX 570 8GB
2. RX 570 8GB
3. RX 570 8GB
4. RX 570 8GB
5. RX 570 8GB
6. RX 570 8GB
7. RX 570 4GB
8. RX 570 4GB
9. RX 570 4GB
10. RX 570 8GB
11. RX 570 4GB


I'm surprised that no one else answered your question. If you search online you'll find answers. Try running 2 GPU threads per card, example for GPU 0 and 1 (repeat for all of your cards):

Code:
{ "index" : 0, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },
{ "index" : 0, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },


{ "index" : 1, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },
{ "index" : 1, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: MagicSmoker on August 16, 2018, 10:02:44 AM
I read some of the xmr stak topic and I saw that they got 800-1000h in their 570 4gb and 8gb cards, I wonder why I only got 600h plus,  I am new to cryptonight algo, since I started mining, I only mined eth and other eth base algo.. can somebody here share some advice below is my settings in amd.txt Is there any way to increase my hashrate.. Thanks in advance to those who are willing to help..  ;)  ;)

Read more of this topic, then, because I just answered the same question on the previous page.

Short answer: lower the intensity to the 800 range, make sure it is an integer multiple of worksize (ie - divisible by 8 ) and double the bracketed entries that start with index for each card to run 2 threads.

EDIT - and I was responding to you that time as well?! Did you not understand what I wrote or did it not work for you or what?



Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 18, 2018, 02:38:02 AM
*deleted*

Start your own thread.  Do not post that here.



This thread is not for 4 post users to piggyback a potential piece of spyware/virus.


Its not you;  its the fact that nobody knows you and your true intentions.  I won't have that here; and you aren't the first one to have a build removed.

No hard feelings.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: nsummy on August 18, 2018, 02:59:34 AM
If you are going to provide this "service" for everyone, you should at least obey the GPL, fork this, and post the source code along with the binaries.   You cannot change the code and only provide binaries.

On a side note its kind of sad that there are so many people in this thread asking technical questions and reporting problems.  You get what you pay for.  Pay the minimal 2% to support the dev and post the issue on their github.  Its quite possible that any problem you are having is a bug in the software.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: impynick on August 18, 2018, 03:08:40 AM
Oh none taken at all. I wasn’t trying to really do anything but help. There’s nothing to “piggyback” especially since there’s no dev fee lol.  Sorry. But yeah 2.4.7 and 2.4.4 worked fine with the 1080. And compiling was fun. Can 2.4.4 mine RYO? Just wondering thanks again!



Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 18, 2018, 03:11:16 AM
Oh none taken at all. I wasn’t trying to really do anything but help. There’s nothing to “piggyback” especially since there’s no dev fee lol.  Sorry. But yeah 2.4.7 and 2.4.4 worked fine with the 1080. And compiling was fun. Can 2.4.4 mine RYO? Just wondering thanks again!



it looks like cryptonight-heavy was asses for 2.4.2/2.4.4 so i don't see why not.


Only small optimizations were made in the later versions.



Ive been busy setting up my machine for my .com, and getting it all configured.... havent stepped in to re-compile the newest source yet.

I plan to do it when the fork for CN7 is coded and released in xmrstak.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: MagicSmoker on August 20, 2018, 11:24:31 AM
If you are going to provide this "service" for everyone, you should at least obey the GPL, fork this, and post the source code along with the binaries.   You cannot change the code and only provide binaries.

Who's going to stop him? The open source software police? Interpol? The Avengers?



Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: Mattthev on August 20, 2018, 11:47:28 AM
If you are going to provide this "service" for everyone, you should at least obey the GPL, fork this, and post the source code along with the binaries.   You cannot change the code and only provide binaries.

Who's going to stop him? The open source software police? Interpol? The Avengers?
Well, downloading something that is open source without available source code is kinda dangerous always. I don't know this guy so he might be trustful. But there are also guys I think it was some russians, that they edited PBE 1.6 and it was stealing something or changing wallet address after copy paste or something like that. And believe me some of my customers also send ETH to different wallets even in e-mails and orders was my wallet due to that paste trojan or whatever is that.
Without source codes you can mine to OP wallet without knowing it... Not saying it does, but there is most likely something shady without any source codes released.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: MadKernel on August 20, 2018, 04:04:10 PM
If you are going to provide this "service" for everyone, you should at least obey the GPL, fork this, and post the source code along with the binaries.   You cannot change the code and only provide binaries.

Who's going to stop him? The open source software police? Interpol? The Avengers?


You can distribuite GPL binaries without source code, but accompanied with an offer to get the source code. The price of the source code cannot be  higher than the price of the binaries.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 21, 2018, 04:09:44 AM
If you are going to provide this "service" for everyone, you should at least obey the GPL, fork this, and post the source code along with the binaries.   You cannot change the code and only provide binaries.

On a side note its kind of sad that there are so many people in this thread asking technical questions and reporting problems.  You get what you pay for.  Pay the minimal 2% to support the dev and post the issue on their github.  Its quite possible that any problem you are having is a bug in the software.

if it had been requested;  it would have been provided.


All changes made were clearly noted.  so yes;  I have made the changes pretty damned available and apparent.  Nowhere in GPL does it require me to post to github or any specific location.



Chill the f out or be deleted.  pretty simple.   I don't have to deal with your BS at all.

As I said before:
If you don't trust me;  don't use it.

if fierce-uk had a problem with what I was doing;  he would contact me as its pretty easy.... and furthermore;  he wouldn't post the source with the ability to edit the devfee.


put away your internet warrior caps;  if you wanna go down that road;  I'll just continually delete every one of your posts.


this is ridiculous.   I flat out wont put up with it past this reply.  Say something again, and ill just delete all of your comments.    You have been warned.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: BigHarryArmsi on August 22, 2018, 05:04:35 AM
Hi, all. Does anyone know or want to volunteer how much power an AMD 580 8gb is consuming or a 580 8gb rig is drawing at the wall? I hear STAK is a low power miner and am very sensitive to wattage at the wall. Any help is appreciated.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: STSToken on August 22, 2018, 08:08:28 AM
Thanks for this.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 22, 2018, 07:35:16 PM
Hi, all. Does anyone know or want to volunteer how much power an AMD 580 8gb is consuming or a 580 8gb rig is drawing at the wall? I hear STAK is a low power miner and am very sensitive to wattage at the wall. Any help is appreciated.


IDK about low power;  it would take a BIOS flash and underclocking to get low consumption. 

I suggest peering over the configuration notes on github on getting the best performance out of it.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 23, 2018, 10:49:25 AM
I read some of the xmr stak topic and I saw that they got 800-1000h in their 570 4gb and 8gb cards, I wonder why I only got 600h plus,  I am new to cryptonight algo, since I started mining, I only mined eth and other eth base algo.. can somebody here share some advice below is my settings in amd.txt Is there any way to increase my hashrate.. Thanks in advance to those who are willing to help..  ;)  ;)

HASHRATE REPORT - AMD
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |  655.1 |  654.4 |  654.7 |  1 |  672.9 |  673.0 |  672.9 |
|  2 |  675.8 |  675.5 |  675.4 |  3 |  682.3 |  682.4 |  682.3 |
|  4 |  683.4 |  683.2 |  683.1 |  5 |  677.3 |  677.5 |  677.5 |
|  6 |  633.4 |  633.5 |  633.9 |  7 |  652.2 |  654.4 |  655.0 |
|  8 |  655.4 |  655.1 |  655.4 |  9 |  654.8 |  654.8 |  654.5 |
| 10 |  672.3 |  671.8 |  671.8 | 11 |  652.7 |  654.7 |  654.5 |
Totals (AMD):  7967.6 7970.4 7970.8 H/s
-----------------------------------------------------------------
Totals (ALL):   7967.6 7970.4 7970.8 H/s
Highest:  7977.6 H/s

List of 12 cards accordingly

0. RX 570 4GB
1. RX 570 8GB
2. RX 570 8GB
3. RX 570 8GB
4. RX 570 8GB
5. RX 570 8GB
6. RX 570 8GB
7. RX 570 4GB
8. RX 570 4GB
9. RX 570 4GB
10. RX 570 8GB
11. RX 570 4GB


I'm surprised that no one else answered your question. If you search online you'll find answers. Try running 2 GPU threads per card, example for GPU 0 and 1 (repeat for all of your cards):

Code:
{ "index" : 0, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },
{ "index" : 0, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },


{ "index" : 1, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },
{ "index" : 1, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },

Thanks for noticing it too!  :D It took for almost weeks my question here is hang and no one try to answer.. Thanks dude i will try you config, and will reply you the result.

Again.. Thanks!


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 23, 2018, 11:36:09 AM
I read some of the xmr stak topic and I saw that they got 800-1000h in their 570 4gb and 8gb cards, I wonder why I only got 600h plus,  I am new to cryptonight algo, since I started mining, I only mined eth and other eth base algo.. can somebody here share some advice below is my settings in amd.txt Is there any way to increase my hashrate.. Thanks in advance to those who are willing to help..  ;)  ;)

HASHRATE REPORT - AMD
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |  655.1 |  654.4 |  654.7 |  1 |  672.9 |  673.0 |  672.9 |
|  2 |  675.8 |  675.5 |  675.4 |  3 |  682.3 |  682.4 |  682.3 |
|  4 |  683.4 |  683.2 |  683.1 |  5 |  677.3 |  677.5 |  677.5 |
|  6 |  633.4 |  633.5 |  633.9 |  7 |  652.2 |  654.4 |  655.0 |
|  8 |  655.4 |  655.1 |  655.4 |  9 |  654.8 |  654.8 |  654.5 |
| 10 |  672.3 |  671.8 |  671.8 | 11 |  652.7 |  654.7 |  654.5 |
Totals (AMD):  7967.6 7970.4 7970.8 H/s
-----------------------------------------------------------------
Totals (ALL):   7967.6 7970.4 7970.8 H/s
Highest:  7977.6 H/s

List of 12 cards accordingly

0. RX 570 4GB
1. RX 570 8GB
2. RX 570 8GB
3. RX 570 8GB
4. RX 570 8GB
5. RX 570 8GB
6. RX 570 8GB
7. RX 570 4GB
8. RX 570 4GB
9. RX 570 4GB
10. RX 570 8GB
11. RX 570 4GB


I'm surprised that no one else answered your question. If you search online you'll find answers. Try running 2 GPU threads per card, example for GPU 0 and 1 (repeat for all of your cards):

Code:
{ "index" : 0, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },
{ "index" : 0, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },


{ "index" : 1, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },
{ "index" : 1, "intensity" : 864, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },

Thanks for noticing it too!  :D It took for almost weeks my question here is hang and no one try to answer.. Thanks dude i will try you config, and will reply you the result.

Again.. Thanks!

Seems that there something wrong with my config, kindly check my config and tell me if Im doing it right.. My hashrate getting to low..

here's my config I don't know if I'm doing it right.

Code:
"gpu_threads_conf" : [
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 0,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 0,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 1,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 1,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },

Is it right?


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: MadKernel on August 23, 2018, 06:19:12 PM
Based on my esperiencies, the best intensity size is near values obtained using this formula: (num compute units-2) *16 that for a 570 card is 480. Try also 960 for 8gb cards.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 24, 2018, 03:59:43 AM
Based on my esperiencies, the best intensity size is near values obtained using this formula: (num compute units-2) *16 that for a 570 card is 480. Try also 960 for 8gb cards.


I am using a moded 570/580 and I got 30-31MH mining eth, but in this algo I only got 600H even I tried different intensity but the highest hash I get is 670H, I am currently using 997 intensity.. I will try yours.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 24, 2018, 03:15:47 PM
Seems that there something wrong with my config, kindly check my config and tell me if Im doing it right.. My hashrate getting to low..

here's my config I don't know if I'm doing it right.

Code:
"gpu_threads_conf" : [
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 0,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 0,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 1,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 1,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },

Is it right?

is your problem with loading errors?

Looks like formatting;  specifically the ], on the last line which is missing....


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 24, 2018, 03:26:17 PM
Seems that there something wrong with my config, kindly check my config and tell me if Im doing it right.. My hashrate getting to low..

here's my config I don't know if I'm doing it right.

Code:
"gpu_threads_conf" : [
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 0,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 0,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 1,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
{ "index" : 1,
    "intensity" : 864, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },

Is it right?

is your problem with loading errors?

Looks like formatting;  specifically the ], on the last line which is missing....

Can I post my config here, then if you don't mind, kindly edit it to the proper coding then I will copy it to my amd txt.. Is it okay dude?

Here's my whole config..

Code:
"gpu_threads_conf" : [
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 0,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 1,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 2,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 3,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 4,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 5,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 6,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 7,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 8,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 9,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 10,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 11,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },

],


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on August 24, 2018, 05:11:32 PM
*snip*

Code:
"gpu_threads_conf" : [
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 0,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 0,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 1,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 1,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 2,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 2,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 3,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 3,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 4,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 4,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 5,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 5,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 6,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 6,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 7,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 7,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 8,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 8,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 9,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 9,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 10,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 10,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 11,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 11,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },

],

just copy/paste to double the threads.

Its up to you to figure out any intensity or worksize changes.....  I don't have the hardware to test.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: john1010 on August 25, 2018, 01:02:55 AM
*snip*

Code:
"gpu_threads_conf" : [
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 0,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 0,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 1,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 1,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 2,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 2,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 3,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 3,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 4,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 4,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 5,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 5,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 6,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 6,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 7,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 7,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 8,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 8,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 9,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 9,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3712
  // compute units: 32
  { "index" : 10,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 10,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  // gpu: Ellesmere memory:3920
  // compute units: 32
  { "index" : 11,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },
  { "index" : 11,
    "intensity" : 997, "worksize" : 8,
    "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2,
    "comp_mode" : true
  },

],

just copy/paste to double the threads.

Its up to you to figure out any intensity or worksize changes.....  I don't have the hardware to test.

Thanks for your help, yeah that intensity running fine in my rig.. I will post an update of what the result I got.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: impynick on August 27, 2018, 10:48:53 PM
https://bitcointalk.org/index.php?topic=3370685.0

Hey JK, I know you have a 1080ti, I thought you and anyone else using the 1080ti find this useful

I used ethlargement on my 1080 ti (link above) and my hash rate when from 930 to 1070. Check it out lmk what you think.

I have pics of said hash rate as well if you want documentation. Just run it in the background of XMR Stak and thats it!

U should get around 10-20% increase. ONLY ON 1080TI

edit: I did upload my config to xmrstak.com so check it out if you'd like. It should be up in a day or two they usually review submissions first.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: impynick on October 16, 2018, 09:25:59 PM
Hi JK hope all is well; I just compiled 2.5 with VS17 and CUDA 10.

Guys just so you know compiling this miner isn't really difficult. You will learn alot just by compiling it yourself. I did this and I have 0 coding or programming experience.

https://github.com/fireice-uk/xmr-stak/blob/master/doc/compile_Windows.md

https://www.youtube.com/watch?v=8-V0eonlpD8

I used these as guides to compile. Anyways 2.5 is working but you will notice a slight drop in hash rate most likely due to the new algo. Make sure to update before 10/18!


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on October 17, 2018, 01:28:31 PM
Hi JK hope all is well; I just compiled 2.5 with VS17 and CUDA 10.

Guys just so you know compiling this miner isn't really difficult. You will learn alot just by compiling it yourself. I did this and I have 0 coding or programming experience.

https://github.com/fireice-uk/xmr-stak/blob/master/doc/compile_Windows.md

https://www.youtube.com/watch?v=8-V0eonlpD8

I used these as guides to compile. Anyways 2.5 is working but you will notice a slight drop in hash rate most likely due to the new algo. Make sure to update before 10/18!
Ahh, they finally released an update.... I've been waiting for this....

I have a separate machine on my main network now I can remote into and have a fresh start with installing VS and the toolkits; and it wont have bandwidth limits like I do at home.  Ill probably get on this soon.

Then the regular stripping of devfee addresses and setting value to 0.0 and compile.

I believe the original intent was Cuda 8.0, and i believe it produced the best hashrates... but i could be wrong.

Looks like I need to get on this tomorrow.  Ill be updating my personal miner with the official release for the short term.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on October 18, 2018, 07:10:17 AM
good news guys, it did compile this time.  I used a fresh new PC.  Everything went well.   Usual changes;  removed donate address and set amount to 0.0.


The not so good news is I compiled under Cuda 10.

Gonna need to update your video drivers most-likely.

I am downloading the updated video drivers at home right now.   Once I get the miner app confirmed mining on my 1080;  Ill upload to mega and update Post #1.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: impynick on October 18, 2018, 07:22:15 AM
Nice! Yeah I used cuda 10 as well. Good thing u waited i recompiled 2.5.1 this time luckily it took only 10 min.


If I run into any issues with my miner I have your's to fall back on :D


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: JaredKaragen on October 18, 2018, 08:01:33 AM
Nice! Yeah I used cuda 10 as well. Good thing u waited i recompiled 2.5.1 this time luckily it took only 10 min.


If I run into any issues with my miner I have your's to fall back on :D

Yep =)

Went smoothly.  May have something to do with my laptop I had used previously.  The laptop I used this time took ~17 min to compile... but its also running a steamcmd server.... lol.


First post updated.  New version works.


Title: Re: XMR-stak-JK 2.4.4 Compiled with no devfee
Post by: Hamliss on October 18, 2018, 08:35:14 AM
Hi JK hope all is well; I just compiled 2.5 with VS17 and CUDA 10.

Guys just so you know compiling this miner isn't really difficult. You will learn alot just by compiling it yourself. I did this and I have 0 coding or programming experience.

https://github.com/fireice-uk/xmr-stak/blob/master/doc/compile_Windows.md

https://www.youtube.com/watch?v=8-V0eonlpD8

I used these as guides to compile. Anyways 2.5 is working but you will notice a slight drop in hash rate most likely due to the new algo. Make sure to update before 10/18!
Ahh, they finally released an update.... I've been waiting for this....

I have a separate machine on my main network now I can remote into and have a fresh start with installing VS and the toolkits; and it wont have bandwidth limits like I do at home.  Ill probably get on this soon.

Then the regular stripping of devfee addresses and setting value to 0.0 and compile.

I believe the original intent was Cuda 8.0, and i believe it produced the best hashrates... but i could be wrong.

Looks like I need to get on this tomorrow.  Ill be updating my personal miner with the official release for the short term.

Thanks for all the efforts. You said you comipled with CUDA, does the miner also work with AMD cards properly?


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: JaredKaragen on October 18, 2018, 09:15:40 AM
Yeah, AMD backend is still as per normal from what I can tell.    Its working with the RX560 in my test rig consisting of a number of mixed AMD/Nvidia/legacy.

If you have any amd issues, its most likely driver related;  and I would recommend to read the alerts on the fireice-uk github at the source about the driver issues people have had;  I saw the alert when I was reading the release notes before compiling.




For those of you whom can't/won't update driver for some reason; you can download the official release from github, and copy the xmrstak_cuda_backend.dll file, but rename it to xmrstak_cuda_backend_cuda9_2.dll and put it in the folder with my release.   This will give you library support for the older drivers/devices as it was with 2.4.x

I had to do this because if I install nvidia driver 400+, my older legacy devices (GTX 5-series and older) will not load a driver in windows.   The require the 3xx version of the nvidia driver to work....   This copying of fireice-uk's cuda DLL is a good alternative.


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: MagicSmoker on October 18, 2018, 03:04:12 PM
I just got 2.5.1-JK running on two different rigs and it was painless for one and quite painful for the other. The painless one is my "daily driver" desktop with a single RX 570 and Ryzen 5 1600, Windows 10 1803 (ie - just got the fall update), AMD 18.5.1 driver, and MSI AB 4.4.0 set to -25% power, 1200 core and 1900 mem.

The problematic rig is 4x RX 560 2GB on an Onda D1800 6-GPU mining mobo running Windows 10 1709 (ie - NOT updated), AMD 18.6.1 (ie - newer driver) and uses OverDrivenTool to setup the GPUs rather than MSI AB. This rig kept crashing either during the bin file compiling or as soon as it logged into the pool. After wrestling with different things for an hour I finally tried bumping up all the voltages in the mem and core clock profiles by 25mV and that stopped the crashing. Of course, that increases the power consumption slightly, but the hashrate is otherwise the same (this is mining Lethean (formerly IntenseCoin), which is still running what is essential CNv7).



Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: Joz76 on October 18, 2018, 07:50:17 PM
Hi, I'm new with XMR-stack, plz help with the config. I want to mine with CPU and join to nanopool, but cant connect to pool with this error:

Fast-connecting to xmr-eu1.nanopool.org:14433 pool ...
Pool xmr-eu1.nanopool.org:14433 connected. Logging in...
SOCKET ERROR - [xmr-eu1.nanopool.org:14433] RECEIVE error: socket closed

My bat file is this:
xmr-stak.exe -o xmr-eu1.nanopool.org:14433 -u myaddress.cpu_gamer/joz976@gmail.com --currency monero -i 0 -p "" -r "" --noNVIDIA --noUAC

and this is my config file:
/ generated by xmr-stak/2.5.1/4e72408ff/master/win/nvidia-amd-cpu/20

/*
 * Network timeouts.
 * Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
 * sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
 * nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
 * long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
 * server usually takes to process our calls.
 *
 * call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
 * retry_time   - How long should we wait before another connection attempt.
 *                Both values are in seconds.
 * giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
 *                don't mine while the connection is lost, so your computer's power usage goes down to idle.
 */
"call_timeout" : 10,
"retry_time" : 30,
"giveup_limit" : 0,

/*
 * Output control.
 * Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
 * really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
 * performance monitors, there is very little reason to spew out pages of text instead of concise reports.
 * Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
 *
 * verbose_level - 0 - Don't print anything.
 *                 1 - Print intro, connection event, disconnect event
 *                 2 - All of level 1, and new job (block) event if the difficulty is different from the last job
 *                 3 - All of level 1, and new job (block) event in all cases, result submission event.
 *                 4 - All of level 3, and automatic hashrate report printing
 *
 * print_motd    - Display messages from your pool operator in the hashrate result.
 */
"verbose_level" : 3,
"print_motd" : true,

/*
 * Automatic hashrate report
 *
 * h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
 *                This option has no effect if verbose_level is not 4.
 */
"h_print_time" : 60,

/*
 * Manual hardware AES override
 *
 * Some VMs don't report AES capability correctly. You can set this value to true to enforce hardware AES or
 * to false to force disable AES or null to let the miner decide if AES is used.
 *
 * WARNING: setting this to true on a CPU that doesn't support hardware AES will crash the miner.
 */
"aes_override" : null,

/*
 * LARGE PAGE SUPPORT
 * Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
 * but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
 * meant as a backup, you won't get stellar results there. If you are running into trouble, especially
 * on Windows, please read the common issues in the README and FAQ.
 *
 * By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
 * You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
 *
 * 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
 * 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
 * 3. Expand Security Settings, and then expand Local Policies.
 * 4. Select the User Rights Assignment folder.
 * 5. The policies will be displayed in the details pane.
 * 6. In the pane, double-click Lock pages in memory.
 * 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
 * 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
 * 9. Reboot for change to take effect.
 *
 * Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
 * to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
 *
 *
 * use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
 * always  - Don't even try to use large pages. Always use slow memory.
 * warn    - We will try to use large pages, but fall back to slow memory if that fails.
 * never   - If we fail to allocate large pages we will print an error and exit.
 */
"use_slow_memory" : "warn",

/*
 * TLS Settings
 * If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
 * to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
 *
 * tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
 */
"tls_secure_algo" : true,

/*
 * Daemon mode
 *
 * If you are running the process in the background and you don't need the keyboard reports, set this to true.
 * This should solve the hashrate problems on some emulated terminals.
 */
"daemon_mode" : false,

/*
 * Output file
 *
 * output_file  - This option will log all output to a file.
 *
 */
"output_file" : "",

/*
 * Built-in web server
 * I like checking my hashrate on my phone. Don't you?
 * Keep in mind that you will need to set up port forwarding on your router if you want to access it from
 * outside of your home network. Ports lower than 1024 on Linux systems will require root.
 *
 * httpd_port - Port we should listen on. Default, 0, will switch off the server.
 */
"httpd_port" : 0,

/*
 * HTTP Authentication
 *
 * This allows you to set a password to keep people on the Internet from snooping on your hashrate.
 * Keep in mind that this is based on HTTP Digest, which is based on MD5. To a determined attacker
 * who is able to read your traffic it is as easy to break a bog door latch.
 *
 * http_login - Login. Empty login disables authentication.
 * http_pass  - Password.
 */
"http_login" : "",
"http_pass" : "",

/*
 * prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
 *               This setting will only be needed in 2020's. No need to worry about it now.
 */
"prefer_ipv4" : true,


Before mxr-stak i use Claymore CPU miner 4.0, but claymore dont update to the new algo :-(


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: impynick on October 18, 2018, 08:26:57 PM
try using port 14444


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: Joz76 on October 18, 2018, 08:36:33 PM
try using port 14444

It works, thanks!


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: JaredKaragen on October 18, 2018, 11:41:21 PM
try using port 14444

yes;  I myself am having issues connecting to nanopool with the TLS settings, and instead am having to choose the standard stratum port for more reliable connections.

Other than that, the switchover seems to be going well.

Look at the network hashrate;  Just on nanopool: from 138Gh to just 33Gh after the fork.....   Shows there are some damned greedy people out there.

Hope they like their bricks.


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: STT on October 19, 2018, 12:45:44 AM
Greed is no surprise, people will just mine whatever makes them the most returns.    Alot of them dont have a choice because the income is required pay off the asset cost of the hardware.   Cant really expect any different really, usually evens out in the end depending on which path is more useful to society overall


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: Efemen on October 21, 2018, 06:07:47 PM
JK, what is your 1080Ti speed for the V8 and the power consumption?


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: JaredKaragen on October 22, 2018, 10:43:49 AM
JK, what is your 1080Ti speed for the V8 and the power consumption?

I have yet to run it on a 1080ti, or hook a power meter up....   I suggest give it a go and share results if anyone has them.   As well as the gpu threads/intensity settings they used =)


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: MagicSmoker on October 23, 2018, 03:36:38 PM
Well, I have to amend my earlier comments about it being painless switching over to 2.5.1... The CN coin I mine - LTHN - just switched to CNv8 and now I am dealing with unrelenting driver and system crashes. I just DDU'ed the 18.5.1 driver and installed/pixel-patched 18.6.1 to no avail. I've also bumped up the core/mem voltages to as high as they were stock (ie - no power saving) and that doesn't seem to help, either.

So I next decided to try SRBMiner and it is crashing the driver, too. I'll keep plugging along for another hour or so, but after that I am just going to stop mining completely.

UPDATE: in a fit of pique I deleted the amd.txt file for both rigs and let xmr-stak automatically generate them. Hashrate is depressingly low - 1020-1060H/s for the RX 570 + Ryzen 5 1600 system (previously ~1180H/s), and <1600H/s for the 4x RX 560 system (previously ~1900H/s), but at least it isn't crashing anymore (and I hope I didn't just jinx myself...).




Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: JaredKaragen on October 24, 2018, 01:05:28 AM
Well, I have to amend my earlier comments about it being painless switching over to 2.5.1... The CN coin I mine - LTHN - just switched to CNv8 and now I am dealing with unrelenting driver and system crashes. I just DDU'ed the 18.5.1 driver and installed/pixel-patched 18.6.1 to no avail. I've also bumped up the core/mem voltages to as high as they were stock (ie - no power saving) and that doesn't seem to help, either.

So I next decided to try SRBMiner and it is crashing the driver, too. I'll keep plugging along for another hour or so, but after that I am just going to stop mining completely.

UPDATE: in a fit of pique I deleted the amd.txt file for both rigs and let xmr-stak automatically generate them. Hashrate is depressingly low - 1020-1060H/s for the RX 570 + Ryzen 5 1600 system (previously ~1180H/s), and <1600H/s for the 4x RX 560 system (previously ~1900H/s), but at least it isn't crashing anymore (and I hope I didn't just jinx myself...).




yeah with the upgrade, all the .txt files need to be re-generated (has something to do with formatting and variable fillout for the new variables stored in the file).

My GTX470 is no longer "stable" enough for mining CNv8.   After 4-24 hours, it will cause a cuda crash in the miner.   After removing it from that test rig, no issues.  Odds are that it was just running to hard for its cooling capability;  remember, the 4-series cards were the most power hungry and hottest of any other Nvidia card ever made.


Hashrate seems to be minus 1/4-1/3 or so compared to cnv7 (accounting for my 470 when it was plugged in as well).   So far, no issues with the rx560.



It only made sense that things went the way they did (more power draw, harder on hardware, etc), because its the only way to overwhelm the FPGAs.   They can only have so much responsiveness, and signal timing across a complex FPGA configuration can be quite a chore.    Ive been doing my research and learning on how FPGA's are programmed and work recently;  and.... well, its not an easy task.    My first project personally will probably be making some sort of RISC cpu (maybe a V) on a FPGA and go from there.

notice many cn7 coins raising in value now;    the mass-FPGA holders are probably doing what it takes to squeeze every little pinch out of cn7 that they can before others catch on and they get dumped down to a realistic value... same thing happened during the cn7 swap.


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: MagicSmoker on October 24, 2018, 11:21:42 AM
...
UPDATE: in a fit of pique I deleted the amd.txt file for both rigs and let xmr-stak automatically generate them. Hashrate is depressingly low - 1020-1060H/s for the RX 570 + Ryzen 5 1600 system (previously ~1180H/s), and <1600H/s for the 4x RX 560 system (previously ~1900H/s), but at least it isn't crashing anymore (and I hope I didn't just jinx myself...).

yeah with the upgrade, all the .txt files need to be re-generated (has something to do with formatting and variable fillout for the new variables stored in the file).
...
Hashrate seems to be minus 1/4-1/3 or so compared to cnv7 (accounting for my 470 when it was plugged in as well).   So far, no issues with the rx560.

I'm still trying to dial everything in with respect to stability and hashrate but as of now I have gone back to 2 threads on the RX 560 rig, using all the other auto-generated parameters except reducing the intensity to less than half what was specified for 1 thread operation (e.g. - 768 for 1 thread goes to 376 for 2 threads). Right now the 4x rig is doing a little over 1800H/s so a massive improvement from the <1600H/s I was getting before! However, I just made this change so now I need to see if it remains stable as I was still having problems with the 1 thread/768 hashrate config (e.g. - hashrate dropped from 400 to 300 on one of the cards sometime over the night). I'm still also still running the RX 570 system with a single thread, worksize of 8, and 768 intensity for now, mainly because I want to see how the other rig behaves before wasting more time fiddling with this one, but I suspect I will be doing the same tweak in a few hours.


It only made sense that things went the way they did (more power draw, harder on hardware, etc), because its the only way to overwhelm the FPGAs. ...

Totally agree - I have slowly but surely come around to the idea that it is the energy cost that determines how secure a network is to the first degree, not the absolute hashrate or cost of the mining hardware, per se. One of the coins I was an early supporter of that remained on the original CN algo (DERO) has a network hashrate in the range of 400-500MH/s which works out to around 2000 ASICs and 1.2MW total power draw. Prior to being ASIC'ed it had a network hashrate of around 4MH/s which works out to ~5300 RX 570 GPUs drawing ~800kW of power; hardly an improvement in network security, really, at the cost of alienating a massive number of previously loyal GPU and CPU miners, but I digress...


UPDATE: Hashrate dropped on one of the RX 560 (not the same one) yet again, then the display driver crashed so I decided to DDU 18.6.1 and install 18.5.1, then pixel patch and set all the cards to compute mode. I also stopped using OverDrivenTool and switched over to MSI AB, as v4.5.0 is once again able to handle more than 3 AMD GPUs. I have core set to 1200, mem set to 1900, power limit set to -20%, no change as of yet to core voltage, and total draw is at an unhealthy 375W with hashrate at 1740H/s. So a slight drop in hashrate, a rather higher increase in power draw, but if it's more stable I'll consider that a fair trade overall.

UPDATE 2: Well, I finally gave up on xmr-stak on the 4x RX 560 rig because it kept losing hashrate on one card then outright crashing the driver if I ignored that long enough. Even though I had no luck with SRBMiner 1.6.8 before, I decided to give it another go since I downgraded the driver to 18.5.1 and whaddyaknow, it now works. It's only been running about 10 minutes so far, but delivering a fairly consistent 1775H/s at 356W; so, a little better hashrate and a little lower power draw. Neither are enough of an improvement to justify the 0.85% dev fee, but if it can stay up for longer than 4 hours without needing a reboot then that will be worth the fee to me. I'd like to stick with xmr-stak on both my rigs, but v2.5.1 clearly needs some bug-fixes and/or additional tweaking.



Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: Umister on October 27, 2018, 10:02:35 AM
The XMR-stak 2.5.2 is out. Will you do a compilaiton? Thanks in advance.


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: MagicSmoker on October 27, 2018, 10:49:21 AM
The XMR-stak 2.5.2 is out. Will you do a compilaiton? Thanks in advance.

Nobody likes a nag. Thanks in arrears.



Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: JaredKaragen on October 30, 2018, 01:57:43 AM
The XMR-stak 2.5.2 is out. Will you do a compilaiton? Thanks in advance.

Nobody likes a nag. Thanks in arrears.



lol.


lemme look at the release notes and if its worth going through the rigmarole.....   and at first glance, its a nvidia patch.


Ill try to compile in a little bit.   Hopefully the machine I used to compile last time has no issues.

*edit* compiling.   Seems like its working properly.... but ill know in ~10 min when the machine spits it out for me.  Once that happens, its off to mega and the link will be posted.


Title: Re: XMR-stak-JK 2.5.1 Compiled with no devfee 2018-10-18 Fork ready
Post by: JaredKaragen on October 30, 2018, 02:37:39 AM
Compile a success.  Uploaded and first post updated.


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: newmz on October 30, 2018, 06:54:33 AM
HEY Nvidia miners!

you should seriously check out CryptoDredge instead of XMR-Stak.

I am mining Loki (CN-heavy) with 1070s and I honestly get 20% more hahs rate. I am not the dev or getting paid or anything -  I just think you should check it out.


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: JaredKaragen on October 30, 2018, 10:22:42 AM
HEY Nvidia miners!

you should seriously check out CryptoDredge instead of XMR-Stak.

I am mining Loki (CN-heavy) with 1070s and I honestly get 20% more hahs rate. I am not the dev or getting paid or anything -  I just think you should check it out.

I know that the memory size was not the focus of the CNv8 changes...  Its all about creating functions that will overwhelm FPGA timing and circuit design... for starts....  Its a complex animal to get into.

But my main purpose for releasing/compiling and pushing xmr-stak specifically:  
1) Ive been trying to keep a no devfee miner app available specifically for monero.
2) I understand the code;  the cpp files and their uses.  I have edited them enough now over enough releases;  I get it.  Finally.
3) The source is 100% open and free.
4) less "fluff" associated with having many algos and functions that 99% of people wont use.  Most people who mine CN coins, only mine CN coins.... and would prefer a more optimized app for all of the the others individually.

I can see what angle you are coming from;  but I think you are missing the fact that you can use a cuda 8.0 library when compiling (or replacing my cuda 10 .dll from a separate compilation as I have mentioned in previous posts) and then you would not have to worry about the limits associated with cuda 10.  In response to your other post in another thread (i research shills in this thread before deleting, and you cut it under the wire ;):  The drivers are cuda backwards compatible (for game compatibility sake in the future for starts) and updating the driver;  is a good thing.  I have yet to have any issues with my 1070 or 1080.  
Only with one game, and one driver version did I have to rollback;  but that was only temporary until the game fixed its bug.

I do 100% understand the power limit you want to set for yourself;  but many people don't set mining limits just based on individual coin power draws;  if they aren't mining to sell immediately.

The official release from githib has: xmrstak_cuda_backend.dll    Just rename it to xmrstak_cuda_backend_9_2.dll and plop it into the folder with my release next to, or in place of my DLL.  See what it does.   Also;  you can just try replacing the file altogether: xmrstak_cuda_backend.dll and it shouldn't have cuda10 libs at the point.     I believe it chooses the cuda DLL based on what driver you have installed;  so if it still tries to load under cuda10 even though you added the cuda8/9 dll's, just replace the file instead of adding along side and it will force it.    I have it added alongside in my personal rigs so that my older generation cards can work alongside my current gen cards in the same machines.


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: JaredKaragen on November 04, 2018, 01:33:20 PM
Ok, so I finally got off my ass and went in and optimized my cards for what I could.

Made my previously ~890H/sec machine into a 1296H/sec machine.... no overclocks or any special configs;  Just modifying the threads, etc.  (poolside i'm seeing 1200-1600h/sec, which is the amount I had on cn7;  Which makes me wonder what it would have been on cn7 if i had done this earlier)


http://www.xmrstak.com   has countless user-submitted configs to give you an idea of what you need to do.  Just compare others' settings to see.      It seems that if I attempt a bios mod on the Rx560 I have, I could go up 30% in hashrate;  but I am not the type of user who does this;  even though I know how to accomplish it and have done it to cards before....   Since my business model isn't based around pinching every penny, or the absolute most efficient;  and the fact that this RX card is not my own as it was graciously lent to me by a fellow board member;  I doubt Ill be doing the bios mod....

But I highly suggest letting the autoconfigs happen, note the hashrates per card, then disable all but one and start trimming the values individually and doing tests;  it's worth the 10-30 min spent.   You can get quite a bump like I did from my 1070; went from ~420H/sec to ~588H/sec with very little effort.  I don't think ill tune it to get the highest possible, this was good enough for me.


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: NachoLibre69 on November 18, 2018, 02:41:47 PM
Hello!

Would really appreciate if you found the time to compile the latest 2.6.0 release for us .

Thank you in advance!


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: impynick on November 18, 2018, 11:27:43 PM
I compiled 2.6 already. Its more of an optimization for cnheavy. Didnt notice any difference on my nvidia or amd card on v8 ONLY.


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: twotwosix on November 19, 2018, 09:38:27 AM
Ok, so I finally got off my ass and went in and optimized my cards for what I could.

Made my previously ~890H/sec machine into a 1296H/sec machine.... no overclocks or any special configs;  Just modifying the threads, etc.  (poolside i'm seeing 1200-1600h/sec, which is the amount I had on cn7;  Which makes me wonder what it would have been on cn7 if i had done this earlier)


http://www.xmrstak.com   has countless user-submitted configs to give you an idea of what you need to do.  Just compare others' settings to see.      It seems that if I attempt a bios mod on the Rx560 I have, I could go up 30% in hashrate;  but I am not the type of user who does this;  even though I know how to accomplish it and have done it to cards before....   Since my business model isn't based around pinching every penny, or the absolute most efficient;  and the fact that this RX card is not my own as it was graciously lent to me by a fellow board member;  I doubt Ill be doing the bios mod....

But I highly suggest letting the autoconfigs happen, note the hashrates per card, then disable all but one and start trimming the values individually and doing tests;  it's worth the 10-30 min spent.   You can get quite a bump like I did from my 1070; went from ~420H/sec to ~588H/sec with very little effort.  I don't think ill tune it to get the highest possible, this was good enough for me.

Can you compile 2.6.0 I would greatly appreciate it


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: JaredKaragen on November 19, 2018, 10:04:40 AM
Ok, so I finally got off my ass and went in and optimized my cards for what I could.

Made my previously ~890H/sec machine into a 1296H/sec machine.... no overclocks or any special configs;  Just modifying the threads, etc.  (poolside i'm seeing 1200-1600h/sec, which is the amount I had on cn7;  Which makes me wonder what it would have been on cn7 if i had done this earlier)


http://www.xmrstak.com   has countless user-submitted configs to give you an idea of what you need to do.  Just compare others' settings to see.      It seems that if I attempt a bios mod on the Rx560 I have, I could go up 30% in hashrate;  but I am not the type of user who does this;  even though I know how to accomplish it and have done it to cards before....   Since my business model isn't based around pinching every penny, or the absolute most efficient;  and the fact that this RX card is not my own as it was graciously lent to me by a fellow board member;  I doubt Ill be doing the bios mod....

But I highly suggest letting the autoconfigs happen, note the hashrates per card, then disable all but one and start trimming the values individually and doing tests;  it's worth the 10-30 min spent.   You can get quite a bump like I did from my 1070; went from ~420H/sec to ~588H/sec with very little effort.  I don't think ill tune it to get the highest possible, this was good enough for me.

Can you compile 2.6.0 I would greatly appreciate it

Looks definitely worth doing.

It will be compiled with cuda 10; and the recommended blockchain SDK version from fireice-uk's github instructions.

It could be tomorrow, it could be in a few days.   I have been in and out of it for a bit;  but ill try and get it done.


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: impynick on November 19, 2018, 07:43:48 PM
since updating ive been getting these errors on my 580.


  24 | AMD Invalid Result GPU ID 0      | 2018-11-19 09:31:03 |

24 times since yesterday! I might revert back to 2.5.2 if it keeps up.

on cryptonight v8


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: NachoLibre69 on November 19, 2018, 10:06:00 PM
since updating ive been getting these errors on my 580.


  24 | AMD Invalid Result GPU ID 0      | 2018-11-19 09:31:03 |

24 times since yesterday! I might revert back to 2.5.2 if it keeps up.

on cryptonight v8



Just revert to (AMD Driver)5.1 or 6.1. Anything above that gives errors.


Cheers!


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: JaredKaragen on November 19, 2018, 10:37:46 PM
since updating ive been getting these errors on my 580.


  24 | AMD Invalid Result GPU ID 0      | 2018-11-19 09:31:03 |

24 times since yesterday! I might revert back to 2.5.2 if it keeps up.

on cryptonight v8

I was about to say;  2.5.2 is the last version I have released;  so what are you using right now if not 2.5.2? lol


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: impynick on November 19, 2018, 11:09:21 PM
I compiled 2.6 on my own. Its giving me errors on my 580.

I am using blockchain drivers (17.xx) as adrenaline drivers (18.xx) was causing instabilities.

:D


Title: Re: XMR-stak-JK 2.5.2 Compiled with no devfee 2018-10-29 CNv8/CNv7
Post by: JaredKaragen on November 23, 2018, 03:03:11 AM
I compiled 2.6 on my own. Its giving me errors on my 580.

I am using blockchain drivers (17.xx) as adrenaline drivers (18.xx) was causing instabilities.

:D

2.6.0 compiled and released.

Let me know if there are any issues.

Same as before, compiled under Cuda 10, i suggest the developer's cuda libraries for older devices as noted in my other posts in this thread.


Enjoy.


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: The?DEvil on December 03, 2018, 06:36:38 PM
Can you pls compile it to "tar.gz" and upload? Thx a lot. I would try using it in HiveOS.


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: JaredKaragen on December 03, 2018, 07:02:52 PM
Can you pls compile it to "tar.gz" and upload? Thx a lot. I would try using it in HiveOS.

I suggest you follow the build instructions for linux;  I am only releasing binaries for windows.

Its much more straightforward to compile on linux, and all you need to do is edit donate-level.cpp for the donate percentage before compiling.


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: zenixchen on December 04, 2018, 08:53:20 AM
Help to compile XMR stak 2.7 0% fee, thanks


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: JaredKaragen on December 04, 2018, 09:57:31 PM
Help to compile XMR stak 2.7 0% fee, thanks

https://github.com/fireice-uk/xmr-stak

scroll down the readme.md, you will see "How to compile"


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: zenixchen on December 04, 2018, 11:16:17 PM
I have ,but I can't figure it out, sad..


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: duckietm on December 06, 2018, 03:02:35 PM
@JaredKaragen
Can you please compile this for me :) i have no clue how to ??? (Windows)


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: JaredKaragen on December 07, 2018, 03:47:57 PM
@JaredKaragen
Can you please compile this for me :) i have no clue how to ??? (Windows)
see page 1 for links.


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: impynick on December 07, 2018, 07:14:48 PM
I haven't had time to compile 2.7

Interesting they say its faster but idk


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: maximus63 on December 08, 2018, 09:13:22 AM
I haven't had time to compile 2.7

Interesting they say its faster but idk

Yes 2.7 faster then xmrig and srb


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: JaredKaragen on December 11, 2018, 04:26:58 AM
I haven't had time to compile 2.7

Interesting they say its faster but idk

Yes 2.7 faster then xmrig and srb


FYI;  2.7.1 compiled and uploaded.

See first page.


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: The?DEvil on December 14, 2018, 11:02:27 PM
Can you pls compile it to "tar.gz" and upload? Thx a lot. I would try using it in HiveOS.

I suggest you follow the build instructions for linux;  I am only releasing binaries for windows.

Its much more straightforward to compile on linux, and all you need to do is edit donate-level.cpp for the donate percentage before compiling.

I tried, but it's really out of my league... :'( So if you or anybody here gets around compiling it for linux, I think you could help a lot of folks like me... that are not on the level of self-compiling stuff and are running HiveOS, SimpleMiningOS or just their own Linux implementation. Thx


Title: Re: XMR-stak-JK 2.6.0 Compiled with no devfee 2018-11-22 CNv8/CNv7
Post by: JaredKaragen on December 15, 2018, 12:17:45 AM
Can you pls compile it to "tar.gz" and upload? Thx a lot. I would try using it in HiveOS.

I suggest you follow the build instructions for linux;  I am only releasing binaries for windows.

Its much more straightforward to compile on linux, and all you need to do is edit donate-level.cpp for the donate percentage before compiling.

I tried, but it's really out of my league... :'( So if you or anybody here gets around compiling it for linux, I think you could help a lot of folks like me... that are not on the level of self-compiling stuff and are running HiveOS, SimpleMiningOS or just their own Linux implementation. Thx

It's all outlined pretty well;  I am not sure what linux HiveOS is based off of, so you could try the ubuntu Tinycore method(s);  they install extras/compilers that may or may not be released with your os....  When you get errors;  search the strings returned from the errors;  find out whats missing; install/add, try again.

https://github.com/fireice-uk/xmr-stak/blob/master/doc/compile_Linux.md


Title: Re: XMR-stak-JK 2.7.1 Compiled with no devfee (Updated: 2018-12-10)
Post by: seobcn on January 25, 2019, 10:05:49 AM
Need help setting up the processor.

https://imgur.com/RWMQyM3  As you can see in the picture, 16 cores are working and not 32

on other coin mining (koto - cryply - .....) the processor runs at 100%

Help exploit the full potential of the processor.


Title: Re: XMR-stak-JK 2.7.1 Compiled with no devfee (Updated: 2018-12-10)
Post by: JaredKaragen on January 26, 2019, 02:27:36 AM
Need help setting up the processor.

https://imgur.com/RWMQyM3  As you can see in the picture, 16 cores are working and not 32

on other coin mining (koto - cryply - .....) the processor runs at 100%

Help exploit the full potential of the processor.


Look at "CPU threads conf" section.

notice every other core is being used.

Create the new entries for the missing cores.

It may or may not be more efficient.   My I3-6100 CPU only configures for 2 cores;  but it has 4 threads....   If I create the extra configs, it doesn't gain a noticeable amount of hashrate, and actually I get less performance on the GPU's in the system as a side effect.

I believe it has to do with the two threads being tied to each core;  thus 16 "cores" with 32 threads....  but im not sure about your processor, im just giving an example.  It may or may not increase or decrease your performance.


Title: Re: XMR-stak-JK 2.7.1 Compiled with no devfee (Updated: 2018-12-10)
Post by: AnonJunkie on January 30, 2019, 11:03:30 PM
can you compile for cuda 8 ? I got an old gaming laptop i want to mine to death but it seem to only like cuda 8


Title: Re: XMR-stak-JK 2.7.1 Compiled with no devfee (Updated: 2018-12-10)
Post by: JaredKaragen on February 02, 2019, 05:06:02 AM
can you compile for cuda 8 ? I got an old gaming laptop i want to mine to death but it seem to only like cuda 8

download the original executable package from the github repository.

see this link (https://bitcointalk.org/index.php?topic=3264773.msg47417932#msg47417932) for notes on adding those DLL files since they are compiled under Cuda 8.5 I believe.... check fireice's build notes.

The app checks for different versions of the libraries now; and they have appropriate filenames.  Should be straightforward.  LMK if you have trouble.   His DLL worked for my 4-series GTX cards.


Title: Re: XMR-stak-JK 2.7.1 Compiled with no devfee (Updated: 2018-12-10)
Post by: VasilyS on February 03, 2019, 08:23:31 AM
Good work! Thank you so much! This miner is the best for my R9 280. This GPU almost doesn't have profit, and additional gain thanks to removal of the fee is a good surprise!


Title: Re: XMR-stak-JK 2.7.1 Compiled with no devfee (Updated: 2018-12-10)
Post by: JaredKaragen on February 04, 2019, 03:17:23 AM
Good work! Thank you so much! This miner is the best for my R9 280. This GPU almost doesn't have profit, and additional gain thanks to removal of the fee is a good surprise!

yes; the constant disconnects and reconnects for the pool add up in lost time with no mining for either side.   And if your internet connection isn't the greatest, the effect is compounded.

I suggest if you like the app; that you donate to the creator instead of using the devfee method... its cleaner for both parties.


Title: Re: XMR-stak-JK 2.8.2 Compiled with no devfee (Updated: 2019-2-15)
Post by: JaredKaragen on February 15, 2019, 11:55:50 AM
Compiled and uploaded version 2.8.2.  For full release notes, please visit FireIce-UK's Github.

If you have issues with this version when upgrading from 2.7.x, delete your config files (.txt), and try again.


This version does not support the new upcoming fork of Monero;  the algo change has not been publicly released yet.  It does however support forks on other coins, as well as some new coins/algos.   Please see the github mentioned above for more info.


Title: Re: XMR-stak-JK 2.8.2 Compiled with no devfee (Updated: 2019-2-16)
Post by: JaredKaragen on February 16, 2019, 05:36:35 PM
Compiled and uploaded V 2.8.3;  same notes as previous post.


Title: Re: XMR-stak-JK 2.8.2 Compiled with no devfee (Updated: 2019-2-16)
Post by: anakbaru on March 02, 2019, 06:43:55 AM
how much RX 570 8 gb when mining alloy?


Title: Re: XMR-stak-JK 2.8.2 Compiled with no devfee (Updated: 2019-2-16)
Post by: Spill on March 03, 2019, 04:54:55 PM
HI sir when is this one good for the new fork  :) ?


Title: Re: XMR-stak-JK 2.8.2 Compiled with no devfee (Updated: 2019-2-16)
Post by: herrdrone on March 04, 2019, 12:02:16 AM
HI sir when is this one good for the new fork  :) ?

A new version was released today, early support for CN-R: https://github.com/fireice-uk/xmr-stak/releases/tag/2.9.0 (https://github.com/fireice-uk/xmr-stak/releases/tag/2.9.0)


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: JaredKaragen on March 04, 2019, 12:05:28 PM
Compiled and uploaded 2.9.0.  See release notes on github for more info.


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: kansv on March 05, 2019, 10:02:07 PM
Hi!
XMR-stak-JK 2.9.0 Compiled with no devfee - the file has been deleted.
Can you update the link ?


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: impynick on March 05, 2019, 11:34:22 PM
xmrig is faster on CPU's. Just a heads up. And its easier to compile than xmrstak :D


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: JaredKaragen on March 06, 2019, 05:32:09 AM
Hi!
XMR-stak-JK 2.9.0 Compiled with no devfee - the file has been deleted.
Can you update the link ?

link updated.  Sorry for the issue.

I missed some DLL files, and needed to re-upload the package;  I thought I had replaced the link; but apparently not.


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: solosequenosenada on March 07, 2019, 09:57:48 AM
The latest version doesn't work for me with my rx 470 rig. Earlier versions have always worked well for me.
What should I do? Maybe it's the version of the AMD driver?
I'm still using the blockchain version as I haven't noticed any performance increase in the new versions of the driver.

Thanks anyway for your work compiling without fee  ;)


[2019-03-07 10:56:16] : Error CL_INVALID_DEVICE when calling clCreateCommandQueueWithProperties.
[2019-03-07 10:56:16] : WARNING: AMD device not found
[2019-03-07 10:56:16] : WARNING: backend AMD (OpenCL) disabled.


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: bubaba on March 07, 2019, 07:58:26 PM
After first start i get this error.
"Cryptonight hash self-test failed. This might be caused by bad compiler optimizations."

whats wrong?

5vega rig, working fine with 2.5 until now, do i need to change smth?


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: JaredKaragen on March 07, 2019, 09:55:16 PM
The latest version doesn't work for me with my rx 470 rig. Earlier versions have always worked well for me.
What should I do? Maybe it's the version of the AMD driver?
I'm still using the blockchain version as I haven't noticed any performance increase in the new versions of the driver.

Thanks anyway for your work compiling without fee  ;)


[2019-03-07 10:56:16] : Error CL_INVALID_DEVICE when calling clCreateCommandQueueWithProperties.
[2019-03-07 10:56:16] : WARNING: AMD device not found
[2019-03-07 10:56:16] : WARNING: backend AMD (OpenCL) disabled.


https://github.com/fireice-uk/xmr-stak/issues/2271
Looks like 2.9.1 will have it fixed.... seems like a known issue being worked on.  some have success, others don't.  I am attempting a recompile with the changes noted in that issue; but i probably wont jump any further down the rabbit hole and just wait for V2.9.1+ if this recompile with the minor changes doesn't help.


After first start i get this error.
"Cryptonight hash self-test failed. This might be caused by bad compiler optimizations."

whats wrong?

5vega rig, working fine with 2.5 until now, do i need to change smth?

could be an issue with a system overclock;   those test functions do work and haven't changed since day one....  They pass on my machines.

could be you need to get your amd.txt from v 2.7.x/2.8.x, and copy the optimizations to the new amd.txt generated by 2.9.0;  so be sure you didnt copy your old .txt files;  you need to edit the new ones.

I had to let mine redo the nvidia and amd txt more than once for some reason.


My test rig:
B250D8P I3-6100 8Gb
GTX 1070, GTX 650Ti, RX560

I did update my video drivers to the current version for Nvidia because of the security bug that was found;  and I left my AMD blockchain drivers alone as its been since I installed the RX560.

Ill zip up and upload the whole folder including my configurations directly from that miner;  and post a link in a minute.  You can see if its any different for you.


I do suggest updating the nvidia drivers though;  the security bug is a real threat; as well as I think needing the updated driver is a reality (I did compile under CUDA 10)


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: JaredKaragen on March 07, 2019, 10:19:45 PM
Ill have the recompiled test version added to this reply once it finishes compiling and being uploaded.  Stay tuned.



*snip*
Here is the updated file: xmr-stak-JK-2.9.0-1.zip (https://mega.nz/#!sagGEQSB!4b80BCoGuMXWDi-XsF1IfN85ZKcoeHnfcDPcBErmjIw)
Be sure you have generated new .txt files for V 2.9.0.


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: dcrowson on March 07, 2019, 11:38:21 PM
2.10.0 is out - https://github.com/fireice-uk/xmr-stak/releases/tag/2.10.0

Dan


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: JaredKaragen on March 08, 2019, 01:07:59 AM
2.10.0 is out - https://github.com/fireice-uk/xmr-stak/releases/tag/2.10.0

Dan

Compiled and uploaded.


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: solosequenosenada on March 08, 2019, 08:22:51 AM
2.10.0 is out - https://github.com/fireice-uk/xmr-stak/releases/tag/2.10.0

Dan

Compiled and uploaded.

This version works well for me, thank you   :-*


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-04)
Post by: bubaba on March 10, 2019, 02:35:48 PM


After first start i get this error.
"Cryptonight hash self-test failed. This might be caused by bad compiler optimizations."

whats wrong?

5vega rig, working fine with 2.5 until now, do i need to change smth?

could be an issue with a system overclock;   those test functions do work and haven't changed since day one....  They pass on my machines.

could be you need to get your amd.txt from v 2.7.x/2.8.x, and copy the optimizations to the new amd.txt generated by 2.9.0;  so be sure you didnt copy your old .txt files;  you need to edit the new ones.

I had to let mine redo the nvidia and amd txt more than once for some reason.


My test rig:
B250D8P I3-6100 8Gb
GTX 1070, GTX 650Ti, RX560

I did update my video drivers to the current version for Nvidia because of the security bug that was found;  and I left my AMD blockchain drivers alone as its been since I installed the RX560.

Ill zip up and upload the whole folder including my configurations directly from that miner;  and post a link in a minute.  You can see if its any different for you.


I do suggest updating the nvidia drivers though;  the security bug is a real threat; as well as I think needing the updated driver is a reality (I did compile under CUDA 10)



I installed new cuda and affined the threads to one cpu-core, working now. Thx for the tip and your work  ;)


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-07)
Post by: dragonmike on March 10, 2019, 05:50:36 PM
So I've tried this on my "regular" GTX 1080's and I'm getting hashrates just below 700 per GPU if I use the automatically generated parameters and the ETHlargement pill on the new Cryptonight/r algo.

Has anybody got better results? Any recommendations for tweaked parameters? I've checked that XMR-Stak bench site but they've got very little results for 1080's...


Title: Re: XMR-stak-JK 2.9.0 Compiled with no devfee (Updated: 2019-3-07)
Post by: JaredKaragen on March 11, 2019, 03:17:48 AM
*snip*

I installed new cuda and affined the threads to one cpu-core, working now. Thx for the tip and your work  ;)


No prob, glad to help.

So I've tried this on my "regular" GTX 1080's and I'm getting hashrates just below 700 per GPU if I use the automatically generated parameters and the ETHlargement pill on the new Cryptonight/r algo.

Has anybody got better results? Any recommendations for tweaked parameters? I've checked that XMR-Stak bench site but they've got very little results for 1080's...

Thats about what I get on my reference style 1080.

you already checked my main recommendation: https://www.xmrstak.com/ (https://www.xmrstak.com/)

You can look up other users settings for optimizations;  I did that for mine and only had to trim a tiny bit on my 1070;  I just left my 1080 on auto since it rarely mines now and is in my daily use PC.

Look at any 1080 ones you see; as well as 1070;  they will probably be similar; just take into count when transposing the 1080 having ~8-10% more computing power.


Title: Re: XMR-stak-JK 2.10.1 Compiled with no devfee (Updated: 2019-3-12)
Post by: JaredKaragen on March 13, 2019, 02:08:35 AM
compiled and uploaded 2.10.1.  Many bugfixes in this release;  I suggest everyone update.


Title: Re: XMR-stak-JK 2.10.1 Compiled with no devfee (Updated: 2019-3-12)
Post by: JaredKaragen on March 13, 2019, 06:59:40 AM
compiled and uploaded 2.10.1.  Many bugfixes in this release;  I suggest everyone update.
when open xmr stak jk say's LIBEAY32.dll and SSLEAY32.dll missing.

Sorry;  forgot to include them.  updated the link on the main page with a new file.


Title: Re: XMR-stak-JK 2.10.1 Compiled with no devfee (Updated: 2019-3-12)
Post by: JaredKaragen on March 16, 2019, 12:38:02 PM
*snip*

I deleted your post;  as it contained links and advertisements that are unrelated to my thread 100%.  This makes me think you are spamming on this website and potentially posting useless content since your post was 100% out of context of this thread; set aside the only correlation that my thread is about a specific build of xmr-stak.  You arent even sharing my build; but in fact one with a reduced devfee that is most likely redirected to your personal account.

To put it simply: I do not know why you posted here, or how it even pertained to this thread.   Please do not do this on bitcointalk.  Its bad manners.


Title: Re: XMR-stak-JK 2.10.1 Compiled with no devfee (Updated: 2019-3-12)
Post by: kopija on March 16, 2019, 03:53:29 PM
Sorry for being slightly OT, first time Monero miner.
Looking at XMR-Stak benchmarks page for Nvidias, it seems to me that the same OC method that works best for ethash is also best for cryptnonight: maximum memory OC and minimum core.
So something like 80PL, +700 memory and -100 core would be best?
Thanks.


Title: Re: XMR-stak-JK 2.10.1 Compiled with no devfee (Updated: 2019-3-12)
Post by: solosequenosenada on March 16, 2019, 06:21:54 PM
https://github.com/fireice-uk/xmr-stak/releases/tag/2.10.2   ::)

This release fixes a memory leak in the OpenCL (AMD) backend if cryptonight_r is mined which filled the full main memory and crashed the miner after a few hours.


Title: Re: XMR-stak-JK 2.10.1 Compiled with no devfee (Updated: 2019-3-12)
Post by: BroganBloodstone on March 16, 2019, 09:52:45 PM
I am able to compile just fine with a Nvidia GPU, but I get errors doing it with an AMD GPU. It seems to still want CUDA according to the error message.

What exactly do you have to do differently when compiling with an AMD GPU or even just using the CPU?


Title: Re: XMR-stak-JK 2.10.1 Compiled with no devfee (Updated: 2019-3-12)
Post by: JaredKaragen on March 17, 2019, 02:24:40 AM
I am able to compile just fine with a Nvidia GPU, but I get errors doing it with an AMD GPU. It seems to still want CUDA according to the error message.

What exactly do you have to do differently when compiling with an AMD GPU or even just using the CPU?

see build notes on github for compiling using --flags to disable options....   best bet i can give you.


Did you follow the instructions for being able to compile for openCL?  Install blockchain drivers/SDK, etc?

*note*  2.10.2 is compiling, I will have it uploaded when its finished.


Title: Re: XMR-stak-JK 2.10.2 Compiled with no devfee (Updated: 2019-3-16)
Post by: JaredKaragen on March 17, 2019, 03:02:25 AM
Compiled and uploaded version 2.10.2.


Title: Re: XMR-stak-JK 2.10.2 Compiled with no devfee (Updated: 2019-3-16)
Post by: dcrowson on March 17, 2019, 07:58:07 PM
Just a heads up that I found 2.10.1 to be stable with my AMD Radeon RX580 cards but 2.10.2 wasn't.

Dan


Title: Re: XMR-stak-JK 2.10.2 Compiled with no devfee (Updated: 2019-3-16)
Post by: JaredKaragen on March 18, 2019, 02:20:05 AM
Just a heads up that I found 2.10.1 to be stable with my AMD Radeon RX580 cards but 2.10.2 wasn't.

Dan

your settings may need to be trimmed a little;   there were changes on the AMD side of 2.10.2.


Title: Re: XMR-stak-JK 2.10.2 Compiled with no devfee (Updated: 2019-3-16)
Post by: solosequenosenada on March 19, 2019, 10:03:35 PM
Compiled and uploaded version 2.10.2.

the previous version crash my rig in a few hours, thanks


Title: Re: XMR-stak-JK 2.10.2 Compiled with no devfee (Updated: 2019-3-16)
Post by: AnonJunkie on March 23, 2019, 12:20:42 AM
2.10.2 give  me an error about failing to open config file .openclcache/.


Title: Re: XMR-stak-JK 2.10.2 Compiled with no devfee (Updated: 2019-3-16)
Post by: JaredKaragen on March 23, 2019, 09:04:59 AM
2.10.2 give  me an error about failing to open config file .openclcache/.

must be driver related.

if not using opencl;  I suggest disabling with a launch --flag as per the github documentation.


Title: Re: XMR-stak-JK 2.10.2 Compiled with no devfee (Updated: 2019-3-16)
Post by: JaredKaragen on March 29, 2019, 04:47:27 AM
New release today 2.10.3: https://github.com/fireice-uk/xmr-stak/releases/tag/2.10.3


Thanks for the heads up.

Compiled and uploaded.  See first post.


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: JaredKaragen on March 29, 2019, 11:05:23 AM
Hi fellas,
Who has an experience with this miner. It seems like one more nothing-new-miner, but web interface looks neat.
*deleted*

This is the miner you're asking about
*deleted*


That person is a banned user.

Your quoting of them is highly suspicious.  I will be paying attention to your posts from now on.....  be warned.


Title: Re: XMR-stak-JK 2.10.2 Compiled with no devfee (Updated: 2019-3-16)
Post by: JaredKaragen on March 31, 2019, 05:04:56 AM
New release today 2.10.3: https://github.com/fireice-uk/xmr-stak/releases/tag/2.10.3


Thanks for the heads up.

Compiled and uploaded.  See first post.

You are best Karagen thank you :). what is nvvp.bat ? :)


TBH;  not sure;  my guess is some sort of driver compatibility patch or something.


It was included with the official release (which is where I pull the non-self-compiled DLL's from) and thought I would throw it in there in case the official documentation/troubleshooting requires it.   Just ignore it.



Sometimes I would include the other DLL's for cuda 8, etc... but I dont think i will do that anymore; plus it keeps the .zip file a lot smaller.  One less step I have to do when packaging it up for upload.


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: ManDoneKTM on March 31, 2019, 04:51:51 PM
Last version , freeze my pc and then is restarting ... using AMD rx 570 4gb .. with another miner /s i dont have any problem .


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: JaredKaragen on April 02, 2019, 11:11:31 PM
New release 2.10.4: https://github.com/fireice-uk/xmr-stak/releases/tag/2.10.4


I compiled under cuda 10.1

you should not see the major bug in my release.


I don't have the ability to compile until later;  the compiler is on a server that is hosting;  and there are currently players on it; so when the players go off for the day;  Ill hop in and compile the new version and upload it for you guys.


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: artur.xx77 on April 14, 2019, 05:45:07 PM
The message is translated using an automatic translator.
Wallet pointed to exmo.com. I do not get paid. Eight days using "XMR-stak-JK 2.10.3".
How to set the minimum payout?
Where to check the number of extracted and unpaid xmr?


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: JaredKaragen on April 15, 2019, 03:10:29 AM
The message is translated using an automatic translator.
Wallet pointed to exmo.com. I do not get paid. Eight days using "XMR-stak-JK 2.10.3".
How to set the minimum payout?
Where to check the number of extracted and unpaid xmr?
you need to seek that information from the place you mine to.... in your example:  exmo.com should have documentation to tell you how to do that.  Typically by signing a message and submitting the hash.


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: zeef on April 23, 2019, 12:50:23 AM
Can i use it to miner uplexa?


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: JaredKaragen on April 24, 2019, 09:43:30 PM
Can i use it to miner uplexa?

check fireice-uk's github for documentation....


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: mauddib77 on May 15, 2019, 11:15:08 PM
did you get a chance to do 10.4?


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: JaredKaragen on May 17, 2019, 11:01:42 PM
This got a sh#tload of virus:

https://www.virustotal.com/#/file-analysis/MTU3YWM2MTJhZWNlMzk3ODVlNGM4ZjRiYWFlZjgzYjQ6MTU1ODAyMjg2NA==

https://cdn1.imggmi.com/uploads/2019/5/16/9756f4704bf28b01031f1ba502de0c47-full.jpg

DONT DOWNLOAD!

scan the same version from the github compiled by fireice-uk..... you see the same detections.

This is because people use these miners in their background processes of their spyware to mine for them....



Might wanna research before you speak.

I did that before and just did it again and with the fireice-ukversion ZERO virus! so who's laughing now friend!

https://www.virustotal.com/#/url/d57a2f9a914f30e2ad70c49d1d17cf18ad9bf9de04058c8f8152f4b382bb0c97/detection

I always double check every download i do these days.



your original link is erroneous.


since you have trouble with the basics:

download the same version I compiled from fireice-UK's github like I just did right now. (noting the github specifically mentions it shows up in virus detections where the download is...)  Do not direct-link the .zip file on github as the web-file scanner won't download the file and scan the hashes from the files inside the zip like it does when you submit it from your own pc.  If you were to upload my file to github and scan it the same as you did his;  you would get no detections because its only hashing the main zip itself; not its contents.


So now:
upload that file to virustotal from your pc like you did with mine originally.  (notice it will scan the hashes inside the zip [unlike the web linked scanner that only checked the zip itself])

see [like i just did] that the results are a near mirror of each other; but there are differences because I modified the original code before I compiled it; as the notes are clear about on page 1.

Here is a valid link, not a screenshot:

https://www.virustotal.com/#/file/f43e59e949b353dd9666d00b3969a1847becb0af3756e8c121f308a5a7399503/detection

*edit* No response to your faulty claim being disproven, so ill delete your messages and leave this one as a reference.


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: kansv on June 14, 2019, 10:35:02 AM
Hi!
XMR-stak-JK 2.10.5 came out a few days ago. Can we expect your recompiled version to be released soon?


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: JaredKaragen on June 15, 2019, 12:15:22 AM
Hi!
XMR-stak-JK 2.10.5 came out a few days ago. Can we expect your recompiled version to be released soon?

yeah, I should be able to have it done by the end of my weekend.


Title: Re: XMR-stak-JK 2.10.3 Compiled with no devfee (Updated: 2019-3-28)
Post by: JaredKaragen on June 16, 2019, 05:24:44 AM
Hi!
XMR-stak-JK 2.10.5 came out a few days ago. Can we expect your recompiled version to be released soon?

yeah, I should be able to have it done by the end of my weekend.

Compiled and uploaded.   Enjoy.


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: JaredKaragen on June 18, 2019, 01:01:02 AM
Have this build running on my B250-D8P rig and tested.   LMK if anyone has any issues.

FYI:  delete all .txt files and let it rebuild them again;  there were minor changes and I needed to do this on my personal rig.


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: a737540903 on June 18, 2019, 02:08:17 AM
suddenly found out the "MS Visual C++ Runtime" link is wrong


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: JaredKaragen on June 18, 2019, 03:09:18 AM
suddenly found out the "MS Visual C++ Runtime" link is wrong
updated the link.  Thanks for the heads up!


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: badhwar on June 19, 2019, 11:24:02 PM
Hi JK !
Thanks a ton for this update. As you say, a special vote of thanks to Fireice-UK
A quick question,: What if we put another wallet address instead of 127.0.0.1 ? why does the dev fee go to an ip address and not to a specific wallet? Will any other changes be needed just in case there is any code trickery ?
Thanks
Badhwar

Followed all instructions on the XMR-stak github to compile.... kinda.  Notes are below.

Huge thanks to Fireice-UK for making this source public.  Without it;  this release would not be here.  If you like it;  I suggest you donate to him directly rather than the devfee as it costs you more than just the donation time of hashrate in the real scope of things.


Compiled using Cuda 10.  
DevFee set to zero.  
Build version number stayed the same, build name was changed (added -JK).  
No major modifications aside from "built by notes", and changing the donate address to '127.0.0.1' for quick timeouts if there is any code trickery I did not catch.  CLi.cpp file was modified to add built by notes, as well as remove excessive fluff.

No donations or whatever required.  Just enjoy.  I know a bunch of you (like me) would like the zero devfee build, but either can't or are too lazy to compile it yourself.   Here you go you lazy ones ;)  If you do feel like taking the time to donate to me for my time, you can find the donation address in the "miner batch" post that is linked in my signature just message me...  But I highly suggest throwing a donation to fireice-uk first... without him, this release would not be possible.

***I literally cut/paste the source and built it 100% as per instruction aside from the edits mentioned above.***

MS Visual C++ Runtime:
 Download here (https://go.microsoft.com/fwlink/?LinkId=746572)

Current Version:
Download XMR-Stak-2.10.5-JK here (https://mega.nz/#!xX4TlYBR!39Qz9TjOwPFyUOzSHHIfG88bL1yvmK7LT3aoAEsL9qM) (NOTE: suggested to delete old .txt files and let them get rebuilt due to some changes)


Previous versions:
Download XMR-Stak-2.10.3-JK here (https://mega.nz/#!kSYyBKxJ!hg6-BZGBm-Gi0UapKRYlYba2wkTLrqtKZMktymbYpLU)
Download XMR-Stak-2.10.2-JK here (https://mega.nz/#!sCRT2CKI!KR6dcrAeQxSNRwO5AQK7rfx4Zbt_GSAamLjZ3JPN4bc)
Download XMR-Stak-2.10.1-JK here (https://mega.nz/#!pKJFlIiK!qyES-LEvOPeztLDrUMCjv4_cXhLYxjkSJ6UnWn3YQv4)
Download XMR-Stak-2.10.0-JK here (https://mega.nz/#!Ne4wRAJC!6XYCwS7X2Bdf19KN1_R8SBdJCHdSkxIBgPQWnq50V_I)
Download XMR-Stak-2.9.0-JK here (https://mega.nz/#!JKpyDCRQ!4OOBWlXmQNrL8x8zfWlhGbTY2UE8nZO25Gv1PL8Noa4)
Download XMR-Stak-2.8.3-JK here (https://mega.nz/#!1DAjyCpa!wxlP39HE_pjXs0HKax_h1A4LzGdkH8a5g82wrPrR16w)
Download XMR-Stak-2.8.2-JK here (https://mega.nz/#!QO5jFYaa!ytrtAEG-hd-NsVeHBS6b2WSsy5dmPt7BAgicNI4Crgo)
Download XMR-Stak-2.7.1-JK here (https://mega.nz/#!cbJSyIpQ!yFGGR87Q6K3DW_60LrFNL46fyEBUYQlOgmGRktvJ64k)
Download XMR-Stak-2.6.0-JK here (https://mega.nz/#!tTYgWAQD!qjv1f3CaHf2KM-Fhl7iAVrPhs1zVPbp2iWfJg4qv5h4)
Download XMR-Stak-2.5.2-JK here (https://mega.nz/#!9WIF0CzC!vxjCH_SxneGBIIH2It_FlTa7xtaEvlDaejZahNfpcaU)
Download XMR-Stak-2.5.1-JK here (https://mega.nz/#!5fB3DSpD!A9Qfwqqk7TV062h16dCDD_T_C7Nb2AFpq0v09ct9c-o)
Download XMR-Stak-2.4.4-JK here (https://mega.nz/#!ASonXAgQ!2LWANRy_UEMsgovLxbOUtd3pJFy46GciG6dDGGni1dY)
Download XMR-Stak-2.4.2-JK here (https://mega.nz/#!BD5DhCoa!WyweiRSEjb_gIDrDBEB4Fo_HmCKyK1bjwL_lB9Z2eT8)

If you are getting slower hashrates on older cards, try these DLL files.  They are from a different release of xmr-stak, thus not compiled by me.  But, another user has reported that replacing the DLL's with these has increased performance.  Your mileage may vary:  https://mega.nz/#!oGY0iIxa!X1tlll_HR5LWTa1aT3jBQIZAR3Bv91_Bgll8huVl84w (https://mega.nz/#!oGY0iIxa!X1tlll_HR5LWTa1aT3jBQIZAR3Bv91_Bgll8huVl84w)  This was applicable on 2.4.x only.

*update*
2019-06-15: Compiled and uploaded 2.10.5
2019-03-28: Compiled and uploaded 2.10.3
2019-03-16: Compiled and uploaded 2.10.2
2019-03-12: Compiled and uploaded 2.10.1
2019-03-07: Compiled tested and uploaded 2.10.0
2019-03-04: Compiled and uploaded 2.9.0
2019-02-16: Compiled and uploaded 2.8.3
2019-02-15: Compiled and uploaded 2.8.2
2018-12-10: Compiled and uploaded 2.7.1
2018-11-23: Compiled and uploaded 2.6.0
2018-10-29: Compiled and uploaded 2.5.2
2018-10-18: Compiled tested and uploaded 2.5.1
2018-06-03: Compiled and uploaded 2.4.4
2018-05-30: Added vc redistributable install link
2018-05-29: Compiled and uploaded 2.4.3/quickly removed partially built binary
2018-04-10: Alternate .dll files from original dev's older release available, download link added.  May give better or worse hashrates.
2018-04-06: Fixed issue with not launching properly.  Added original usage docs from source.

Just run xmr-stak.exe and fill out the questions.  from there after, just run xmr-stak.exe and theres no need to put any commands after.
See my below replies for notes on disabling CPU and GPU's individually.  I can help if you need assistance with your configuration.

Please see all of the build and usage notes on the original github: By clicking here (https://github.com/fireice-uk/xmr-stak/blob/master/README.md).



If you are looking for XTL-stak, that's right here (https://bitcointalk.org/index.php?topic=4416202).


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: JaredKaragen on June 20, 2019, 06:54:42 AM
Hi JK !
Thanks a ton for this update. As you say, a special vote of thanks to Fireice-UK
A quick question,: What if we put another wallet address instead of 127.0.0.1 ? why does the dev fee go to an ip address and not to a specific wallet? Will any other changes be needed just in case there is any code trickery ?
Thanks
Badhwar

*snip*

its not a wallet address;  its a pool address (donate.xmr-stak.com:xxxx)

Here's a copy/paste from the source I compiled to give you an idea....  they used to have a URL in place of 127.0.0.1.

Since devfee is set to 0%, it should technically never run this code;  but just in case, i changed it so it times out quickly.    I haven't really followed all of the functions in executor.cpp to the point of fully understanding them and their workflow;   maybe I will one day.....

im pretty sure his donate pool doesn't require a username or password and just accepts blind connections.  Makes modifying the source to redirect the donation a bit trickier;  which im not trying to do myself anyways.  researching executor.cpp will teach me more;  but i have no reason to do it as of right now.

I could set them to NULL or blank;  but;  who knows what kind of error that could cause.

Code:
switch(jconf::inst()->GetCurrentCoinSelection().GetDescription(0).GetMiningAlgo())
{
case cryptonight_heavy:
if(dev_tls)
pools.emplace_front(0, "127.0.0.1:8888", "", "", "", 0.0, true, true, "", true);
else
pools.emplace_front(0, "127.0.0.1:5555", "", "", "", 0.0, true, false, "", true);
break;
case cryptonight_gpu:
if(dev_tls)
pools.emplace_front(0, "127.0.0.1:8811", "", "", "", 0.0, true, true, "", false);
else
pools.emplace_front(0, "127.0.0.1:5511", "", "", "", 0.0, true, false, "", false);
break;
case cryptonight_monero_v8:
if(dev_tls)
pools.emplace_front(0, "127.0.0.1:8800", "", "", "", 0.0, true, true, "", false);
else
pools.emplace_front(0, "127.0.0.1:5500", "", "", "", 0.0, true, false, "", false);
break;
case cryptonight_aeon:
if(dev_tls)
pools.emplace_front(0, "127.0.0.1:7777", "", "", "", 0.0, true, true, "", true);
else
pools.emplace_front(0, "127.0.0.1:4444", "", "", "", 0.0, true, false, "", true);
break;
case cryptonight_r:
if(dev_tls)
pools.emplace_front(0, "127.0.0.1:8822", "", "", "", 0.0, true, true, "", false);
else
pools.emplace_front(0, "127.0.0.1:5522", "", "", "", 0.0, true, false, "", false);
break;
default:
if(dev_tls)
pools.emplace_front(0, "127.0.0.1:6666", "", "", "", 0.0, true, true, "", true);
else
pools.emplace_front(0, "127.0.0.1:3333", "", "", "", 0.0, true, false, "", true);
break;
}


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: aly0sh4 on June 25, 2019, 10:52:51 PM
when I start xmr stak jk 2.10.5 there is the missing dll error, LIBEAY32 and SSLEAY32


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: JaredKaragen on June 25, 2019, 10:58:37 PM
when I start xmr stak jk 2.10.5 there is the missing dll error, LIBEAY32 and SSLEAY32

I forgot to include them in the package, you can download an older copy from here and copy the two files, or you can download the original build from github and copy them from there...

they are just the SSL libraries.


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: alfredmicro on July 09, 2019, 07:09:25 AM
regards; someone has a valid configuration for 7970 or rx280 the most I get is 400 h / s


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: JaredKaragen on July 09, 2019, 10:36:32 PM
regards; someone has a valid configuration for 7970 or rx280 the most I get is 400 h / s

sounds about right for the older cards...

do you mean R9-280?

I run a RX560  and see at most 380h/s but typically ~320.

check https://www.xmrstak.com/  It is the place people post their configs.

You may need to mess with the AMD.txt file and fine tune your particular cards.


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: alucard20724 on July 09, 2019, 10:40:01 PM
regards; someone has a valid configuration for 7970 or rx280 the most I get is 400 h / s

sounds about right for the older cards...

do you mean R9-280?

I run a RX560  and see at most 380h/s but typically ~320.

check https://www.xmrstak.com/  It is the place people post their configs.

You may need to mess with the AMD.txt file and fine tune your particular cards.

has anyone tried it with a 5700XT yet?


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: herrdrone on July 10, 2019, 03:55:44 AM
Quote
has anyone tried it with a 5700XT yet?

Bits Be Trippin' did a review recently: https://www.youtube.com/watch?v=1j5WM29ECPk

Edit: edited.


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: alucard20724 on July 10, 2019, 04:15:59 AM
Quote
has anyone tried it with a 5700XT yet?

Bits Be Trippin' did a review recently: https://www.youtube.com/watch?v=1j5WM29ECPk

Edit: edited.

don't need to see it... i verified.  it doesn't.


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: herrdrone on July 10, 2019, 08:46:03 PM
Quote
has anyone tried it with a 5700XT yet?

Bits Be Trippin' did a review recently: https://www.youtube.com/watch?v=1j5WM29ECPk

Edit: edited.

don't need to see it... i verified.  it doesn't.

Rather than spitting empty sentences, base your opinions on facts.

It is a 12 minutes recap from 2 hours livestream, where Phoenix Miner was the only one he got working and JCE for cryptonight. Card still new and need driver improvement to work.



Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: alucard20724 on July 10, 2019, 09:02:38 PM
Quote
has anyone tried it with a 5700XT yet?

Bits Be Trippin' did a review recently: https://www.youtube.com/watch?v=1j5WM29ECPk

Edit: edited.

don't need to see it... i verified.  it doesn't.

Rather than spitting empty sentences, base your opinions on facts.

It is a 12 minutes recap from 2 hours livestream, where Phoenix Miner was the only one he got working and JCE for cryptonight. Card still new and need driver improvement to work.



sure... i ran in on my card.. .it doesn't run.   there's nothing empty about that.  I don't need to see a two hour video on something i already know.  if you want to talk about JCE, then go over to that thread.  I was posting in the "XMR-stak-JK 2.10.5 Compiled with no devfee" thread


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: alucard20724 on July 22, 2019, 02:50:26 AM
Will you be releasing a version for XMR-stak version 2.10.6?

https://github.com/fireice-uk/xmr-stak/releases


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: JaredKaragen on July 22, 2019, 12:45:56 PM
im on my way to hawaii.  ill do it as soon as i can.


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: alucard20724 on July 23, 2019, 02:38:57 AM
im on my way to hawaii.  ill do it as soon as i can.

screw that... enjoy Hawaii instead.  ;D


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: JaredKaragen on July 23, 2019, 07:27:12 AM
im on my way to hawaii.  ill do it as soon as i can.

screw that... enjoy Hawaii instead.  ;D

Compiled and uploaded 2.10.6 remotely.  Did not have time to test.  Hopefully I remembered all the DLL files this time.

Enjoy!


Title: Re: XMR-stak-JK 2.10.5 Compiled with no devfee (Updated: 2019-6-15)
Post by: impynick on July 23, 2019, 09:23:35 AM
im on my way to hawaii.  ill do it as soon as i can.

screw that... enjoy Hawaii instead.  ;D

Compiled and uploaded 2.10.6 remotely.  Did not have time to test.  Hopefully I remembered all the DLL files this time.

Enjoy!

I was just there (Maui) 2 weeks ago! Enjoy your trip  8)


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: Apprentice on July 23, 2019, 07:57:54 PM
came across 8 GT 690 to add mining XMR.

the auto config is detecting 2 cards (per card), is this correct? can anyone share the optimal configuration? blocks, threads?

which cuda version should be used with GTX 690?

thanks


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: JaredKaragen on July 23, 2019, 09:23:33 PM
came across 8 GT 690 to add mining XMR.

the auto config is detecting 2 cards (per card), is this correct? can anyone share the optimal configuration? blocks, threads?

which cuda version should be used with GTX 690?

thanks

some cards like multiple threads as they can multitask better...

check http://www.xmrstak.com for user-uploaded settings.


Yep;  its beautiful over here!   I will definitely enjoy my time!


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: impynick on July 30, 2019, 06:47:09 AM
came across 8 GT 690 to add mining XMR.

the auto config is detecting 2 cards (per card), is this correct? can anyone share the optimal configuration? blocks, threads?

which cuda version should be used with GTX 690?

thanks

some cards like multiple threads as they can multitask better...

check http://www.xmrstak.com for user-uploaded settings.


Yep;  its beautiful over here!   I will definitely enjoy my time!

I am trying to run cn-gpu but im getting invalid submits. With the release version its working fine?? Even when I compiled myself I was getting invalid submits. Can you try it on your end to see if its working properly?


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: JaredKaragen on July 30, 2019, 07:21:18 AM
came across 8 GT 690 to add mining XMR.

the auto config is detecting 2 cards (per card), is this correct? can anyone share the optimal configuration? blocks, threads?

which cuda version should be used with GTX 690?

thanks

some cards like multiple threads as they can multitask better...

check http://www.xmrstak.com for user-uploaded settings.


Yep;  its beautiful over here!   I will definitely enjoy my time!

I am trying to run cn-gpu but im getting invalid submits. With the release version its working fine?? Even when I compiled myself I was getting invalid submits. Can you try it on your end to see if its working properly?

cn-gpu?   is that a separate algo?  where are you mining to?

I could remotely test, but when I left for vacation I powered off my test rig and need to be there to physically power it on.

Send me the details of what pool you are mining to, a copy of your AMD/NVIDIA.txt file(s) or cpu.txt files using this format:
nvidia.txt
Code:
Code quoting examples like this one using the hashtag button

As well as provide the model of graphics card and vendor of card you are using; and any other applicable specific details I may need to know to test.

I will do a little research and see if I can have an answer for you.


I literally remotely compiled and uploaded the recent build while away on vacation, and could not test myself, though the initial party(s) haven't complained about any issue other than a potential reduced hashrate to other versions which may have just been the .txt files being reset to the new relaxed settings that were noted in the changelog/release notes on fireice's github.

I personally only use xmr-stak 100% for XMR; and no other coins/algos.   If you are mining a different coin/algo... I would have to set up to mine at whatever pool you are using so if that is so;  provide me your username and hopefully it has no password (or just an 'x') so i can use your profile to test and not worry about setting up a wallet for an address to mine-to, etc. because to be frank;  that is too much hassle for this free service I am providing.  If you are going to provide me your pool credentials;  send me a PM with your pools.txt using the code quoting example above.

And as a side note, im not sure if XTL-stak is even a thing that is present/used today.... I only compiled it once upon request because it uses almost identical code structures and compile settings.


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: impynick on July 31, 2019, 10:22:27 AM
came across 8 GT 690 to add mining XMR.

the auto config is detecting 2 cards (per card), is this correct? can anyone share the optimal configuration? blocks, threads?

which cuda version should be used with GTX 690?

thanks

some cards like multiple threads as they can multitask better...

check http://www.xmrstak.com for user-uploaded settings.


Yep;  its beautiful over here!   I will definitely enjoy my time!

I am trying to run cn-gpu but im getting invalid submits. With the release version its working fine?? Even when I compiled myself I was getting invalid submits. Can you try it on your end to see if its working properly?

cn-gpu?   is that a separate algo?  where are you mining to?

I could remotely test, but when I left for vacation I powered off my test rig and need to be there to physically power it on.

Send me the details of what pool you are mining to, a copy of your AMD/NVIDIA.txt file(s) or cpu.txt files using this format:
nvidia.txt
Code:
Code quoting examples like this one using the hashtag button

As well as provide the model of graphics card and vendor of card you are using; and any other applicable specific details I may need to know to test.

I will do a little research and see if I can have an answer for you.


I literally remotely compiled and uploaded the recent build while away on vacation, and could not test myself, though the initial party(s) haven't complained about any issue other than a potential reduced hashrate to other versions which may have just been the .txt files being reset to the new relaxed settings that were noted in the changelog/release notes on fireice's github.

I personally only use xmr-stak 100% for XMR; and no other coins/algos.   If you are mining a different coin/algo... I would have to set up to mine at whatever pool you are using so if that is so;  provide me your username and hopefully it has no password (or just an 'x') so i can use your profile to test and not worry about setting up a wallet for an address to mine-to, etc. because to be frank;  that is too much hassle for this free service I am providing.  If you are going to provide me your pool credentials;  send me a PM with your pools.txt using the code quoting example above.

And as a side note, im not sure if XTL-stak is even a thing that is present/used today.... I only compiled it once upon request because it uses almost identical code structures and compile settings.


It seems 2.16 is bugged for cn-GPU (RYO). I had to update my visual studios and cmake to get rid of the invalid shares.  Just a heads up if you want to mine another cn-GPU (ryo) this one will throw invalid submits.

Try it for yourself when you're back https://miningpoolstats.stream/ryo


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: JaredKaragen on July 31, 2019, 09:09:23 PM
What version of VS and cmake (respectively) did you update to?

If this is so, I should submit a note to fireice-uk to have it noted in his build notes.


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: impynick on July 31, 2019, 09:53:53 PM
What version of VS and cmake (respectively) did you update to?

If this is so, I should submit a note to fireice-uk to have it noted in his build notes.


I had to update to VS 19 and cmake 3.15 i think. https://www.reddit.com/r/XmrStak/wiki/guides/startup#wiki_3._windows_7.2F10_.2B_nvidia_.28compiling_from_source.29


Code:
3.1.3 Navigate to Visual Studio Community 2019 setup page. Run installer (it will download some files to prepare installation).

Note1: Check carefully if you select all components.

Note2: This step will require up to 12Gb of HDD space in total. Make sure you have enough free space on drive C.

Install choose following components:

(left side of window) Desktop development with C++
(Tab "Individual Components", section "Compilers, build tools, and runtimes") leave all auto-marked components and make sure these checkboxes are checked:
C++ 2019 Redistributable MSMs
C++ 2019 Redistributable Update
C++ CMake tools for Windows
C++ Modules for v142 build tools (x64/86 experimental)
C++ Universal Windows Platform Runtime for v142 build tools
C++/CLI support for v142 build tools
MSBuild
MSVC v142 - VS 2019 C++ x64/x86 build tools (v14.20)
MSVC v142 - VS 2019 C++ x64/x86 Spectre mitigated libs (v14.20)
Windows Universal CRT SDK
Section "Development activities":

C++ core features
Section "SDKs, libraries and frameworks":

Windows 10 SDK (10.0.17763.0)


3.1.4 Reboot after VS 2019 install finished

3.1.5 Navigate to https://developer.nvidia.com/cuda-downloads Select: Windows-> x84_64 -> 10 -> exe (local) and press Download (2.4Gb) button

Note: next step may vary depending on if you have installed display driver version higher than 410 on your system or not. If you have it installed - install only CUDA toolkit, if not - make sure you install Display driver that ships with this package.

3.1.6 Run downloaded installer (agree to unpack files to temporary folder) and select "custom installation" and choose either:

CUDA
CUDA + Display driver
Other checkboxes like "Nvidia 3D vision" can be unchecked.

Note: leave default paths on next step (these paths will be used in next steps). If you change NVIDIA paths, make sure you edit SET commands according to your paths. (3.2.2)

3.1.7 Reboot after CUDA toolkit install finished

3.1.8 Navigate to https://cmake.org/download/ pick Windows win64-x64 Installer and install CMake (After install set: Add CMake to the system PATH for all users).

3.1.9 Reboot (yes, it is Windows..)


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: JaredKaragen on July 31, 2019, 10:13:33 PM
Ill give this a shot when I get home;  I just hope that it doesn't break my compiler like the last time I tried to migrate from 2015 to 2017;   I ended up having to install VS2017 on one of my game host servers and do all of my compiling there remotely....   all the players always complain of lag spikes when I compile the latest version of XMR-stak... lol!

Maybe Ill just attempt to install the whole ensemble onto my new daily driver laptop as it was replaced many months ago so i no longer use that machine that had its VS15/17 tainted and I could never get a complete compile/build of xmr-stak... this way I can still fallback onto a setup/config that I know still works for my primary goal.


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: impynick on July 31, 2019, 10:42:43 PM
Ill give this a shot when I get home;  I just hope that it doesn't break my compiler like the last time I tried to migrate from 2015 to 2017;   I ended up having to install VS2017 on one of my game host servers and do all of my compiling there remotely....   all the players always complain of lag spikes when I compile the latest version of XMR-stak... lol!

Maybe Ill just attempt to install the whole ensemble onto my new daily driver laptop as it was replaced many months ago so i no longer use that machine that had its VS15/17 tainted and I could never get a complete compile/build of xmr-stak... this way I can still fallback onto a setup/config that I know still works for my primary goal.

The wiki they created is really helpful. I do compile on my personal PC but updating everything took a while. PS they just released 2.10.7.

Thanks for the merit! If I can help in anyway just let me know  :)


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: JaredKaragen on August 01, 2019, 01:45:59 AM
Ill give this a shot when I get home;  I just hope that it doesn't break my compiler like the last time I tried to migrate from 2015 to 2017;   I ended up having to install VS2017 on one of my game host servers and do all of my compiling there remotely....   all the players always complain of lag spikes when I compile the latest version of XMR-stak... lol!

Maybe Ill just attempt to install the whole ensemble onto my new daily driver laptop as it was replaced many months ago so i no longer use that machine that had its VS15/17 tainted and I could never get a complete compile/build of xmr-stak... this way I can still fallback onto a setup/config that I know still works for my primary goal.

The wiki they created is really helpful. I do compile on my personal PC but updating everything took a while. PS they just released 2.10.7.

Thanks for the merit! If I can help in anyway just let me know  :)

Thanks for the heads up.  Ill get on 2.10.7 a day or two after I get back to the mainland tomorrow;  I wanna bask in what remains of my stay here =)

NP on the merit;  you definitely earned it.


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: ouray on August 05, 2019, 11:55:53 PM
I wanna bask in what remains of my stay here =)

I guess he's still basking longer than usual.   ::)


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: JaredKaragen on August 06, 2019, 12:17:17 AM
I wanna bask in what remains of my stay here =)

I guess he's still basking longer than usual.   ::)

yep, been non-stop busy handling all the things that fell apart while away from home.  I'm finally taking a day for myself, hopefully Ill be up to getting it compiled tonight.... but I wont have it compiled on the updated VS, or CMake, ill be compiling it on my already configured remote machine;  I need to get myself to a good internet connection to be able to download and install the newer apps on my laptop.

Give it a day or two longer.  Ill get it done.


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: ouray on August 11, 2019, 07:26:39 PM
I wanna bask in what remains of my stay here =)

I guess he's still basking longer than usual.   ::)

yep, been non-stop busy handling all the things that fell apart while away from home.  I'm finally taking a day for myself, hopefully Ill be up to getting it compiled tonight.... but I wont have it compiled on the updated VS, or CMake, ill be compiling it on my already configured remote machine;  I need to get myself to a good internet connection to be able to download and install the newer apps on my laptop.

Give it a day or two longer.  Ill get it done.
I guess he is still non-stop busy handling all the things that fell apart while he's away from home!!! ???


Title: Re: XMR-stak-JK 2.10.6 Compiled with no devfee (Updated: 2019-7-23)
Post by: JaredKaragen on August 12, 2019, 11:15:08 AM
I wanna bask in what remains of my stay here =)

I guess he's still basking longer than usual.   ::)

yep, been non-stop busy handling all the things that fell apart while away from home.  I'm finally taking a day for myself, hopefully Ill be up to getting it compiled tonight.... but I wont have it compiled on the updated VS, or CMake, ill be compiling it on my already configured remote machine;  I need to get myself to a good internet connection to be able to download and install the newer apps on my laptop.

Give it a day or two longer.  Ill get it done.
I guess he is still non-stop busy handling all the things that fell apart while he's away from home!!! ???

Yeah, dealing with the day to day stuff is tougher given my disability....

but alas, I just finished compiling it, and its updated in the first post.   Hopefully I didn't forget to include the required DLL's again.


Thanks for the patience guys.


Ill try to finally get out of the house in the next day or two (hopefully today if my body is up to it) and will get VS2019 and the new cmake installed on my workstation laptop;  attempt a recompile for the ryo guys who had issues with the last build.


Title: Re: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-12)
Post by: artur.xx77 on August 12, 2019, 06:50:26 PM
Hi.
I am new to mining.
XMR-stak-JK_2.10.7 can be configured for double mining? If you can tell me how.
I want to mine with CPU: XMR, with GPU: ETH.


Title: Re: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-12)
Post by: JaredKaragen on August 13, 2019, 01:46:41 AM
Hi.
I am new to mining.
XMR-stak-JK_2.10.7 can be configured for double mining? If you can tell me how.
I want to mine with CPU: XMR, with GPU: ETH.

You will need to use your regular ETH gpu solution....   

for CPU;  just run xmr-stak, let it auto-config itself,   then close it.   Go in and edit nvidia.txt/amd.txt and comment out/delete the threads for the GPU's (see examples found by reading this thread's history as it is in there). 

Now it will only use the CPU.


Title: Re: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-18)
Post by: JaredKaragen on August 19, 2019, 02:11:14 AM
Ok, got to the internet hub and updated my business laptop.

Compiled and uploaded 2.10.7 again on my laptop;  released as "VS2019" release.    Give it a whirl for Ryo and the other cryptos that were having the issues;  If all goes well;  let me know and ill keep up with the 2019 releases built from my laptop.


Cheers!


Title: Re: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-18)
Post by: JaredKaragen on November 21, 2019, 09:12:06 AM
Will the next XMR-STAK-RX versions be uploaded here (in case there will be a dev-fee in the next releases)?
Thanks

yeah, ill continue them here when necessary.  since this initial release is no fee, i figured i'd leave it to the devs.


Title: Re: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-18)
Post by: coinbeamer on December 02, 2019, 04:23:53 PM
Why only XMR-STAK RX and not R?

All my old rigs stopped because with R9 280x theres no randomx mining soft as far as i know?!

Is there a way to mine randomx coins with these cards?


Title: Re: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-18)
Post by: JaredKaragen on December 03, 2019, 10:08:51 AM
Why only XMR-STAK RX and not R?

All my old rigs stopped because with R9 280x theres no randomx mining soft as far as i know?!

Is there a way to mine randomx coins with these cards?

im not certain what you mean...

rx stands for random x....


id go look at fireice's github for notes on compatibility and driver requirement changes...   but... furthermore;   you are wasting an exponential amount of power to mine on a gpu vs ANY cpu for the most part...

That was the purpose of randomx...  to even the playing field so to speak.


Title: Re: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-18)
Post by: coinbeamer on December 03, 2019, 10:35:28 AM

im not certain what you mean...

rx stands for random x....


id go look at fireice's github for notes on compatibility and driver requirement changes...   but... furthermore;   you are wasting an exponential amount of power to mine on a gpu vs ANY cpu for the most part...

That was the purpose of randomx...  to even the playing field so to speak.

Sorry, it was unclear :-)
RX = randomx on the one hand but i thought it also means RX cards (RX458 ...) as far as i know the software doesnt work with R-cards as 280x ...

You are right, AMDs CPUs are better but i still have some old R9 rigs left :-(


Title: Re: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-18)
Post by: JaredKaragen on December 03, 2019, 10:50:21 AM

im not certain what you mean...

rx stands for random x....


id go look at fireice's github for notes on compatibility and driver requirement changes...   but... furthermore;   you are wasting an exponential amount of power to mine on a gpu vs ANY cpu for the most part...

That was the purpose of randomx...  to even the playing field so to speak.

Sorry, it was unclear :-)
RX = randomx on the one hand but i thought it also means RX cards (RX458 ...) as far as i know the software doesnt work with R-cards as 280x ...

You are right, AMDs CPUs are better but i still have some old R9 rigs left :-(

yep.  randomx takes advantage of the fact that certain operators (divide, add, subtract, multiply) take certain amounts of time to calculate; and the amount of data that it would need in cache as to be accessed quickly.   It is very clever since ASICS would need that very same circuitry, so it would be redundant by nature.   at least... this is kind of how I understand it.

yeah... its all about optimizing the intensity so that everything stays on the CPU cache; and you get good performance.   If you go over that, performance drops like a rock.


Title: Re: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-18)
Post by: JaredKaragen on January 23, 2020, 09:26:45 AM
hi, how can be set difference  d=?

You need to read the manual on github for specifics...  But diff is typically pool set.


Title: Re: XMR-stak 2.4.2 Compiled with no devfee
Post by: Herry Toms on January 25, 2020, 03:03:30 PM
Is that program faster than the Claymore miner for the R9 290 or 390?
Try xmr-stak-rx maybe it can improve hashrate and it is also free, I'm mining monero and Loki and it is working fine. Hashrate is good and stable.


Title: Re: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-18)
Post by: JaredKaragen on September 01, 2020, 08:37:53 PM
who can give me linux version ???
go to the github; download the source... compile.

its very easy.  they have step by step instructions on github.

better yet;  get xmr-stak-rx, this version is very outdated by now.