Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 77. (Read 703583 times)

Sxemini, hello.

You suggested everything correctly. I figured it out, it works fine. Thank.

One of my rigs is running Ubuntu 20.04 desktop with 2 GPUs as follows:

GPU 0 EVGA 1070Ti PCI Bus ID 1
GPU 1 MSI 1070 PCI Bus ID 2

Both are showing up in the GPU tab and both are hashing.

However, for some reason I'm only able to control the power and clock settings for GPU 0.

When I go to tools/GPU clocking, only GPU 0 is showing up.

All my other rigs, mostly running nvOC (Ubuntu based) and Win10, do not have this issue.

Any ideas?

Thanks

Thanks for your question. From what I've seen from ZIL mining so far is that you connect to a specific mining pool (one pool) that takes care of the ZIL + ETH mining. So from Awesome Miner point of view, it's a single pool that do both coins behind the scene.

I'm not sure if there are any ZIL mining pools that allows you to actually mine ETH elsewhere. I think the ZIL+ETH concept is more like merged mining rather than dual mining. Again, I'm not an expert on this specific coin so there might be other users here with more information on how it actually works.

Did you specify a number after "-fast"? Otherwise Bminer will not accept your custom command line argument. It must be "-fast 1" or similar.

With the latest definition update I've mapped "ethash" for T-Rex miner.

For Mining Pool Hub, it looks like some incompatibility between the T-Rex miner and their Ethereum pool.

The Nicehash, this requires a small code change in Awesome Miner to change the protocol to "nicehash+tcp" as you pointed out. This will be part of the next release.

I've just pushed a mining software definition update where most of the SrbMiner algorithms are mapped by default. Click on "Update mining software definitions" via the blue Menu button.

Please note the following:
- The recent versions of SrbMiner is very sensitive to the command line argument order so manually specifying the algorithm via "Command line arguments" in the Properties of a miner will not work. It must be added by Awesome Miner to ensure the correct order.
- Like sxemini pointed out, it's possible to manually specify the command line arguments for an algorithm via the Options dialog, Managed Software section.
- In the case of RandomEpic, this algorithm wasn't included in Awesome Miner by default. With the recent definition update it is, so no need to manually add it.

Can you please open the Properties for your Icemining RandomEpic pool, and set the algorithm to either "Unspecified RandomEpic" or if you have any specific coin for this defined. Once Awesome Miner knows the algorithm of the pool, it should be able to map it to a command line argument (like 'randomepic' for SrbMiner). Can you please verify this once you have the latest mining software definition update?

Thanks!

I really want it to mine nicehash eth and zil in another stratum, I don't know if the miners are prepared for that, or they should only use a single stratum.

hi @patrike, I can't find a way to do dual mining with claymore, if I activate it for dual there is no option for ZIL. How can I do to mine ETH + ZIL?

Hi Patrike.

Looks like AM delegate a wrong parameter config for Bminer 16.3.1 with new param -fast I am was unable to start mining process, Syntax error.

AM sent this string:
/root/.config/AwesomeMinerService/bminer-v16.3.1-135666e-amd64.tar_1/bminer-v16.3.1-135666e/bminer   -fast -watchdog=false -uri ethash://0x71c0c1e65dfb0a24dc59b851701fd92d51f37910.1070_@eu1.ethermine.org:4444 -api=0.0.0.0:4028

Bminer crash output:
invalid value "-watchdog=false" for flag -fast: strconv.ParseInt: parsing "-watchdog=false": invalid syntax
Bminer: When Crypto-mining Made Fast (v16.3.1-135666e)

AM v.8.0.2

And big thanks for great HeatMap feature.

Regards


Upd. without -fast flag i can start Bminer, but miner not find any valid shares, miner only in DAG file creation loop till crash.
8x1070 rig, Linux, hiveOS 0.6-157, NVIDIA driver 440.82 (Tested on ethermine, nicehash)

Hi Patrik,

the new version of T-Rex mining Ethereum at NiceHash needs a special prefix:

"0.17.2 * Add "ethash" algorithm (for Ethereum). For Nicehash mining use "nicehash+tcp://" pool url prefix."

I know in Online Services / Properties. But how can this be done, if we also want to use other miners than just T-Rex for Ethereum at NiceHash? These other miners would also get the new prefix which should not work. And T-Rex will not work with the standard prefix. Is there a workaround or can you do some magical auto detecting tricks here for that case?

Using latest AM v8.0.2 with latest t-rex-0.17.2 which added ethash algorithm for Ethereum.  Had to manually enable algo ethash in Managed software options.

Diagnostics when starting t-rex with -a ethash :

Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner version: 8.0.2
OS: Microsoft Windows 10 Pro 64-bit
GPU Details:
  nVidia driver version: 445.75
  nVidia OpenCL Platform ID: 0
  GPUs: RTX 2080, RTX 2070 SUPER
Prerequisites:
  Microsoft .NET Framework: 4.8
  Microsoft VC++ 2013 runtime installed: Yes
  Microsoft VC++ 2015 runtime installed: Yes
  Microsoft VC++ 2017 runtime installed: Yes
  Microsoft VC++ 2019 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 2
Engine Type: TrexMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: TrexMiner, IsProfitMiner: False)
====================================================================================================
C:\Users\micha\AppData\Local\AwesomeMiner\t-rex-0.17.2-win-cuda10.0_2\t-rex.exe  --no-watchdog -a ethash -o stratum+tcp://us-east.ethash-hub.miningpoolhub.com:20535 -u xxxxxx -p x --api-bind-http 0.0.0.0:4029
====================================================================================================
Mining Engine Process started, PID: 2768
20200918 14:50:07 T-Rex NVIDIA GPU miner v0.17.2  -  [CUDA v10.0]
20200918 14:50:07 r.f5cafaef2077
20200918 14:50:07
20200918 14:50:07 NVIDIA Driver v445.75
20200918 14:50:07 CUDA devices available: 2
20200918 14:50:07
20200918 14:50:07 WARN: DevFee 1% (ethash)
20200918 14:50:07
20200918 14:50:07 URL : stratum+tcp://us-east.ethash-hub.miningpoolhub.com:20535
20200918 14:50:07 USER: xxxxxx
20200918 14:50:07 PASS: x
20200918 14:50:07
20200918 14:50:07 WARN: Built-in watchdog has been disabled!
20200918 14:50:07 Starting on: us-east.ethash-hub.miningpoolhub.com:20535
20200918 14:50:08 ApiServer: HTTP server started on 0.0.0.0:4029
20200918 14:50:08 ------------------------------------------------------
20200918 14:50:08 For control navigate to: http://192.168.1.13:4029/trex
20200918 14:50:08 ------------------------------------------------------
20200918 14:50:08 ApiServer: Telnet server started on 0.0.0.0:4068
20200918 14:50:08 Authorizing...
20200918 14:50:08 WARN: GPU #0[80000]: ASUS GeForce RTX 2070 SUPER, intensity set to 20
20200918 14:50:08 WARN: GPU #1[a0000]: ASUS GeForce RTX 2080, intensity set to 20
20200918 14:50:10 WARN: failed to subscribe, JSON-RPC call failed: member "id" is null (original json {"id":null,"method":"mining.notify","params":["91f8","0x8f218018500cb90ec56d2c7aee7de389f5b14a68b75b62d3443e0006554e5a50","0x8552ce848ce6b5e0b813e271bd44862eda17e35032821ba00a44f2e4ace34fcd","0x000000007ffffffe00000007ffffffe00000007ffffffe00000007ffffffe000",true]}
)
20200918 14:50:13 WARN: failed to subscribe, JSON-RPC call failed: member "id" is null (original json {"id":null,"method":"mining.notify","params":["91f9","0x865576c840f9577939573a578c4f38b0f001443a7afa763cd1ea506716afbc81","0x8552ce848ce6b5e0b813e271bd44862eda17e35032821ba00a44f2e4ace34fcd","0x000000007ffffffe00000007ffffffe00000007ffffffe00000007ffffffe000",true]}
)
20200918 14:50:13 ERROR: No connection, retry after 10 seconds
20200918 14:50:23 Authorizing...
20200918 14:50:26 WARN: failed to subscribe, JSON-RPC call failed: member "id" is null (original json {"id":null,"method":"mining.notify","params":["91fc","0xbf832e7cc5abe63c15ffe066820c9cf96b390828c3094925bcb4f473e4d8c18e","0x8552ce848ce6b5e0b813e271bd44862eda17e35032821ba00a44f2e4ace34fcd","0x000000007ffffffe00000007ffffffe00000007ffffffe00000007ffffffe000",true]}
)
20200918 14:50:26 WARN: failed to subscribe, JSON-RPC call failed: member "id" is null (original json {"id":null,"method":"mining.notify","params":["91fd","0xc01057f1394d2505a01d2310e4843abf45806d85c2e0cee45e46c17dfcec76ad","0x8552ce848ce6b5e0b813e271bd44862eda17e35032821ba00a44f2e4ace34fcd","0x000000007ffffffe00000007ffffffe00000007ffffffe00000007ffffffe000",true]}
)
20200918 14:50:26 ERROR: No connection, retry after 10 seconds


