Bitcoin Forum
November 18, 2024, 06:19:29 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 [403] 404 405 406 407 408 409 410 411 412 413 414 415 416 »
  Print  
Author Topic: [OS] nvOC easy-to-use Linux Nvidia Mining  (Read 418244 times)
Brainfruit_Me
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
August 17, 2018, 08:20:58 PM
 #8041

Is CUDA 9.1 implementation coming soon? To install it myself now requires too much hand holding from someone else. I'm losing a lot of possible hash by not being able to run better miners.

**EDIT** Couple posts above says in a week or so?
papampi_2
Jr. Member
*
Offline Offline

Activity: 112
Merit: 3

Linux Forever... Resistance is futile!!!


View Profile WWW
August 18, 2018, 07:45:44 AM
 #8042


thank you

I am editing new bash file now, and I noticed this:


Code:
WTM_AUTO_SWITCH_SYNC_INTERVAL="3"             # Time to sync with WTM for best coin, minimum 3 minutes.

WTM_PROFIT_CHECK_INTERVAL="30"                # interval between checking profit for web info

WTM_MIN_DIFFERENCE="6"                        # Mininumum difference in percent when switch to new coin, to prevent too many switches.

WTM_MINIMUM_MINING_TIME="1800"               # Minimum mining time before checking and switching to prevent fast switches.

WTM_LOWER_MIN_DIFFERENCE="3"                  # When Minimum Mining time passed, next top coin will switch with lower difference

WTM_FORCE_SWITCH="8"                          # If profit gain is more than this value make the switch and dont wait for minimum mining time.

WTM_CURRENCY="USD"                            # USD, AUD, BRL, CAD, CHF, CLP, CNY, DKK, EUR, GBP, HKD, INR, ISK, JPY, KRW, NZD, PLN, RUB, SEK, SGD, THB, TWD
more specifically
Code:
WTM_MINIMUM_MINING_TIME="1800"  

is it in seconds or in minutes? looks like everything else is in minutes, and if minimum mining time is also in minutes, isn't it a little too much?



Yes Minimum mining time is in seconds, should add that to its comment info.
Default is set for 30 minutes, you can lower it if you want, but too many switches is not good.

https://github.com/papampi/nvOC_by_fullzero_Community_Release
papampi_2
Jr. Member
*
Offline Offline

Activity: 112
Merit: 3

Linux Forever... Resistance is futile!!!


View Profile WWW
August 18, 2018, 07:55:50 AM
Last edit: August 18, 2018, 08:15:47 AM by papampi_2
 #8043

Is CUDA 9.1 implementation coming soon? To install it myself now requires too much hand holding from someone else. I'm losing a lot of possible hash by not being able to run better miners.

**EDIT** Couple posts above says in a week or so?

Cuda-9.2 is added to new ubuntu 18.04.1 image.
Will try to release it as soon as possible,

The only problem for now is that Canonical moved to libcurl4 on ubuntu 18.04 which breaks many miners dependency.
So if we install cmake it will install libcurl4 and remove libcurl3.
If we remove cmake and install libcurl3, then users cant recompile their miners
Working on workarounds for nvOC until Canonical solve the issue.


Its a waste of storage to add all cuda-9 variants as each version takes almost 1.5 GB of storage.
Almost all new miners work on cuda-9.2 and old miners switching to cuda-8.0 with no problem in my tests.


https://github.com/papampi/nvOC_by_fullzero_Community_Release
Brainfruit_Me
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
August 18, 2018, 01:49:12 PM
 #8044

Is CUDA 9.1 implementation coming soon? To install it myself now requires too much hand holding from someone else. I'm losing a lot of possible hash by not being able to run better miners.

**EDIT** Couple posts above says in a week or so?

Cuda-9.2 is added to new ubuntu 18.04.1 image.
Will try to release it as soon as possible,

The only problem for now is that Canonical moved to libcurl4 on ubuntu 18.04 which breaks many miners dependency.
So if we install cmake it will install libcurl4 and remove libcurl3.
If we remove cmake and install libcurl3, then users cant recompile their miners
Working on workarounds for nvOC until Canonical solve the issue.


