Its been stated that there is no support for Hawaii multiple times. Those are ANCIENT GPUs, with terrible performance/power. The devs for sure will not bother giving ANY support for them. 99% of the used GPUs for mining (AMD ones) are Polaris and Vega cards. |
|
|
|
Can i run 12 vegas under windows same rig with this miner?
The miner is not going to stop you. Its probably Windows and the AMD driver. |
|
|
|
Windows 10
XFX RX580 8GB x 1
Asus B250
Corsair HX1200i x 3
9 minutes and 30 seconds later —> Reboots my rig —> each and every time!
Claymore (eth) same rig but with 13 GPUs —> NO problem for weeks!
Claymore charges 1%
TRM charges 2.5% (RVN) and doesn’t pay for my Advils!
Any other mining tool for RVN?
Change your vBIOS timings, GPU voltage/clocks or play with the miner settings? Just because it works with claymore, it does not mean same settings will work for other mines as well. |
|
|
|
Team Red Miner v0.6.1 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.6.1 - Added pool failover and load balancing.
- Added better error messages when failing to allocate eth DAG buffers.
- Added server name for TLS SNI.
- Added automatic setting for environment variables for 4GB GPUs.
- Extended maximum length of usernames and passwords (for some merged mining setups).
- Added report of pool stats.
- Changed initial pool auto detect mode to eth proxy.
- Various fixes for submitting hashrate to pools.
It's been a long time coming, but we finally did it; we added pool failover support  We also added pool hashrate stats to help with tracking multi-pool use. For the more advanced users, we also support load balancing pool strategies. (See the --help output for more info) If you want to try it out, there is an example start_multipool.sh/bat file included in the miner packages. Hi! Are you not supported HAWAI (r9 390/390x/290/290x etc..)? Its a not good if its a true! There are a lot of them in the mining market. I could not run these cards on sveral machines, maybe other drivers are needed? They are not supported. Even newer generations cards were barely profitable 2 months ago, you want a 300W for 30MH/s on ETH ? |
|
|
|
Hello,
I am sure, somebody asked this question,
is it possible to run this miner with R9 290 cards, i have some of them and would like to run this miner not only with my rx cards.
any way to do this?
No, the miner does not support the Hawaii cards. |
|
|
|
TeamRedMiner is very good miner but it will be match better if you add Remote monitoring tool or something similair like Claymore did in his Ethereum dual miner.
You already have it. Its the SGMiner API. |
|
|
|
guys. have an answer to the question? https://bitcointalk.org/index.php?topic=5123724.msg53244888#msg53244888How to apply an automatically saved profile? example. I have an ETH.xml profile file How do I run AMDMemoryTweak so that it applies this profile at startup? I tried to run through the bat file. like this AMDMemoryTweak.exe --ETH.xml does not work. to be AMDMemoryTweak.exe ETH.xml does not work. how to run correctly Huh Tell me please. Run the tool with --help and see what are the available commands... |
|
|
|
For those wondering, what performance improvement we can see on Ethash, i asked todxx in the Discord. 8:41 AM] todxx: On polaris we've seen varying results depending on clocks/voltages/timings, typically results are in the +0-2% improvment range, with typical values in the +0.5-1% range
[8:42 AM] todxx: We haven't done extensive tune testing, but so far we've seen that TRM will run the same or slightly better in terms of stability for a given hardware configuration.
[8:42 AM] todxx: Some of our early testers reported being able to lower voltage slightly more than with CM/PM
[8:44 AM] todxx: Also you'll need to keep in mind that I'm referring to poolside hashrate here (I.E. real effective hashrate). We've noticed that CM/PM are often optimistic about reporting their hashrate compared to actual effective hashrate.
[8:45 AM] todxx: You can see this in PM directly as it prints the effective/pool hashrate in the miner, and it is typically less than the hashrate it reports for GPUs
[8:50 AM] todxx: As for vega, we do see a consistent +1.5-2% over other miners for Vegas with samsung mem. Vega 56s with hynix mem do much much better with trm and the right tuning, easily hitting 50Mh/s with very low power usage.
[8:51 AM] todxx: For the VII we are seeing +5-7% increase in hashrate compared to other miners.
[8:55 AM] todxx: To get good performance on the VIIs you'll need to make sure you're running the v106 bios, hence the pinned message above with the v106 bios installer.
|
|
|
|
If a thread dies, the hash should drop.
but Hash does not decrease‧
There was post like this. One of the threads has died, but the other keeps on working. The hash drops only a bit. The remaining thread gets the freed resources of the dead thread and raises its own performance. |
|
|
|
 gpu3 display dead. but gpu3 has share, and hash is normal. The error count is 0. Is it a false warning? There was post like this. One of the threads has died, but the other keeps on working. |
