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

uga

newbie

Activity: 6

Merit: 0

Quote from: papampi_2 on July 21, 2018, 09:03:43 AM

Quote from: uga on July 21, 2018, 01:58:46 AM

I have also just tried on the new beta version as I was under the impression that the new v0_3 version EWBF would be on there, but it does not look like it is.

Any help would be greatly appreciated!

Cheers

You should update the beta image to latest

Update beta image to latest and it has ewbf v0.3:

Code:

bash ~/NVOC/mining/nvOC upgrade

Or:

Code:

cd ~/NVOC/mining
git pull

Remember, latest default 1bash is changed to 1bash.template
Edit and save it as 1bash, reboot.

Thank you so much for your help - greatly appreciated!
I have run the script:

Code:

cd ~/NVOC/mining
git pull

And it looks like it has run the update.
I had to rename 1bash, 3main and another file in the www directory for the update to generate the 1bash.template and run smoothly.

However, I am still unable to run the miner, I get the following error message:

Code:

/home/m1/NVOC/mining/2unix: line 48: 3572 Terminated
/home/m1/NVOC/mining/2unix: line 31: /home/m1/NVOC/mining/1bash.template: No such file or directory

I then copied 1bash and renamed it 1bash.template, so that I have both a 1bash and 1bash.template, but I still get the issue:

Code:

/home/m1/NVOC/mining/2unix: line 48: 3572 Terminated

Not sure if it matters, but the number before Terminated (above 3572) changes and goes in an increasing pattern.

It actually seems to be an issue I face with the beta version even before I run the script to upgrade to the latest.
I have tried a couple coins, but it has no impact.

Any insight into how to address this?
I am in way above my head here

Thanks guys!

P.S: Also wondering about something: when I look into the miner folder, for some reason I cannot locate a EWBF folder - Not sure if this is normal? I had a look to see if it was perhaps burried into another subfolded in the miner folder but no luck.

gs777

member

Activity: 118

Merit: 10

Just out of curiosity
Is anyone mining BCI and
what is your setup for this?

LuKePicci

jr. member

Activity: 128

Merit: 1

Sure you can. zpool, nicehash and mph are some kind of special pools that require special configurations so they have their own sections in 1bash. If you are on ethermine (I'm on ethermine too), you just need to setup ETH coin with ethermine pool settings. There is a quite long list of coin settings, scroll down to ETH and set the pool address, your worker name, wallet address and port and you're done. If you see settings for mph in there,, they're just examples of what you should put in these configs for a generic pool.

Ventero

newbie

Activity: 15

Merit: 0

Hello guys,

I was looking into bash template here https://github.com/papampi/nvOC_by_fullzero_Community_Release/blob/release/1bash.template

I would like to use ethermine.org and I did not find option how to setup it for this pool. Is it possible or this OS works only with zpool, nicehash and miningpoolhub?

I was thinking if I can add my pool here, I'm not sure

ALT_POOL="NO" # YES or NO, Set to YES if you want to enable poolswitch.
# Switch to alternate pool if main pool goes down.
# Dual mining and salfter auto switch not supported.
# If pool goes down, poolswitch will stop/disable wtm auto switch and will enable/start it after pool comes up to prevent coin data mixed up.
# If main pool use username, alternate pool should use same username and workername.
# If anonymous mining with coin address alternate pool should use same.
# If ALT_POOL="YES" add as follow to your coins data (order should be the same).

###alternate pool setup example:
#ZCL_POOL_1="europe.equihash-hub.miningpoolhub.com"
#ZCL_PORT_1="20575"
#ZCL_POOL_2="zcl.suprnova.cc"
#ZCL_PORT_2="4042"
#ZCL_POOL=$ZCL_POOL_1 #Dont edit this
#ZCL_PORT=$ZCL_PORT_1 #Dont edit this

Thanks for advice ;-)

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: uga on July 21, 2018, 01:58:46 AM

I have also just tried on the new beta version as I was under the impression that the new v0_3 version EWBF would be on there, but it does not look like it is.

Any help would be greatly appreciated!

Cheers

You should update the beta image to latest

Update beta image to latest and it has ewbf v0.3:

Code:

bash ~/NVOC/mining/nvOC upgrade

Or:

Code:

cd ~/NVOC/mining
git pull

Remember, latest default 1bash is changed to 1bash.template
Edit and save it as 1bash, reboot.

uga

newbie

Activity: 6

Merit: 0

I have also just tried on the new beta version as I was under the impression that the new v0_3 version EWBF would be on there, but it does not look like it is.

Any help would be greatly appreciated!

Cheers

uga