Its a waste of storage to add all cuda-9 variants as each version takes almost 1.5 GB of storage.
Almost all new miners work on cuda-9.2 and old miners switching to cuda-8.0 with no problem in my tests.




Thanks, I'm basically just trying to run the newest CryptoDregde.
papampi_2
Jr. Member
*
Offline Offline

Activity: 112
Merit: 3

Linux Forever... Resistance is futile!!!


View Profile WWW
August 19, 2018, 06:45:29 AM
 #8045

Is CUDA 9.1 implementation coming soon? To install it myself now requires too much hand holding from someone else. I'm losing a lot of possible hash by not being able to run better miners.

**EDIT** Couple posts above says in a week or so?

Cuda-9.2 is added to new ubuntu 18.04.1 image.
Will try to release it as soon as possible,

The only problem for now is that Canonical moved to libcurl4 on ubuntu 18.04 which breaks many miners dependency.
So if we install cmake it will install libcurl4 and remove libcurl3.
If we remove cmake and install libcurl3, then users cant recompile their miners
Working on workarounds for nvOC until Canonical solve the issue.


Its a waste of storage to add all cuda-9 variants as each version takes almost 1.5 GB of storage.
Almost all new miners work on cuda-9.2 and old miners switching to cuda-8.0 with no problem in my tests.




Thanks, I'm basically just trying to run the newest CryptoDregde.

If you are on 19-2.1, you can add it by running the upgrade command and check for miners update.
Set algos you want to "CryptoDredge"  
Remember CryptoDredge intensity is "0-6"

Code:
bash ~/NVOC/mining/nvOC upgrade

https://github.com/papampi/nvOC_by_fullzero_Community_Release
Brainfruit_Me
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
August 20, 2018, 03:52:05 AM
 #8046

Is CUDA 9.1 implementation coming soon? To install it myself now requires too much hand holding from someone else. I'm losing a lot of possible hash by not being able to run better miners.

**EDIT** Couple posts above says in a week or so?

Cuda-9.2 is added to new ubuntu 18.04.1 image.
Will try to release it as soon as possible,

The only problem for now is that Canonical moved to libcurl4 on ubuntu 18.04 which breaks many miners dependency.
So if we install cmake it will install libcurl4 and remove libcurl3.
If we remove cmake and install libcurl3, then users cant recompile their miners
Working on workarounds for nvOC until Canonical solve the issue.


Its a waste of storage to add all cuda-9 variants as each version takes almost 1.5 GB of storage.
Almost all new miners work on cuda-9.2 and old miners switching to cuda-8.0 with no problem in my tests.




Thanks, I'm basically just trying to run the newest CryptoDregde.

If you are on 19-2.1, you can add it by running the upgrade command and check for miners update.
Set algos you want to "CryptoDredge"  
Remember CryptoDredge intensity is "0-6"

Code:
bash ~/NVOC/mining/nvOC upgrade

AH, I'm only on 2.0 Should I wait for a new release or get 2.1 hmmm
papampi_2
Jr. Member
*
Offline Offline

Activity: 112
Merit: 3

Linux Forever... Resistance is futile!!!


View Profile WWW
August 20, 2018, 12:43:22 PM
 #8047

Is CUDA 9.1 implementation coming soon? To install it myself now requires too much hand holding from someone else. I'm losing a lot of possible hash by not being able to run better miners.

**EDIT** Couple posts above says in a week or so?

Cuda-9.2 is added to new ubuntu 18.04.1 image.
Will try to release it as soon as possible,

The only problem for now is that Canonical moved to libcurl4 on ubuntu 18.04 which breaks many miners dependency.
So if we install cmake it will install libcurl4 and remove libcurl3.
If we remove cmake and install libcurl3, then users cant recompile their miners
Working on workarounds for nvOC until Canonical solve the issue.


