[OS] nvOC easy-to-use Linux Nvidia Mining - page 22.

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: LuKePicci on June 24, 2018, 07:25:37 PM

vertminer is already in the miners repo, and to use it you should only need to edit the miner name into 1bash, however vertminer executables does not call itself "ccminer" as 0miner is expecting so having

Code:

LYRA2V2_MINER="vertminer"

is now failing. I've just fixed this.

Will add SUPRminer also, I opened a new issue for that on GitHub,

I also updated the README on the nvOC_miners repo with steps that collaborators needs to add/update a miner for releasing to all nvOC users. If you feel confident in that, please, open your PR, even if they're not perfectly written, we will help you fix them.

Thank you all for your help.

If it's possible to have a miner software thaht have no fee or less than 2% or vertminer fee, i take it immediatly. I was using nanashi ccminer before, but i don't know what is his fee. I just know that it was a best miner than TPruvot for Lyra2vv2. I recompiled Tpruvot latest miner but, i fail to mine with it. when i have more time, i post an issue ont his github

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

I have this message on my wiorst GTX1060 that heating a lot :

Quote

INFO: GPU 4, Tue Jun 26 17: 07: 22 CEST 2018 - Adjusting Power Limit for GPU4. Old Limit: 91 New Limit: 88 Fan speed: 100
Provided power limit 88.00 W is not a valid power limit which should be between 90.00 W and 200.00 W for GPU 00000000: 06: 00.0

What can i do to solve ?

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: CryptAtomeTrader44 on June 24, 2018, 12:44:01 PM

Another question : Where do the variable $NVOC come from Huh

? Which script launch it at firt time in all theses collection scripts ?

Both gnome-terminal (by profile custom command) and systemd (if you setup nvoc to run as a service) starts nvOC by running 2unix. The $NVOC variable is automatically set to proper value with the path to your running nvOC version. In your case NVOC is set to '/home/m1/NVOC/mining'. Its value is reported m minerinfo web page amd 'bash nvOC report' as well.

LuKePicci

jr. member

Activity: 128

Merit: 1

vertminer is already in the miners repo, and to use it you should only need to edit the miner name into 1bash, however vertminer executables does not call itself "ccminer" as 0miner is expecting so having

Code:

LYRA2V2_MINER="vertminer"

is now failing. I've just fixed this.

Will add SUPRminer also, I opened a new issue for that on GitHub,

I also updated the README on the nvOC_miners repo with steps that collaborators needs to add/update a miner for releasing to all nvOC users. If you feel confident in that, please, open your PR, even if they're not perfectly written, we will help you fix them.

Thank you all for your help.

terex

newbie

Activity: 7

Merit: 0

Hi,

Testing the 19.2-1 beta image - coin set to RVN - In 1bash line 460 mentions SUPRminer, but suprminers not in miners update script. I cloned/built suprminer into the miners directory, the directory is suprminer all lowecase, the comment has SUPRminer. Changed it to match the directory name and it works fine. Can you add it to the miners update script & fix the comment.

I want to say thanks to pap and LuKe for the awesome re-write.

Don

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

I do not understand why when I want to mine LYRA2V2 [MONA] on this new testing version, ALL ccminers take more than 2 minutes to start when they actually start

Would it be related to the old version of CUDA? CUDA8.0.

I tried to compile several mining software and more or less successful, but each time, it takes more than 2 minutes before the software starts hash.

Only one software seems to start a quarter turn, but Papampi seems not to have found it good to put it in the scripts: Vertminer.
I cloned it from Gihub and recompiled without any problems. It is a little longer to get started, it rises gradually in charge, but he leaves immediately. Another problem: he has a fee of 2% (bouuuuuuuuhhhhhh)

I think I will reconnect my old disk for now. I hope I helped advance the new version. I will probably be back in the next few days of this week rereading your answers.

I think this section should be modified to integrate vertminer in 0miner file. This file has been heavily modified and i'm not sure what i must doing to moke possible to use vertminer.

From line 167 of 0miner script file :

Code:

elif [[ $ALGO == X16R || $ALGO == SIB || $ALGO == LYRA2Z || $ALGO == SKUNK || $ALGO == KECCAK || $ALGO == SKEIN || $ALGO == NEOSCRYPT || $ALGO == LYRA2V2 || $ALGO == BITCORE || $ALGO == PHI || $ALGO == LBRY || $ALGO == DMD_GR || $ALGO == GROESTL || $ALGO == MYR_GR || $ALGO == DECRED || $ALGO == SIA || $ALGO == X13 || $ALGO == XEVAN ]]
then
  UCCALGO="-a ${ALGO,,}"
  HCD="${NVOC}"/miners/"${!xminer}"/ccminer
  $LAUNCH $HCD $UCCALGO -o stratum+tcp://"${!xpool}":"${!xport}" -u "${!xaddr}""${!xwallet}""${!xwork}" -p "$MINER_PWD" -i "${!xintensity}" $CCMINER_OPTS ${!xext}

