[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 35.

Commie

full member

Activity: 621

Merit: 108

Quote from: sxemini on December 01, 2021, 04:15:30 AM

Quote from: Commie on December 01, 2021, 04:10:06 AM

Quote from: sxemini on December 01, 2021, 04:00:48 AM

you have a failure in your pool connection stratum1? Why stratum1? only stratum+tcp://

And i would prefer lolminer for LHR cards

If T-Rex support dual stratum - you must write the complete commandline in the commandline parameters.

As I said this was just a try, nor stratum neither stratum1 worked with any pool/miner

Did you ping the server. But the t-rex picture is showing that you have an failure in your commandline.

Ok i checked t-rex miner:

setup your ethermine pool normal with your normal eth address and without zil specific arguments and add the following to your commandline parameters:

--coin eth+zil --url2 stratum+tcp://eu.ezil.me:5555 --user2 "eth-wallet"."zil-wallet".WORKER --extra-dag-epoch 0

Did you click on details in AM and checked the whole commandline? Can you please the commandline from AM here? So that we can check it? And test other rustpool server please.

And did you activate "add to worker name:" in the miner properties? If so, please deactivate it.

It's weird. I pinged all pools and everything is ok with low latency around 15-40ms. However, I just tried adding this line to command parameters of my usual Ethermine pool settings and again - no connection.

sxemini

member

Activity: 1558

Merit: 69

Quote from: Commie on December 01, 2021, 04:10:06 AM

Quote from: sxemini on December 01, 2021, 04:00:48 AM

you have a failure in your pool connection stratum1? Why stratum1? only stratum+tcp://

And i would prefer lolminer for LHR cards

If T-Rex support dual stratum - you must write the complete commandline in the commandline parameters.

As I said this was just a try, nor stratum neither stratum1 worked with any pool/miner

Did you ping the server. But the t-rex picture is showing that you have an failure in your commandline.

Ok i checked t-rex miner:

setup your ethermine pool normal with your normal eth address and without zil specific arguments and add the following to your commandline parameters:

--coin eth+zil --url2 stratum+tcp://eu.ezil.me:5555 --user2 "eth-wallet"."zil-wallet".WORKER --extra-dag-epoch 0

Did you click on details in AM and checked the whole commandline? Can you please the commandline from AM here? So that we can check it? And test other rustpool server please.

And did you activate "add to worker name:" in the miner properties? If so, please deactivate it.

Commie

full member

Activity: 621

Merit: 108

Quote from: sxemini on December 01, 2021, 04:00:48 AM

you have a failure in your pool connection stratum1? Why stratum1? only stratum+tcp://

And i would prefer lolminer for LHR cards

If T-Rex support dual stratum - you must write the complete commandline in the commandline parameters.

As I said this was just a try, nor stratum neither stratum1 worked with any pool/miner

sxemini

member

Activity: 1558

Merit: 69

you have a failure in your pool connection stratum1? Why stratum1? only stratum+tcp://

And i would prefer lolminer for LHR cards

If T-Rex support dual stratum - you must write the complete commandline in the commandline parameters.

Ok i checked t-rex miner:

setup your ethermine pool normal with your normal eth address and without zil specific arguments and add the following to your commandline parameters:

--coin eth+zil --url2 stratum+tcp://eu.ezil.me:5555 --user2 "eth-wallet"."zil-wallet".WORKER --extra-dag-epoch 0

Commie

full member

Activity: 621

Merit: 108

Quote from: sxemini on December 01, 2021, 02:34:37 AM

My config only works for rustpool or shardpool. Why all using ezil for mining zil? Ezil is a eth+zil in one pool.
If you want to mine zil on ezil and eth on ethermine, you need dual stratum connections -> teamredminer, lolminer, srbminer can handle it, but you need many more arguments for the commandline.b (maybe t-rex miner also, but also with more arguments)

Thing is, exactly the same is happening with rustpool and I can't figure out what I missed.

I've tried changing stratum1 to stratum and back, no effect

Also tried Gminer on rustpool+ethermine, it didn't work either.

My objective is to keep T-Rex as it's currently the best for Nvidia LHR cards and Ethermine pool for ETH, ZIL pool can be any. There are plenty of sample configs for HiveOS but none for AM. I'm obviously missing some small detail but what can it be?

Quote from: patrike on December 01, 2021, 01:56:48 AM

From what I can see, there is no concept of specifying your own ETH-mining pool here.

1) The "Pool URL" field in Awesome Miner should be: stratum+tcp://asia.ezil.me:5555
2) The "Worker name" field in Awesome Miner should be on the following format, as it's corresponding to the full user name: ETH_WALLET.ZIL_WALLET
3) The "Password" and "Wallet address" fields in Awesome Miner should be left blank.

In case you want to use the "WORKER" parameters as well (optional), you may have to manually add "-w WORKER" in the additional command line.