Its a waste of storage to add all cuda-9 variants as each version takes almost 1.5 GB of storage.
Almost all new miners work on cuda-9.2 and old miners switching to cuda-8.0 with no problem in my tests.




Thanks, I'm basically just trying to run the newest CryptoDregde.

If you are on 19-2.1, you can add it by running the upgrade command and check for miners update.
Set algos you want to "CryptoDredge"  
Remember CryptoDredge intensity is "0-6"

Code:
bash ~/NVOC/mining/nvOC upgrade

AH, I'm only on 2.0 Should I wait for a new release or get 2.1 hmmm

Better wait for next stable release.

https://github.com/papampi/nvOC_by_fullzero_Community_Release
fk2
Jr. Member
*
Offline Offline

Activity: 67
Merit: 2


View Profile
August 20, 2018, 04:14:26 PM
Last edit: August 20, 2018, 04:33:30 PM by fk2
 #8048

some of you remember me complaining about NICE_ETHASH not working. I investigated further, this is how 2.1 starts NICE_ETHASH with ethminer:

Code:
/home/m1/NVOC/testing/miners/ethminer/latest/ethminer -P stratum+tcp://3FK6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.AnyMine01:x@daggerhashimoto.usa.nicehash.com:3353 -U

resulting in

Code:
m1@m1-desktop:~/NVOC/testing$ /home/m1/NVOC/testing/miners/ethminer/latest/ethminer -P stratum+tcp://3CW6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.LuisenMine01:x@daggerhashimoto.usa.nicehash.com:3353 -U
  m  08:58:04|ethminer|  ethminer version 0.14.0
  m  08:58:04|ethminer|  Build: linux / release +git. 24c65cf
 cu  08:58:04|ethminer|  Using grid size 8192 , block size 128
  ℹ  08:58:05|ethminer|  Selected pool daggerhashimoto.usa.nicehash.com:3353
  m  08:58:05|ethminer|  not-connected
  ℹ  08:58:05|stratum |  Trying 172.65.194.252:3353 ...
  ℹ  08:58:05|stratum |  Connected to daggerhashimoto.usa.nicehash.com  [172.65.194.252:3353]
  ℹ  08:58:05|stratum |  Spinning up miners...
  ℹ  08:58:05|cuda-0  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-1  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-2  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-3  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-4  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-5  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-6  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-7  |  No work. Pause for 3 s.
  ℹ  08:58:05|stratum |  Subscribed to stratum server
  ℹ  08:58:05|stratum |  Authorized worker 3CW6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.LuisenMine01
  ✘  08:58:05|stratum |  Got unknown method [ mining.set_difficulty ] from pool. Discarding ...
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<dev::BadHexCharacter>'
  what():  BadHexCharacter
Aborted
m1@m1-desktop:~/NVOC/testing$

Here is what worked for me according to their page here: https://www.nicehash.com/help/ethereum-mining

Code:
/home/m1/NVOC/testing/miners/ethminer/latest/ethminer -SP 2 -U -S daggerhashimoto.eu.nicehash.com:3353 -O 3FK6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.AnyMine01:x

If I choose genoil this starts the process:
Code:
/home/m1/NVOC/testing/miners/Genoil-U/ethminer -S daggerhashimoto.usa.nicehash.com:3353 -O 3FK6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.AnyMine01:x -SP 1 -U 
but the Genoil-U folder doesn't even exist. might be because I couldn't compile Genoil because I have still cuda 8.0 on this rig but I am not sure.

In 0miner I found bminer in the ethash protocol but it is not mentioned as an option in my 1bash. I had another failed try here:
Code:
m1@m1-desktop:~/NVOC/testing$ /home/m1/NVOC/testing/miners/bminer/latest/bminer -uri stratum+tcp://3CW6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.LuisenMine01:x@daggerhashimoto.usa.nicehash.com:3353
invalid value "stratum+tcp://3FK6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.AnyMine01:x@daggerhashimoto.usa.nicehash.com:3353" for flag -uri: Unsupported scheme