ANother question : Where do the variable $NVOC come from Huh

? Which script launch it at firt time in all theses collection scripts ?

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: papampi on June 24, 2018, 03:27:18 AM

I think you run the 19-2.0 miner update script in 19-2.1 and it created those folders in /home/m1/
You should do this in 19-2.1

Code:

cd /home/m1/NVOC/mining
git submodule update --init --depth 1 --remote miners
cd /home/m1/NVOC/mining/miners
bash nvOC_miner_update.sh

Ok, it's also what I thought, but i can affirm you that this script i execute in /home/m1/NVOC/mining/miners was the script in your new image file of 19.2.1 for testings. I never upload this script in my new system disk.

Finally, i had deleted all miners folders in /home/m1/. BTW, They were empty.

I've not tested TPccmioner, but i remember that last time, when i used terminal profile for testings, i had this problem of several miners software that i use.
I know it take more time to use and mine, but i say again, that some miners have to be recompiled before lauching mining.
I'm actuelly using theses miners sofwares: KTccminer, NAccminer, TPccminer, Bminer, DSTM, Claymore, xmr-stak (sometimes). In this list, i think it's necesary to recompile 3 first softwares.

I tried to recompile last KTccminer but i don't succeded. I post an issue :
https://github.com/KlausT/ccminer/issues/249?_pjax=%23js-repo-pjax-container

I just saw his response :

Quote

You are probably using CUDA 8.0, I think.
There are two ways to fix the error:
You can either remove this line in the Makefile.am:
nvcc_ARCH += -gencode=arch=compute_70,code=sm_70
or you can install a newer CUDA version, like CUDA 9.2
https://developer.nvidia.com/cuda-downloads

Which version of CUDA are installed on last NVOC image ?

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: LuKePicci on June 23, 2018, 06:58:41 PM

I'm not sure what papampi left in the home folder of the full beta testing image, but I'm pretty confident it has the same suggested structure for side-by-side testing proposed before in the beta testing guide for existing 2.0 images but the default directory is "NVOC/mining" instead of "NVOC/testing". Basically this beta image should be a 2.0 image with beta testing environment already set up, if I understand correctly. All the new stuff should still be under /home/m1/NVOC/. BTW a new image without the old legacy code will come, but if you would like to keep the chance of quickly rolling back to 2.0 I think either the manual installation guide of testing env or this 2.1 beta testing image is fine as long as its content is updated the same way by version control.

I used another USB disk for theses tests. So if i want to come back to 19.2.0, i can easily and rapidly. BTW, my 19.2.0 disk also have testing scripts. So, i can say i définitly upgrade version

Quote from: LuKePicci on June 23, 2018, 06:58:41 PM

Uhm, I'm quite confident that if you add at line 955 of 1bash v0019-2.1.0028:

Code:

NICE_ETHASH_EXTENSION_ARGUMENTS=""

it will work.

Edit: just noticed @pap has already added all of them in latest 1bash v0019-2.1.0029 some hours ago.

yes i saw new 1bash.template too on github

I will test again all theses updates newt week end. Now i try to stabilize my RIG in ETH mining with Bminer

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Is it possible to put theses parameters to mine ETHAHS et EQUIHASh with the same miner [BMINER] alternatively ?

I think it's not possible because i tried, and i recieved some messages that indicate the miner bminer can't interpret the equihash "shares" correctly

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: CryptAtomeTrader44 on June 23, 2018, 10:54:48 AM

I think there is a problem with nvOC_miner_update.sh because i can see some forlders that shouldn't be here

Code:

m1@m1-desktop:~$ pwd
/home/m1
m1@m1-desktop:~$ ls
2unix~      Desktop    KTccminer-cryptonight  SILENTminer        xmr-stak
ANXccminer  Downloads  KXccminer              SPccminer          ZENEMYminer
ASccminer   dstm       MSFTccminer            TPccminer
backups     ethminer   NAccminer              Untitled Document
bminer      gocode     NVOC                   vertminer
claymore    KTccminer  nvoc_logs              www

I think you run the 19-2.0 miner update script in 19-2.1 and it created those folders in /home/m1/
You should do this in 19-2.1

Code:

cd /home/m1/NVOC/mining
git submodule update --init --depth 1 --remote miners
cd /home/m1/NVOC/mining/miners
bash nvOC_miner_update.sh

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: CryptAtomeTrader44 on June 23, 2018, 04:53:46 PM

I've not testing dierctory in NVOC directory. I think this is the pb of "nvOC_miner_update.sh" script in the new image file posted by papampi on mega/nz last day.
NVOC/testing/miners was the directory when i used beta1 of nvOC 19-2.1, but i'm using the new complete image file recently posted by papampi that have a different tree structure.
before this day, i used terminal profile for testing on 19-2.0 nvOC, but this is no longer the case.

I'm not sure what papampi left in the home folder of the full beta testing image, but I'm pretty confident it has the same suggested structure for side-by-side testing proposed before in the beta testing guide for existing 2.0 images but the default directory is "NVOC/mining" instead of "NVOC/testing". Basically this beta image should be a 2.0 image with beta testing environment already set up, if I understand correctly. All the new stuff should still be under /home/m1/NVOC/. BTW a new image without the old legacy code will come, but if you would like to keep the chance of quickly rolling back to 2.0 I think either the manual installation guide of testing env or this 2.1 beta testing image is fine as long as its content is updated the same way by version control.

Quote from: CryptAtomeTrader44 on June 23, 2018, 04:53:46 PM

Ok, but i'm not sure that papampi can easily correct this problem because his country have banned nicehash in their great firewall in Iran...
I think the problem is because of esm 3 instead of -esm2 for MPH. I think we need a more variable like ETH_EXTENSION_ARGUMENTS="" but for nicehash_ETH.
Something like that :
#NICE_ETHASH_ARGUMENTS="" # add any additional Claymore miner arguments here

Uhm, I'm quite confident that if you add at line 955 of 1bash v0019-2.1.0028:

Code:

NICE_ETHASH_EXTENSION_ARGUMENTS=""

it will work.

Edit: just noticed @pap has already added all of them in latest 1bash v0019-2.1.0029 some hours ago.

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: LuKePicci on June 23, 2018, 02:58:15 PM

Ok, so your main tree is fine. Please, repeat the same command but this time from inside the 'NVOC/testing/miners' folder. Let's see what is wrong there.

My current directory was

Code:

m1@m1-desktop:~$ cd NVOC/mining/miners/
m1@m1-desktop:~/NVOC/mining/miners$ ls
ANXccminer  bminer    dstm      KTccminer              KXccminer    NAccminer             README.md    SPccminer  vertminer  ZENEMYminer
ASccminer   claymore  ethminer  KTccminer-cryptonight  MSFTccminer  nvOC_miner_update.sh  SILENTminer  TPccminer  xmr-stak

Quote from: LuKePicci on June 23, 2018, 02:58:15 PM

(EDIT: Just a quick info: was NVOC/testing/miners your current directory when you launched the nvOC_miner_update.sh script? )

I've not testing dierctory in NVOC directory. I think this is the pb of "nvOC_miner_update.sh" script in the new image file posted by papampi on mega/nz last day.
NVOC/testing/miners was the directory when i used beta1 of nvOC 19-2.1, but i'm using the new complete image file recently posted by papampi that have a different tree structure.
before this day, i used terminal profile for testing on 19-2.0 nvOC, but this is no longer the case. I hope i'm clear and understandable because my english and that of translator looks bad.

Quote from: LuKePicci on June 23, 2018, 02:58:15 PM

The error with guake usually happens when another instance of guake is still running in the background. Either a reboot or a logout/login cycle should solve.

Well, precisely, it appears when i retart miner, never when i use "sudo service lightdm restart" command

Quote from: LuKePicci on June 23, 2018, 02:58:15 PM

About the NICE_ETHASH with Claymore you need to wait for @papampi to take a look.

Ok, but i'm not sure that papampi can easily correct this problem because his country have banned nicehash in their great firewall in Iran...
I think the problem is because of esm 3 instead of -esm2 for MPH. I think we need a more variable like ETH_EXTENSION_ARGUMENTS="" but for nicehash_ETH.
Something like that :
#NICE_ETHASH_ARGUMENTS="" # add any additional Claymore miner arguments here

But, i saw he unified all algo commands lines in 0miner file. So, it' possibly more complicated to make...Idon't know.

I'll be content with Bminer for now.
I note for about an hour that the temperature acts greatly on the stability of my RIG. In the evening, open window, it is more stable than the rest of the day.

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: CryptAtomeTrader44 on June 23, 2018, 01:20:06 PM

Result of command git status :

Code:

cd NVOC/mining/
m1@m1-desktop:~/NVOC/mining$ git status
On branch 19-2.1
Your branch is up-to-date with 'origin/19-2.1'.
Changes not staged for commit:
  (use "git add ..." to update what will be committed)
  (use "git checkout -- ..." to discard changes in working directory)
  (commit or discard the untracked or modified content in submodules)

        modified:   1bash
        modified:   3main
        modified:   miners (new commits, untracked content)
        modified:   nvOC
        modified:   www/cgi-bin/minerinfo

Untracked files:
  (use "git add ..." to include in what will be committed)

        5_watchdoglog
        6_autotemplog
        Untitled Document
        WTM.json
        WTM_1.json
        WTM_24H_REV
        WTM_BTC_EXCHANGE_RATE
        WTM_current_profit
        WTM_current_revenue
        WTM_switch_history
        WTM_top_coin
        cpuOPT/
        firstBOOT

no changes added to commit (use "git add" and/or "git commit -a")

Ok, so your main tree is fine. Please, repeat the same command but this time from inside the 'NVOC/testing/miners' folder. Let's see what is wrong there.

(EDIT: Just a quick info: was NVOC/testing/miners your current directory when you launched the nvOC_miner_update.sh script? )

The error with guake usually happens when another instance of guake is still running in the background. Either a reboot or a logout/login cycle should solve.

About the NICE_ETHASH with Claymore you need to wait for @papampi to take a look.

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: Rev123 on June 23, 2018, 12:43:21 PM

Hello.
Does the new version support Equihash 144.5 & 192.7? If not then when is planned? THX.

