Quote from: papampi_2 on September 22, 2018, 07:44:11 AM

Quote from: CryptAtomeTrader44 on September 21, 2018, 07:22:14 PM

I have several problems with xmr-stak 2.4.7 on CUDA 9.2

1- That code only works from within the script, if you run it individually the variable will not be recognized

2- Input for compiling xmr-stak is X (uppercase x) not x

3- I dont have much experience with xmr-stak to help with. You may ask in their from for the parameters and add them to:

Code:

XMR_EXTENSION_ARGUMENTS=""

Or let us know if it needs some adjustments in 0miner.

4- There is already a miner password in 1bash what other passwords you are looking for?

Code:

MINER_PWD="x" # Set the miner password. Default: x

1/ I think your variable

Code:

"${!xversion}"/

is not functionnal like the error message returned to me (line 159 and 179). I modified like i wrote and when i launch the miner with your code (startup machine, and/or starting console) it works with my code.

2/ Ok, i noticed it. But i finally recompiled it me myself by downloading the source from their GITHUB. It was very long to compile the two cuda backend.

3/I think the -r options to define name of the rig will be a good solution in this extension arguments. I will test it. Because without this,i experienced that xmr-stak ask to press enter at startup

4/ supportxmr pool give us possibility to add options in password option. they create and account to modify minimum payout if you put your email address as password.
Because i will mine only xmr, it's not a problem for me, but if someone want to mine with profit switching on supportxmr instead of nanopool it can't modify his password that is often "x" (lowercase)

Another problem with xmr-stak is to define largest memory page before starting minning software with the command :

Code:

sudo sysctl -w vm.nr_hugepages=128

I added it in cryptonight section on 0miner file

and modifying this file : /etc/security/limits.conf like developers explained in the config.txt file.

Quote

* 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.
*
* 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.
*
* On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
* ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
* and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
* recommended for security reasons.
*
* Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
* command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
* locked and unlocked memory. If that is your setup see option "no_mlck".

I give here my CC, MC and PL settings with FAN SPEED at 40 RPM

Code:

#####################################################################
# Individual GPU_SPECIFIC Power Limit, Temp and Clock settings #
#####################################################################

# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=65 # GTX 1070
TARGET_TEMP_1=65 # GTX 1060
TARGET_TEMP_2=65 # GTX 1060
TARGET_TEMP_3=65 # GTX 1070
TARGET_TEMP_4=65 # GTX 1060
TARGET_TEMP_5=65 # GTX 1070
TARGET_TEMP_6=65 # GTX 1070
TARGET_TEMP_7=65 # GTX 1060
TARGET_TEMP_8=65 # GTX 1060
TARGET_TEMP_9=65 # GTX 1070

# Set individual powerlimits here if POWERLIMIT_MODE is GPU_SPECIFIC
INDIVIDUAL_POWERLIMIT_0=100
INDIVIDUAL_POWERLIMIT_1=100
INDIVIDUAL_POWERLIMIT_2=100
INDIVIDUAL_POWERLIMIT_3=100
INDIVIDUAL_POWERLIMIT_4=100
INDIVIDUAL_POWERLIMIT_5=100
INDIVIDUAL_POWERLIMIT_6=100
INDIVIDUAL_POWERLIMIT_7=100
INDIVIDUAL_POWERLIMIT_8=100
INDIVIDUAL_POWERLIMIT_9=100

# Set individual clocks here if OVERCLOCK_MODE is GPU_SPECIFIC
__CORE_OVERCLOCK_0=115 # GTX 1070
MEMORY_OVERCLOCK_0=1400 # GTX 1070

__CORE_OVERCLOCK_1=115 # GTX 1060
MEMORY_OVERCLOCK_1=1400 # GTX 1060

__CORE_OVERCLOCK_2=115 # GTX 1060
MEMORY_OVERCLOCK_2=1400 # GTX 1060

__CORE_OVERCLOCK_3=115 # GTX 1070
MEMORY_OVERCLOCK_3=1500 # GTX 1070

__CORE_OVERCLOCK_4=115 # GTX 1060
MEMORY_OVERCLOCK_4=1400 # GTX 1060

__CORE_OVERCLOCK_5=115 # GTX 1070
MEMORY_OVERCLOCK_5=1400 # GTX 1070

__CORE_OVERCLOCK_6=115 # GTX 1070
MEMORY_OVERCLOCK_6=1400 # GTX 1070

__CORE_OVERCLOCK_7=115 # GTX 1060
MEMORY_OVERCLOCK_7=1400 # GTX 1060

__CORE_OVERCLOCK_8=115 # GTX 1060
MEMORY_OVERCLOCK_8=1400 # GTX 1060

__CORE_OVERCLOCK_9=115 # GTX 1070
MEMORY_OVERCLOCK_9=1600 # GTX 1070

The results of these settings are :

Quote

HASHRATE REPORT - NVIDIA
| ID | 10s | 60s | 15m | ID | 10s | 60s | 15m |
| 0 | 725.1 | 724.6 | (na) | 1 | 517.5 | 517.0 | (na) |
| 2 | 518.1 | 518.0 | (na) | 3 | 734.2 | 733.7 | (na) |
| 4 | 516.9 | 516.9 | (na) | 5 | 725.2 | 724.9 | (na) |
| 6 | 723.9 | 723.8 | (na) | 7 | 549.4 | 549.4 | (na) |
| 8 | 549.2 | 549.1 | (na) | 9 | 741.3 | 741.3 | (na) |
Totals (NVIDIA): 6300.8 6298.7 0.0 H/s
-----------------------------------------------------------------
Totals (ALL): 6300.8 6298.7 0.0 H/s
Highest: 6308.8 H/s
-----------------------------------------