====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
Diagnostics completed

Yes patrike write it is sensitive and i give you the right way. You don´t need to add it to the bat file.

IF YOU ADD THIS AS I DESCRIBED, AWESOMEMINER WILL ADD THE RIGHT ALGO AND NO EMPTY SPACE.  

AS YOU CAN SEE IN MY PICTURE THE DEFAULT COMMAND FOR VERUSHASH IS EMPTY SO IT ADDS A EMPTY SPACE, YOU MUST ADD IT IN THE USER DEFINED LINE.

I do what patrike with the next release will do. But if you don´t understand my point it´s also ok.

Patrike has no activate verushash and m7m for srbminer 0.5.2. So you must add it manualy in Options -> managed software -> search srb 0.5.2 miner in the list -> edit and add verushash and m7m.

  Yes, Patrick, I deleted - yescrypt algorithm, miner started, data is displayed. But on other algorithms awesome does not give the desired algorithm, and it does not start in manual mode, I checked it with the m7m, verushash algorithms with srb 5.2

There are no changes for SrbMiner in this release.

Did you try to remove your custom command line argument " --algorithm yescrypt" as I suggested via PM earlier? SrbMiner 0.5 seems to be very sensitive to the order of the command line arguments, so for the algorithm it's better to let Awesome Miner add it for you.

Great that you found the incorrect file version. When I install the latest nVidia drivers, this nvml.dll file was updated correctly so you might just have had some back luck with the nVidia installer.

Nothing has changed for me, srbminer for cpu does not start, problem with api. I downloaded version 5.2 still does not start.

Hi patrike,

Seems there is an issue with the driver updater from Nvidia, as the nvml.dll file was not getting updated in the "C:\Windows\system32" folder.

I copied over the latest file to this folder and all is well now.

Thanks for the help with this issue.

Awesome Miner version 8.0.2 (Development preview of 8.1)

 Features
  - Heat maps can be displayed in the web interface
  - Improved sorting of miners in the list of available miners for a heat map
  - The information column can display the MAC address of a miner
 Integration
  - Wallet balance feature can be configured to send custom HTTP headers when requesting balance from a block explorer
 Mining software
  - WildRig 0.26.0
  - Bminer 16.3.1
  - T-rex miner 0.17.2
 Corrections
  - Correction to list of groups when moving miners in web interface
  - Corrected tooltip display for miners in the heat map

Thanks for making the tests. For some reason it works fine and I see the power usage on RTX 2080 with both 452.06 and the new 456.38 I'm running right now.

Can you please click the button "View GPU details" in the GPU tab and send me the details via PM? Thanks!

Does anyone else experience this problem on the latest nVidia drivers?

Edit: One more question. Can you please look at the file version of "nvml.dll"? Please search for the file as it may be located in more folders than "C:\Windows\system32".