I'm not sure if nicehash need exceptions on the right format of parameters. E: I temporarly edited my 0miner like this in order to work:
Code:
  elif [[ $ETHASH_MINER == ETHMINER ]]
  then
        if [[ $COIN == NICE_ETHASH ]]
        then
        HCD="${NVOC}/miners/ethminer/latest/ethminer -SP 2 -U -S ${!xpool}:${!xport} -O ${!xaddr}${!xwallet}${!xwork}:$MINER_PWD"
        else
        HCD="${NVOC}/miners/ethminer/latest/ethminer -P ${!xproto}://${!xaddr}${!xwallet}${!xwork}:$MINER_PWD@${!xpool}:${!xport} -U ${!xext} $ETHMINER_OPTS"
        fi
  elif [[ $ETHASH_MINER == CLAYMORE ]]

As I did I might noticed that this could be erroneous due to the stratum:// extension
infowire
Newbie
*
Offline Offline

Activity: 96
Merit: 0


View Profile
August 20, 2018, 07:08:23 PM
 #8049

How can i tell which slot with card belongs to? From CPU closest is 0, then next to that is 1, 2 and so on ?
fk2
Jr. Member
*
Offline Offline

Activity: 67
Merit: 2


View Profile
August 20, 2018, 07:26:08 PM
 #8050

How can i tell which slot with card belongs to? From CPU closest is 0, then next to that is 1, 2 and so on ?
on most boards you count from the cpu socket away. at first the large pciex16 slots, then the small pciex4 slots.


edit: here a picture how to count
papampi_2
Jr. Member
*
Offline Offline

Activity: 112
Merit: 3

Linux Forever... Resistance is futile!!!


View Profile WWW
August 20, 2018, 08:39:01 PM
 #8051

some of you remember me complaining about NICE_ETHASH not working. I investigated further, this is how 2.1 starts NICE_ETHASH with ethminer:

Code:
/home/m1/NVOC/testing/miners/ethminer/latest/ethminer -P stratum+tcp://3FK6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.AnyMine01:x@daggerhashimoto.usa.nicehash.com:3353 -U

resulting in

Code:
m1@m1-desktop:~/NVOC/testing$ /home/m1/NVOC/testing/miners/ethminer/latest/ethminer -P stratum+tcp://3CW6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.LuisenMine01:x@daggerhashimoto.usa.nicehash.com:3353 -U
  m  08:58:04|ethminer|  ethminer version 0.14.0
  m  08:58:04|ethminer|  Build: linux / release +git. 24c65cf
 cu  08:58:04|ethminer|  Using grid size 8192 , block size 128
  ℹ  08:58:05|ethminer|  Selected pool daggerhashimoto.usa.nicehash.com:3353
  m  08:58:05|ethminer|  not-connected
  ℹ  08:58:05|stratum |  Trying 172.65.194.252:3353 ...
  ℹ  08:58:05|stratum |  Connected to daggerhashimoto.usa.nicehash.com  [172.65.194.252:3353]
  ℹ  08:58:05|stratum |  Spinning up miners...
  ℹ  08:58:05|cuda-0  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-1  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-2  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-3  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-4  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-5  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-6  |  No work. Pause for 3 s.
  ℹ  08:58:05|cuda-7  |  No work. Pause for 3 s.
  ℹ  08:58:05|stratum |  Subscribed to stratum server
  ℹ  08:58:05|stratum |  Authorized worker 3CW6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.LuisenMine01
  ✘  08:58:05|stratum |  Got unknown method [ mining.set_difficulty ] from pool. Discarding ...
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<dev::BadHexCharacter>'
  what():  BadHexCharacter
Aborted
m1@m1-desktop:~/NVOC/testing$

Here is what worked for me according to their page here: https://www.nicehash.com/help/ethereum-mining

Code:
/home/m1/NVOC/testing/miners/ethminer/latest/ethminer -SP 2 -U -S daggerhashimoto.eu.nicehash.com:3353 -O 3FK6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.AnyMine01:x