|
|
|
Team Red Miner v0.5.9 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.5.9 - Added x16rv2 for the upcoming Ravencoin fork.
- Optimization work on x16r: +8-10% hashrate depending on clocks.
- Optimization work on x16r: mem clock no longer as important.
- Issue fix: kernels split into multiple binaries to fix linux amdgpu-pro driver issues.
While the biggest change in this release was the addition of x16rv2, there are also some fixes for CN algos to work around driver bugs/crashes. If anyone was having issues with CN algos resulting in crashes in v0.5.8, we suggest trying v0.5.9. windows 7, blockchain drivers mixed rig - nvidia 1070 + amd rx 570 Team Red Miner version 0.5.9 [2019-09-27 19:57:41] Auto-detected AMD OpenCL platform 0 [2019-09-27 19:57:42] Initializing GPU 0. [2019-09-27 19:57:43] OpenCL enqueue error: -55 [2019-09-27 19:57:43] Warning: failed to initialize device number 0 (-28), retrying. Upd: on amd rig same error Update drivers... Blockchain are really old. |
|
|
|
A bit of reading for me ... Thanks for that. Edit - It seems the third link is dead. #crysx Seems like the domain was closed. Cant do anything about that. |
|
|
|
Hi.
I have problem with my vega rig on grin 29.
Hashrate jumps from 4 to 6 mh constantly (every 1~2 seconds) on all gpus and non of them can reach 7mh.
I disabled all vegas and tried one by one but same problem appears on each of them in single mining mode. (This rig works fine with all other algos including c31)
On the other rig I have one vega (+some 580) and it works normal...constantly 7.3mh without hashreate drops.
On both rigs I use same odt settings and have same driver version (Adrenaline 19.6.2)
What can be the potential issue?
Temperature or power throttling. |
|
|
|
I get error when starting TRM on cnr algo
- Failed to initialize device idx 5 (-31)
Well, I can't say you overdid it providing details about your setup  . The error is a buffer allocation error, so I'm guessing you're running win10 and have too little swap available to support >= 6 cards? If so, is it possible to increase it to at least >= 48GB? Another wild guess is that your 6th is a smaller gpu, but you have specified a cn_config that tries to allocate more scratchpads than the gpu can support. 48GB did the job, but i am getting around 800 h/s on each rx 570 x 6 (1250/2100mhz) You know, Ethash timings are not the same as CN timings. |
|
|
|
hi all,
i have a small farm of 144 x rx580 8gb cards
currently mining ETH with 4.55ghs
will this miner be more profitable ?
if yes, then by how much, and at which coin?
can anyone show the best earnings for rx580 8gb cards ?
thanks.
Uh.... You have to calculate it by yourself for each coin. But this miner does not support Ethash. Profitability right now between ETH and XMR is about the same with this miner for XMR. Depends on your electricity price and your memory timing mods. With 12x 580s per rig, you should be pulling ~1400W per rig, while doing 1kh/s+ per card. |
|
|
|
Ha мнoгo кapтoчныx cиcтeмax нe пoнятнo кaк paбoтaeт нa фepмe из 6 кapт дa вce xopoшo, нo кoгдa иx 12 (я пpo xeш нa пyлe) билибepдa пoлнaя, дoпycтим Vega 64 Luqid 12 штyк xeш 29+ aлгo кpиптoнит P, нa пyлe и нa MPP peгитcя 19+ и пpыгaeт пpиxoдитcя oткaтывaтьcя нa 4.2 вepcию, бeдa пpocтo, c кaкoгo-тo xepa peшил вce пoмeнять нa 5.7 в peзyльтaтe c 128 кн/c cкaтилcя дo 110- нy кyдa этo гoдитcя?.......
Hi! Sorry to say no one in our team speaks Russian. The google translate was pretty much crap as well. Could anyone in the community translate maybe? I'm guessing you're seeing a performance regression and need to run 0.4.2 for some reason, and you're not particularly happy about it? From what i understand: "I do not understand how this should work on multu-GPU systems. On a 6 GPU system, everything is good, but on a 12 GPU one (prohash pool), the dashboard on the pool (MPP) reports 19kh/s+, while the miner reports 29kh/s+, with 12 Vega 64 LC on CN_R. There is difference in the hashrate between v4.2 and v5.7, showing 128kh/s and going down to 110kh/s, why is that?" Note, this is bad translation, i do not think this is russian, but rather than that ukrainian. I couldnt understand half of the stuff. |
|
|
|
ouch! where did this come from?!
I've already have 6 rigs using this miner.....!
and since I mine to a proxy, I need fail over pool
Will monitor the hashrate and compare hashrate with the fees and manage my profitability.
also to let you know that it does work on other AMD GPUs. I have tried WX 4100/7100 and fire pro, think cause they have polaris too.
Hi, sent you a PM. Nice with the other GPUs, there are a few that we haven't tested on ourselves. It's all about what device string the driver is presenting the GPU with, if we recognize it we present our kernels for that architecture, if we don't recognize it we crap out. Hey Kerney, no need to even respond to such comments, like "Hurr durr, dev fee too high". You did a great job with the CN kernels, and you keep on delivering the goodies for other algos. Keep up the good work! |
|
|
|
That is rather odd and should definitely not be happening. Can you tell us a bit more about your setup?
Which OS version are you using? What version drivers are you running? Which version of the miner are you running?
Do the stats still display when you press 's' ? How do you know if it's just one GPU that crashes? 8 x Vega56 MSI Air (original bios, no software timing mods) Win10 LTSB, 18.6.1 drivers, latest 0.5.7 miner 's' shows only one string as in attached image. one gpu is just a guess. first it began rebooting with "GPU 6: detected DEAD" in log for the last two days. than began hanging like screened. if I reboot in manually, it works for serveral minutes, after that same behaviour again. rig power drops to ~370W. I realize that code is multi-thread, but it seems like it waits for something before giving them next jobs. txt log shows the same thing, nothing special. upd now I've disabled gpu6 using "-d" key - same result some time later  upd2 now another rig shows almost same picture. it has 8 Vega64 liquid. same OS, drivers and miner, same pool. maybe there's something connected to difficulty growth?  I was getting the same issue with my Polaris cards. Its because one of them was crashing, due to ASIC temp reaching too high temp. |
|
|
|
Could someone repost his/her settings for RX570 4GB please?
I've updated from windows 10 1803 to 1903 and my settings are messed-up. I've lost 30-35% hashrate because of the update. I didn't change anything else.
I'm using TRM 0.5.3
Reinstall drivers and re-enable Compute mode. |
|
|
|
|
Show Posts