newbie

Activity: 6

Merit: 0

Hi guys,

First a huge thank you to the dev team and everyone who has contributed here - amazing result!
I have been running NVOC for a few months and it has been mega stable.
I went on a 4months streak without a reboot or anything.

I am running version 2.0 and am trying to add EWBF v0_3 to mine BTG on their new algo.
I am a linux newbie and struggling to get this done.

Would anyone be able to share some tips/a resolution as to how to get the new EWBF miner on so I can mine?

Thanks a lot guys.

Cheers

Cjm_258

newbie

Activity: 21

Merit: 0

Can someone please post the link that walks me through how to setup to mine with nicehash.

Thank you

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: ?? on ??

Quote from: CryptAtomeTrader44 on July 14, 2018, 04:36:13 AM

Quote from: ?? on ??

No, and its just for NICE_ETHASH.

Bminer is the best miner for ethash, but not for ethash on nicehash.
I made some tests and i discovered on the web and on my RIG that claymore is better for NICE_ETASH.

No pb with ETC or ETH on mininpoolhub with bminer, but bminer relaunch dag every 10-15 minutes on NICE_ETASH. It's a real problem.

@Luckpicci, is it possible to mine ethash on nicehash only with Claymore and other ethash coins with Bminer ?

Have you set claymore recommended arguments for nice_eth?
For claymore you should add:

Code:

NICE_ETHASH_EXTENSION_ARGUMENTS="-esm 3 -allpools 1 -estale 0 "

P.S: My account is hacked waiting for unblocking by forum admins

Tigel

newbie

Activity: 66

Merit: 0

Quote from: gs777 on July 17, 2018, 03:12:43 AM

Quote from: Tigel on July 17, 2018, 01:06:32 AM

I still have the old problem lurking around even with latest beta, i.e. my home network freezes completely, usually roughly after one day period. After unplugging nvOC miners one by one the network recovers. I remember this would be an Ubuntu update issue but shouldn't the Ubuntu updates be disabled by default?
Any ideas why this could happen?

I am using 19-20 and latest beta (nvOC V19-2.1 beta Ubuntu-16.04 Nvidia-390 2018.07.07) in my rigs. Today this happened with latest beta which made me worry. Sad

Yes, I use cheap switches and already ordered new ones.

--
Tigel

I used to have same problem.
After all I find out the problem was with My WiFi/wired router.
So, I connected all my rigs through wired Ethernet switch (TP-Link TL-SG105)
It fixed network freezes issue.

It's just weird that this does not happen with Windows machines on the network but maybe they behave differently from network point of view.

--
Tigel

gs777

member

Activity: 118

Merit: 10

Quote from: Tigel on July 17, 2018, 01:06:32 AM

I still have the old problem lurking around even with latest beta, i.e. my home network freezes completely, usually roughly after one day period. After unplugging nvOC miners one by one the network recovers. I remember this would be an Ubuntu update issue but shouldn't the Ubuntu updates be disabled by default?
Any ideas why this could happen?

I am using 19-20 and latest beta (nvOC V19-2.1 beta Ubuntu-16.04 Nvidia-390 2018.07.07) in my rigs. Today this happened with latest beta which made me worry. Sad

Yes, I use cheap switches and already ordered new ones.

--
Tigel

I used to have same problem.
After all I find out the problem was with My WiFi/wired router.
So, I connected all my rigs through wired Ethernet switch (TP-Link TL-SG105)
It fixed network freezes issue.

Tigel

newbie

Activity: 66

Merit: 0

I still have the old problem lurking around even with latest beta, i.e. my home network freezes completely, usually roughly after one day period. After unplugging nvOC miners one by one the network recovers. I remember this would be an Ubuntu update issue but shouldn't the Ubuntu updates be disabled by default?
Any ideas why this could happen?

I am using 19-20 and latest beta (nvOC V19-2.1 beta Ubuntu-16.04 Nvidia-390 2018.07.07) in my rigs. Today this happened with latest beta which made me worry. Sad

Yes, I use cheap switches and already ordered new ones.

--
Tigel

LuKePicci

jr. member

Activity: 128

Merit: 1

The new EWBF v0.3 is already in miners repo, we have some doubts on how we should handle the new algo variants: should each variant be meant as a different algo or not? @papampi worked on a patch for new ewbf but it is pending since WTM has not listed the new algo yet and there is no common agreement on which is the new algo name, Zhash, EquihashBTG, Equihash-BTG, Equihash <144,5> and so on. Meanwhile the new ewbf is a totally different miner from the old versions and does not support the classic Equihash, but is shares a similar versioning scheme so we currently have ewbf 0.3, which is the new one, and ewbf 0.3.3 and 0.3.4, the old ones… if you have any suggestion on this topic you're welcome, just discuss it on the github PR page here.

