You think it is a good solution to punish normal russian people?
By using the Putin miner (Gminer, Team Red Miner) you donate 1% of your mining revenue to support the war. We all knew you were already an absolute disgrace of a miner programmer, but this is beyond low. I'm from Sweden, Todxx is from the US. This is known and can be verified by god knows how many parties in the mining world who know us by name, incl a few well-known S&P500 companies. Also, being a Scandinavian yourself you know very f-ing well how excited we all are at the moment. But then again, you don't really care about anything to get people to run your absolute garbage product now do you, incl smearing good names and involving f-ing ongoing tragedies in the world in your fake narratives? I honestly can't believe you're so dumb that you think that "Team Red" is a reference to some "Red Army", or are you actually? |
|
|
|
launched a farm profile that worked on version 8.4 to version 8.5 and shows some kind of error -8 on one of the 5700 video cards with ADL fan control and will not start, I had to return version 8.4
when activating the option --fan_control = 63 ::: 50: 1: 90 in version 8.5, the program does not start if there are 5700 video cards , fix it otherwise it is impossible to control the fans Interesting, can you tell me what driver version you're on and I'll try to reproduce? of course ATI_AdrenalinDrivers20.5.1. OverdriveNTool2.9 works with these drivers, so I use them I believe I reproduced this issue and it will be fixed in 0.8.6, released in a few days from now. I'll downgrade to 20.5.1 myself tomorrow and test as well to verify. |
|
|
|
Any plans on adding support for Radeon VII with newer drivers?
I updated to most recent drivers for the 6800 XT, which really helped a lot of features and stability, but it killed my R7.
Works with other miners, but really like TRM
ditto We'll release 0.8.6 in 1-2 days that should address the issues for R7 on newer Adrenalin drivers. I'd love to get a few more users to verify it runs ok for them as well though. If you have a chance of joining our Discord server and send me (Kerney666) a DM there I'll give you a beta release to test. |
|
|
|
launched a farm profile that worked on version 8.4 to version 8.5 and shows some kind of error -8 on one of the 5700 video cards with ADL fan control and will not start, I had to return version 8.4
when activating the option --fan_control = 63 ::: 50: 1: 90 in version 8.5, the program does not start if there are 5700 video cards , fix it otherwise it is impossible to control the fans  Interesting, can you tell me what driver version you're on and I'll try to reproduce? |
|
|
|
Anybody knows why TR miner on Polaris cards (470/480/570/580/590) builds DAG so long?
TR miner build it in about 12-13 sec. on my 580 8Gb cards. 1st of all I'm thought that it's only 1st time after launching (cache, etc.). But every time when DAG changes it take so long as at launch.
But other miners (Claymore, lol, Phoenix) builds DAG about 7-8 seconds.
Well, we just got tired of reports of aggressive (and in some aspects suboptimal) Polaris straps that caused the DAG build read/write pattern to crash gpus, so we defaulted to a very slow and safe version. For continuous ethash mining it's 4-5 secs extra every 4.5 days, 0.0016% penalty, but naturally worse if you switch between epochs more often for some reason, or crash every 2-3h and restart the miner. I honestly don't remember exactly what type of cap we ended up with, but try adding --eth_dag_slowdown=0 and check the DAG build time. |
|
|
|
I manage about 30 amd rigs in the birmingham area of the uk.
really like your miner - it does all you claim and is slightly better than the competition.
its especially good on radeon VII and rx5700 .
at present the rigs all have the following set in the config.txt file
core clock
mem clock
core volts
mem volts
fixed fan speed
max temp before gpu throttles (this is vital)
theres other stuff but those 6 things are the main ones.
if your miner could set those 6 things within its config - i would dump the competition and use your miner on all rigs.
yes i know about overdriventool and msi afterburner but in my experience on rigs with 470, 570,480,580,5500, 5700, radeon vii -
those tools are hit and miss and too much trubble .
we use windows 10 ghost spectre (no updates, bloat or telemetry) and mostly amd driver 20.9.1
the one rig that isnt 20.9.1 - has a vega frontier edition 16gb water cooled - i should do a video on
that rig - what a palaver to get that card mining. but we did it with driver 19.7.1 and the registry hack
ghost spectre rocks - you will be amazed. no updates . rock solid . tiny ram usage . tiny disk usage.
best wishes from manchester uk
Clocks/voltage support is being worked on, most probably windows only in the first release. Fan support already exists, see --fan_control in the USAGE.txt docs (incl tracking core and/or mem temp, using a static speed, defined min/max range and more), but we've also fixed some Navi fan control issues for the next release. For temps, we don't throttle per se to keep the gpu running close to the limit, it's assumed the user should make sure to keep temps within the expected range and the protection is rather against broken fans or similar incidents. We do a hard cutoff at 85C (default) and stop mining until the gpu reaches 65C again. See --temp_limit and --temp_resume for more info. Last, I'm sure you're well aware that VIIs do excel under linux with our C-mode becoming available after a few kernel parameter tweaks, just mentioning it just in case. I'm guessing running is homogeneous environment is more important for you guys. |
|
|
|
Hi, guys I have 4 GPUs (3 rx 580 and 1 rx 570) of 4 gb, I started mining Ravencoin (kawpow) after ETH. I have a problem, after 40 minutes of work, the machine shuts down. It's my turn to reboot and restart, does anyone have any ideas? This is my configuration: teamredminer.exe -a kawpow --temp_limit=95 --enable_compute -o stratum+tcp://rvn-us-east1.nanopool.org:12222 -u WALLET.VMGV/myemail -p x I thought it might be the temperatures and I limited them, it keeps restarting. I adjusted the power limit on MSI Afterburner and it continues to reset. I have 4 gb of RAM, SSD 60gb, modified virtual memory, enough disk space, windows 10, tweaks, windows defender off, etc. I wait for some suggestion, thanks! Just a guess, but this sounds like a PSU issue to me? Do I understand you correctly that you get sudden hard reboots, machine just bounces without any form of proper shutdown? |
|
|
|
Hello.
Can anyone tell me the simplest way to reboot rig, when any videocard detects faulty?
In RaveOS.
Can you tell me exact example?
Thank you in advance.
Iirc, RaveOS inspects the kernel logs looking gpu errors, then first tries to restart the miner, then the next time it reboots the system. It sounds like you want to have the miner reboot immediately? The problem is that RaveOS sends a hard kill signal, most probably terminating the miner before it has a chance to launch a watchdog script. But, if I'm wrong and that functionality isn't enabled for you in RaveOS, you can try adding --watchdog_script=watchdog_sysrq.sh, that's our standard forced reboot script. That will only work if RaveOS bundles that with the miner in their own internal miner package. So, the bottom line is that the RaveOS support is probably better for helping you if the above doesn't work. |
|
|
|
Is it possible to have the miner shutdown when a GPU reaches a certain temperature instead of just stopping the GPU?
Thanks
Sorry, no, we only have the hard pause/resume functionality to protect against e.g. broken fans, would have to be executed externally with some script either polling our API for gpu temps, or inspecting the gpu sensors in some other way. |
|
|
|
I wanted to give TRM a chance mining ETH but I am not having good luck with it.
I'm using RaveOS. My setup is just a 5x RX570 rig. Using the exact same OC/voltage settings for Phoenix and TRM.
TRM's reported number is a little less, which I expected, but (with TRM) after about 4-5 hours my rig drops from 153 MH/s to 120 MH/s (every card drops to about 20MH/s instead of running at just over 30 MH/s).
Phoenix is stable for days with the exact same OC settings at 156 MH/s
I would like to make TRM work with stability if I can without sacrificing power consumption.
That sounds odd, so not a specific gpu crash, but all gpus drop to 20 MH/s each instead? That's not the typical error scenario really, I wonder what's going on with the rig at that time. You don't see any excessive cpu consumption, and gpu temps are fine all the time, Rave is controlling fans? |
|
|
|
Is it possible to set Intensity with this miner I like to use my computer for word and still mine at the same time.
and I also get all the time
dev pool failed to connect.
to which pool is connecting and which port?
Hm that's odd. If you come to our Discord we can debug over a DM session there, I need to know your area/region and have you try a few things. |
|
|
|
thanks a lot!
one more question. i now run the vegas with ref 15600 rc 35 rcdrd 19 get 47 mh/s hashrate when auto tune set konfig on a1024.
but autotune set is not erverytime the same for example now 1 card is on eth config a736 and there are only 44mh's hashrate . Same cards with the same settings.
Can i set the eth config fix in the command line? or start autotune new?
and i need help with a batch file for amd tweak tool for startup i've the amdtweaktoolxl and i wrote
(folder of tweak toolxl...).exe --i 0,1,2,3,4,5 --rcdrd 19 --REF 15600 --rfc 164 --rc 35
it opens the tweak tool but didn't set any settings?
thx
Use --eth_config=A1024 to make all cards use A1024. If you have a mixed rig, you might need to specify each gpu individually with --eth_config=A1024,A288,A1024 for a Vega+Polaris+Vega setup. The autotune shouldn't really miss that much though, I wonder if you were throttled or something during the tuning, hmm. For the mem tweaks, you need to download the command line tool, not the xl tool. Grab it here: https://github.com/Eliovp/amdmemorytweak/releases/tag/0.1.9.1. Download WinAMDTweak.exe, IOMap.sys, IOMap64.sys. Then, you need to go to version 0.1.8.1 and download EIO.dll as well. ElioVP missed including that file in the 0.1.9.1 release. Last, run WinAMDTweak.exe as Administrator using your arguments listed above and it should work. |
|
|
|
Hello Miners!
Can you please tell me if there any way to decrease mining intensity when particular card is overheating, like options "-ttli" and "-tstop" in claymore?
Thank you, and "May the Profit be with you"
Sorry, not atm. The plan is to tie it to our fan control, i.e. you provide the target temp for the fans, if we can't manage to hold the target temp even with fans blasting, we'll revert to throttling the intensity instead. For hard start/stop limits (more for protection against broken fans) we have: --temp_limit=TEMP Sets the temperature at which the miner will stop GPUs that are too hot.
Default is 85C.
--temp_resume=TEMP Sets the temperature below which the miner will resume GPUs that were previously
stopped due to temperature exceeding limit. Default is 60C.
|
|
|
|
api_listen=127.0.0.1:3333 doesnt seem to work with claymores miner manager 4.0
We'll add a built-in adapter to our own API so it'll work with Claymore's old stuff shortly, one-two versions away. |
|
|
|
[2020-12-12 18:37:57] Pool eu-01.miningrigrentals.com received new job. (job_id: 0x3bef404a660..., diff 0.250 / 1074 MH)
[2020-12-12 18:37:57] Pool eu-01.miningrigrentals.com share rejected. (GPU3) Error code: 23 - Low difficulty (a:126 r:1u) (356 ms) (diff 4.98 GH)
What is this error? i see this error every 2-3 hour and reject
miner is stable and work fine 3-4 days but have 1% reject
other ring identical. work fine but 1% reject for error code 23
Pretty high accept roundtrip time on that share, looks like a Nicehash reject as well. Is this a rental period or are you falling back to Nicehash between rentals? Nicehash are horrible with their reject policy, they pump out jobs and reject anything for "old" jobs from 200ms ago. You can see that you just received a new job right before the share was rejected, so my guess is simply that the share was for the prev job, and the underlying pool (Nicehash or not) rejects it. |
|
|
|
Hi guys,
Does any one know how to set core memory speed and voltage on bat file?thanks
Hi! Sorry, we don't support setting clocks/voltages/timings in the miner, we're relying on mining os distros and tools like OverdriveNTool or MSI Afterburner on win. We do have it on the roadmap, but it most probably won't happen before the ongoing crazy 4GB period has slowed down. |
|
|
|
kerney666 - thanks for moving the ETH Cfg values into the upper table of detail stats with the v0.7.19 release. Was going to request something like that, so ETH Cfg didn't take up it's own section of extra lines per gpu, but now it's already nice and compacted.
Yeah I moved it since it became even more ridiculous when the new (optional) high score list was added, using even more vertical space  . I also enjoy this version much more myself, should have moved it with the last rewrite of the stats output really. |
|
|
|
hi,
i'm new on TRM. i have 4 vega red evil 56 card hynix ,with my settings from claymore i get a hashrate on 43mh/s
930mhz mem 1050 core on 900mv can't get the mem higher.
i try modded the mem timings with the amdmemorytweakxl tool.
i always get the 43mh/s
i'm not sure i've im doing it right. try the changes from the ethgenreraltuning list in tweak tool. apply.
does TRM auto tuning reset this settings? or do i have to add anything in the command line?
thy
The 43 MH/s is the classic limit at stock timings, so it really sounds like the changed timings aren't being applied properly for you. The miner doesn't touch anything related to clocks/voltages/timings, only the fan curve if you have fan control enabled. It's hard to say why the timings aren't being applied. If you start the miner and let it run for a few mins, then open amdmemtweakxl and e.g. boost tREF to 17000 or make a slight adjustment down for tRCDWR and apply the changes, does the hashrate move in the miner? If not, what timing are displayed of you close+reopen amdmemtweakxl, are your changes there? hi, thx now i got 46 mh/s with 1700 on ref and 20rcdrd and 4 rcdwr. there was no diference with rcdwr starts on 10. does the settings from tweak tool reset after pc restart? watchdog is enabled with restart the system. can i set a target temp for fan with command line ? or just settingfan speed? My bad, I wrote rcdwr but really meant rcdrd. That's the one you want to lower slowly. Also, did you do 1700 or 17000 for ref? For fan control, you can target a core temp, junction temp, or mem temp, set the initial fan speed or a static fan speed. Use --fan_control --fan_default_vega=::70:60 to target 70C mem temp with fans initially at 60%. |
|
|
|
hi,
i'm new on TRM. i have 4 vega red evil 56 card hynix ,with my settings from claymore i get a hashrate on 43mh/s
930mhz mem 1050 core on 900mv can't get the mem higher.
i try modded the mem timings with the amdmemorytweakxl tool.
i always get the 43mh/s
i'm not sure i've im doing it right. try the changes from the ethgenreraltuning list in tweak tool. apply.
does TRM auto tuning reset this settings? or do i have to add anything in the command line?
thy
The 43 MH/s is the classic limit at stock timings, so it really sounds like the changed timings aren't being applied properly for you. The miner doesn't touch anything related to clocks/voltages/timings, only the fan curve if you have fan control enabled. It's hard to say why the timings aren't being applied. If you start the miner and let it run for a few mins, then open amdmemtweakxl and e.g. boost tREF to 17000 or make a slight adjustment down for tRCDWR and apply the changes, does the hashrate move in the miner? If not, what timing are displayed of you close+reopen amdmemtweakxl, are your changes there? |
|
|
|
Guys i have idea-- if 6800 have cache like processor, is it possible to make them mine randomX  ?!! It most probably means RandomX runs better on a 6800 than e.g. a 5700XT. That said, I don't think it will be the rational choice as a miner, there aren't enough 2MB pads available in 128MB to even run a single hash on each compute unit on a 6800XT. |
|
|
|
|
Show Posts