If I choose genoil this starts the process:
Code:
/home/m1/NVOC/testing/miners/Genoil-U/ethminer -S daggerhashimoto.usa.nicehash.com:3353 -O 3FK6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.AnyMine01:x -SP 1 -U 
but the Genoil-U folder doesn't even exist. might be because I couldn't compile Genoil because I have still cuda 8.0 on this rig but I am not sure.

In 0miner I found bminer in the ethash protocol but it is not mentioned as an option in my 1bash. I had another failed try here:
Code:
m1@m1-desktop:~/NVOC/testing$ /home/m1/NVOC/testing/miners/bminer/latest/bminer -uri stratum+tcp://3CW6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.LuisenMine01:x@daggerhashimoto.usa.nicehash.com:3353
invalid value "stratum+tcp://3FK6n5M7vTtAzwc1xMQAZGkdNb299VzyAw.AnyMine01:x@daggerhashimoto.usa.nicehash.com:3353" for flag -uri: Unsupported scheme

I'm not sure if nicehash need exceptions on the right format of parameters. E: I temporarly edited my 0miner like this in order to work:
Code:
  elif [[ $ETHASH_MINER == ETHMINER ]]
  then
        if [[ $COIN == NICE_ETHASH ]]
        then
        HCD="${NVOC}/miners/ethminer/latest/ethminer -SP 2 -U -S ${!xpool}:${!xport} -O ${!xaddr}${!xwallet}${!xwork}:$MINER_PWD"
        else
        HCD="${NVOC}/miners/ethminer/latest/ethminer -P ${!xproto}://${!xaddr}${!xwallet}${!xwork}:$MINER_PWD@${!xpool}:${!xport} -U ${!xext} $ETHMINER_OPTS"
        fi
  elif [[ $ETHASH_MINER == CLAYMORE ]]

As I did I might noticed that this could be erroneous due to the stratum:// extension


You should set Ethermine new stratum protocol scheme , many Ethermine old command arguments are deprecated and not going to be used in latest 0.15.0 anymore
I suggest you to check 1bash info lines and update your 1bash and nvOC to latest.


~/NVOC/mining/miners/ETHMINER/0.14.0/ethminer --help:
Code:
    -SP, --stratum-protocol <n> (deprecated) Choose which stratum protocol to use:
        0: official stratum spec: ethpool, ethermine, coinotron, mph, nanopool (default)
        1: eth-proxy compatible: dwarfpool, f2pool, nanopool (required for hashrate reporting to work with nanopool)
        2: EthereumStratum/1.0.0: nicehash

    -P URL Specify a pool URL. Can be used multiple times. The 1st for for the primary pool, and the 2nd for the failover pool.
        URL takes the form: scheme://user[:password]@hostname:port[/emailaddress].
        for getwork use one of the following schemes:
          http
        for stratum use one of the following schemes:
          stratum+ssl stratum+tcp stratum+tls stratum+tls12 stratum1+ssl stratum1+tcp stratum1+tls stratum1+tls12 stratum2+ssl stratum2+tcp stratum2+tls stratum2+tls12
        Example 1 : stratum+ssl://0x012345678901234567890234567890123.miner1@ethermine.org:5555
        Example 2 : stratum1+tcp://0x012345678901234567890234567890123.miner1@nanopool.org:9999/john.doe@gmail.com
        Example 3 : stratum1+tcp://0x012345678901234567890234567890123@nanopool.org:9999/miner1/john.doe@gmail.com



~/NVOC/mining/miners/ETHMINER/0.15.0/ethminer --help:
Code:
  -P,--pool TEXT ...          Specify one or more pool URLs. See below for URL syntax