Rev123

newbie

Activity: 14

Merit: 0

Hello

Is there a EWBF v0.3 for 144.5 & 192.7 algorithms in nvOC V19-2.1 beta Ubuntu-16.04 Nvidia-390 2018.07.07?
If not, when about it can be expected?
THX

LuKePicci

jr. member

Activity: 128

Merit: 1

> Specific ethash miner for NICE_ETHASH

It is feasible patching nvOC to handle NICE_ETHASH as using a different algo, which I think is not such a good thing. Do you really think there may be someone which has both NICE_ETHASH and, for instance, ETH in its auto-switching coins list?

> I see that scripts now update themselves from the start of the terminal at logon

They doesn't update at logon. They only updates when you manually gives 'bash nvOC upgrade' command.
If you are referring to the firstboot of latest nvOC full os images then no update take place, the latest nvOC tree from your branch of choice is installed.
Don't worry, the default 'release' branch won't be updated so often as it is now during beta, until it will actually contain a released stable version.

> keeping 1bash up-to-date

It is not true in general that you need to update your customized 1bash each time you perform an nvOC version upgrade. You will see a warning during nvOC startup if and only if the 1bash.template has been updated with potentially breaking changes, but still scripts will try to run anyway.
If you need some new available settings from the new 1bash.template or you are getting errors using your old 1bash then it will be the time to update your 1bash with 1bash.template contents. You can do it very easily with any graphical text merge tool such as Meld, Beyond Compare, KDiff3.

> Minerinfo shown values

I don't know exactly what values are you referring to but not all values are available in all nvOC configurations, some will only show up with particular settings or when there is support for parsing the miner output. I have some ideas on that but don't know if I will have time to experiment with these.

> Compiling miners

I see you run nvOC_miner_update.sh manually, avoid doing so in general. Keep in mind that in such a way you are not fetching updated version of the nvOC_miner repo, that script only updates your installed miners with what is contained into fetched tarballs. It should have been renamed to something different, I agree, maybe in future.
So, if you do 'bash nvOC miners-upgrade' you will be sure to upgrade your miners repo installers and get the patched version.
There is a README inside the miners folder with instructions on how to contribute to nvOC_miners repo by updating or adding miners, would be awesome if you or anybody here would like to help be keeping the collection up-to-date, for example with KT 8.21

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

I see that scripts now update themselves from the start of the terminal at logon. It's a good thing, but I'd like it to be easier to update the bash file 1 anyway.

Would you have an order that would allow me to recover the maximum value of the old 1bash without touching the new settings added because it makes me tired to redo this file each time. The Diff command can be?

I also find that minerinfo does not work properly because it lacks some information that is not displayed when loading the page. In the script there are a lot more values than what I see in my navifgator.

I already have some errors on ASccminer and KTccminer. it seems that Klaust post a cuda 9 (8.21) version but it can disabled by editing the makefile like i post a few page ago. the KTccminer in nvOC_miners repository is outdated (8.20).

Code:

Compiling alexis ccminer
This could take a while ...
Submodule 'ASccminer/src' (https://github.com/alexis78/ccminer) registered for p                                                                                      ath 'src'
Cloning into 'ASccminer/src'...
remote: Counting objects: 329, done.
remote: Compressing objects: 100% (283/283), done.
remote: Total 329 (delta 31), reused 257 (delta 25), pack-reused 0
Receiving objects: 100% (329/329), 30.86 MiB | 476.00 KiB/s, done.
Resolving deltas: 100% (31/31), done.
Checking connectivity... done.
fatal: reference is not a tree: aafe2d19b6d9eb07d942d70ced3049e9aed1c241
Unable to checkout 'aafe2d19b6d9eb07d942d70ced3049e9aed1c241' in submodule path                                                                                       'src'
Update from shallow clone failed, fetching old commits...
remote: Counting objects: 3903, done.
remote: Compressing objects: 100% (1169/1169), done.
remote: Total 3903 (delta 2810), reused 3786 (delta 2693), pack-reused 0
Receiving objects: 100% (3903/3903), 26.53 MiB | 495.00 KiB/s, done.
Resolving deltas: 100% (2810/2810), completed with 99 local objects.
remote: Counting objects: 24, done.
remote: Total 24 (delta 0), reused 0 (delta 0), pack-reused 24
Unpacking objects: 100% (24/24), done.
......
......
.....
......
ccminer.cpp:45:26: fatal error: cuda_runtime.h: No such file or directory
compilation terminated.
Makefile:1398: recipe for target 'ccminer-ccminer.o' failed
make[2]: *** [ccminer-ccminer.o] Error 1
make[2]: *** Waiting for unfinished jobs....
mv -f .deps/ccminer-bench.Tpo .deps/ccminer-bench.Po
api.cpp: In function ‘void gpuhwinfos(int)’:
api.cpp:286:31: warning: format ‘%lu’ expects argument of type ‘long unsigned in                                                                                      t’, but argument 8 has type ‘uint32_t {aka unsigned int}’ [-Wformat=]
   cgpu->gpu_sn, cgpu->gpu_desc);
                               ^
