kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
November 24, 2020, 11:26:26 AM |
|
Hello, seems that hotkey for disable and enable GPU works only for gpu number 0-9. key A-F doesn't work. For example A or a is read as GPU 0, B as GPU 1 and so on. Is this a bug or I miss something?
regards
edit: I'm using v0.7.17
It's fixed in the next release 0.7.18, out in a few hours from now (unless something pops up in the final tests).
|
|
|
|
|
|
|
|
You get merit points when someone likes your post enough to give you some. And for every 2 merit points you receive, you can send 1 merit point to someone else!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
ETC365
Newbie
Offline
Activity: 2
Merit: 0
|
|
November 24, 2020, 04:27:51 PM |
|
Hello, seems that hotkey for disable and enable GPU works only for gpu number 0-9. key A-F doesn't work. For example A or a is read as GPU 0, B as GPU 1 and so on. Is this a bug or I miss something?
regards
edit: I'm using v0.7.17
It's fixed in the next release 0.7.18, out in a few hours from now (unless something pops up in the final tests). Looking forward to the next release, fantastic work!
|
|
|
|
TheSkyTurk
Jr. Member
Offline
Activity: 47
Merit: 3
|
|
November 25, 2020, 01:06:20 AM |
|
I have 15 GH eth mining hashrate. I use Phoenixminer but it gives many incorrect shares only on navi gpus last two days. There was any problem before. I m looking for a different miner. I m trying TeamRedMiner with RX 5700 XT GPUs. I realized TeamRedMiner gives lower hashrate with same settings. What should i do ?
Well, I would maybe ask you to run the miner for 1-2 days to assess the poolside hashrate. With 15 GH you don't have that much variance. You'll notice that we actually do hit the reported hashrate - dev fee over time, adjusted for stales. If you have any questions we're always around in our discord, and much more active there than here on Bitcointalk. i decided to give a shot TRM. if it is better than Phoenix, i will use it on my all miners. I know each miner and each OS has different oc settings. So, i have to find the weet spots for the rig. I set the highest core, VDD, VDDCI and MVDD. First, I will find the highest memory for each GPU. HiveOS Version: 0.6-175@201120, Kernel Version: 5.0.21-hiveos-beta, AMD Driver Version: 19.30 Team Red Miner Version: 0.7.17 12 x Sapphire Nitro+ RX 5700 XT Samsung Memory. IS: Invalid Shares. 644.6 MH/s, 1730W, CORE 1400, VDD 800, MEM 875, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 648.3 MH/s, 1735W, CORE 1400, VDD 800, MEM 880, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 651.8 MH/s, 1745W, CORE 1400, VDD 800, MEM 885, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 655.5 MH/s, 1750W, CORE 1400, VDD 800, MEM 890, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 659.0 MH/s, 1755W, CORE 1400, VDD 800, MEM 895, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 662.7 MH/s, 1760W, CORE 1400, VDD 800, MEM 900, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 666.4 MH/s, 1765W, CORE 1400, VDD 800, MEM 905, MVDD 1350, VDDCI 850 - GPU1-IS1_GPU3-IS6 after 10m mining. XXX.X MH/s, XXXXW, CORE 1400, VDD 800, MEM 905_GPU3-900, MVDD 1350, VDDCI 850 - GPU1-IS1_GPU3-IS1_GPU5-DEAD_GPU7-IS1 - teamredminer reboot after 7m mining. XXX.X MH/s, XXXXW, CORE 1400, VDD 800, MEM 905_GPU3-900_GPU5-900, MVDD 1350, VDDCI 850 - GPU7-IS1 - teamredminer reboot without any reason after 8m mining. XXX.X MH/s, XXXXW, CORE 1400, VDD 800, MEM 905_GPU3-900_GPU5-900, MVDD 1350, VDDCI 850 - teamredminer reboot without any reason after 8m mining. XXX.X MH/s, XXXXW, CORE 1400, VDD 800, MEM 905_GPU3-900_GPU5-900, MVDD 1350, VDDCI 850 - teamredminer reboot without any reason after 7m mining. teamredminer reboot: === Last 50 lines of /var/log/miner/teamredminer/teamredminer.log === [2020-11-25 01:16:51] Watchdog script executor thread executing script 'watchdog.sh' [2020-11-25 01:16:51] ------------------------------------------------------------------------------------------------ [2020-11-25 01:16:51] Mining ethash with 12 GPU workers [2020-11-25 01:16:51] GPU PCIe CUs CoreMHz SocMHz MemMHz TEdge TJct TMem FanPct FanRpm VDDC [2020-11-25 01:16:51] 0 03:00.0 40 1400 950 905 68C 75C 88C 40.78% 1407 781 mV [2020-11-25 01:16:51] 1 06:00.0 40 1400 950 905 68C 76C 88C 50.98% 1738 781 mV [2020-11-25 01:16:51] 2 09:00.0 40 1400 950 905 66C 72C 86C 43.92% 1498 781 mV [2020-11-25 01:16:51] 3 0c:00.0 40 1400 950 900 68C 76C 90C 42.75% 1495 781 mV [2020-11-25 01:16:51] 4 0f:00.0 40 1400 950 905 66C 75C 88C 53.73% 1857 781 mV [2020-11-25 01:16:51] 5 13:00.0 40 1400 1085 100 59C 62C 64C 34.90% 1200 793 mV [2020-11-25 01:16:51] 6 16:00.0 40 1400 950 905 67C 76C 88C 40.78% 1411 781 mV [2020-11-25 01:16:51] 7 19:00.0 40 1400 950 905 67C 74C 88C 42.75% 1467 781 mV [2020-11-25 01:16:51] 8 1c:00.0 40 1400 950 905 67C 72C 88C 41.96% 1461 781 mV [2020-11-25 01:16:51] 9 1f:00.0 40 1400 950 905 67C 75C 88C 43.92% 1526 781 mV [2020-11-25 01:16:51] 10 22:00.0 40 1400 950 905 67C 74C 88C 44.71% 1557 781 mV [2020-11-25 01:16:51] 11 25:00.0 40 1400 950 905 67C 75C 88C 51.76% 1799 781 mV [2020-11-25 01:16:51] [2020-11-25 01:16:51] Current eth configs: [2020-11-25 01:16:51] GPU 0 A624 [2020-11-25 01:16:51] GPU 1 A620 [2020-11-25 01:16:51] GPU 2 A608 [2020-11-25 01:16:51] GPU 3 A612 [2020-11-25 01:16:51] GPU 4 A628 [2020-11-25 01:16:51] GPU 5 A624 [2020-11-25 01:16:51] GPU 6 A624 [2020-11-25 01:16:51] GPU 7 A620 [2020-11-25 01:16:51] GPU 8 A616 [2020-11-25 01:16:51] GPU 9 A618 [2020-11-25 01:16:51] GPU10 A608 [2020-11-25 01:16:51] GPU11 A616 [2020-11-25 01:16:51] [2020-11-25 01:16:51] Stats Uptime: 0 days, 00:07:04 [2020-11-25 01:16:51] ----------------------------------------- GPU Status ------------------------------------------- [2020-11-25 01:16:51] GPU 0 [68C, fan 40%] ethash: 55.54Mh/s, avg 54.00Mh/s, pool 38.09Mh/s a:4 r:0 hw:0 [2020-11-25 01:16:51] GPU 1 [68C, fan 50%] ethash: 55.53Mh/s, avg 54.02Mh/s, pool 38.11Mh/s a:4 r:0 hw:0 [2020-11-25 01:16:51] GPU 2 [66C, fan 43%] ethash: 55.53Mh/s, avg 54.03Mh/s, pool 76.25Mh/s a:8 r:0 hw:0 [2020-11-25 01:16:51] GPU 3 [68C, fan 42%] ethash: 55.24Mh/s, avg 53.76Mh/s, pool 66.75Mh/s a:7 r:0 hw:0 [2020-11-25 01:16:51] GPU 4 [66C, fan 53%] ethash: 55.54Mh/s, avg 54.08Mh/s, pool 57.24Mh/s a:6 r:0 hw:0 [2020-11-25 01:16:51] GPU 5 [59C, fan 34%] ethash: 54.82Mh/s, avg 50.44Mh/s, pool 47.72Mh/s a:5 r:0 hw:0 [2020-11-25 01:16:51] GPU 6 [67C, fan 40%] ethash: 55.55Mh/s, avg 54.13Mh/s, pool 47.75Mh/s a:5 r:0 hw:0 [2020-11-25 01:16:51] GPU 7 [67C, fan 42%] ethash: 55.54Mh/s, avg 54.14Mh/s, pool 57.32Mh/s a:6 r:0 hw:0 [2020-11-25 01:16:51] GPU 8 [67C, fan 41%] ethash: 55.53Mh/s, avg 54.16Mh/s, pool 76.47Mh/s a:8 r:0 hw:0 [2020-11-25 01:16:51] GPU 9 [67C, fan 43%] ethash: 55.54Mh/s, avg 54.18Mh/s, pool 28.69Mh/s a:3 r:0 hw:0 [2020-11-25 01:16:51] GPU10 [67C, fan 44%] ethash: 55.53Mh/s, avg 54.19Mh/s, pool 47.84Mh/s a:5 r:0 hw:0 [2020-11-25 01:16:51] GPU11 [67C, fan 51%] ethash: 55.54Mh/s, avg 54.21Mh/s, pool 28.72Mh/s a:3 r:0 hw:0 [2020-11-25 01:16:51] Total ethash: 665.4Mh/s, avg 645.3Mh/s, pool 610.9Mh/s a:64 r:0 hw:0 [2020-11-25 01:16:51] ----------------------------------------- Pool Status ------------------------------------------ [2020-11-25 01:16:51] eu1.ethermine.org ethash: 621.6Mh/s, avg 636.4Mh/s, pool 609.4Mh/s a:64 r:0 [2020-11-25 01:16:51] eu1.ethermine.org ethash: 0.000 h/s, avg 0.000 h/s, pool 0.000 h/s a:0 r:0 [2020-11-25 01:16:51] ------------------------------------------------------------------------------------------------ Miner doesnt say which GPU has problem because of the high memory value. How will i find it ? I have to find the highest memory value for each GPU, then i will reduce power usage. I can find the highest memory value in Phoenix cause it tells me which GPU has hw error. Help me to find it in TRM, please.
|
|
|
|
catfish78
Newbie
Offline
Activity: 142
Merit: 0
|
|
November 25, 2020, 06:30:17 AM |
|
Can I set cclock, mclock, cvddc, mvddc with this miner or do I need extra tool for that?
|
|
|
|
komalige
Newbie
Offline
Activity: 3
Merit: 0
|
|
November 25, 2020, 10:39:32 AM |
|
Hi, can someone please tell me if there is in TRM intensity control for single GPU? And could someone give me and full example how to use --fan_control, cos i didnt understand it from usage.txt Thanks in advance.
|
|
|
|
komalige
Newbie
Offline
Activity: 3
Merit: 0
|
|
November 25, 2020, 11:08:33 AM |
|
Can I set cclock, mclock, cvddc, mvddc with this miner or do I need extra tool for that?
Hi, i think you can do it with OverdriveNTool or similar 3rd party soft. I guess you cannot mine with claymore same as me
|
|
|
|
sys2007
Newbie
Offline
Activity: 10
Merit: 0
|
|
November 26, 2020, 04:42:17 PM |
|
Hello ! Failed to add support for RX5500XT yf 4GB?
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
November 27, 2020, 12:35:03 PM |
|
I have 15 GH eth mining hashrate. I use Phoenixminer but it gives many incorrect shares only on navi gpus last two days. There was any problem before. I m looking for a different miner. I m trying TeamRedMiner with RX 5700 XT GPUs. I realized TeamRedMiner gives lower hashrate with same settings. What should i do ?
Well, I would maybe ask you to run the miner for 1-2 days to assess the poolside hashrate. With 15 GH you don't have that much variance. You'll notice that we actually do hit the reported hashrate - dev fee over time, adjusted for stales. If you have any questions we're always around in our discord, and much more active there than here on Bitcointalk. i decided to give a shot TRM. if it is better than Phoenix, i will use it on my all miners. I know each miner and each OS has different oc settings. So, i have to find the weet spots for the rig. I set the highest core, VDD, VDDCI and MVDD. First, I will find the highest memory for each GPU. HiveOS Version: 0.6-175@201120, Kernel Version: 5.0.21-hiveos-beta, AMD Driver Version: 19.30 Team Red Miner Version: 0.7.17 12 x Sapphire Nitro+ RX 5700 XT Samsung Memory. IS: Invalid Shares. 644.6 MH/s, 1730W, CORE 1400, VDD 800, MEM 875, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 648.3 MH/s, 1735W, CORE 1400, VDD 800, MEM 880, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 651.8 MH/s, 1745W, CORE 1400, VDD 800, MEM 885, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 655.5 MH/s, 1750W, CORE 1400, VDD 800, MEM 890, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 659.0 MH/s, 1755W, CORE 1400, VDD 800, MEM 895, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 662.7 MH/s, 1760W, CORE 1400, VDD 800, MEM 900, MVDD 1350, VDDCI 850 - No memory error after 10m mining. 666.4 MH/s, 1765W, CORE 1400, VDD 800, MEM 905, MVDD 1350, VDDCI 850 - GPU1-IS1_GPU3-IS6 after 10m mining. XXX.X MH/s, XXXXW, CORE 1400, VDD 800, MEM 905_GPU3-900, MVDD 1350, VDDCI 850 - GPU1-IS1_GPU3-IS1_GPU5-DEAD_GPU7-IS1 - teamredminer reboot after 7m mining. XXX.X MH/s, XXXXW, CORE 1400, VDD 800, MEM 905_GPU3-900_GPU5-900, MVDD 1350, VDDCI 850 - GPU7-IS1 - teamredminer reboot without any reason after 8m mining. XXX.X MH/s, XXXXW, CORE 1400, VDD 800, MEM 905_GPU3-900_GPU5-900, MVDD 1350, VDDCI 850 - teamredminer reboot without any reason after 8m mining. XXX.X MH/s, XXXXW, CORE 1400, VDD 800, MEM 905_GPU3-900_GPU5-900, MVDD 1350, VDDCI 850 - teamredminer reboot without any reason after 7m mining. teamredminer reboot: === Last 50 lines of /var/log/miner/teamredminer/teamredminer.log === [2020-11-25 01:16:51] Watchdog script executor thread executing script 'watchdog.sh' [2020-11-25 01:16:51] ------------------------------------------------------------------------------------------------ [2020-11-25 01:16:51] Mining ethash with 12 GPU workers [2020-11-25 01:16:51] GPU PCIe CUs CoreMHz SocMHz MemMHz TEdge TJct TMem FanPct FanRpm VDDC [2020-11-25 01:16:51] 0 03:00.0 40 1400 950 905 68C 75C 88C 40.78% 1407 781 mV [2020-11-25 01:16:51] 1 06:00.0 40 1400 950 905 68C 76C 88C 50.98% 1738 781 mV [2020-11-25 01:16:51] 2 09:00.0 40 1400 950 905 66C 72C 86C 43.92% 1498 781 mV [2020-11-25 01:16:51] 3 0c:00.0 40 1400 950 900 68C 76C 90C 42.75% 1495 781 mV [2020-11-25 01:16:51] 4 0f:00.0 40 1400 950 905 66C 75C 88C 53.73% 1857 781 mV [2020-11-25 01:16:51] 5 13:00.0 40 1400 1085 100 59C 62C 64C 34.90% 1200 793 mV [2020-11-25 01:16:51] 6 16:00.0 40 1400 950 905 67C 76C 88C 40.78% 1411 781 mV [2020-11-25 01:16:51] 7 19:00.0 40 1400 950 905 67C 74C 88C 42.75% 1467 781 mV [2020-11-25 01:16:51] 8 1c:00.0 40 1400 950 905 67C 72C 88C 41.96% 1461 781 mV [2020-11-25 01:16:51] 9 1f:00.0 40 1400 950 905 67C 75C 88C 43.92% 1526 781 mV [2020-11-25 01:16:51] 10 22:00.0 40 1400 950 905 67C 74C 88C 44.71% 1557 781 mV [2020-11-25 01:16:51] 11 25:00.0 40 1400 950 905 67C 75C 88C 51.76% 1799 781 mV [2020-11-25 01:16:51] [2020-11-25 01:16:51] Current eth configs: [2020-11-25 01:16:51] GPU 0 A624 [2020-11-25 01:16:51] GPU 1 A620 [2020-11-25 01:16:51] GPU 2 A608 [2020-11-25 01:16:51] GPU 3 A612 [2020-11-25 01:16:51] GPU 4 A628 [2020-11-25 01:16:51] GPU 5 A624 [2020-11-25 01:16:51] GPU 6 A624 [2020-11-25 01:16:51] GPU 7 A620 [2020-11-25 01:16:51] GPU 8 A616 [2020-11-25 01:16:51] GPU 9 A618 [2020-11-25 01:16:51] GPU10 A608 [2020-11-25 01:16:51] GPU11 A616 [2020-11-25 01:16:51] [2020-11-25 01:16:51] Stats Uptime: 0 days, 00:07:04 [2020-11-25 01:16:51] ----------------------------------------- GPU Status ------------------------------------------- [2020-11-25 01:16:51] GPU 0 [68C, fan 40%] ethash: 55.54Mh/s, avg 54.00Mh/s, pool 38.09Mh/s a:4 r:0 hw:0 [2020-11-25 01:16:51] GPU 1 [68C, fan 50%] ethash: 55.53Mh/s, avg 54.02Mh/s, pool 38.11Mh/s a:4 r:0 hw:0 [2020-11-25 01:16:51] GPU 2 [66C, fan 43%] ethash: 55.53Mh/s, avg 54.03Mh/s, pool 76.25Mh/s a:8 r:0 hw:0 [2020-11-25 01:16:51] GPU 3 [68C, fan 42%] ethash: 55.24Mh/s, avg 53.76Mh/s, pool 66.75Mh/s a:7 r:0 hw:0 [2020-11-25 01:16:51] GPU 4 [66C, fan 53%] ethash: 55.54Mh/s, avg 54.08Mh/s, pool 57.24Mh/s a:6 r:0 hw:0 [2020-11-25 01:16:51] GPU 5 [59C, fan 34%] ethash: 54.82Mh/s, avg 50.44Mh/s, pool 47.72Mh/s a:5 r:0 hw:0 [2020-11-25 01:16:51] GPU 6 [67C, fan 40%] ethash: 55.55Mh/s, avg 54.13Mh/s, pool 47.75Mh/s a:5 r:0 hw:0 [2020-11-25 01:16:51] GPU 7 [67C, fan 42%] ethash: 55.54Mh/s, avg 54.14Mh/s, pool 57.32Mh/s a:6 r:0 hw:0 [2020-11-25 01:16:51] GPU 8 [67C, fan 41%] ethash: 55.53Mh/s, avg 54.16Mh/s, pool 76.47Mh/s a:8 r:0 hw:0 [2020-11-25 01:16:51] GPU 9 [67C, fan 43%] ethash: 55.54Mh/s, avg 54.18Mh/s, pool 28.69Mh/s a:3 r:0 hw:0 [2020-11-25 01:16:51] GPU10 [67C, fan 44%] ethash: 55.53Mh/s, avg 54.19Mh/s, pool 47.84Mh/s a:5 r:0 hw:0 [2020-11-25 01:16:51] GPU11 [67C, fan 51%] ethash: 55.54Mh/s, avg 54.21Mh/s, pool 28.72Mh/s a:3 r:0 hw:0 [2020-11-25 01:16:51] Total ethash: 665.4Mh/s, avg 645.3Mh/s, pool 610.9Mh/s a:64 r:0 hw:0 [2020-11-25 01:16:51] ----------------------------------------- Pool Status ------------------------------------------ [2020-11-25 01:16:51] eu1.ethermine.org ethash: 621.6Mh/s, avg 636.4Mh/s, pool 609.4Mh/s a:64 r:0 [2020-11-25 01:16:51] eu1.ethermine.org ethash: 0.000 h/s, avg 0.000 h/s, pool 0.000 h/s a:0 r:0 [2020-11-25 01:16:51] ------------------------------------------------------------------------------------------------ Miner doesnt say which GPU has problem because of the high memory value. How will i find it ? I have to find the highest memory value for each GPU, then i will reduce power usage. I can find the highest memory value in Phoenix cause it tells me which GPU has hw error. Help me to find it in TRM, please. Hi! Sorry for the late reply, haven't been checking in here the last few days. The issue in your output is that we see no reason for a reboot. The log might have been truncated, but that's a little strange as well. However, piecing things together I'm pretty sure it's gpu 5 above. You can see that its avg hashrate has dropped to ~50 MH/s instead of continuing to build a higher average like the other gpus, and that it's running a 100 MHz mem clock, indicating the driver tried to reset the gpu after a crash. I also see this: XXX.X MH/s, XXXXW, CORE 1400, VDD 800, MEM 905_GPU3-900, MVDD 1350, VDDCI 850 - GPU1-IS1_GPU3-IS1_GPU5-DEAD_GPU7-IS1 - teamredminer reboot after 7m mining....which indicates gpu 5 was the reason for the first reboot (GPU5-DEAD in the logged line). For the other reboots, I just don't know without any more data. The only reason I can see is a driver bug that occurs at times that crashes the gpu and starts leaking mem at a very high rate, then the os kills the miner. When gpus are just overclocked too much and generate bad shares, you'll see the hw err column to the right increasing for some gpu(s).
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
November 27, 2020, 12:36:08 PM |
|
Can I set cclock, mclock, cvddc, mvddc with this miner or do I need extra tool for that?
Hi, i think you can do it with OverdriveNTool or similar 3rd party soft. I guess you cannot mine with claymore same as me Correct, for the time being we don't support setting clocks/voltages/timings/etc. It will most probably be added at some point, but for now you need to revert to wattman/overdriventool/afterburner or some other tool.
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
November 27, 2020, 12:45:18 PM |
|
Hi, can someone please tell me if there is in TRM intensity control for single GPU? And could someone give me and full example how to use --fan_control, cos i didnt understand it from usage.txt Thanks in advance.
If I assume you're meaning intensity for ethash, you use --eth_config=Axyz where xyz is a number between 0 and 16 x Compute Units available on the gpu. For a 470/570, the range is 0-512, 480/580 0-576, Vega 56 0-896, Vega 64 0-1024, Navi 5700XT 0-640, Navi 5700/5600XT 0-576, etc. The first char also denotes the "mode" we're using. It doesn't matter for most gpus atm, it's mostly for the Radeon VIIs these days. You can see what mode the auto-tuner chooses for you in the stats output every 30s and use that as a base. Lower the number to decrease the intensity. What gpu type are you looking to control the intensity for? For fan control, you add --fan_control to enable it. For a single gpu, you can just add a custom config directly with the same argument: --fan_control=45:::50 would be "keep core temp at 45C, start the fans at 50% of max". If you have a gpu with mem temp sensors (check the stats output if there's any value reported in that column or not for the gpu), you can rather use that temp as the target: --fan_control=45::70:50 would add the condition "...also keep mem temp <= 70C" to the previous example.
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
November 27, 2020, 12:45:58 PM |
|
Hello ! Failed to add support for RX5500XT yf 4GB?
The driver support was just horrible. Can't run on either ETH or ETC atm. Might return to it if I find time and check newer drivers.
|
|
|
|
Pe_Da
Jr. Member
Offline
Activity: 58
Merit: 5
|
|
November 27, 2020, 06:29:59 PM |
|
Is there a plan to implement the Octopus algorithm?
|
|
|
|
komalige
Newbie
Offline
Activity: 3
Merit: 0
|
|
November 27, 2020, 11:10:21 PM |
|
Hi, can someone please tell me if there is in TRM intensity control for single GPU? And could someone give me and full example how to use --fan_control, cos i didnt understand it from usage.txt Thanks in advance.
If I assume you're meaning intensity for ethash, you use --eth_config=Axyz where xyz is a number between 0 and 16 x Compute Units available on the gpu. For a 470/570, the range is 0-512, 480/580 0-576, Vega 56 0-896, Vega 64 0-1024, Navi 5700XT 0-640, Navi 5700/5600XT 0-576, etc. The first char also denotes the "mode" we're using. It doesn't matter for most gpus atm, it's mostly for the Radeon VIIs these days. You can see what mode the auto-tuner chooses for you in the stats output every 30s and use that as a base. Lower the number to decrease the intensity. What gpu type are you looking to control the intensity for? For fan control, you add --fan_control to enable it. For a single gpu, you can just add a custom config directly with the same argument: --fan_control=45:::50 would be "keep core temp at 45C, start the fans at 50% of max". If you have a gpu with mem temp sensors (check the stats output if there's any value reported in that column or not for the gpu), you can rather use that temp as the target: --fan_control=45::70:50 would add the condition "...also keep mem temp <= 70C" to the previous example. @kerney666 you answered very clearly, thanks a lot. By the way i'm using RX 580.
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
November 28, 2020, 01:20:40 AM |
|
Is there a plan to implement the Octopus algorithm?
Unfortunately, there really is no point spending the time. It's a fun algo, you could play around a lot with abstract algebra tricks. However, the tensor cores in the Nvidia RTX cards are giving them such an enormous edge for this algo, so no rational AMD owner would run the implementation. The FP16 throughput using the tensor cores just blows AMD and other Nvidia gpus out of the water. For example, a 1080ti is by no means a weak compute card, but you can see how pathetic the hashrate is vs e.g. a 2070ti. AMD owners would always be better off mining ETH and buy Conflux instead.
|
|
|
|
Pe_Da
Jr. Member
Offline
Activity: 58
Merit: 5
|
|
November 28, 2020, 12:31:09 PM Last edit: November 28, 2020, 01:34:15 PM by Pe_Da |
|
Is there a plan to implement the Octopus algorithm?
Unfortunately, there really is no point spending the time. It's a fun algo, you could play around a lot with abstract algebra tricks. However, the tensor cores in the Nvidia RTX cards are giving them such an enormous edge for this algo, so no rational AMD owner would run the implementation. The FP16 throughput using the tensor cores just blows AMD and other Nvidia gpus out of the water. For example, a 1080ti is by no means a weak compute card, but you can see how pathetic the hashrate is vs e.g. a 2070ti. AMD owners would always be better off mining ETH and buy Conflux instead. To bad but understandable if the algo is moore optimized at nVidia. Any news about the RX6000 Series Et(c)hash and Kawpow implementation? Is there a chance for a speed up the hashrate, because of the new "Infinity Cache" or "Smart Access Memory"? Thank you!
|
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
|
November 29, 2020, 03:34:19 PM Last edit: November 29, 2020, 09:35:40 PM by livada |
|
i read this but no understud --eth_hashwatch(=M,M) Defines a min/max watchdog hashrate in MH/s expected when gpus are hashing. If a GPU falls outside of this range for too long it will be considered faulty and the watchdog will be triggered. The default min/max values are 2 MH/s and 150 MH/s. To activate with default values, use --eth_hashwatch. To set your own values, use e.g. --eth_hashwatch=1.25,60. The same range is used for all gpus in the rig. A negative value for one side disables it, e.g. use --eth_hashwatch=-1,1000 to handle gpu resets that result in huge fake hashrates but no minimum check. what is what in this? --eth_hashwatch=1.25,60 1 is gPU1 ? 25 is minimum 25mh ? 60 is maximum 60mh? or 1.25 is MH min? i have 6 vega and 1 vega give 45-50mh/s - all rig have 280mh this option use only1 gpu HR or all rig HR ? what command i must use? or this option use for 1,vega- and i use only default command --eth_hashwatch?? i wont restart miner if my rig give 200mh or less. pls what comand i use for this? this command --eth_hashwatch=200,300 is good? 200hr min 300 max? why i must use MAX? or i must use for 1 gpu limit? this command --eth_hashwatch=40,51
|
|
|
|
geck
Member
Offline
Activity: 145
Merit: 10
|
|
November 30, 2020, 02:25:02 PM |
|
Hi,
I'm unable to get awesomeminer to link up with trm running on hiveos. I have --api_listen=4028 in hiveos config, however awesomeminer is unable to see it. Is there something else i should be doing or is my config wrong?
|
|
|
|
mitak64
|
|
November 30, 2020, 08:25:32 PM |
|
Hi,
I'm unable to get awesomeminer to link up with trm running on hiveos. I have --api_listen=4028 in hiveos config, however awesomeminer is unable to see it. Is there something else i should be doing or is my config wrong?
Correct port for TRed on HiveOS is 65078.
|
|
|
|
heavyarms1912
|
|
December 01, 2020, 01:37:44 AM |
|
i read this but no understud --eth_hashwatch(=M,M) Defines a min/max watchdog hashrate in MH/s expected when gpus are hashing. If a GPU falls outside of this range for too long it will be considered faulty and the watchdog will be triggered. The default min/max values are 2 MH/s and 150 MH/s. To activate with default values, use --eth_hashwatch. To set your own values, use e.g. --eth_hashwatch=1.25,60. The same range is used for all gpus in the rig. A negative value for one side disables it, e.g. use --eth_hashwatch=-1,1000 to handle gpu resets that result in huge fake hashrates but no minimum check. what is what in this? --eth_hashwatch=1.25,60 1 is gPU1 ? 25 is minimum 25mh ? 60 is maximum 60mh? or 1.25 is MH min? i have 6 vega and 1 vega give 45-50mh/s - all rig have 280mh this option use only1 gpu HR or all rig HR ? what command i must use? or this option use for 1,vega- and i use only default command --eth_hashwatch?? i wont restart miner if my rig give 200mh or less. pls what comand i use for this? this command --eth_hashwatch=200,300 is good? 200hr min 300 max? why i must use MAX? or i must use for 1 gpu limit? this command --eth_hashwatch=40,51 --eth_hashwatch=1.25,60 means every gpu follows this range in your mining config. if any GPU falls under 1.25 MHs it would trigger watchdog. If it goes beyond 60 MHs it would trigger the watchdog. Ethash is in MHs for almost every card hence the MHs is unit of measurement. You can use anything below 40 for min and anything above 60 or a more flexible range like 35 as min,70 as max.
|
|
|
|
geck
Member
Offline
Activity: 145
Merit: 10
|
|
December 01, 2020, 11:49:01 AM |
|
Hi,
I'm unable to get awesomeminer to link up with trm running on hiveos. I have --api_listen=4028 in hiveos config, however awesomeminer is unable to see it. Is there something else i should be doing or is my config wrong?
Correct port for TRed on HiveOS is 65078. Thanks! works perfectly.
|
|
|
|
|