Pool URL Specification:
    URL takes the form: scheme://user[:password]@hostname:port[/emailaddress].
    for getwork use one of the following schemes:
      http
    for stratum use one of the following schemes:
      stratum+ssl stratum+tcp stratum+tls stratum+tls12 stratum1+ssl stratum1+tcp stratum1+tls stratum1+tls12 stratum2+ssl stratum2+tcp stratum2+tls stratum2+tls12
    Stratum variants:
      stratum:  official stratum spec: ethpool, ethermine, coinotron, mph, nanopool (default)
      stratum1: eth-proxy compatible: dwarfpool, f2pool, nanopool (required for hashrate reporting to work with nanopool)
      stratum2: EthereumStratum/1.0.0: nicehash
    Example 1: stratum+ssl://0x012345678901234567890234567890123.miner1@ethermine.org:5555
    Example 2: stratum1+tcp://0x012345678901234567890234567890123.miner1@nanopool.org:9999/john.doe@gmail.com
    Example 3: stratum1+tcp://0x012345678901234567890234567890123@nanopool.org:9999/miner1/john.doe@gmail.com


1bash.template:
Code:
#        Default Coin Pool Protocols is stratum+tcp, If your pool has other protocols check miner support before changing it
#        stratum+ssl, stratum+tcp, stratum+tls, stratum+tls12, stratum1+ssl, stratum1+tcp, stratum1+tls, stratum1+tls12, stratum2+ssl, stratum2+tcp, stratum2+tls, stratum2+tls12

#        If using bminer use these on coin pool protocols:
#        Equihash Stratum: "stratum", Equihash Stratum+SSL:"stratum+ssl"
#        Ethash Stratum:"ethash", Ethash Stratum+SSL:"ethash+ssl", Ethereum Proxy:"ethproxy" ethereum Stratum:"ethstratum"
#        ZHash Algos like BTG: "zhash"
#        Tensority based coins like BTM: "tensority"


In your case I think you should use  "stratum2+tcp" for Ethermine on nicehash


https://github.com/papampi/nvOC_by_fullzero_Community_Release
infowire
Newbie
*
Offline Offline

Activity: 96
Merit: 0


View Profile
August 20, 2018, 09:54:06 PM
 #8052

How can i tell which slot with card belongs to? From CPU closest is 0, then next to that is 1, 2 and so on ?
on most boards you count from the cpu socket away. at first the large pciex16 slots, then the small pciex4 slots.


edit: here a picture how to count
https://www.pic-upload.de/view-35823125/IMG_0842.jpg.html

so when i do
nvOC gpuinfo
0. card
1. card
2. card

The 0 card is at the one x16 closest to the processor ? I have MSI gaming m5 Z170
papampi_2
Jr. Member
*
Offline Offline

Activity: 112
Merit: 3

Linux Forever... Resistance is futile!!!


View Profile WWW
August 21, 2018, 08:06:28 AM
 #8053

How can i tell which slot with card belongs to? From CPU closest is 0, then next to that is 1, 2 and so on ?
on most boards you count from the cpu socket away. at first the large pciex16 slots, then the small pciex4 slots.


edit: here a picture how to count


so when i do
nvOC gpuinfo
0. card
1. card
2. card

The 0 card is at the one x16 closest to the processor ? I have MSI gaming m5 Z170

If you have local access to your rig you can use gpumap,
it will turn on/off GPU fans and leds one by one to help you locate them.

19-2.1:
Code:
bash ~/NVOC/mining/nvOC gpumap


Or if on 19-2.0:
Code:
bash ~/nvOC gpumap

https://github.com/papampi/nvOC_by_fullzero_Community_Release
fk2
Jr. Member
*
Offline Offline

Activity: 67
Merit: 2


View Profile
August 21, 2018, 03:13:04 PM
 #8054

@papampi: thats all good but for nicehash there is no option to change the protocol. besides, please send me some wallet of yours to donate you a coffee for your great support in the last couple of months dude Wink
papampi_2
Jr. Member
*
Offline Offline

Activity: 112
Merit: 3

Linux Forever... Resistance is futile!!!


View Profile WWW
August 21, 2018, 04:33:27 PM
Last edit: August 21, 2018, 04:58:43 PM by papampi_2
 #8055

@papampi: thats all good but for nicehash there is no option to change the protocol. besides, please send me some wallet of yours to donate you a coffee for your great support in the last couple of months dude Wink

Add it like this for ethermine:

Code:
NICE_ETHASH_POOL_PROTOCOL="stratum2+tcp"

for bminer use one of these, no idea which one:
Code:
Ethash Stratum:"ethash", Ethash Stratum+SSL:"ethash+ssl", Ethereum Proxy:"ethproxy" ethereum Stratum:"ethstratum"


Check and let me know if it works for ethermine or not.
Thanks for the coffee offer  Wink




https://github.com/papampi/nvOC_by_fullzero_Community_Release
infowire
Newbie
*
Offline Offline

Activity: 96
Merit: 0


View Profile
August 25, 2018, 06:27:00 PM
 #8056

How do i find out what the original card settings are ?
my cards say memory Clock: 8008 MHz and 150W, so what's the number i have to enter in 1bash? Power 150, core clock memory ?
Rev123
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
August 26, 2018, 11:01:27 AM
 #8057

Hello.
Where I can download the latest version?
I download the nvOC_V19-2.1beta_U16.04_N390_D180707 (for nvOC >= 2.1), but here is no miner for equihash 144,5 and 1bash is for old version.
Also the update doesn't work.
papampi_2
Jr. Member
*
Offline Offline

Activity: 112
Merit: 3

Linux Forever... Resistance is futile!!!


View Profile WWW
August 26, 2018, 08:32:56 PM
 #8058

Hello.
Where I can download the latest version?
I download the nvOC_V19-2.1beta_U16.04_N390_D180707 (for nvOC >= 2.1), but here is no miner for equihash 144,5 and 1bash is for old version.
Also the update doesn't work.

Both bminer and new ewbf are capable of mining new equihash algos, and both available in 19-2.1
What do you mean by the update doesnt work?

https://github.com/papampi/nvOC_by_fullzero_Community_Release
Rev123
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
August 29, 2018, 04:23:55 PM
 #8059

Hello.
Where I can download the latest version?
I download the nvOC_V19-2.1beta_U16.04_N390_D180707 (for nvOC >= 2.1), but here is no miner for equihash 144,5 and 1bash is for old version.
Also the update doesn't work.

Both bminer and new ewbf are capable of mining new equihash algos, and both available in 19-2.1
What do you mean by the update doesnt work?


In the process of updating there was an error that I did not have time to read.
Then, at the start of the terminal, the following was issued:
"There is something wrong with your 1bash settings file, nvOC can't start. Check if it exist or contains errors. SSH access is now being enabled to let you debug. This program will restart in a minure."
Also I find 1bash and there I turn on TeamViewer, but after restart terminal it still did not work.
papampi_2
Jr. Member
*
Offline Offline

Activity: 112
Merit: 3

Linux Forever... Resistance is futile!!!


View Profile WWW
August 30, 2018, 05:48:36 AM
 #8060

Hello.
Where I can download the latest version?
I download the nvOC_V19-2.1beta_U16.04_N390_D180707 (for nvOC >= 2.1), but here is no miner for equihash 144,5 and 1bash is for old version.
Also the update doesn't work.

Both bminer and new ewbf are capable of mining new equihash algos, and both available in 19-2.1
What do you mean by the update doesnt work?


In the process of updating there was an error that I did not have time to read.
Then, at the start of the terminal, the following was issued:
"There is something wrong with your 1bash settings file, nvOC can't start. Check if it exist or contains errors. SSH access is now being enabled to let you debug. This program will restart in a minure."
Also I find 1bash and there I turn on TeamViewer, but after restart terminal it still did not work.

As you can read your 1bash is corrupted or missing.
You should make a copy of 1bash.template and edit it so the latest changes takes effect.

Code:
cp ~/NVOC/mining/1bash.template ~/NVOC/mining/1bash

To edit from ssh:
Code:
nano ~/NVOC/mining/1bash

or if on local or teamviewer:
Code:
gedit ~/NVOC/mining/1bash

https://github.com/papampi/nvOC_by_fullzero_Community_Release
Pages: « 1 ... 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 [403] 404 405 406 407 408 409 410 411 412 413 414 415 416 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!