api.cpp:286:31: warning: format ‘%lu’ expects argument of type ‘long unsigned in                                                                                      t’, but argument 8 has type ‘uint32_t {aka unsigned int}’ [-Wformat=]
mv -f .deps/ccminer-pools.Tpo .deps/ccminer-pools.Po
mv -f .deps/ccminer-api.Tpo .deps/ccminer-api.Po
mv -f .deps/ccminer-util.Tpo .deps/ccminer-util.Po
mv -f .deps/ccminer-bignum.Tpo .deps/ccminer-bignum.Po
make[2]: Leaving directory '/home/m1/NVOC/mining/miners/ASccminer/src'
Makefile:1558: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/m1/NVOC/mining/miners/ASccminer/src'
Makefile:545: recipe for target 'all' failed
make: *** [all] Error 2
cp: cannot stat '/home/m1/NVOC/mining/miners/ASccminer/src/ccminer': No such fil                                                                                      e or directory
Finished compiling alexis ccminer



m1@m1-desktop:~/NVOC/mining/miners$ ./nvOC_miner_update.sh
Updating miners for nvOC V0019-2.1
Will check and restart miner if needed

Checking EWBF Equihash miner
EWBF Equihash miner is already up-to-date

Checking Equihash DSTM zm miner 0.6.1
DSTM zm miner is already up-to-date

Checking Z-Enemy 1.10
z-enemy is already up-to-date

Checking xmr-stak 2.4.4
xmr-stak is already up-to-date

Checking Silent Miner 1.1.0
Silent Miner is already up-to-date

Checking Claymore v11.8
Claymore is already up-to-date

Checking SP Mod ccminer-1.8.2
SPccminer is already up-to-date

Checking alexis ccminer
ASccminer is already up-to-date

Checking Krnlx ccminer
KXccminer is already up-to-date

Checking Tpruvot ccminer-2.2.5
Tpruvot ccminer is already up-to-date

Checking KlausT ccminer 8.20
KlausT ccminer is already up-to-date

Checking Vertminer v1.0-stable.2 Release
Vertminer is already up-to-date

Checking nanashi-ccminer-2.2-mod-r2
nanashi-ccminer is already up-to-date

Checking Ethminer 0.14.0
ethminer is already up-to-date

Checking KTccminer-cryptonight v2.06
KTccminer-cryptonight is already up-to-date

Checking Equihash Bminer 8.0.0
Bminer is already up-to-date

Checking ANXccminer (git@cd6fab68823e247bb84dd1fa0448d5f75ec4917d)
ANXccminer is already at up-to-date

Checking MSFT Tpruvot ccminer-2.2.5 (RVN)
MSFTccminer is already up-to-date

Checking SUPRminer 1.5
SUPRminer is already up-to-date

Checking cpuminer-opt
cpuminer is already up-to-date


Extracting and checking new miners for nvOC-v0019-2.x finished


Do you want to re-compile your miners (y/N)?  y

Checking if bn.h bignum error is fixed for compiling miners or not
bn.h openssl already fixed for compiling miners

Select miners to compile (multiple comma separated values: 1,6,7)
1 - ASccminer
2 - KTccminer
3 - KTccminer-cryptonight
4 - KXccminer
5 - NAccminer
6 - SPccminer
7 - TPccminer
8 - vertminer
9 - ANXccminer
C - cpuminer
R - MSFTccminer (RVN)
U - SUPRminer
X - xmr-stak

Do your Choice: [A]LL [1] [2] [3] [4] [5] [6] [7] [8] [9] [C] [R] [U] [X] [E]xit                                                                                      : 2
2
Compiling KlausT ccminer
 This could take a while ...