I've created a new issue for that on the nvOC_miners repo
(https://github.com/papampi/nvOC_miners/issues/9)

It will probably get support in time for the upcoming network update of BTG.

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Code:


Software info:
Report ver    :  v0019-2.0.002
nvOC (1bash)  :  nvOC v0019-2.1 - Community Release
nvOC (3main)  :  nvOC v0019-2.1 - Community Release
1bash ver     :  v0019-2.1.0026
3main ver     :  v0019-2.1.0022
5watchdog ver :  v0019-2.0.018
6tempcontrol v:  v0019-2.1.0006
wtm switch ver:  v0019-2.0.0021
Kernel        :  4.4.0-128-generic
OS            :  Ubuntu 16.04.4 LTS
System        :  (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
nvidia driver :  390.67

Hardware info:
Motherboard   :  BIOSTAR Group TB250-BTC PRO
BIOS ver.     :  5.12 06/07/2017
CPU Model     :  Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores     :  2 (Cores + Threads)
Mem Total     :         4011868 kB
Mem Free      :         1394544 kB
Swap Total    :               0 kB
Swap Free     :               0 kB
  Ethernet      :  Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

HDD and Partion info:
NAME     SIZE FSTYPE TYPE ROTA HOTPLUG TRAN VENDOR   MODEL             REV MOUNTPOINT
sda    465.8G        disk    1       1 usb  ATA      WDC WD5000LPCX-2 1A01
├─sda1     9M vfat   part    1       1                                     /media/m1/12D3-A869
└─sda2 465.8G ext4   part    1       1                                     /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0b:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)

1bash settings:
1bash version .............: v0019-2.1.0026
LOCAL or REMOTE ...........: LOCAL
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO

Watchdog ..................: YES
SYSRQ Reboot ..............: YES
Watchdog Cycle ............: 15
GPU Utilization Threshold .: 70
Alternate Pool ............: NO

Temp Control ..............: YES
MANUAL_FAN ................: NO
TARGET_TEMP ...............: 70
__FAN_ADJUST ..............: 3
POWER_ADJUST ..............: 3
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 85
MINIMAL_FAN_SPEED .........: 55
MAXIMAL_FAN_SPEED .........: 100

CLEAR_LOGS_ON_BOOT ........: NO
AUTO_UPDATE ...............: STABLE
AUTO_REBOOT ...............: NO
_Parallax_MODE (upPaste)...: NO

TELEGRAM_MESSAGES .: YES
TELEGRAM_ALERTS ...: YES
TELEGRAM_TYPE .............: papampi
TELEGRAM_TIMEOUT_IN_MINUTES: 60
TELEGRAM_CHATID ...........: CHATID_NOT_SHOWN
TELEGRAM_APIKEY ...........: APIKEY_NOT_SHOWN

HEADLESS MODE:.............: NO
GPUPowerMizerMode_Adjust...: NO
ETH Pill ..................: NO

POWERLIMIT MODE ...........: GPU_SPECIFIC
GPU0 Power Limit ..........: 116
GPU1 Power Limit ..........: 116
GPU2 Power Limit ..........: 116
GPU3 Power Limit ..........: 116
GPU4 Power Limit ..........: 116
GPU5 Power Limit ..........: 116
GPU6 Power Limit ..........: 100
GPU7 Power Limit ..........: 116
GPU8 Power Limit ..........: 116
GPU9 Power Limit ..........: 116
OVERCLOCK MODE ............: GPU_SPECIFIC
GPU0 Core Overclock ........: 110
GPU0 Memory Overclock ......: 1150
GPU1 Core Overclock ........: 110
GPU1 Memory Overclock ......: 1150
GPU2 Core Overclock ........: 110
GPU2 Memory Overclock ......: 1150
GPU3 Core Overclock ........: 110
GPU3 Memory Overclock ......: 1100
GPU4 Core Overclock ........: 110
GPU4 Memory Overclock ......: 1100
GPU5 Core Overclock ........: 110
GPU5 Memory Overclock ......: 1150
GPU6 Core Overclock ........: 110
GPU6 Memory Overclock ......: 1100
GPU7 Core Overclock ........: 110
GPU7 Memory Overclock ......: 1400
GPU8 Core Overclock ........: 110
GPU8 Memory Overclock ......: 1400
GPU9 Core Overclock ........: 110
GPU9 Memory Overclock ......: 1500

GLOBAL WORKERNAME .........: YES
AUTO WORKERNAME ...........: CUSTOM
WORKERNAME ................: ATOMICMINER44
plusCPU ...................: NO

COIN ......................: NICE_ETHASH
ALGO ......................: ETHASH
MINER .....................: CLAYMORE
NICE_ETHASH WORKER ................: ATOMICMINER44
NICE_ETHASH ADDRESS ...............: ...
NICE_ETHASH POOL ..................: daggerhashimoto.usa.nicehash.com
NICE_ETHASH PORT ..................: 3353
ETHASH INTENSITY ..........:

I have errors with NICE_ETHAH using Claymore :

Code:

SCREEN -c /home/m1/NVOC/mining/screenrc-miner -dmSL miner /home/m1/NVOC/mining/miners/claymore/latest/ethdcrminer64 -epool daggerhashimoto.usa.nicehash.com:3353 -ewal 3NnQB7tEeJhLVdgydP9zgkxwPgGQYUqYvE.ATOMICMINER44 -epsw x -mode 1 -dbg -1 -esm 2 -allpools 1 -allcoins 1 SCREEN -c /home/m1/NVOC/mining/screenrc-miner -dmSL miner /home/m1/NVOC/mining/miners/claymore/latest/ethdcrminer64 -epool daggerhashimoto.usa.nicehash.com:3353 -ewal 3NnQB7tEeJhLVdgydP9zgkxwPgGQYUqYvE.ATOMICMINER44 -epsw x -mode 1 -dbg -1 -esm 2 -allpools 1 -allcoins 1

▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ͻ
▒                Claymore's Dual GPU Miner - v11.8               ▒
▒              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             ▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ͼ

ETH: 1 pool is specified
Main Ethereum pool is daggerhashimoto.usa.nicehash.com:3353
AMD OpenCL platform not found
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool, "x" to select GPU
CUDA initializing...

NVIDIA Cards available: 10
CUDA Driver Version/Runtime Version: 9.1/8.0
GPU #0: GeForce GTX 1070, 8119 MB available, 15 compute units, capability: 6.1  (pci bus 1:0:0)
GPU #1: GeForce GTX 1060 6GB, 6078 MB available, 10 compute units, capability: 6.1  (pci bus 2:0:0)
GPU #2: GeForce GTX 1060 6GB, 6078 MB available, 10 compute units, capability: 6.1  (pci bus 3:0:0)
GPU #3: GeForce GTX 1070, 8119 MB available, 15 compute units, capability: 6.1  (pci bus 5:0:0)
GPU #4: GeForce GTX 1060 6GB, 6078 MB available, 10 compute units, capability: 6.1  (pci bus 6:0:0)
GPU #5: GeForce GTX 1070, 8119 MB available, 15 compute units, capability: 6.1  (pci bus 7:0:0)
GPU #6: GeForce GTX 1070, 8119 MB available, 15 compute units, capability: 6.1  (pci bus 8:0:0)
GPU #7: GeForce GTX 1060 6GB, 6078 MB available, 10 compute units, capability: 6.1  (pci bus 9:0:0)
GPU #8: GeForce GTX 1060 6GB, 6078 MB available, 10 compute units, capability: 6.1  (pci bus 10:0:0)
GPU #9: GeForce GTX 1070, 8119 MB available, 15 compute units, capability: 6.1  (pci bus 11:0:0)
Total cards: 10

You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.

ETH: Stratum - connecting to 'daggerhashimoto.usa.nicehash.com' <169.62.79.78> port 3353 (unsecure)
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
ETH: miner-proxy stratum mode
"-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
"-allcoins" option is set, default pools will be used for devfee, check "Readme" file for details.
Watchdog enabled
Remote management (READ-ONLY MODE) is enabled on port 3333

ETH: Stratum - Connected (daggerhashimoto.usa.nicehash.com:3353) (unsecure)
ETH: Authorized
cannot convert blob3 data
cannot convert blob3 data
ETH: Job timeout, disconnect, retry in 20 sec...
GPU0 t=35C fan=55%, GPU1 t=40C fan=55%, GPU2 t=36C fan=55%, GPU3 t=32C fan=55%, GPU4 t=44C fan=55%, GPU5 t=34C fan=55%, GPU6 t=35C fan=55%, GPU7 t=35C fan=55%, GPU8 t=39C fan=55%, GPU9 t=33C fan=55%
    SCREEN -c /home/m1/NVOC/mining/screenrc-miner -dmSL miner /home/m1/NVOC/mining/miners/claymore/latest/ethdcrminer64 -epool daggerhashimoto.usa.nicehash.com:3353 -ewal 3NnQB7tEeJhLVdgydP9zgkxwPgGQYUqYvE.ATOMICMINER44 -epsw x -mode 1 -dbg -1 -esm 2 -allpools 1 -allcoins 1 SCREEN -c /home/m1/NVOC/mining/screenrc-miner -dmSL miner /home/m1/NVOC/mining/miners/claymore/latest/ethdcrminer64 -epool daggerhashimoto.usa.nicehash.com:3353 -ewal 3NnQB7tEeJhLVdgydP9zgkxwPgGQYUqYvE.ATOMICMINER44 -epsw x -mode 1 -dbg -1 -esm 2 -allpools 1 -allcoins 1

▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ͻ
▒                Claymore's Dual GPU Miner - v11.8               ▒
▒              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             ▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ͼ

ETH: 1 pool is specified
Main Ethereum pool is daggerhashimoto.usa.nicehash.com:3353
AMD OpenCL platform not found
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool, "x" to select GPU
CUDA initializing...

NVIDIA Cards available: 10
CUDA Driver Version/Runtime Version: 9.1/8.0
GPU #0: GeForce GTX 1070, 8119 MB available, 15 compute units, capability: 6.1  (pci bus 1:0:0)
GPU #1: GeForce GTX 1060 6GB, 6078 MB available, 10 compute units, capability: 6.1  (pci bus 2:0:0)
GPU #2: GeForce GTX 1060 6GB, 6078 MB available, 10 compute units, capability: 6.1  (pci bus 3:0:0)
GPU #3: GeForce GTX 1070, 8119 MB available, 15 compute units, capability: 6.1  (pci bus 5:0:0)
GPU #4: GeForce GTX 1060 6GB, 6078 MB available, 10 compute units, capability: 6.1  (pci bus 6:0:0)
GPU #5: GeForce GTX 1070, 8119 MB available, 15 compute units, capability: 6.1  (pci bus 7:0:0)
GPU #6: GeForce GTX 1070, 8119 MB available, 15 compute units, capability: 6.1  (pci bus 8:0:0)
GPU #7: GeForce GTX 1060 6GB, 6078 MB available, 10 compute units, capability: 6.1  (pci bus 9:0:0)
GPU #8: GeForce GTX 1060 6GB, 6078 MB available, 10 compute units, capability: 6.1  (pci bus 10:0:0)
GPU #9: GeForce GTX 1070, 8119 MB available, 15 compute units, capability: 6.1  (pci bus 11:0:0)
Total cards: 10

You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.

ETH: Stratum - connecting to 'daggerhashimoto.usa.nicehash.com' <169.62.79.78> port 3353 (unsecure)
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
ETH: miner-proxy stratum mode
"-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
"-allcoins" option is set, default pools will be used for devfee, check "Readme" file for details.
Watchdog enabled
Remote management (READ-ONLY MODE) is enabled on port 3333

ETH: Stratum - Connected (daggerhashimoto.usa.nicehash.com:3353) (unsecure)
ETH: Authorized
cannot convert blob3 data
cannot convert blob3 data
ETH: Job timeout, disconnect, retry in 20 sec...
GPU0 t=34C fan=55%, GPU1 t=39C fan=55%, GPU2 t=36C fan=55%, GPU3 t=32C fan=55%, GPU4 t=42C fan=55%, GPU5 t=33C fan=55%, GPU6 t=35C fan=55%, GPU7 t=34C fan=55%, GPU8 t=38C fan=55%, GPU9 t=33C fan=55%
ETH: Stratum - connecting to 'daggerhashimoto.usa.nicehash.com' <169.62.79.78> port 3353 (unsecure)
ETH: Stratum - Connected (daggerhashimoto.usa.nicehash.com:3353) (unsecure)
ETH: Authorized
cannot convert blob3 data

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Code:

nvOC v0019-2.1 - Community Release

 nvOC v0019-2.1 - Community Release 


No Sockets found in /var/run/screen/S-m1.


(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .

(guake:2379): libglade-WARNING **: unknown attribute `swapped' for .
INFO:guake.guake_app:Logging configuration complete
/usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
  self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)

** (guake:2379): WARNING **: Binding 'F12' failed!
^CTraceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/lib/python2.7/dist-packages/guake/main.py", line 239, in 
    exec_main()
  File "/usr/lib/python2.7/dist-packages/guake/main.py", line 236, in exec_main
    gtk.main()

I already had this mistake of guake a few months ago, at the time I had solved the problems by doing an update.

I thought it worth/merit to be reported

EDIT : It seems that this error don't stop the scritps after 3main, but i've not all tabs in guake terminal if i press F12

Rev123

newbie

Activity: 14

Merit: 0

Quote from: CryptAtomeTrader44 on June 23, 2018, 01:08:52 PM

Quote from: Rev123 on June 23, 2018, 12:43:21 PM

Quote from: papampi on June 20, 2018, 01:39:24 AM

nvOC 19-2.1 beta image, Ubuntu 16.04, Nvidia 390, Date 180619

Thanks to all contributors.

This is a beta image and not fully tested yet.
Please post bugs, errors,questions and any problems here in forum or GitHub issues.

nvOC_V19-2.1beta_U16.04_N390_D180619.img sha256:
cb607c8e028d3bc0a0e274c34b4e0def0c71330053f0c8328120a717e0029938

nvOC_V19-2.1beta_U16.04_N390_D180619.img.zip sha256:
7700dfdfc1cabab8a1dd9816a6322d6653c89943cb63afa59e79f88cfe14a6a9

Zip download size 3.6 Gb, Image size 9 Gb
Auto expand to fill all the volume at first boot.

Download link

Write the image with your favourite image writer of choice
Browse to the small fat partition you can see on the drive, edit 1bash.
Auto start miner is set to no, change it when you are sure all settings are correct.
Attach the SSD/USB/HDD to rig and boot up.
USB install not recommended for mining, only use it for testing.

Good luck.
Keep calm and carry on mining.

Hello.
Does the new version support Equihash 144.5 & 192.7? If not then when is planned? THX.

What are you talking about Huh

I think i missed some informations about algo forks. Is it from bitmain equihash ASIC miners to make forks on equihash algos ?

Yeah, its new algos for ASIC resistance on Equihash. Now such coins as BTCZ, LTZ, SAFE are mined on this algo, then they will be joined by others.

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: LuKePicci on June 23, 2018, 12:23:24 PM

Quote from: CryptAtomeTrader44 on June 22, 2018, 07:28:21 PM

Quote from: LuKePicci on June 15, 2018, 05:31:17 AM

Quote from: CryptAtomeTrader44 on June 13, 2018, 05:44:37 PM

When do you plan to provide a new ISO file ? How much time testing ?

Thank you for all your feedbacks, please test again the miners update procedure, we did some chenges recently, in case of any issue with the testing version please report on github, to avoid confusing people here. As you see lot of things changed, and the testing stage is just at the beginning. The more people test the new beta version, the more we feel confident in declaring it as ready. Please remember to always attach a report anytime you report issues because the report contains version info needed to understand which test version you are running at that time.

A few pages ago, we had discussed updating to a newer version of ubuntu that was to be released last spring. What about these projects?

As I wrote, I think Xubuntu could do the trick and be a little lighter. I know that leenoox also wanted to propose many other systems even more minimalist but I do not know if he finally gave up his idea to lighten the image of nvOC.

A lot of work has been done to decople the whole nvOC thing, including miners and firstboot management from Ubuntu as a base OS. Now, if someone in this nice community would like to work on an image built on top of Xubuntu/Lubuntu or whatever is at least "doable" without taking care of patching nvOC scripts. All scripts are now portable enough, I think, the only work to do in case someone want to run it on a different OS is to install nvidia and motherboard support drivers, together with all kind of system optimizations he want. In other words, what @leenux was proposing is now an easy task to deal with, for anyone, BUT keep in mind that, as @leenux pointed out in this discussion on GitHub, it would be quite impossible for anybody here to be able to support you if you're using an image which is custom built by you.

Thank you for all your answers LukePicci.

I've not finished all the tests on the new image nvOC 19-2.1. I have nice_ALGOS coin in WTM-switching to test.

I've not capacity to make mon own distro. I know that it could be more difficult to use if the system is not a large public adopted one.

ZEC was the Default coin i saw in 1bash in this ISO file

A few month ago, i post a message that evoke this portability, and finally, you, all scipters and devellopers, are very close to be able to make a sort of package ! Good jobs !

Result of command git status :

Code:

cd NVOC/mining/
m1@m1-desktop:~/NVOC/mining$ git status
On branch 19-2.1
Your branch is up-to-date with 'origin/19-2.1'.
Changes not staged for commit:
  (use "git add ..." to update what will be committed)
  (use "git checkout -- ..." to discard changes in working directory)
  (commit or discard the untracked or modified content in submodules)

        modified:   1bash
        modified:   3main
        modified:   miners (new commits, untracked content)
        modified:   nvOC
        modified:   www/cgi-bin/minerinfo

Untracked files:
  (use "git add ..." to include in what will be committed)

        5_watchdoglog
        6_autotemplog
        Untitled Document
        WTM.json
        WTM_1.json
        WTM_24H_REV
        WTM_BTC_EXCHANGE_RATE
        WTM_current_profit
        WTM_current_revenue
        WTM_switch_history
        WTM_top_coin
        cpuOPT/
        firstBOOT

no changes added to commit (use "git add" and/or "git commit -a")

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: Rev123 on June 23, 2018, 12:43:21 PM

Quote from: papampi on June 20, 2018, 01:39:24 AM

nvOC 19-2.1 beta image, Ubuntu 16.04, Nvidia 390, Date 180619

Thanks to all contributors.

This is a beta image and not fully tested yet.
Please post bugs, errors,questions and any problems here in forum or GitHub issues.

nvOC_V19-2.1beta_U16.04_N390_D180619.img sha256:
cb607c8e028d3bc0a0e274c34b4e0def0c71330053f0c8328120a717e0029938

nvOC_V19-2.1beta_U16.04_N390_D180619.img.zip sha256:
7700dfdfc1cabab8a1dd9816a6322d6653c89943cb63afa59e79f88cfe14a6a9

Zip download size 3.6 Gb, Image size 9 Gb
Auto expand to fill all the volume at first boot.

Download link

Write the image with your favourite image writer of choice
Browse to the small fat partition you can see on the drive, edit 1bash.
Auto start miner is set to no, change it when you are sure all settings are correct.
Attach the SSD/USB/HDD to rig and boot up.
USB install not recommended for mining, only use it for testing.

Good luck.
Keep calm and carry on mining.

Hello.
Does the new version support Equihash 144.5 & 192.7? If not then when is planned? THX.

What are you talking about Huh

I think i missed some informations about algo forks. Is it from bitmain equihash ASIC miners to make forks on equihash algos ?

Rev123

newbie

Activity: 14

Merit: 0

Quote from: papampi on June 20, 2018, 01:39:24 AM

nvOC 19-2.1 beta image, Ubuntu 16.04, Nvidia 390, Date 180619

Thanks to all contributors.

This is a beta image and not fully tested yet.
Please post bugs, errors,questions and any problems here in forum or GitHub issues.

nvOC_V19-2.1beta_U16.04_N390_D180619.img sha256:
cb607c8e028d3bc0a0e274c34b4e0def0c71330053f0c8328120a717e0029938

nvOC_V19-2.1beta_U16.04_N390_D180619.img.zip sha256:
7700dfdfc1cabab8a1dd9816a6322d6653c89943cb63afa59e79f88cfe14a6a9

Zip download size 3.6 Gb, Image size 9 Gb
Auto expand to fill all the volume at first boot.

Download link

Write the image with your favourite image writer of choice
Browse to the small fat partition you can see on the drive, edit 1bash.
Auto start miner is set to no, change it when you are sure all settings are correct.
Attach the SSD/USB/HDD to rig and boot up.
USB install not recommended for mining, only use it for testing.

Good luck.
Keep calm and carry on mining.

Hello.
Does the new version support Equihash 144.5 & 192.7? If not then when is planned? THX.

Topic: [OS] nvOC easy-to-use Linux Nvidia Mining - page 22. (Read 418244 times)