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

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.

Tigel

newbie

Activity: 66

Merit: 0

Code:

[quote author=papampi link=topic=1854250.msg41714773#msg41714773 date=1530989106]
[center][size=20pt][b][color=green]nvOC V19-2.1 beta Ubuntu-16.04 Nvidia-390 2018.07.07[/color][/b][/size]
[/center]

Download link: [url=https://mega.nz/#!od1HGYjZ!kMp4ihj2TK81hNz6GkBR1--UkPhNf-JmdGHHEeDw3Ig][u]nvOC_V19-2.1beta_U16.04_N390_D180707.img.zip[/u][/url]

[/quote]

tzconfig is not installed, sure I can just download it but do you have plans to include it in image? Or is it replaced by something else?

m1@m1-desktop:~$ sudo dpkg-reconfigure tzconfig
dpkg-query: package 'tzconfig' is not installed and no information is available

nvm, it's tzdata Wink

Naming rigs based on ip is something I do manually for all my rigs. Helps to know where I am when I ssh back and forth between rigs.

--
Tigel

Brainfruit_Me

newbie

Activity: 23

Merit: 0

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

LuKePicci

jr. member

Activity: 128

Merit: 1

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.

Brainfruit_Me

newbie

Activity: 23

Merit: 0

Can anyone help me with a compile for Z-enemy 1.12a? Papampi add it to the miner update??

Trying to get some better hash rates on LUX, PHI2 algo.

LuKePicci

jr. member

Activity: 128

Merit: 1

New EWBF is quite different and will require modifications in nvOC scrpts. Also, there are two different binaries for cuda 8.0 and 9.x.

gs777

member

Activity: 118

Merit: 10

Quote from: papampi on July 08, 2018, 04:46:12 AM

Quote from: gs777 on July 07, 2018, 11:01:47 PM

Is anyone know does it include EWBF v0.3
for equihas 144.5 mining
Huh

Is the new 0.3 version command line arguments are same as before or there are new options?
Can you please post new arguments if its changed, so we can make the changes in 0miner and 1bash if needed.

Hi Papampi!

Unfortunately I don't know much about EWBF v0.3 myself
but that's what I found in the 'EWBF's Cuda Equihash Miner' tread

Code:

miner --algo 144_5 --server us-east.equihash-hub.miningpoolhub.com --port 20595 --pass x --user me.myrig --pers BgoldPoW

and

Code:

+-------------------------------------------------+
| EWBF's Eqihash CUDA miner. v0.3 |
+-------------------------------------------------+
20:15:04 INFO: Current pool: btg.suprnova.cc:8866
20:15:04 INFO: Selected pools: 1
20:15:04 INFO: Algorithm: 144_5 "BgoldPoW"
20:15:04 INFO: Devices: User defined.
20:15:04 INFO: Temperature limit: 90
20:15:04 INFO: Api: Disabled
---------------------------------------------------

hope it will be helpful

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: LuKePicci on July 07, 2018, 02:53:18 PM

Quote from: papampi on July 07, 2018, 01:45:06 PM

Edit firstboot.json to enable/disable auto_expand and recompile miners on first boot. ("true" or "false")

You can set auto_expand to "true" or "false" depending on your choice, while recompile_miners can be either "false" if you do not intend to let any miner be recompiled during first image boot, or a list of miners do you want to recompile, written in the same way as you are used to do with the nvOC_update_miner.sh. For exampt recompile_miners:"7 U" will recompile TPccminer(7) and SUPPRminer(U), recompile_miners:"A" will recompile all(A) miners. The letter/number associated to each recompilable miner depends on the latest nvOC_miner_update.sh script you find in the nvOC_miners repository on GitHub.

Exactly, enter the nvOC_Miner_Update.sh script choice menu in the readme because I was caught in a loop that asked me to choose at first boot.

I VOLUNTARILY chose to recompile ALL of the software on my machine to check if the mining software update script runs well and does the job properly.

On the other hand, it seems that there are problems to clone and compile some mining software. I copied below extracts from the log displayed in terminal console that is displayed after reboot.

Code:

Sun Jul 8 08:12:36 MST 2018 - nvOC FirstBoot start

+ Looking for the small fat partition
/media/m1/12D3-A869 is a mountpoint

+ Parsing firstboot.json
++ selected branch: 'release'
++ nvOC will install to: '/home/m1/NVOC/mining'

+ Wait for internet connection to continue nvOC setup
Connection to google.com 443 port [tcp/https] succeeded!

+ Cloning 'release' nvOC branch into /home/m1/NVOC/mining
++ Checking if selected branch actually exists...
0a8378ceb49c778f19134af18f421dba7f42ace3 refs/heads/release
++ /home/m1/NVOC/mining already exists, cleaning up
Cloning into '/home/m1/NVOC/mining'...
remote: Counting objects: 40, done.
remote: Compressing objects: 100% (36/36), done.
remote: Total 40 (delta 7), reused 15 (delta 1), pack-reused 0
Checking connectivity... done.

+ Updating miners submodule
++ No cache found in /home/m1/.miners-cache
Submodule 'miners' (https://github.com/papampi/nvOC_miners.git) registered for path 'miners'
Cloning into 'miners'...
Submodule path 'miners': checked out 'ee963aa25b6b8d4f8299a2d5f13749fc6bdee498'

+ Checking free space
++ Available free space in root partition: 178460508 KB

+ Installing miners (recompile: A)
~/NVOC/mining/miners ~
Updating miners for nvOC V0019-2.1
Will check and restart miner if needed

Checking Equihash DSTM zm miner 0.6.1
cat: /home/m1/NVOC/mining/miners/dstm/latest/version: No such file or directory
Extracting DSTM zm miner

Checking Z-Enemy 1.10
cat: /home/m1/NVOC/mining/miners/ZENEMYminer/version: No such file or directory
Extracting z-enemy

Checking xmr-stak 2.4.4
cat: /home/m1/NVOC/mining/miners/xmr-stak/version: No such file or directory
Extracting xmr-stak

Checking Silent Miner 1.1.0
cat: /home/m1/NVOC/mining/miners/SILENTminer/version: No such file or directory
Extracting Silent Miner

Checking Claymore v11.8
cat: /home/m1/NVOC/mining/miners/claymore/latest/version: No such file or directory
Extracting Claymore

Checking SP Mod ccminer-1.8.2
cat: /home/m1/NVOC/mining/miners/SPccminer/version: No such file or directory
Extracting SPccminer

Checking alexis ccminer
cat: /home/m1/NVOC/mining/miners/ASccminer/version: No such file or directory
Extracting ASccminer

Checking Krnlx ccminer
cat: /home/m1/NVOC/mining/miners/KXccminer/version: No such file or directory
Extracting KXccminer

Checking Tpruvot ccminer-2.2.5
cat: /home/m1/NVOC/mining/miners/TPccminer/version: No such file or directory
Extracting Tpruvot

Checking KlausT ccminer 8.20
cat: /home/m1/NVOC/mining/miners/KTccminer/version: No such file or directory
Extracting Klaust ccminer

Checking Vertminer v1.0-stable.2 Release
cat: /home/m1/NVOC/mining/miners/vertminer/version: No such file or directory
Extracting vertminer

Checking nanashi-ccminer-2.2-mod-r2
cat: /home/m1/NVOC/mining/miners/NAccminer/version: No such file or directory
Extracting nanashi ccminer

Checking Ethminer 0.14.0
cat: /home/m1/NVOC/mining/miners/ethminer/latest/version: No such file or directory
Extracting and making changes for Ethminer

Checking KTccminer-cryptonight v2.06
cat: /home/m1/NVOC/mining/miners/KTccminer-cryptonight/version: No such file or directory
Extracting KTccminer-cryptonight

Checking Equihash Bminer 8.0.0
cat: /home/m1/NVOC/mining/miners/bminer/latest/version: No such file or directory
Extracting Bminer

Checking ANXccminer (git@cd6fab68823e247bb84dd1fa0448d5f75ec4917d)
cat: /home/m1/NVOC/mining/miners/ANXccminer/version: No such file or directory
Extracting ANXccminer

Checking MSFT Tpruvot ccminer-2.2.5 (RVN)
cat: /home/m1/NVOC/mining/miners/MSFTccminer/version: No such file or directory
Extracting MSFT Tpruvot ccminer

Checking SUPRminer 1.5
cat: /home/m1/NVOC/mining/miners/SUPRminer/version: No such file or directory
Extracting SUPRminer

Checking cpuminer-opt
cat: /home/m1/NVOC/mining/miners/cpuOPT/version: No such file or directory
Extracting cpuminer

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

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

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

ALL
Compiling alexis ccminer

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 int’, 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 int’, 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 file or directory
Finished compiling alexis ccminer

Compiling Vertminer
This could take a while ...
Submodule 'vertminer/src' (https://github.com/vertcoin-project/vertminer-nvidia) registered for path 'src'
Cloning into 'vertminer/src'...
fatal: reference is not a tree: 48b170a5828256600ca71e66d4c114af4e114236
Unable to checkout '48b170a5828256600ca71e66d4c114af4e114236' in submodule path 'src'
Update from shallow clone failed, reinit and fetching old commits...
From https://github.com/vertcoin-project/vertminer-nvidia
* [new tag] v1.0-beta.1 -> v1.0-beta.1
* [new tag] v1.0-beta.6 -> v1.0-beta.6
* [new tag] v1.0-beta.7 -> v1.0-beta.7
* [new tag] v1.0-stable.0 -> v1.0-stable.0
* [new tag] v1.0-stable.1 -> v1.0-stable.1
fatal: reference is not a tree: 48b170a5828256600ca71e66d4c114af4e114236
Unable to checkout '48b170a5828256600ca71e66d4c114af4e114236' in submodule path 'src'
bash: /home/m1/NVOC/mining/miners/vertminer/src/autogen.sh: No such file or directory
bash: /home/m1/NVOC/mining/miners/vertminer/src/configure: No such file or directory
bash: /home/m1/NVOC/mining/miners/vertminer/src/build.sh: No such file or directory
cp: cannot stat '/home/m1/NVOC/mining/miners/vertminer/src/vertminer': No such file or directory

/home/m1/NVOC/mining/miners/ANXccminer/src/build.sh: line 11: ./autogen.sh: Permission denied
done
/home/m1/NVOC/mining/miners/ANXccminer/src/build.sh: line 14: ./configure.sh: Permission denied
make: *** No targets specified and no makefile found. Stop.
cp: cannot stat '/home/m1/NVOC/mining/miners/ANXccminer/src/ccminer': No such file or directory

Finished compiling anorganix ccminer

Would it be possible to have the compilation results in a log file specifically for this recompilation of mining software?

Is there a functional check or operational check of all mining software after automated recompilation?

The recompilations of all the software took about 1h15 on my machine, but it is also necessary to know that some recompliations have aborted and that the software is not operational.
On wet finger, I think it should warn the user that the recompilation of all minning software will take about 90 to 120 minutes

When the recompilations are completed, it starts again in a loop by dragging the choice by interaction with the user.
If I close and restart the console, then it resumes the synchonization of the papampi gihub nvOC_Miners repository.

Same thing if I restart the system.

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: papampi on July 07, 2018, 01:45:06 PM

nvOC V19-2.1 beta Ubuntu-16.04 Nvidia-390 2018.07.07

-Complete new first boot process (Thanks to LukePicci)
-New additions and bug fixes

Extract the zip, flash your SSD/USB with the extracted img file
Open small fat partition.
Edit 1bash.template and save it as 1bash
Edit firstboot.json to enable/disable auto_expand. ("true" or "false")
recompile miners on first boot ("false" for no recompile, "A" for all, The letter/number associated to each recompilable miner depends on the latest nvOC_miner_update.sh script you find in the nvOC_miners repository on GitHub)
Auto recompile may take long time to download and recompile all miners.

On first boot, firstboot gnome-terminal profile will expand partition to full size, after reboot it will add latest nvOC and miners from GitHub repo.
firstboot gnome-terminal will stop and open mining gnome-terminal profile.
May reboot again if xorg.conf needs update.

Download link: nvOC_V19-2.1beta_U16.04_N390_D180707.img.zip
Image size: 9 Gb
Zip size: 3.5 Gb

sha256:

Code:

nvOC_V19-2.1beta_U16.04_N390_D180707.img:
f1f02c1cd704d3a33c954f64c5b6856f3a75612243b68d66da2fc9acd7bea8a5

nvOC_V19-2.1beta_U16.04_N390_D180707.img.zip
6334067606176ed90191b3e4980b21102d14a9c8f14ec63508669d1cb27d6e33

Ok, i'll download it and try it this night on antother HDD USB.

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: gs777 on July 07, 2018, 11:01:47 PM

Is anyone know does it include EWBF v0.3
for equihas 144.5 mining
Huh

Is the new 0.3 version command line arguments are same as before or there are new options?
Can you please post new arguments if its changed, so we can make the changes in 0miner and 1bash if needed.

gs777

member

Activity: 118

Merit: 10

Is anyone know does it include EWBF v0.3
for equihas 144.5 mining
Huh

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: LuKePicci on July 07, 2018, 02:53:18 PM

Two quick notes for preciseness:

Quote from: papampi on July 07, 2018, 01:45:06 PM

Edit 1bash.template and save it as 1bash

You always find the needed 1bash.template file from GitHub, at the link you find in the small fat partition.

Quote from: papampi on July 07, 2018, 01:45:06 PM

Edit firstboot.json to enable/disable auto_expand and recompile miners on first boot. ("true" or "false")

You can set auto_expand to "true" or "false" depending on your choice, while recompile_miners can be either "false" if you do not intend to let any miner be recompiled during first image boot, or a list of miners do you want to recompile, written in the same way as you are used to do with the nvOC_update_miner.sh. For exampt recompile_miners:"7 U" will recompile TPccminer(7) and SUPPRminer(U), recompile_miners:"A" will recompile all(A) miners. The letter/number associated to each recompilable miner depends on the latest nvOC_miner_update.sh script you find in the nvOC_miners repository on GitHub.

Thanks for the reminder, edited compile section.

LuKePicci

jr. member

Activity: 128

Merit: 1

Two quick notes for preciseness:

Quote from: papampi on July 07, 2018, 01:45:06 PM

Edit 1bash.template and save it as 1bash

You always find the needed 1bash.template file from GitHub, at the link you find in the small fat partition.

Quote from: papampi on July 07, 2018, 01:45:06 PM

Edit firstboot.json to enable/disable auto_expand and recompile miners on first boot. ("true" or "false")

You can set auto_expand to "true" or "false" depending on your choice, while recompile_miners can be either "false" if you do not intend to let any miner be recompiled during first image boot, or a list of miners do you want to recompile, written in the same way as you are used to do with the nvOC_update_miner.sh. For exampt recompile_miners:"7 U" will recompile TPccminer(7) and SUPPRminer(U), recompile_miners:"A" will recompile all(A) miners. The letter/number associated to each recompilable miner depends on the latest nvOC_miner_update.sh script you find in the nvOC_miners repository on GitHub.

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

nvOC V19-2.1 beta Ubuntu-16.04 Nvidia-390 2018.07.07

-Complete new first boot process (Thanks to LukePicci)
-New additions and bug fixes

Extract the zip, flash your SSD/USB with the extracted img file
Open small fat partition.
Edit 1bash.template and save it as 1bash
Edit firstboot.json to enable/disable auto_expand. ("true" or "false")
recompile miners on first boot ("false" for no recompile, "A" for all, The letter/number associated to each recompilable miner depends on the latest nvOC_miner_update.sh script you find in the nvOC_miners repository on GitHub)
Auto recompile may take long time to download and recompile all miners.

On first boot, firstboot gnome-terminal profile will expand partition to full size, after reboot it will add latest nvOC and miners from GitHub repo.
firstboot gnome-terminal will stop and open mining gnome-terminal profile.
May reboot again if xorg.conf needs update.

Download link: nvOC_V19-2.1beta_U16.04_N390_D180707.img.zip
Image size: 9 Gb
Zip size: 3.5 Gb

sha256:

Code:

nvOC_V19-2.1beta_U16.04_N390_D180707.img:
f1f02c1cd704d3a33c954f64c5b6856f3a75612243b68d66da2fc9acd7bea8a5

nvOC_V19-2.1beta_U16.04_N390_D180707.img.zip
6334067606176ed90191b3e4980b21102d14a9c8f14ec63508669d1cb27d6e33

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: Spiralx on July 03, 2018, 03:53:12 PM

Only thing I didn't like was no option to set a max fan speed before limiting power as I never want fans to run at 100% since they tend to be the most likely component to fail first as well as being noisy.

That option now exists in 2.1beta.

Quote from: Spiralx on July 03, 2018, 03:53:12 PM

Only other complaint is that I can't seem to get the telegram bot to work. I used the video tutorial and made sure the chat id & api is correct but nothing is ever sent to the bot.

That's strange, Make sure you put the full chat id, including eventual minus sign in front of the chat id number. If your chat id is referring to a group, make sure group messaging is enabled for that bot you created. Try to set message type to "papampi" since I can guarantee at least that one is working.

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: tomlev5 on July 03, 2018, 03:51:21 PM

I would like to try ethminer + pill on nvOC. Is there an easy way to do this on V0019-2.0 (I have access to the rig on ssh)? Or is it best that I burn V19-2.1beta on a HDD?

The easiest and safest thing you can do is to follow the guide to update to nvOC 2.1beta from your current image, it is safer than trying to burn the beta image as it is a mixture of old 2.0 stuff and old 2.1beta stuff which you would need to update before using it, even if the eth+pill works fine. Moreover if something do not work in the new beta you can revert to 2.0 in exactly 8 mouse clicks. Your other option is to find in this thread previous instructions to manually patch 2.0 tu support the pill. Can be done but it is neither the easiest nor the quickest way.

Spiralx

newbie

Activity: 6

Merit: 0

I had my rigs on Win 10 for many months without any issues but since the introduction of equihash ASIC's it became necessary to start moving rigs to ETH. One of my rigs consists of 3gb 1060's which don't work in Win10 for ETH so I searched for alternative operating systems.

I have no experience using Linux before but nvoc was a piece of cake to setup. Simple editing of the 1bash to setup overclocks and enabling teamviewer was pretty much all that had to be done. Only thing I didn't like was no option to set a max fan speed before limiting power as I never want fans to run at 100% since they tend to be the most likely component to fail first as well as being noisy. I was able to fix that myself though just by opening the fan script and replacing the line checking if fan speed is at 100 to 80 instead.

Only other complaint is that I can't seem to get the telegram bot to work. I used the video tutorial and made sure the chat id & api is correct but nothing is ever sent to the bot.

tomlev5

newbie

Activity: 35

Merit: 0

I would like to try ethminer + pill on nvOC. Is there an easy way to do this on V0019-2.0 (I have access to the rig on ssh)? Or is it best that I burn V19-2.1beta on a HDD?

WaveFront

member

Activity: 126

Merit: 10

Quote from: CryptAtomeTrader44 on June 30, 2018, 01:51:41 PM

Quote from: LuKePicci on June 30, 2018, 11:54:48 AM

Quote from: WaveFront on June 29, 2018, 01:27:25 PM

Hello,

Anyone using bminer to mine Ethash?
Do you see any differences in hash rate between miner and ethminer?
I tried to run them side by side, but I cannot see any noticeable difference in speed.

What do you think?

@CryptAtomeTrader44 said something about thet in some previous posts.

I use Bminer because at the beta2 start, there wasn't been possible to use Claymore for NICE_ETHASH coin checking in WTM_PROFIT SWITCHING. I hadn't seen any hasrate différence between claymore and Bminer.
Precisley, i mine only ETH, or ETC with Bminer. I saw it's possible tu DUAL mine with it, but i don't.
I don't retry to mine on nicehash with claymore.

Is seems to me that Bminer is slightly more stable.

Hello and thank you for your answer. I was reading in forums that Bminer was way more effective than Claymore and Ethminer, so I thought about giving it a try.
I cannot see any noticeable difference in hash rate (if you factor in the developer fee). Nevertheless, I see that Bminer has an integrated watchdog that catches GPU crashes pretty fast (not all of them), so overall efficiency is slightly better than ethminer.

By the way, is there a way to generate a reported hash rate like with Claymore

fk2

jr. member

Activity: 67

Merit: 2

Quote from: LuKePicci on June 30, 2018, 11:43:43 AM

Quote from: fk2 on June 29, 2018, 06:32:28 AM

the first time ever I heard about that SSD resize issue. you guys seriously need to consider that there are people like me who dont want to hook up a fucking display to a rig every time they want to install one. now I shall use gparted to do things but rig reboots every time when display is connected wtf guys seriously. this is ultra annoying when I update rigs by remote and now don't have local access whos idea was this?

If it has not resized automatically it is a bug and not an intended behavior. I suggested the gparted way only as a workaround for your specific situation. I would not suggest you to test the beta version without a monitor.

Just to have a clue on what happened to you: was the latest 2.0 w/ auto-expand image working for you or you previously used 1.4+update or 2.0 w/o auto-expand?

I used 2.0 image and got the hint for SSD resize so I just did that. I tried 2.0 before without monitor and had issues so I guess there is a problem with 2.0 image.

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