Bitcoin Forum
December 16, 2024, 07:18:08 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 »
  Print  
Author Topic: NBMiner v42.2, 100% LHR unlock for ETH mining !  (Read 54347 times)
nebutech (OP)
Member
**
Offline Offline

Activity: 134
Merit: 26


View Profile
January 19, 2019, 01:27:11 AM
Last edit: June 06, 2022, 02:21:37 AM by nebutech
Merited by nc50lc (5), CjMapope (5), suchmoon (4), VoskCoin (2), philipma1957 (1), Lafu (1)
 #1



NBMiner

GPU Miner for ETH, CFX, RVN, BEAM, AE, ZIL, ERGO.

Contact Us


Download

Download from official website: https://nbminer.com

Performance (stock frequency)

Features
  • Support Windows & Linux.
  • Nvidia LHR GPU ethash 100% unlock.
  • Support backup mining pool configuration.
  • Support SSL connection to mining pools.

Dev Fee

ethash 1%, cuckoo 2%,kawpow 2%, beamv3 2%, octopus 3%, ergo 2%

Requirements

Code:
| Algorithm        |  Coin   | Compute Capability | Memory (Win7 & Linux) | Memory (Win10) |
| :--------------- | :-----: | :----------------: | :-------------------: | :------------: |
| ethash           |   ETH   | 6.0, 6.1, 7.0, 7.5, 8.0,8.6 |          5GB          |      6GB      |
| cuckoo_ae        |   AE    | 6.0, 6.1, 7.0, 7.5, 8.0,8.6 |          5GB          |      6GB       |
| kawpow           |   RVN   | 6.0, 6.1, 7.0, 7.5, 8.0,8.6 |          3GB          |      4GB      |
| beamv3 | BEAM | 6.0, 6.1, 7.0, 7.5 | 3GB | 3GB |
| octopus | CFX | 6.0, 6.1, 7.0, 7.5, 8.0,8.6 | 5GB | 6GB |
| ergo | ERGO | 6.0, 6.1, 7.0, 7.5, 8.0,8.6 | 3GB | 3GB |
        Sample Usages

        ETH
        • ethermine:  nbminer -a ethash -o ethproxy+tcp://asia1.ethermine.org -u 0x12343bdgf.worker
        • sparkpool:   nbminer -a ethash -o ethproxy+tcp://cn.sparkpool.com:3333 -u 0x12343bdgf.worker
        • f2pool:        nbminer -a ethash -o ethproxy+tcp://eth.f2pool.com:8008 -u 0x12343bdgf.worker
        • nanopool:   nbminer -a ethash -o ethproxy+tcp://eth-asia1.nanopool.org:9999 -u 0x12343bdgf.worker
        • nicehash:    nbminer -a ethash -o nicehash+tcp://daggerhashimoto.eu.nicehash.com:3353 -u btc_address.worker

        ETH+ZIL

        • ezil: nbminer -a ethash -o stratum+tcp://cn.ezil.me:5555 -u ETH_WALLET.ZIL_WALLET.WORKER --enable-dag-cache
        • shardpool: nbminer -a ethash -o stratum+tcp://ch1-zil.shardpool.io:3333 -u ETH_WALLET.WORKER -p ZIL_WALLET@cn.sparkpool.com:3333 -enable-dag-cache

        AE
        • f2pool:        nbminer -a cuckoo_ae -o stratum+tcp://ae.f2pool.com:7898 -u ak_xxxxxxx.worker:passwd
        • beepool:     nbminer -a cuckoo_ae -o stratum+tcp://ae-pool.beepool.org:9505 -u ak_xxxx.worker:passwd
        • uupool:       nbminer -a cuckoo_ae -o stratum+tcp://ae.uupool.cn:6210 -u ak_xxxxxx.worker:passwd
        • nicehash:   nbminer -a cuckoo_ae -o nicehash+tcp://cuckoocycle.eu.nicehash.com:3376 -u btc_address.test

        RVN
        • beepool: nbminer -a kawpow -o  stratum+tcp://rvn-pool.beepool.org:9531 -u wallet.worker:passwd
        • f2pool: nbminer -a kawpow -o  stratum+tcp://raven.f2pool.com:3636 -u wallet.worker:passwd
        • minermore: nbminer -a kawpow -o stratum+tcp://us.rvn.minermore.com:4501 -u wallet.worker:paswd
        • bsod: nbminer -a kawpow -o stratum+tcp://pool.bsod.pw:2640 -u wallet.worker:passwd
        • nbminer -a kawpow -o stratum+tcp://rvn.woolypooly.com:55555 -u wallet.worker:passwd

        BEAM
        • sparkpool: nbminer -a beamv3 -o stratum+ssl://beam.sparkpool.com:2222 -u wallet.worker:passwd
        • leafpool: nbminer -a beamv3 -o stratum+ssl://beam-eu.leafpool.com:3333 -u wallet.worker:passwd
        • nicehash: nbminer -a beamv3 -o stratum+tcp://beamv3.eu.nicehash.com:3387 -u btc_address.worker

        CONFLUX
        • beepool: nbminer -a octopus -o stratum+tcp://cfx-pool.beepool.org:9555 -u wallet.worker
        • f2pool: nbminer -a octopus -o stratum+tcp://cfx.f2pool.com:6800 -u username.worker
        • matpool: nbminer -a octopus -o  stratum+tcp://cfx.matpool.io:10620 -u wallet.worker

        ERGO
        • herominers: nbminer -a ergo -o stratum+tcp://ergo.herominers.com:10250 -u wallet.worker
        • woolypooly: nbminer -a ergo -o stratum+tcp://erg.woolypooly.com:3100 -u wallet.worker
        • nanopool: nbminer -a ergo -o stratum+tcp://ergo-eu1.nanopool.org:11111 -u wallet.worker
        • 666pool: nbminer -a ergo -o stratum+tcp://ergo.666pool.cn:9556 -u wallet.worker

        CMD options
        • -h, --help    Displays this help.
        • -v, --version    Displays version information.
        • -c, --config <config file path>    Use json format config file rather than cmd line options.
        • -a, --algo <algo>    Select mining algorithm
        •                      BTM: tensority
        •                      ETH: ethash
        •                      BTM+ETH: tensority_ethash
        •                      Grin29: cuckaroo
        •                      Grin31: cuckatoo
        •                      SWAP:  cuckaroo_swap
        • --api  <host:port>    The endpoint for serving REST API.
        • -o, --url <url>    Mining pool url.
        •                    BTM: stratum+tcp://btm.f2pool.com:9221
        •                    BTM with SSL: stratum+ssl://btm.f2pool.com:9443
        •                    ETH: ethproxy+tcp://eth.f2pool.com:8008
        •                    ETH with NiceHash: ethnh+tcp://daggerhashimoto.eu.nicehash.com:3353
        • -u, --user <user>    User used in Mining pool, wallet address or username.
        • -o1, --url1 <url> url for backup mining pool 1.
        • -u1, --user1 <user> username for backup mining pool 1.
        • -o2, --url2 <url> url for backup mining pool 2.
        • -u2, --user2 <user> username for backup mining pool 2.
        • -p,  --password \<password>  password for mining pool
        • -p1,  --password1 \<password>  password for backup mining pool1
        • -p2,  --password2 \<password>  password for backup mining pool2
        • -d, --devices <devices>    Specify GPU list to use. Format: "-d 0,1,2,3" to use first 4 GPU.
        • -i, --intensity \<intensities>    Comma-separated list of intensities (1 -100).
        • -strict-ssl    Check validity of certificate when use SSL connection.
        • --cuckoo-intensity <intensity>    Set intensity of cuckoo, cuckaroo, cuckatoo, [1, 12]. Set to 0 means autumatically adapt. Default: 0.
        • --cuckatoo-power-optimize Set this option to reduce the range of power consumed by rig when minining with algo cuckatoo. This feature can reduce the chance of power supply shutdown caused by overpowered. Warning: Setting this option may cause drop on minining performance.
        • --temperature-limit, --tl \<temp-limit>    Set temperature limit of GPU, if exceeds, stop GPU.
        • --temperature-start, --ts \<temp-start>    Set cool-down temperature target if GPU is stopped by `temperature-limit`, default to \<temp-limit> - 5.
        • -log    Generate log file named `log_<timestamp>.txt`.
        • --log-file <filename>    Generate custom log file. Note: This option will override `--log`.
        • --no-nvml    Do not query cuda device health status.
        • -long-format    Use 'yyyy-MM-dd HH:mm:ss,zzz' for log time format.
        • --device-info Print device cuda information.
        • --fee <fee>    Change devfee in percentage, [0-5]. Set to '0' to turn off devfee with lower hashrate. Otherwise, devfee = max(set_value, def_value).
        • --generate-config \<filename>    Generate a sample config json file.
        • --no-watchdog    Disable watchdog process.
        • --platform \<platform>    Choose platform,0: NVIDIA+AMD (default), 1: NVIDIA only, 2: AMD only
        • --proxy Socks5 proxy used to eastablish connection with pool, format: username:password@host:port. E.g. 127.0.0.1:1080
        • --share-check \<value>    If \<value> minutes without share, reboot miner, set 0 to disable. Default: 30
        • --mt, --memory-tweak <mode> Memory timings optimize for Nvidia GDDR5 & GDDR5X gpus. range [1-6]. Higher value equals higher hashrate. Individual value can be set via comma seperated list. Power limit may need to be tuned up to get more hashrate. Higher reject share ratio can happen if mining rig hits high temperature, set lower value of `-mt` can reduce reject ratio.
        • --power-limit, --pl \<limit>    Set power limit of GPU.  Set PL in watts: -pl 200. Set PL in percetage of default PowerLimit: -pl 75%
        • --cclock \<clocks>    Set core clock in MHz. Set clock offsets: -cclock 100, -cclock -500 (Windows only). Set locked clock: -cclock @1500.
        • --mclock \<clocks>    Set memory clock offsets in MHz. (Windows only)
        • --lock-cv \<cv>    Set locked core voltages in mV. (Windows only)
        • --fan \<speed>    Set GPU fan speed in percentage. (Windows only)

        API Reference

        Web Monitor
        Open http://api_host:port/ in your browser to use web monitor.
        Default: http://127.0.0.1:22333

        Requests

        [/list][/list][/list]
        Code:
        GET http://api_host:port/api/v1/status

        Response Sample
        Code:
        {
            "miner": {
                "devices": [
                    {
                        "accepted_shares": 4,
                        "core_clock": 1530,
                        "core_utilization": 100,
                        "fan": 59,
                        "hashrate": "61.50 M",
                        "hashrate2": "0.000 ",
                        "hashrate2_raw": 0,
                        "hashrate_raw": 61497708.17088159,
                        "id": 0,
                        "info": "NVIDIA GeForce RTX 3070",
                        "invalid_shares": 0,
                        "lhr": 0,
                        "memTemperature": -1,
                        "mem_clock": 8000,
                        "mem_utilization": 100,
                        "pci_bus_id": 1,
                        "power": 131,
                        "rejected_shares": 0,
                        "temperature": 57
                    },
                    {
                        "accepted_shares": 3,
                        "core_clock": 1035,
                        "core_utilization": 100,
                        "fan": 80,
                        "hashrate": "85.07 M",
                        "hashrate2": "0.000 ",
                        "hashrate2_raw": 0,
                        "hashrate_raw": 85069773.34248555,
                        "id": 1,
                        "info": "NVIDIA GeForce RTX 3080 Ti LHR",
                        "invalid_shares": 0,
                        "lhr": 74,
                        "memTemperature": 104,
                        "mem_clock": 10251,
                        "mem_utilization": 100,
                        "pci_bus_id": 48,
                        "power": 258,
                        "rejected_shares": 0,
                        "temperature": 64
                    }
                ],
                "total_hashrate": "146.6 M",
                "total_hashrate2": "0.000 ",
                "total_hashrate2_raw": 0,
                "total_hashrate_raw": 146567481.51336715,
                "total_power_consume": 389
            },
            "reboot_times": 0,
            "start_time": 1637549633,
            "stratum": {
                "accepted_shares": 7,
                "algorithm": "ethash",
                "difficulty": "4.295 G",
                "dual_mine": false,
                "invalid_shares": 0,
                "latency": 217,
                "pool_hashrate_10m": "217.9 M",
                "pool_hashrate_24h": "217.9 M",
                "pool_hashrate_4h": "217.9 M",
                "rejected_shares": 0,
                "url": "asia2.ethermine.org:5555",
                "use_ssl": true,
                "user": "0x4296116d44a4a7259B52B1A756e19083e675062A"
            },
            "version": "40.0"
        }

        Change Log

        v42.2(2022-05-26)

          ** Compared to v41.5

        • `feature`: `ethash` Add a new option `--lhr-mode` to select LHR unlock mode.
          - `--lhr-mode 1` is the default mode and is the same as which in `v41.5`
          - Try to use `--lhr-mode 2` if stability issue encountered in `mode 1`, for json config, use `"lhr-mode": "2"`
          - `LHR v3` GPUs can only use `mode 1`
        • `feature`: `ethash` Extend LHR unlocker to work with old driver versions. Starting from `Windows v512.95` and `Linux v515.x`, LHR unlocker no longer works, make sure not to use these new driver versions.
        • `optimize`: `ethash` small hashrate improvement on Nvidia GPUs.
        • `feature`: Add `GDDR6X` memory temp in summary table for Linux.
        • `feature`: Add `GPU RAM type` and `GPU RAM vendor` in log.
        • `feature`: Add Nvidia driver versoin in summary table.
        • `feature`: `ethash` Add `eth_submitHashrate` for `nicehash (EthereumStratum)` protocol.
        • `feature`: If `Overclock` applies through `nbminer`, reset settings to stock when miner exit.
        • `feature`: `-mt` option on windows does not require custom driver anymore (admin priviledge is required).
        • `NOTE`: NBMiner versions older than v39.5 (not included) will run into issue when ETH reaches `EPOCH 520` (Approx mid September). Please make sure to upgrade to a newer version before that if ETH is still with POW.

        v41.5(2022-05-13)
        • `feature`: `ethash` Add 90% LHR unlocker for `3080 12G` & `3050`.
        • `feature`: `ergo` Add LHR unlocker support.
        • `fix`: `ethash` LHR unlocker improve stability.

        v41.3(2022-05-10)
        • `fix`: `ethash` Improve stability of LHR unlocker.
        • `fix`: `ethash` Fix crash on AMD GPUs
        • `fix`: `ethash` Improve compatibility on rigs with small system memory.
        • `note`: **Recommend driver versions: `512.15` for Windows, `510.60` for Linux.**

        v41.0(2022-05-08)
        • `feature`: `ethash` 100% LHR unlocker added, for both Windows & Linux.
                   - Run nbminer with admin priviledge to get 100% LHR unlock
                    - Tested and verified on drivers: `512.15` for Windows, `510.60` for Linux.
                    - Other driver versions may have some compatibility issue.
                    - Previous LHR mode are removed.

        v40.0(2021-11-23)
        • `feature`: Add overclock options for Nvidia GPUs, require admin priviledge, accept comma seprated list to specify for each GPU.
                   - `-power-limit, -pl`: Set power limitation of GPU. Examples:
            ​                         Set PL in watts: `-pl 200`
           ​                                Set PL in percentage of default PowerLimit: `-pl 75%` (in Windows bat file, need dual `%` , `-pl 75%%`)
                    - `-cclock`: Set core clock in MHz. Examples:
            ​                    Set clock offsets: `-cclock 100`  (Windows only)
                                 Set locked clocks: `-cclock @1500`
                    - `-mclock`: Set memory clock offsets in MHz (Windows only)
                    - `-lock-cv`: Set locked core voltage of GPU in mV, support Turing and newer GPUs. (Windows only)
                    - `-fan`: Set fan speed in percentage of GPU. (Windows only)
        • `feature`: Display current LHR value in console summary table and web monitor.
        • `feature`: `-proxy` options now support username & password for SOCKS5 proxy. format: `-proxy user:pass@host:port`
        • `feature`: Web monitor changes, delete unused information for dual mining.
        • `feature`: new options for log control.
                   - `-log-no-job`: Turn off the `New job` line in console.
                    - `-log-cycle`: Set to change the cycle of Summary table show in console and log, in seconds, defaults to 30.
        • `fix`: `ethash` Change CPU share validation to independent thread, lower performance degradation when mining at very low difficulty pools.
        • `fix`: LHR lock detected failure on some cases.

        v39.7(2021-10-30)
        • `feature`: LHR mode support new GA104 version of 3060
        • `feature`: `ethash` Turn on LHR mode by default for 3060 v1, disabled by default only on windows 470.05
        • `fix`: `ethash` Fail to detect LHR lock on certain situation.
        • `fix`: Nvidia GPU power consumption issue on certain rig config.
        • `delete`: support for `sero`.

        v39.6(2021-10-27)
        • `optimize`:`ethash` LHR mode significant improvement:
                   - higher hashrate, more stable LHR unlocking for both `-lhr-mode 1` and `-lhr-mode 2`
                    - default LHR mode changes to `-lhr-mode 1` for LHR GPUs
                    - default values of LHR mode increased, `-lhr-mode 1` -> 74, `-lhr-mode 2` -> 71
                    - added 3 new options for LHR auto-tuning control, at most cases you don't need to change:
                        - `-lhr-reduce-value`: the amount to reduce `-lhr` value on a single `-lhr` tuning. defaults to `0.5`.
                        - `-lhr-reduce-time`: When LHR lock is detected, and the time since the last lock exceeds this value, the `-lhr` reduce will not perform. defaults to `15`, which means 15 minutes.
                        - `-lhr-reduce-limit`: the maximum number of times to reduce `-lhr` value, defaults to `6`.
                    - Typical hashrate: 3060Ti LHR on defaults options, 45.5 MH/s @ mem+1200 (win10)
        • `feature`: `ergo` also adapts the 3 new LHR options.
        • `feature`: add `-cmd-output` option to specify command line outpu to `stdout` or `stderr`, `1=stdout`, `2=stderr`, defaults to `2`.
        • `feature`: disable SNI extension for ssl connections by default, can be enabled with `-enable-sni` option
        • `delete`: `cuckatoo` & `cuckatoo32` support

        v39.5(2021-09-24)
        • `feature`: `ergo` new LHR mode for mining ERGO, enable it by manually adding `-lhr` option
                   - Same as LHR mode in `ethash`, `-lhr` value represents expected hashrate to reach `value` percent of non-LHR GPU's hashrate, supports comma-seperated list to indicate `-lhr` value for each GPU, and `-lhr -1` to disable.
                    - For GPUs with Hynix GDDR6 memory, LHR mode is not recommended for the poor performance.
                    - For GPUs with non-Hynix GDDR6 memory, e.g. 3060 3060ti 3070, start trying with `-lhr 85`
                    - For GPUs with GDDR6X memory, e.g. 3070ti 3080 3080ti, start trying with `-lhr 100`
                    - When mining lock is detected during ERGO mining, miner will automatically decrease `-lhr` value by 0.5, and continue mining. max decrease times is 10, which sums to 5.0
        • `optimize`: `ergo` Lower power consumption on Nvidia GPUs.

        v39.4(2021-09-21)
        • `fix`: `octopus` Fix error hash issue.

        v39.3(2021-09-18)
        • `feature`: `ethash` new low power LHR mode, add `-lhr-mode` option.
                   - `-lhr-mode 2` is the default LHR mode, which is the new lower power mode.
                    - `-lhr-mode 1` changes LHR mode to old version, which is the same as `v39.2`
                    - `-lhr-mode 1` is suitable for only power limit bounded GPU, can achieve higher hashrate than mode 2
                    - `-lhr-mode 2` is able to achieve lower average power and temperature. espacially suitable for GPUs with gddr6x e.g.3070ti, 3080, 3080ti. Power consumtion is fluctuating in this mode, better be used with locked core clock.
        • `feature`: `-lhr` support decimal value
        • `feature`: for LHR GPUs, when mining lock is detected, miner will automatically decrease `-lhr` value by 0.1, and continue mining. max decrease times is 10, which sums to 1.0
        • `fix`: higher CPU usage when set `--share-check 0`

        v39.2(2021-09-01)
        • `feature`: `ethash` added LHR lock detection and recovery in LHR mode.
        • `feature`: added `memory temperature` display  (if available) for Nvidia and AMD GPU under windows.
        • `fix`: `ergo` more robust protocol handle.

        **Note: LHR mode requires NVML library to work, please make sure the driver is installed properly and do not add `-no-health` argument.**

        v39.1(2021-08-21)
        • `optimize`: `ethash` improve hashrate of `LHR` mode 1 - 2%,default value of `-lhr`changes from 68 to 69,manually set to 70 is also very promising.
        • `fix`: `LHR` mode support on windows driver 471.11
        • `fix`: `kawpow` issue of v39.0
        • `fix`: `Radeon vii` issue on windows driver 21.6.1+

        39.0(2021-08-15)
        • `feature`: `ethash` New LHR mode for ETH mining on RTX 30 series LHR GPUs, supports Windows & Linux, able to get ~70% of maximum unlocked hashrate.
                   - This mode can be tuned by argument `-lhr`, only works for `ethash` right now.
                    - `-lhr` default to 0, meaning even if `-lhr` is not set, LHR mode with `-lhr 68` will be applied to LHR GPUs if certain GPUs are detected.
                    - Tune LHR mode by setting `-lhr <value>`, a specific value will tell miner **try to reach** `value` percent of maximum unlocker hashrate, e.g. `-lhr 68` will expect to get 68% of hashrate for same model non-LHR GPU.
                    - Higher `-lhr` value will results in higher hashrate, but has higher possibility to run into lock state, which will leads to much less hashrate.
                    - A good start tuning value is 68, which has been tested to be stable on most rig configurations.
                    - `-lhr` value can be set for each GPU by using comma separeted list, `-lhr 65,68,0,-1`, where `-1` means turn off LHR mode.

        v38.2(2021-07-27)
        • `fix`: AMD kernel error on certain GPUs with 21.6.1+ drivers under windows.

        v38.1(2021-06-29)
        • `fix`: high CPU usage in v38.0

        v38.0(2021-06-29)
        • `feature`: `ergo` add `mining.extranonce.subscribe` support.
        • `fix`: eliminate memory leak by NVML library for Nvidia driver 460+ on windows.
        • `fix`: `--enable-dag-cache` causes crash on certain situation.

        v37.6(2021-06-03)
        • `fix`: `ethash` `--enable-dag-cache` cause crash on AMD GPUs when switch DAG file.
        • `fix`: `ergo` support on `AMD Vega` GPUs.

        v37.5(2021-05-21)
        changes from 37.3
        • `new algo`: `ergo` for AMD GPU, can be faster with ETH mining timings
        • `optimize`: `ergo` slightly improce hashrate on Nvidia GPUs
        • `feature`: use --temperature-limit & --temperature-start to protect GPU from overheat, detail in readme.md

        v37.3(2021-05-06)
        • `feature`: add option `--enable-dag-cache` to allow an extra `DAG` for different `epoch` cached in GPU memory, useful for `ETH+ZIL` mining and mining on `NiceHash`.

        v37.2(2021-04-24)
        • `feature`: add option `-p -p1 -p2` for setting `password` of mining pool, old format `-u wallet.worker:passwd` is disabled,`:` can be added as part of worker or wallet
        • `optimize`: `ethash` minor hashrate improvement on RDNA GPUs
        • `fix`: compatibility issue on lasted AMD `21.4.1` driver.

        v37.1(2021-03-25)
        • `fix`: `ergo` high reject ratio on 10 series Nvidia GPUs
        • `fix`: `ergo` pool compatibility
        • Recommend miners with `p106-90` & `1060 3G` to mine `ERGO`, hashrate will be increased significantly with `-mt` option.

        v37.0(2021-03-19)
        • `new algo`: `ergo` for mining `ERGO` coin on Nvidia GPUs.
        • `delete algo`: `bfc` `cuckarood` for Nvidia, `octopus` for AMD
        • `fix`: `octopus` support `CFX` new address format
        • `fix`: 'clBuildProgram error' issue on Vega for versions 35.0 - 36.1
        • `feature`: disable AMD iGPU by default, can be enabled back by setting `--enable-igpu`
        • `other`: minor bug fix, improve overall stability

        v36.1(2021-01-11)
        • `optimize`: `octopus` Lower power comsumption for 20、30 series Nvidia GPU, improve hashrate 2% on 16 series Nvidia GPU
        • `fix`: `ethash` Fix performance  degradation  under win8 & win8.1 for Nvidia 10 series GPUs.
        • `fix`: `ethash` Slightly reduce stale ratio.
        • `fix`: A random crash bug fix, improve overall stability
        • `feature`: Add `detail datetime` & `cpu usage` in summary log
        • `feature`: `ethash` If DAG verification failed, display corresponding GPU name in red in summary.

        v36.0(2020-12-28)
        • `fix`: `kawpow` crash on some GPUs in versions `35.x`
        • `fix`: `ethash` performance  degradation  under win7 for Nvidia 10 series GPUs.
        • `delete algo`: `eaglesong`, `eaglesong_ethash`, `trb`, `trb_ethash`, `hns`, `hns_ethash`, `sipc`, `cuckaroo`, `cuckaroo_swap`
        • `feature`: smaller binary size

        v35.2(2020-12-22)
        • `optimize`: `ethash` More stable under high OC for Nvidia 16、20、30 series GPUs.
        • `optimize`: `octopus` Improve hashrate 1-3% for 16, 20, 30 Nvidia GPUs
        • `feature`: `ethash` DAG verification after creation, if miner showed log in red font: `Verification failed, invalid 2.0%`, please consider lower GPU overclock

        v35.0(2020-12-14)
        • `feature`: `ethash` Add statistics for `invalid shares`, in cmd log, api and web monitor.
        • `feature`: Turn off limitation for not allowing to run under Virtual Machine.
        • `feature`: Add statistics for Health information of AMD GPU
        • `fix`: More detail error information of OpenCL api
        • `fix`: Reduce CPU usage.
        kcanup
        Legendary
        *
        Offline Offline

        Activity: 1484
        Merit: 1000


        View Profile
        January 19, 2019, 11:12:59 PM
         #2

        When AMD miner?  Wink
        nebutech (OP)
        Member
        **
        Offline Offline

        Activity: 134
        Merit: 26


        View Profile
        January 20, 2019, 01:46:48 AM
        Last edit: January 21, 2019, 12:18:10 AM by nebutech
         #3

        [Author]

        Currently focus on Nvidia cards, no plans for AMD cards.
        mrpcrp2
        Newbie
        *
        Offline Offline

        Activity: 12
        Merit: 0


        View Profile
        January 20, 2019, 01:06:09 PM
        Last edit: January 20, 2019, 01:25:50 PM by mrpcrp2
         #4

        best grin miner for multigpu righs , but not 100% utilizing more than 6 gpus even though CPU > i5
        Howardroid
        Newbie
        *
        Offline Offline

        Activity: 16
        Merit: 0


        View Profile
        January 20, 2019, 06:19:02 PM
         #5

        can you please explain what the other 2 port 80 & 443 connection for? And the following ip has bad rep. IDK its allowed or not to post ip so i removed from screenshot

        https://i.imgur.com/snlNXSO.png
        arielbit
        Legendary
        *
        Offline Offline

        Activity: 3444
        Merit: 1061


        View Profile
        January 20, 2019, 08:15:03 PM
         #6

        looks good, support windows 7 for grin mining.
        nebutech (OP)
        Member
        **
        Offline Offline

        Activity: 134
        Merit: 26


        View Profile
        January 21, 2019, 12:10:52 AM
         #7

        can you please explain what the other 2 port 80 & 443 connection for? And the following ip has bad rep. IDK its allowed or not to post ip so i removed from screenshot



        The 443 connection is a https request to update where to mine the dev fee.

        The 80 connection is a http request to detect the IP address of the rig, which will later be used as worker name when mining the dev fee.
        nebutech (OP)
        Member
        **
        Offline Offline

        Activity: 134
        Merit: 26


        View Profile
        January 21, 2019, 12:17:33 AM
         #8

        [Author]

        The current version of miner do not turn on the Grin Difficulty Check feature.

        The reason for this is on early days of Grin mining, mining pools do not have a united definition mining difficulty, which will cause a even more trouble if miner do check difficulty.

        I recently checked several pool, they seems to have united the definition.

        The problem will be solved in next version.
        Howardroid
        Newbie
        *
        Offline Offline

        Activity: 16
        Merit: 0


        View Profile
        January 21, 2019, 07:21:20 AM
         #9

        can you please explain what the other 2 port 80 & 443 connection for? And the following ip has bad rep. IDK its allowed or not to post ip so i removed from screenshot

        https://i.imgur.com/snlNXSO.png

        The 443 connection is a https request to update where to mine the dev fee.

        The 80 connection is a http request to detect the IP address of the rig, which will later be used as worker name when mining the dev fee.


        Anyway look good i test 1060 get around 1.8 graph/s.
        Just fyi i wont use this for now because of this connection. and the connecting to port 80 ip address doesnt look good.

        i google that ip and its shows something like this
        https://i.imgur.com/AIdb5UJ.png

        You should set the dev fee static or dynamic address within the program, i hope you consider to remove those suspicious connection and i might use it., thank you.

        swogerino
        Legendary
        *
        Offline Offline

        Activity: 3374
        Merit: 1248


        Bitcoin Casino Est. 2013


        View Profile
        January 21, 2019, 08:33:42 AM
         #10

        Mining on Windows 10 with 1060 , are you claiming you can mine Ethereum with 3 Gb cards ? That is impossible with other miners , so if you do it is awesome. I will give a try mining Grin with my 1060 rig , actually I am mining CryptonightHeavy with Xmr-Stak.

        ███▄▀██▄▄
        ░░▄████▄▀████ ▄▄▄
        ░░████▄▄▄▄░░█▀▀
        ███ ██████▄▄▀█▌
        ░▄░░███▀████
        ░▐█░░███░██▄▄
        ░░▄▀░████▄▄▄▀█
        ░█░▄███▀████ ▐█
        ▀▄▄███▀▄██▄
        ░░▄██▌░░██▀
        ░▐█▀████ ▀██
        ░░█▌██████ ▀▀██▄
        ░░▀███
        ▄▄██▀▄███
        ▄▄▄████▀▄████▄░░
        ▀▀█░░▄▄▄▄████░░
        ▐█▀▄▄█████████
        ████▀███░░▄░
        ▄▄██░███░░█▌░
        █▀▄▄▄████░▀▄░░
        █▌████▀███▄░█░
        ▄██▄▀███▄▄▀
        ▀██░░▐██▄░░
        ██▀████▀█▌░
        ▄██▀▀██████▐█░░
        ███▀░░
        nebutech (OP)
        Member
        **
        Offline Offline

        Activity: 134
        Merit: 26


        View Profile
        January 21, 2019, 08:49:39 AM
         #11

        can you please explain what the other 2 port 80 & 443 connection for? And the following ip has bad rep. IDK its allowed or not to post ip so i removed from screenshot



        The 443 connection is a https request to update where to mine the dev fee.

        The 80 connection is a http request to detect the IP address of the rig, which will later be used as worker name when mining the dev fee.


        Anyway look good i test 1060 get around 1.8 graph/s.
        Just fyi i wont use this for now because of this connection. and the connecting to port 80 ip address doesnt look good.

        i google that ip and its shows something like this


        You should set the dev fee static or dynamic address within the program, i hope you consider to remove those suspicious connection and i might use it., thank you.



        Thanks for your advice.

        The 443 https requests a dev fee content from https://gist.githubusercontent.com.

        The 80 http requests ip address from http://ipv4bot.whatismyipaddress.com.

        Using ip address as workername is a convenient way to get statistics of users, without an extra connection to our own server.

        Static or in-app dynamic will be used later, when grin mining username formats are united among mining pools.
        nebutech (OP)
        Member
        **
        Offline Offline

        Activity: 134
        Merit: 26


        View Profile
        January 21, 2019, 08:56:03 AM
         #12

        Mining on Windows 10 with 1060 , are you claiming you can mine Ethereum with 3 Gb cards ? That is impossible with other miners , so if you do it is awesome. I will give a try mining Grin with my 1060 rig , actually I am mining CryptonightHeavy with Xmr-Stak.

        Nope.

        No special tuning trick for ETH mining right now.

        In fact, adding ETH mining support mainly due to a pre-test for developing the BTM+ETH dual mining mode. Smiley
        BZiGER
        Newbie
        *
        Offline Offline

        Activity: 19
        Merit: 0


        View Profile
        January 22, 2019, 08:49:46 PM
         #13

        Is there going to be some faster miner.
        with GTX 1060 I have tried bminer in windows and i am geting 2.6 and with nbminer 13.2 i am geting 1.9 max mining GRIN.
        nebutech (OP)
        Member
        **
        Offline Offline

        Activity: 134
        Merit: 26


        View Profile
        January 23, 2019, 12:20:32 AM
         #14

        Is there going to be some faster miner.
        with GTX 1060 I have tried bminer in windows and i am geting 2.6 and with nbminer 13.2 i am geting 1.9 max mining GRIN.


        Yes, new version under development.
        BZiGER
        Newbie
        *
        Offline Offline

        Activity: 19
        Merit: 0


        View Profile
        January 23, 2019, 01:26:18 PM
         #15

        Great  Wink
        I get a lot of restarts of my RIG GTX 1060 and i have measured wattage from the wall is not going over 600w with 6x1060 anyone know what is could be the problem ?
        stolarzz
        Newbie
        *
        Offline Offline

        Activity: 111
        Merit: 0


        View Profile
        January 23, 2019, 01:35:06 PM
         #16

        Is there going to be some faster miner.
        with GTX 1060 I have tried bminer in windows and i am geting 2.6 and with nbminer 13.2 i am geting 1.9 max mining GRIN.

        How did you manage to run 1060 in windows? Im getting out of memory with bminer.
        BZiGER
        Newbie
        *
        Offline Offline

        Activity: 19
        Merit: 0


        View Profile
        January 23, 2019, 02:13:54 PM
         #17

        We are in Nbminer topic  Cheesy Bminer is only working in Windows on 1060 if you have a few 1070 in a rig.
        haliy-2017
        Newbie
        *
        Offline Offline

        Activity: 74
        Merit: 0


        View Profile
        January 26, 2019, 04:48:34 PM
         #18

        I can not run NBMiner 13.2 on the eu.stratum.grin-pool.org pool, how to create a batch file?
        nebutech (OP)
        Member
        **
        Offline Offline

        Activity: 134
        Merit: 26


        View Profile
        January 30, 2019, 09:22:33 AM
         #19

        New version update
        V14.0. Grin
        promomei
        Sr. Member
        ****
        Offline Offline

        Activity: 399
        Merit: 254



        View Profile
        January 30, 2019, 12:13:43 PM
         #20

        New version update
        V14.0. Grin

        1060 6gb suported ?
        Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 »
          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!