Patrik, here's what shardpool recommends for Gminer: miner.exe --algo eth --server as1-zil.shardpool.io:3333 --user ETH_wallet.Rig2 --pass [email protected]:4444 --proto stratum
Since T-Rex also supports dual mining I wonder how to transfer that to AM pool config.

sxemini

member

Activity: 1558

Merit: 69

Quote from: Commie on November 29, 2021, 08:52:11 AM

Quote from: STSMiner on November 29, 2021, 07:03:56 AM

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

In my case Patrik helped me to find another active copy of AM on my other notebook, which was causing conflicts and delays. The situation improved after I disabled it. However, BSODs still happen regardless of OC settings, no idea what to do with that.

Also, I'm still having trouble configuring ETH+ZIL dual mining. I re-read sxemini's guide, studied pool instructions but currently my miner (T-rex) immediately connects to Ezil/Rustpool instead of Ethermine and drops connection by timeout. Screenshots are attached, what am I doing wrong?

PS Tried adding following line to extra parameters, same result: -a ethash -o stratum+tcp://asia.ezil.me:5555 -u -p @asia1.ethermine.org:4444 -w Rig2 --extra-dag-epoch 0

My config only works for rustpool or shardpool. Why all using ezil for mining zil? Ezil is a eth+zil in one pool.
And you must understand, if you mining over for example rustpool -> it will only connect to rustpool, but you get the jobs from ethermine, because rustpool work as an proxy server.

If you want to mine zil on ezil and eth on ethermine, you need dual stratum connections -> teamredminer, lolminer, srbminer can handle it, but you need many more arguments for the commandline.b (maybe t-rex miner also, but also with more arguments)

There are so many ways to mine zil+eth/rvn/erg/vtc and so on, but first you must understand how zil mining and the pools are working (not so hard by the way)

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Commie on November 29, 2021, 08:52:11 AM

Quote from: STSMiner on November 29, 2021, 07:03:56 AM

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

In my case Patrik helped me to find another active copy of AM on my other notebook, which was causing conflicts and delays. The situation improved after I disabled it. However, BSODs still happen regardless of OC settings, no idea what to do with that.

Also, I'm still having trouble configuring ETH+ZIL dual mining. I re-read sxemini's guide, studied pool instructions but currently my miner (T-rex) immediately connects to Ezil/Rustpool instead of Ethermine and drops connection by timeout. Screenshots are attached, what am I doing wrong?

PS Tried adding following line to extra parameters, same result: -a ethash -o stratum+tcp://asia.ezil.me:5555 -u -p @asia1.ethermine.org:4444 -w Rig2 --extra-dag-epoch 0

The ezil.me mining pool uses the following configuration concept (taken from https://ezil.me/start)
t-rex -a ethash -o stratum+tcp://asia.ezil.me:5555 -u ETH_WALLET.ZIL_WALLET -p x -w WORKER

From what I can see, there is no concept of specifying your own ETH-mining pool here.

1) The "Pool URL" field in Awesome Miner should be: stratum+tcp://asia.ezil.me:5555
2) The "Worker name" field in Awesome Miner should be on the following format, as it's corresponding to the full user name: ETH_WALLET.ZIL_WALLET
3) The "Password" and "Wallet address" fields in Awesome Miner should be left blank.

In case you want to use the "WORKER" parameters as well (optional), you may have to manually add "-w WORKER" in the additional command line.

cajunsands

newbie

Activity: 6

Merit: 0

for some reason i had set it to manually start as admin the shortcut, put it back to normal and checked the *run at startup* rebooted now it all seems ok ...odd

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: cajunsands on November 29, 2021, 08:26:20 AM

Anyone having issues with remote agent refusing to restart with windows reboot?

Remote Agent is set to automatically start with Windows, but you must still start it manually each time? Is this a default setup where Remote Agent runs under your local user account or have you modified any permissions or forced Admin-permissions for the Remote Agent executable (not recommended). Any security software running that could prevent applications for automatically starting?

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: STSMiner on November 29, 2021, 08:44:21 AM

Quote from: sxemini on November 29, 2021, 08:00:55 AM

Quote from: STSMiner on November 29, 2021, 07:03:56 AM

Quote from: Commie on November 21, 2021, 03:38:18 AM

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating nvlddmkm.sys pagefile error, no idea how to fix this so far Sad

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

Not getting the reboots tho, using the latest Nvidia DCH drivers here.

@patrike, maybe you can look into the first issue to see what's causing this.

This happens if something is wrong with your Remote client installation or the windows of the remote client. And sometimes AM need a little bit to recognize a client after the reboot, but i think it is normal.

Did not have this issue before until version 9.0.X .... and nothing has changed here on the rigs other than drivers for the GPU's and the re-install of the client and main app in an attempt to fix the issue, but it still persists and can take up to 2 minutes to see the remote rigs on the same network / submask.