EDIT, IT seems after several hours that theses settings looks making my rig unstable. So i returned my olds settings what i used before for mining ETH and others algos :

Quote

# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=65                  # GTX 1070
TARGET_TEMP_1=65                  # GTX 1060
TARGET_TEMP_2=65                  # GTX 1060
TARGET_TEMP_3=65                  # GTX 1070
TARGET_TEMP_4=65                  # GTX 1060
TARGET_TEMP_5=65                  # GTX 1070
TARGET_TEMP_6=65                  # GTX 1070
TARGET_TEMP_7=65                  # GTX 1060
TARGET_TEMP_8=65                  # GTX 1060
TARGET_TEMP_9=65                  # GTX 1070
TARGET_TEMP_10=75
TARGET_TEMP_11=75
TARGET_TEMP_12=75
TARGET_TEMP_13=75
TARGET_TEMP_14=75
TARGET_TEMP_15=75
TARGET_TEMP_16=75
TARGET_TEMP_17=75
TARGET_TEMP_18=75

# Set individual powerlimits here if POWERLIMIT_MODE is GPU_SPECIFIC
INDIVIDUAL_POWERLIMIT_0=105
INDIVIDUAL_POWERLIMIT_1=105
INDIVIDUAL_POWERLIMIT_2=105
INDIVIDUAL_POWERLIMIT_3=105
INDIVIDUAL_POWERLIMIT_4=100
INDIVIDUAL_POWERLIMIT_5=100
INDIVIDUAL_POWERLIMIT_6=100
INDIVIDUAL_POWERLIMIT_7=110
INDIVIDUAL_POWERLIMIT_8=110
INDIVIDUAL_POWERLIMIT_9=115
INDIVIDUAL_POWERLIMIT_10=100
INDIVIDUAL_POWERLIMIT_11=100
INDIVIDUAL_POWERLIMIT_12=100
INDIVIDUAL_POWERLIMIT_13=100
INDIVIDUAL_POWERLIMIT_14=100
INDIVIDUAL_POWERLIMIT_15=100
INDIVIDUAL_POWERLIMIT_16=100
INDIVIDUAL_POWERLIMIT_17=100
INDIVIDUAL_POWERLIMIT_18=100

# Set individual clocks here if OVERCLOCK_MODE is GPU_SPECIFIC
__CORE_OVERCLOCK_0=100                     # GTX 1070
MEMORY_OVERCLOCK_0=1125               # GTX 1070

__CORE_OVERCLOCK_1=100                     # GTX 1060
MEMORY_OVERCLOCK_1=1050               # GTX 1060

__CORE_OVERCLOCK_2=100                     # GTX 1060
MEMORY_OVERCLOCK_2=1050               # GTX 1060

__CORE_OVERCLOCK_3=100                  # GTX 1070
MEMORY_OVERCLOCK_3=1050               # GTX 1070

__CORE_OVERCLOCK_4=100                  # GTX 1060
MEMORY_OVERCLOCK_4=1000               # GTX 1060

__CORE_OVERCLOCK_5=100                  # GTX 1070
MEMORY_OVERCLOCK_5=1050               # GTX 1070

__CORE_OVERCLOCK_6=100                  # GTX 1070
MEMORY_OVERCLOCK_6=1050               # GTX 1070

__CORE_OVERCLOCK_7=100                  # GTX 1060
MEMORY_OVERCLOCK_7=1300               # GTX 1060

__CORE_OVERCLOCK_8=100                  # GTX 1060
MEMORY_OVERCLOCK_8=1300               # GTX 1060

__CORE_OVERCLOCK_9=100                  # GTX 1070
MEMORY_OVERCLOCK_9=1500               # GTX 1070

That give me less hashrate displayed on miner but more hash because more shares on pool :

Quote

HASHRATE REPORT - NVIDIA
| ID | 10s | 60s | 15m | ID | 10s | 60s | 15m |
| 0 | 702.6 | 703.9 | 703.6 | 1 | 496.8 | 496.7 | 496.8 |
| 2 | 497.5 | 497.4 | 497.3 | 3 | 698.5 | 698.9 | 698.7 |
| 4 | 494.5 | 494.4 | 494.4 | 5 | 697.8 | 697.1 | 697.4 |
| 6 | 697.3 | 697.5 | 697.1 | 7 | 543.4 | 543.3 | 543.3 |
| 8 | 543.2 | 542.9 | 543.1 | 9 | 735.8 | 735.9 | 735.9 |
Totals (NVIDIA): 6107.4 6107.9 6107.7 H/s
-----------------------------------------------------------------
Totals (ALL): 6107.4 6107.9 6107.7 H/s
Highest: 6155.3 H/s

Miner displayed before : 6,3 KHs but pool displayed average hashrate was 4.5 - 5KHs

Now : Miner display 6.1 KHs but pools display average 6 kHs minimum with top at 9KHs !