Submodule 'KTccminer/src' (https://github.com/KlausT/ccminer.git) registered for                                                                                       path 'src'
Cloning into 'KTccminer/src'...
remote: Counting objects: 294, done.
remote: Compressing objects: 100% (268/268), done.
remote: Total 294 (delta 47), reused 135 (delta 21), pack-reused 0
Receiving objects: 100% (294/294), 13.26 MiB | 452.00 KiB/s, done.
Resolving deltas: 100% (47/47), done.
Checking connectivity... done.
fatal: reference is not a tree: c5ab73837c8024f1e6b8fe7ad46e6881fb8366e6
Unable to checkout 'c5ab73837c8024f1e6b8fe7ad46e6881fb8366e6' in submodule path                                                                                       'src'
Update from shallow clone failed, fetching old commits...
remote: Counting objects: 10566, done.
remote: Compressing objects: 100% (2712/2712), done.
remote: Total 10566 (delta 8016), reused 10340 (delta 7790), pack-reused 0
Receiving objects: 100% (10566/10566), 68.20 MiB | 454.00 KiB/s, done.
Resolving deltas: 100% (8016/8016), completed with 152 local objects.
remote: Counting objects: 18, done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 18 (delta 0), reused 18 (delta 0), pack-reused 0
Unpacking objects: 100% (18/18), done.

nvcc fatal   : Unsupported gpu architecture 'compute_70'
Makefile:1898: recipe for target 'cuda_groestlcoin.o' failed
make[2]: *** [cuda_groestlcoin.o] Error 1
make[2]: *** Waiting for unfinished jobs....
mv -f .deps/ccminer-nvml.Tpo .deps/ccminer-nvml.Po
mv -f .deps/ccminer-groestlcoin.Tpo .deps/ccminer-groestlcoin.Po
mv -f sph/.deps/ccminer-fugue.Tpo sph/.deps/ccminer-fugue.Po
make[2]: Leaving directory '/home/m1/NVOC/mining/miners/KTccminer/src'
Makefile:1452: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/m1/NVOC/mining/miners/KTccminer/src'
Makefile:504: recipe for target 'all' failed
make: *** [all] Error 2
cp: cannot stat '/home/m1/NVOC/mining/miners/KTccminer/src/ccminer': No such fil                                                                                      e or directory

Finished compiling KlausT ccminer

Translated from French with Google translation

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: ?? on ??

No, and its just for NICE_ETHASH.

Bminer is the best miner for ethash, but not for ethash on nicehash.
I made some tests and i discovered on the web and on my RIG that claymore is better for NICE_ETASH.

No pb with ETC or ETH on mininpoolhub with bminer, but bminer relaunch dag every 10-15 minutes on NICE_ETASH. It's a real problem.

@Luckpicci, is it possible to mine ethash on nicehash only with Claymore and other ethash coins with Bminer ?

LuKePicci

jr. member

Activity: 128

Merit: 1

I would like to check the miner command line you get printed in the terminal/miner-log when the miner is launched.

LuKePicci

jr. member

Activity: 128

Merit: 1

Does it work with a different miner?

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: Brainfruit_Me on July 11, 2018, 01:48:39 PM

Quote from: LuKePicci on July 11, 2018, 01:16:04 PM

I think it requires cuda 9.1, so we can add it but you will need to provide cuda-9-1 runtime otherwise it won't work.

Okay, yeah maybe that's why it wasn't working for me. I've never used Cuda before, does it operate independently of our nvoc bash files?
I've compiled a couple miners before but they were always straight forward

Yes, it is independent from nvOC scripts, but the last image is bundled with nvidia 390 distribution specific drivers. which means you need distribution specific cuda runtime packages.
Distribution specific means: add nvidia ppa to ubuntu and install packages from those repo. Do not install generic cuda package, always install cuda-X-Y packages to keep all versions side by side. The cuda 8.0 currently installed into all past nvOC images up to now is not installed by distribution specific package but from standalone runfile, and it was a mistake since nvidia does not support distribution spec. driver + standalone runfile cuda combination, they have to be both distribution specific or standalone runfile. So to manually add cuda-9-1 to latest nvOC images you need to:
-add nvidia cuda ppa for ubuntu 16.04 distribution specific packages
-don't need to add nvidia driver ppa for ubuntu 16.04 distribution specific packages
since it is added already into nvOC images
- install cuda-9-1 package, it will also update driver to nvidia-396
-WARNING: do it from tty session otherwise during driver install apt will kill the desktop environment and therefore also apt itself, stopping abnormally the driver install
-reboot to load the new driver module

From now on you have both cuda 8.0 and 9.1 but your /usr/local/cuda symlink will point to /usr/local/cuda-9.1, so every miner unless differently set up will run under 9.1. Support for different cuda runtimes is coming, I hope for next nvOC images also.

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