Can you please send me the Awesome Miner and Remote Agent log file and let me know the time of the issue? I will of course investigate to see what the issue might be. As Commie pointed out, his case was related to running two Awesome Miner instances connected to the same Remote Agent.

Commie

full member

Activity: 621

Merit: 108

Quote from: STSMiner on November 29, 2021, 07:03:56 AM

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

In my case Patrik helped me to find another active copy of AM on my other notebook, which was causing conflicts and delays. The situation improved after I disabled it. However, BSODs still happen regardless of OC settings, no idea what to do with that.

Also, I'm still having trouble configuring ETH+ZIL dual mining. I re-read sxemini's guide, studied pool instructions but currently my miner (T-rex) immediately connects to Ezil/Rustpool instead of Ethermine and drops connection by timeout. Screenshots are attached, what am I doing wrong?

PS Tried adding following line to extra parameters, same result: -a ethash -o stratum+tcp://asia.ezil.me:5555 -u -p @asia1.ethermine.org:4444 -w Rig2 --extra-dag-epoch 0

STSMiner

full member

Activity: 270

Merit: 115

Quote from: sxemini on November 29, 2021, 08:00:55 AM

Quote from: STSMiner on November 29, 2021, 07:03:56 AM

Quote from: Commie on November 21, 2021, 03:38:18 AM

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating nvlddmkm.sys pagefile error, no idea how to fix this so far Sad

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

Not getting the reboots tho, using the latest Nvidia DCH drivers here.

@patrike, maybe you can look into the first issue to see what's causing this.

This happens if something is wrong with your Remote client installation or the windows of the remote client. And sometimes AM need a little bit to recognize a client after the reboot, but i think it is normal.

Did not have this issue before until version 9.0.X .... and nothing has changed here on the rigs other than drivers for the GPU's and the re-install of the client and main app in an attempt to fix the issue, but it still persists and can take up to 2 minutes to see the remote rigs on the same network / submask.

cajunsands

newbie

Activity: 6

Merit: 0

Anyone having issues with remote agent refusing to restart with windows reboot?

sxemini

member

Activity: 1558

Merit: 69

Quote from: STSMiner on November 29, 2021, 07:03:56 AM

Quote from: Commie on November 21, 2021, 03:38:18 AM

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating nvlddmkm.sys pagefile error, no idea how to fix this so far Sad

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

Not getting the reboots tho, using the latest Nvidia DCH drivers here.

@patrike, maybe you can look into the first issue to see what's causing this.

This happens if something is wrong with your Remote client installation or the windows of the remote client. And sometimes AM need a little bit to recognize a client after the reboot, but i think it is normal.

STSMiner

full member

Activity: 270

Merit: 115

Quote from: Commie on November 21, 2021, 03:38:18 AM

Since 9.0.4 or 9.0.5 weird things are happening to AM and one of my rigs. Whenever it reboots AM just doesn't see it until minutes later, then reports rig as stopped and doesn't start the miner (manually or automatically) until I restart the AM on my controlling PC. All machines run Win10 with latest Nvidia drivers, I tried reinstalling both but it didn't solve the problem. Another rig works just fine. Has anyone else experienced this?

PS Reboots started happening a week or two ago with BSOD indicating nvlddmkm.sys pagefile error, no idea how to fix this so far Sad

Yup, been having the same issue here, remote rigs are not seen for a good minute or two, even re-installed the main program and clients and drivers for GPU's, still get the same results.

Not getting the reboots tho, using the latest Nvidia DCH drivers here.

@patrike, maybe you can look into the first issue to see what's causing this.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: cajunsands on November 29, 2021, 12:19:40 AM

running the latest develpment version , running it for Raptoreum mining, when will it officlaly be added? (cant track the coin)

Thanks for your request. We will add it during the day.

cajunsands

newbie

Activity: 6

Merit: 0

running the latest develpment version , running it for Raptoreum mining, when will it officlaly be added? (cant track the coin)

patrike

legendary

Activity: 3346

Merit: 1094

Version 9.0.8 (Development preview of 9.1)

GPU mining
- Improved compatibility for setting GPU memory voltage for AMD on Linux
Features
- Mining history export will include current device count and the current number of failed hash boards
Mining software
- PhoenixMiner 5.9c
- WildRig 0.30.6.1
- XmRig 6.16.0
Corrections
- Correction to ASIC type detection

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates.

Sensis82

newbie

Activity: 1

Merit: 0

Can someone give me a little Setup Guide for MRR on Awesome Miner please ?

Kind regards

Dominik

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Firstblackhaw on November 25, 2021, 10:46:50 PM

Awesome Miner have not displayed hashrate of SRB Miner new versions (0.83 and 0.84). Please update Awesome Miner software !

Please upgrade to Awesome Miner development version v9.0.7.

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