Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 14. (Read 85791 times)

I will also try the watchdog option, although if W10 freezes, there will be no reboot worth. As a collateral measure, I have programmed a script in an Rpi to ping my rig every two hours, and send me an email if there is no response. So I can turn it off remotely via wifi plug.
It is not the desired solution, but it is a solution.

Are you solo-mining? Otherwise, most pools I've used have a hashrate drop notification feature... Although since you've already set up your own alternative, i suppose it's not much help now.

Quote from: joseph32 on April 30, 2019, 01:45:17 PM

About API, I would like this option: "I've been debating adding a public domain integrated http server so people can just point a browser towards the API port and see stats." Grin

You might find this useful in the meantime: https://github.com/rdugan/cgminerhttpinterface

Hi @pbfarmer
Im mining on a NH pool (stratum+tcp://lyra2rev3.eu.nicehash.com:3373). Not sure how to check hashrate drop. Im now using its explorer (https://www.nicehash.com/miner/address)

It is not a very effective solution, because the TRM and pool values rarely coincide.

I also use Teamviewer to connect to my rig and watch TRM live, but it is a very manual measure.

I understand that everything would be much easier with an API and an http connection (easy to monitor, not configure hehehhe). I will investigate about cgminerhttpinterface, but the first impression is that it is not intended for Windows.

Ok - haven't used NH for a while, so not sure whether they have an alert.

I wrote that http interface - for windows initially, but it also works on linux. It's a python app, so you just need to first install python (https://www.python.org/downloads/release/python-373/) if you haven't already.

romeoxxx

newbie

Activity: 2

Merit: 0

Any plans to add lyra2c0ban to your great miner?

bbvedf

member

Activity: 588

Merit: 61

@bbvedf

Why not just use AwesomeMiner? Very easy to use, and great rules for everything.

https://bitcointalksearch.org/topic/awesome-miner-powerful-windows-gui-to-manage-and-monitor-up-to-200000-miners-676942

Hi @joseph32
AwesomeMiner sounds like Minerstat. All good together, very showy, but at the moment when something goes wrong it's hard to touch or look to solve it.
As I have more than obvious OC / UV problems (the rig does not last for three days), I prefer to reduce all the software to a minimum in order to better limit it.

Currently only TRM (GPU's), Xmrig (CPU), ONT (OC/UV) and GPUZ (Monitor) in a clean W10.

I continue "touching buttons", to see if I can stabilize it ... Grin

joseph32

member

Activity: 418

Merit: 21

@bbvedf

Why not just use AwesomeMiner? Very easy to use, and great rules for everything.

https://bitcointalksearch.org/topic/awesome-miner-powerful-windows-gui-to-manage-and-monitor-up-to-200000-miners-676942

bbvedf

member

Activity: 588

Merit: 61

Quote from: pbfarmer on April 30, 2019, 02:52:37 AM

I will also try the watchdog option, although if W10 freezes, there will be no reboot worth. As a collateral measure, I have programmed a script in an Rpi to ping my rig every two hours, and send me an email if there is no response. So I can turn it off remotely via wifi plug.
It is not the desired solution, but it is a solution.

Are you solo-mining? Otherwise, most pools I've used have a hashrate drop notification feature... Although since you've already set up your own alternative, i suppose it's not much help now.

About API, I would like this option: "I've been debating adding a public domain integrated http server so people can just point a browser towards the API port and see stats." Grin

You might find this useful in the meantime: https://github.com/rdugan/cgminerhttpinterface

Hi @pbfarmer
Im mining on a NH pool (stratum+tcp://lyra2rev3.eu.nicehash.com:3373). Not sure how to check hashrate drop. Im now using its explorer (https://www.nicehash.com/miner/address)

It is not a very effective solution, because the TRM and pool values rarely coincide.

I also use Teamviewer to connect to my rig and watch TRM live, but it is a very manual measure.

I understand that everything would be much easier with an API and an http connection (easy to monitor, not configure hehehhe). I will investigate about cgminerhttpinterface, but the first impression is that it is not intended for Windows.

pbfarmer

member

Activity: 340

Merit: 29

I will also try the watchdog option, although if W10 freezes, there will be no reboot worth. As a collateral measure, I have programmed a script in an Rpi to ping my rig every two hours, and send me an email if there is no response. So I can turn it off remotely via wifi plug.
It is not the desired solution, but it is a solution.

Are you solo-mining? Otherwise, most pools I've used have a hashrate drop notification feature... Although since you've already set up your own alternative, i suppose it's not much help now.

Quote from: kerney666 on April 29, 2019, 10:25:13 AM

About API, I would like this option: "I've been debating adding a public domain integrated http server so people can just point a browser towards the API port and see stats." Grin

You might find this useful in the meantime: https://github.com/rdugan/cgminerhttpinterface

bbvedf

member

Activity: 588

Merit: 61

Quote from: bbvedf on April 29, 2019, 09:39:34 AM

Quote from: ku4eto on April 29, 2019, 09:22:13 AM

Quote from: bbvedf on April 29, 2019, 09:39:34 AM

Well guys.
At last Ive installed W10.
AMD official driver 19.4.3
Wattomine for OC/UV (btw, saves its configuration in an xml file, like OverdriveTool)

Atm same hashrate and performance than Minerstat. It's early to know if any GPU will die or when.

Finally, Ive two questions about these parameters.

--watchdog_script(=X)

Ive never used it, but i find it awesome: Check your dead GPU, restart system, ... cool!

--api_listen=IP:PORT

Same. Ive never setup that, but from what I've been reading, it serves to monitor the miner from other machines and/or via web.
[/list]

Do you use these options? Any usage/guide recommendation?

No, the API is not web based, you do not have httpd server in the miner. Although, if you try to access it via the browser, you will get the JSON response as well.

It has been running for 19 hours

When some GPU dies (which will happen), I look at how to add the two parameters.

@ku4eto, do you have any script example for the watchdog?
And as for the API, do I understand that if I enable it and connect via browser to the URL:PORT of the miner, I will see an answer? A "json" answer?

I have never used any of the two parameters, so it still comes a bit big to me Cry

Hi!

For a watchdog script, it depends a little on what you want to do. Most people do a full reboot using e.g. "shutdown /r" in a batch script. Just put that in a watchdog.bat file in the same dir as the miner, and add the --watchdog_script cmd line parameter.

For the API, we chose to include a sgminer-compatible API so that 3rd party tools like Awesome Miner could include our miner with 5 mins work. The design of this API is horrible though. I've been debating adding a public domain integrated http server so people can just point a browser towards the API port and see stats. Right now this is rather raw tcp/ip communication, so it won't work well from a browser.

Hi @kerney666
Finally, W10 freezes. I'm not sure what OC is making my life miserable Cry

I'm going to try another configuration in Wattman, to see if it's better.

I will also try the watchdog option, although if W10 freezes, there will be no reboot worth. As a collateral measure, I have programmed a script in an Rpi to ping my rig every two hours, and send me an email if there is no response. So I can turn it off remotely via wifi plug.
It is not the desired solution, but it is a solution.

About API, I would like this option: "I've been debating adding a public domain integrated http server so people can just point a browser towards the API port and see stats." Grin

kerney666

member

Activity: 658

Merit: 86

Quote from: ku4eto on April 29, 2019, 09:22:13 AM

Quote from: ku4eto on April 29, 2019, 09:22:13 AM

Well guys.
At last Ive installed W10.
AMD official driver 19.4.3
Wattomine for OC/UV (btw, saves its configuration in an xml file, like OverdriveTool)

Atm same hashrate and performance than Minerstat. It's early to know if any GPU will die or when.

Finally, Ive two questions about these parameters.

--watchdog_script(=X)

Ive never used it, but i find it awesome: Check your dead GPU, restart system, ... cool!

--api_listen=IP:PORT

Same. Ive never setup that, but from what I've been reading, it serves to monitor the miner from other machines and/or via web.
[/list]

Do you use these options? Any usage/guide recommendation?

No, the API is not web based, you do not have httpd server in the miner. Although, if you try to access it via the browser, you will get the JSON response as well.

It has been running for 19 hours

When some GPU dies (which will happen), I look at how to add the two parameters.

@ku4eto, do you have any script example for the watchdog?
And as for the API, do I understand that if I enable it and connect via browser to the URL:PORT of the miner, I will see an answer? A "json" answer?

I have never used any of the two parameters, so it still comes a bit big to me Cry

Hi!

For a watchdog script, it depends a little on what you want to do. Most people do a full reboot using e.g. "shutdown /r" in a batch script. Just put that in a watchdog.bat file in the same dir as the miner, and add the --watchdog_script cmd line parameter.

For the API, we chose to include a sgminer-compatible API so that 3rd party tools like Awesome Miner could include our miner with 5 mins work. The design of this API is horrible though. I've been debating adding a public domain integrated http server so people can just point a browser towards the API port and see stats. Right now this is rather raw tcp/ip communication, so it won't work well from a browser.

bbvedf

member

Activity: 588

Merit: 61

Well guys.
At last Ive installed W10.
AMD official driver 19.4.3
Wattomine for OC/UV (btw, saves its configuration in an xml file, like OverdriveTool)

Atm same hashrate and performance than Minerstat. It's early to know if any GPU will die or when.

Finally, Ive two questions about these parameters.

--watchdog_script(=X)

Ive never used it, but i find it awesome: Check your dead GPU, restart system, ... cool!

--api_listen=IP:PORT

Same. Ive never setup that, but from what I've been reading, it serves to monitor the miner from other machines and/or via web.
[/list]

Do you use these options? Any usage/guide recommendation?

No, the API is not web based, you do not have httpd server in the miner. Although, if you try to access it via the browser, you will get the JSON response as well.

It has been running for 19 hours

When some GPU dies (which will happen), I look at how to add the two parameters.

@ku4eto, do you have any script example for the watchdog?
And as for the API, do I understand that if I enable it and connect via browser to the URL:PORT of the miner, I will see an answer? A "json" answer?

I have never used any of the two parameters, so it still comes a bit big to me Cry

ku4eto

jr. member

Activity: 194

Merit: 4

Quote from: kerney666 on April 27, 2019, 05:38:51 AM

Well guys.
At last Ive installed W10.
AMD official driver 19.4.3
Wattomine for OC/UV (btw, saves its configuration in an xml file, like OverdriveTool)

Atm same hashrate and performance than Minerstat. It's early to know if any GPU will die or when.

Finally, Ive two questions about these parameters.

--watchdog_script(=X)

Ive never used it, but i find it awesome: Check your dead GPU, restart system, ... cool!

--api_listen=IP:PORT

Same. Ive never setup that, but from what I've been reading, it serves to monitor the miner from other machines and/or via web.
[/list]

Do you use these options? Any usage/guide recommendation?

No, the API is not web based, you do not have httpd server in the miner. Although, if you try to access it via the browser, you will get the JSON response as well.

bbvedf

member

Activity: 588

Merit: 61

Well guys.
At last Ive installed W10.
AMD official driver 19.4.3
Wattomine for OC/UV (btw, saves its configuration in an xml file, like OverdriveTool)

Atm same hashrate and performance than Minerstat. It's early to know if any GPU will die or when.

Finally, Ive two questions about these parameters.

--watchdog_script(=X)

Ive never used it, but i find it awesome: Check your dead GPU, restart system, ... cool!

--api_listen=IP:PORT

Same. Ive never setup that, but from what I've been reading, it serves to monitor the miner from other machines and/or via web.
[/list]

Do you use these options? Any usage/guide recommendation?

bbvedf

member

Activity: 588

Merit: 61

Quote from: bbvedf on April 27, 2019, 01:11:17 AM

Quote from: ku4eto on April 27, 2019, 12:40:54 AM

Yes, Kerney and todd have stated, that you may have issues with the miner, if you mine with the CPU as well.

Also, why use that other tool, and not Wattman?

>Yes, Kerney and todd have stated, that you may have issues with the miner, if you mine with the CPU as well.
I had read something in the thread of TRM CN, so I thought it was appropriate to comment on the use of CPU.
Since the last restart, it has been running 24 without problems (CPU + GPU). If a GPU dies again, I will configure Minerstat so that it does not use the CPU and try one more time Cool

>Also, why use that other tool, and not Wattman?
OverdriveTool is the fastest tool to test configurations. It has command line too based on xml, which gives many facilities for scripting.

Hi! To clarify: it should be 100% ok to cpu mine in parallel with TRM. The issue is at _start-up_, which can fail if an aggressive cpu miner is active at the same time. Once TRM has started mining, you can start the cpu miner as well.

Ty @kerney666
It is not my case then Undecided

I start both miners in parallel, and after a few hours/days (indefinite), some of the GPU dies (usually the 4).
This morning was the last time. I have tried the solution of not starting the CPU miner. At the moment without problems, but seeing what you say, I guess it will end up dying again some of my GPU.

I like Minerstat a lot, but for some things it is not manageable (or I do not know how to do it).

In conclusion, the idea of W10 comes back to life.

kerney666

member

Activity: 658

Merit: 86

Quote from: bbvedf on April 27, 2019, 01:11:17 AM

Quote from: ku4eto on April 27, 2019, 12:40:54 AM

Yes, Kerney and todd have stated, that you may have issues with the miner, if you mine with the CPU as well.

Also, why use that other tool, and not Wattman?

>Yes, Kerney and todd have stated, that you may have issues with the miner, if you mine with the CPU as well.
I had read something in the thread of TRM CN, so I thought it was appropriate to comment on the use of CPU.
Since the last restart, it has been running 24 without problems (CPU + GPU). If a GPU dies again, I will configure Minerstat so that it does not use the CPU and try one more time Cool

>Also, why use that other tool, and not Wattman?
OverdriveTool is the fastest tool to test configurations. It has command line too based on xml, which gives many facilities for scripting.

Hi! To clarify: it should be 100% ok to cpu mine in parallel with TRM. The issue is at _start-up_, which can fail if an aggressive cpu miner is active at the same time. Once TRM has started mining, you can start the cpu miner as well.

bbvedf

member

Activity: 588

Merit: 61

Quote from: ku4eto on April 27, 2019, 12:40:54 AM

Yes, Kerney and todd have stated, that you may have issues with the miner, if you mine with the CPU as well.

Also, why use that other tool, and not Wattman?

>Yes, Kerney and todd have stated, that you may have issues with the miner, if you mine with the CPU as well.
I had read something in the thread of TRM CN, so I thought it was appropriate to comment on the use of CPU.
Since the last restart, it has been running 24 without problems (CPU + GPU). If a GPU dies again, I will configure Minerstat so that it does not use the CPU and try one more time Cool

>Also, why use that other tool, and not Wattman?
OverdriveTool is the fastest tool to test configurations. It has command line too based on xml, which gives many facilities for scripting.

ku4eto

jr. member

Activity: 194

Merit: 4

Quote from: bbvedf on April 26, 2019, 02:38:24 AM

Quote from: ku4eto on April 21, 2019, 02:48:20 PM

Quote from: bbvedf on April 20, 2019, 01:58:48 PM

Quote from: ku4eto on April 21, 2019, 02:48:20 PM

...

Well, aside from advising to try if the same happens with another OS, there is nothing else that i can say.

Yeah. I can try any other. I had thought of HiveOS, which is also very well known (although I do not know if it has support for TRM Roll Eyes

)
Nor would I mind using a live-USB from any Linux distro, although maybe the configuration is a bit complicated.
What I do not want is to use Windows (it gave me many problems of locks and restarts).

You know, any recommendation is welcome Grin

Uhh... If it locks, it means bad OC. If it restarts, it means not-so bad OC. I am using Windows on my rig, and uptime is like... 1 month on CN and before that, 1 month on Lyra?

I guess I've found the correct OC / UV for the "damn" GPU.

Quote

FAN 68 68 68 68%
CORE 1257 1257 1257 1237 MHz
MEM 300 300 1000 1000 MHz
VDDC 945 945 0 955 mV
VDDCI 0 0 0 0 mV

Three stable days, without stoppages or restarts. Cheesy

Dammit. If I open my mouth first ...
The gpu3 has failed me again, and this time the gpu1 has accompanied him.
Shit OC. It's driving me crazy.

@ku4eto, do you also have RX580? Can you tell me your setup? I do not mind going back to Windows if I find stability.

Windows 10 1703, a i5-3470 i think, 4GB RAM.

850W PSU.

19.2.1 drivers i think.

1x Gigabyte Aorus 570 4GB Elpida
1x Power Color Red Dragon 580 4GB Samsung
2x MSI Gaming X 580 4GB Elpida

Running 0.4.3 TRM.

Clocks are 1240Mhz core on all 4 GPUs. Voltages are in the 0.875V-0.891V range. Using the same IMC voltage ("Memory" voltage) as the Core one.

All Elpida cards are running for CN on 1850Mhz memory. The Samsung one is on 2050Mhz. Below those, i start to lose hashrate. Otherwise, i was running the memory before that on 1950/2100.

On Lyra, i set the memory slider on below 1750 Mhz, which forces DPM0 for some reason.

Hi @ku4eto!
I have tried another miner (with permission from TRM Roll Eyes

) and apart from getting less hashrate I have not solved anything: GPUs are still dying after a few hours of use.
This weekend I will try a clean Windows 10, to see if it improves.

Two questions, friend:
1. I also use two CPU threads (of 4) with xmrig. Can that affect TRM?

2. In Windows I use OverdriveNTool for OC/UV. Do you see these values well for lyra2rev3?

Quote

[Profile_5]
Name = 1215-910_LUX
GPU_P0 = 300; 750
GPU_P1 = 600; 769
GPU_P2 = 900; 881
GPU_P3 = 1220; 910
GPU_P4 = 1220; 910
GPU_P5 = 1220; 910
GPU_P6 = 1220; 910
GPU_P7 = 1220; 910
Mem_P0 = 300; 750
Mem_P1 = 1000; 800; 0
Mem_P2 = 300; 800
Fan_Min = 800
Fan_Max = 2280
Fan_Target = 75
Fan_Acoustic = 1366
Power_Temp = 80
Power_Target = 0

It's the same profile that I used for PHI2 algo, which does not require memory either.

Yes, Kerney and todd have stated, that you may have issues with the miner, if you mine with the CPU as well.

Also, why use that other tool, and not Wattman?

bbvedf

member

Activity: 588

Merit: 61

Quote from: bbvedf on April 20, 2019, 01:58:48 PM

Quote from: bbvedf on April 20, 2019, 01:58:48 PM

...

Well, aside from advising to try if the same happens with another OS, there is nothing else that i can say.

Yeah. I can try any other. I had thought of HiveOS, which is also very well known (although I do not know if it has support for TRM Roll Eyes

)
Nor would I mind using a live-USB from any Linux distro, although maybe the configuration is a bit complicated.
What I do not want is to use Windows (it gave me many problems of locks and restarts).

You know, any recommendation is welcome Grin

Uhh... If it locks, it means bad OC. If it restarts, it means not-so bad OC. I am using Windows on my rig, and uptime is like... 1 month on CN and before that, 1 month on Lyra?

I guess I've found the correct OC / UV for the "damn" GPU.

Quote

FAN 68 68 68 68%
CORE 1257 1257 1257 1237 MHz
MEM 300 300 1000 1000 MHz
VDDC 945 945 0 955 mV
VDDCI 0 0 0 0 mV

Three stable days, without stoppages or restarts. Cheesy

Dammit. If I open my mouth first ...
The gpu3 has failed me again, and this time the gpu1 has accompanied him.
Shit OC. It's driving me crazy.

@ku4eto, do you also have RX580? Can you tell me your setup? I do not mind going back to Windows if I find stability.

Windows 10 1703, a i5-3470 i think, 4GB RAM.

850W PSU.

19.2.1 drivers i think.

1x Gigabyte Aorus 570 4GB Elpida
1x Power Color Red Dragon 580 4GB Samsung
2x MSI Gaming X 580 4GB Elpida

Running 0.4.3 TRM.

Clocks are 1240Mhz core on all 4 GPUs. Voltages are in the 0.875V-0.891V range. Using the same IMC voltage ("Memory" voltage) as the Core one.

All Elpida cards are running for CN on 1850Mhz memory. The Samsung one is on 2050Mhz. Below those, i start to lose hashrate. Otherwise, i was running the memory before that on 1950/2100.

On Lyra, i set the memory slider on below 1750 Mhz, which forces DPM0 for some reason.

Hi @ku4eto!
I have tried another miner (with permission from TRM Roll Eyes

) and apart from getting less hashrate I have not solved anything: GPUs are still dying after a few hours of use.
This weekend I will try a clean Windows 10, to see if it improves.

Two questions, friend:
1. I also use two CPU threads (of 4) with xmrig. Can that affect TRM?

2. In Windows I use OverdriveNTool for OC/UV. Do you see these values well for lyra2rev3?

Quote

[Profile_5]
Name = 1215-910_LUX
GPU_P0 = 300; 750
GPU_P1 = 600; 769
GPU_P2 = 900; 881
GPU_P3 = 1220; 910
GPU_P4 = 1220; 910
GPU_P5 = 1220; 910
GPU_P6 = 1220; 910
GPU_P7 = 1220; 910
Mem_P0 = 300; 750
Mem_P1 = 1000; 800; 0
Mem_P2 = 300; 800
Fan_Min = 800
Fan_Max = 2280
Fan_Target = 75
Fan_Acoustic = 1366
Power_Temp = 80
Power_Target = 0

It's the same profile that I used for PHI2 algo, which does not require memory either.

ku4eto

jr. member

Activity: 194

Merit: 4

...

Well, aside from advising to try if the same happens with another OS, there is nothing else that i can say.

Yeah. I can try any other. I had thought of HiveOS, which is also very well known (although I do not know if it has support for TRM Roll Eyes

)
Nor would I mind using a live-USB from any Linux distro, although maybe the configuration is a bit complicated.
What I do not want is to use Windows (it gave me many problems of locks and restarts).

You know, any recommendation is welcome Grin

Uhh... If it locks, it means bad OC. If it restarts, it means not-so bad OC. I am using Windows on my rig, and uptime is like... 1 month on CN and before that, 1 month on Lyra?

I guess I've found the correct OC / UV for the "damn" GPU.

Quote

FAN 68 68 68 68%
CORE 1257 1257 1257 1237 MHz
MEM 300 300 1000 1000 MHz
VDDC 945 945 0 955 mV
VDDCI 0 0 0 0 mV

Three stable days, without stoppages or restarts. Cheesy

Dammit. If I open my mouth first ...
The gpu3 has failed me again, and this time the gpu1 has accompanied him.
Shit OC. It's driving me crazy.

@ku4eto, do you also have RX580? Can you tell me your setup? I do not mind going back to Windows if I find stability.

Windows 10 1703, a i5-3470 i think, 4GB RAM.

850W PSU.

19.2.1 drivers i think.

1x Gigabyte Aorus 570 4GB Elpida
1x Power Color Red Dragon 580 4GB Samsung
2x MSI Gaming X 580 4GB Elpida

Running 0.4.3 TRM.

Clocks are 1240Mhz core on all 4 GPUs. Voltages are in the 0.875V-0.891V range. Using the same IMC voltage ("Memory" voltage) as the Core one.

All Elpida cards are running for CN on 1850Mhz memory. The Samsung one is on 2050Mhz. Below those, i start to lose hashrate. Otherwise, i was running the memory before that on 1950/2100.

On Lyra, i set the memory slider on below 1750 Mhz, which forces DPM0 for some reason.

bbvedf

member

Activity: 588

Merit: 61

...

Well, aside from advising to try if the same happens with another OS, there is nothing else that i can say.

Yeah. I can try any other. I had thought of HiveOS, which is also very well known (although I do not know if it has support for TRM Roll Eyes

)
Nor would I mind using a live-USB from any Linux distro, although maybe the configuration is a bit complicated.
What I do not want is to use Windows (it gave me many problems of locks and restarts).

You know, any recommendation is welcome Grin

Uhh... If it locks, it means bad OC. If it restarts, it means not-so bad OC. I am using Windows on my rig, and uptime is like... 1 month on CN and before that, 1 month on Lyra?

I guess I've found the correct OC / UV for the "damn" GPU.

Quote

FAN 68 68 68 68%
CORE 1257 1257 1257 1237 MHz
MEM 300 300 1000 1000 MHz
VDDC 945 945 0 955 mV
VDDCI 0 0 0 0 mV

Three stable days, without stoppages or restarts. Cheesy

Dammit. If I open my mouth first ...
The gpu3 has failed me again, and this time the gpu1 has accompanied him.
Shit OC. It's driving me crazy.

@ku4eto, do you also have RX580? Can you tell me your setup? I do not mind going back to Windows if I find stability.

bbvedf

member

Activity: 588

Merit: 61