|
Have any of you guys played around with editing HBM2 memory timings on linux?
If anyone has a reference V64/V56/FE card with Samsung Mem on linux and is feeling adventurous, could you guys try the following timings?
--rp 10 --rc 45 --rfc 290
Please keep in mind that editing timings can result in damage to your cards.
These timings work for me on my Vega FE, but there's no guarantee they will work for other cards.
In particular, I'm curious what your cn trtl results are. Timings currently have a very limited impact on our other kernels.
|
|
|
|
Team Red Miner v0.4.3 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.4.3 - Added cryptonight v8 turtle (--algo cnv8_trtl) algo for coins such as turtle coin and loki.
- Added support for running CN mining single-threaded using Y+0 configurations.
- Changed the auto config mode for Radeon VII to L30+0 as a temporary setting.
We've added support for the CN Turtle algo! Those of you who try it will notice a significant speed up compared to other currently available miners  We've also added some improved auto-config support for VIIs, more tuning is still to come.
|
|
|
|
Sup? I have a fair amount of R9 cards (Fury) and have a question and a statement.
Question: Has anyone gotten TeamRedMiner to work on R9 cards? (AMD) and specifically R9 Fury?
Statement: If not, I am willing to sponsor development for an implementation/development (Feel free to give me a ballpark idea of $$/BTCBTC)
Feel free to PM me. This is an alt-account since I don't feel super comfortable with my main account here since the many database hacks and doxxing etc. I can verify ownership of my mining farm etc. and if needed pay for part of development up-front if developer is a community known or whatever is needed. If it matters I intend to run the miner under EthOS mainly for Monero (new cryptonite algo). If you are in the U.S and need it I can supply development hardware rig with relevant hardware to serious developer (3x Sapphire Nitro Fury 4GB HBM, Micro-ATX, 8GB, SSD, Celeron in metal frame).
Hi neuromancer4867, Fiji and Tonga based cards should be somewhat supported already. We've had several people report decent hashrates on Fiji based cards, though we have not done any testing ourselves. Have you tried running the miner on a Fiji rig? If you have problems, we can help troubleshoot them if you can provide some info as to what's going wrong. |
|
|
|
Any plans to support Vega VII? I get this error message when trying to use Lyra2Rev3 algo:
[2019-03-23 14:54:35] Initialize error, unknown device name: 'gfx907'
[2019-03-23 14:54:35] Failed to initialize device idx 4 (-8)
Seems we might be missing the device name for VII when HBCC is enabled. We'll add it in the next release. For the time being, if you disable HBCC on your VII it should work. |
|
|
|
0.4.2 version has "dead gpu" problem again. One of my two vegas started crashing (underclocked gpu and memory). Latest 3.x version was working fine. Now testing 0.4.1.
Hi alexmpa, Which algorithm are you comparing between those two versions? |
|
|
|
Hi got an issue mining phil2 Gway Coin, it did work few months back ok for AGM, cards work ok with X22i & X16r with no reboot after trying teamredminer
nothing has been updated in months on Rig and works fine with other miners
command line below
teamredminer.exe -a phi2 -o stratum+tcp://uk.thepool.life:5124 -u Wallet address -p c=GWAY -d 3,4
miner working fine on my PC to same pool
Team Red Miner version 0.3.10
[2019-03-13 12:55:19] Auto-detected AMD OpenCL platform 0
[2019-03-13 12:55:22] Initializing GPU 0.
[2019-03-13 12:55:22] Watchdog thread starting.
[2019-03-13 12:55:22] Pool uk.thepool.life connecting to address 95.179.206.161.
[2019-03-13 12:55:22] Pool uk.thepool.life successfully connected to address 95.179.206.161.
[2019-03-13 12:55:22] Pool uk.thepool.life successfully subscribed. (8 ms)
[2019-03-13 12:55:23] Pool uk.thepool.life authorization succeeded.
[2019-03-13 12:55:23] Dev pool connected and ready.
[2019-03-13 12:55:23] Pool uk.thepool.life set difficulty to 1.000000
[2019-03-13 12:55:23] Pool uk.thepool.life received new job. (job_id: 1b0e)
[2019-03-13 12:55:23] Pool uk.thepool.life extranonce subscribe succeeded. (944 ms)
[2019-03-13 12:55:52] Stats Uptime: 0 days, 00:00:31
[2019-03-13 12:55:52] GPU 0 [45C, fan 59%] phi2: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:55:52] GPU 1 [48C, fan 25%] phi2: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:55:52] Total phi2: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:56:06] Pool uk.thepool.life received new job. (job_id: 1b0f)
[2019-03-13 12:56:22] Stats Uptime: 0 days, 00:01:01
[2019-03-13 12:57:02] GPU 0: detected DEAD (05:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:37] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:57:12] Pool uk.thepool.life received new job. (job_id: 1b10)
[2019-03-13 12:58:37] GPU 1: detected DEAD (08:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:37] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:58:37] Pool uk.thepool.life received new job. (job_id: 1b11)
[2019-03-13 12:58:37] GPU 0 [38C, fan 25%] phi2: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:37] GPU 1 [48C, fan 0%] phi2: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:37] Total phi2: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:47] GPU 0: detected DEAD (05:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:47] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:58:47] GPU 1: detected DEAD (08:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:47] Please use command line argument --watchdog_script to handle dead GPUs.
Thanks
fixed it saw earlier post about CPU mining which i stopped and working fine now
Hi redzep, It seems that the GPUs are crashing, probably due to the OC/UV profile you are running. Even though your current settings might be stable on other miners/algos, different miners and algos will behave differently and have different OC/UV limits. In this case, phi2 is a rather core heavy algo, and will probably require dropping your clocks a bit. A good sanity check is to see if it works at stock clocks/voltages, and then go from there. |
|
|
|
0.4.1 is working just fine...
Here is the clinfo
Based on your clinfo output, setting the option "--platform 0" should work. Can you double check that setting this option doesn't work? Also the clinfo output you pasted seems to be cut off at the end. Can you paste your full clinfo output, but maybe put it inside of a code block so not too spam the thread? (You can insert code blocks using the # button when editing posts.) It would also help to know which driver version you are running. |
|
|
|
MRR>xmr.nanopool.org error  I have no problems connecting to support xmr through MRR. Yes, there is no problem, just when such errors occur, the statistics are reset to 0 and the new one !!!!! And let's essentially !!! Please try adding the --pool_broken_rpc option to your command line arguments for the miner. This should fix the issue you are seeing with nanopool. If you are running in windows, you can do this by editing the .bat file that you use to start the miner. |
|
|
|
MRR>xmr.nanopool.org error And did you try using the option it suggested? |
|
|
|
Team Red Miner v0.4.2 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.4.2 - Added cryptonight v8 half (--algo cnv8_half) algo for coins such as stellite and masari.
- Added cryptonight v8 double (--algo cnv8_dbl) algo for coins such as x-cash.
- Added cryptonight v8 reverse waltz (--algo cnv8_rwz) algo for coins such as graft.
- Added support for running devices on multiple OpenCL platforms.
- Fixed more issues with console colors on older windows versions.
- Added more cpu verification optimization for CN/R. CN/R cpu usage should decrease ~70%.
In this release we've added some more CN variants! We've also fixed a couple bugs, and sped up our CN/R cpu verification code which should help rigs with low end celeron cpus.
|
|
|
|
Todxx, your Lyra2REv3 Dev-Pool is often not available these days, so mining is reduced. Can you please check that?
Confirm, nicehash cnr mining - many rejected shares - job not found.
And "Dev pool connection was closed by remote side. Mining will proceed at reduced rate etc etc"
Same problem with Dev pool connection.  What option for disable colors? Blue color is very unreadable... (only linux, windows colors - cyan is ok) The dev pool connection issue you guys are seeing today is likely because we are doing maintenance on the dev pool which often requires miners to reconnect. However, the miner should reconnect to the dev pool about 10-15 seconds after a disconnect, so the total effect for your hashrate should not be noticeable. As long as you see the message "Dev pool connected and ready." after the error for the dev pool connection being closed, it means the miner is good to go again. @Velmerk The option to disable colors is --disable_colors |
|
|
|
So I'm still running 0.4.0 (because it worked so far)... but I noticed it stopped displaying hashrate info completely after a while.
Is that something that's been fixed in 0.4.1 at all? Haven't seen it in the changelog...
EDIT: could it be related with the miner losing connection to devpool? I'm getting these every now and then:
"Dev pool connection was closed by remote side.
Mining will proceed at reduced rate etc etc"
...shortly followed by "Dev pool connected and ready"
...and hashrate clearly falls on the pool.
The hashrate display stopping completely indicates some kind of host-side hang. We haven't seen this issue recently, but we will look into it. I can't say that anything we changed in 0.4.1 should affect that. Please let us know if it happens to you again. As for the dev pool connection issue, we can't find any problems on our end. One guess is that because we switched to using port 80 in v0.4.0, some network filters are occasionally killing connections. In 0.4.1 we switched default port to 4000, if that fails it will try to use port 80 again. |
|
|
|
Team Red Miner v0.4.1 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.4.1 - Removed server name verification for SSL connections. (Pools like supportxmr now work with SSL)
- Fixed bug causing GPUs to fail to initialize on some systems.
- Fixed bug causing GPUs to only run one thread (but display 2x hashrate)
- Fixed bug where having GPU_MAX_WORKGROUP_SIZE set too high would cause GPUs to crash.
- Fixed bug where older windows versions would get no console output.
- Added work-around for driver bug in linux amdgpu-pro drivers resulting in low pool-side hash for polaris cards in rare cases.
- Added some cpu verification optimizations. CN/R cpu usage should decrease about 15%.
The changes in this version are mostly addressing issues people have been reporting with the v0.4.0 release. If v0.4.0 is working for you without issue, updating to v0.4.1 isn't urgent, but probably a good idea when you get the chance.
|
|
|
|
Team Red Miner v0.4.0 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.4.0 - Added cryptonight R support. (--algo cnr)
- Added support for ssl/tls pool connections using the stratum+ssl:// prefix.
- Added colors (and an option to disable them).
- Slight performance increase for lyra2rev3 (~0.5%).
- Fix for occasional crashes when pool disconnects.
- Added more messages regarding not being connected to dev pool.
- Changed printing to not block mining progress if stdout writes block.
A bit delayed with this post, but better late than never. The main change in this version is the addition of CN/R support. Performance of CN/R is roughly the same on Vegas as cnv8. Polaris cards are a bit slower with larger cards losing about 0.5% and the smaller cards like rx550s losing ~1.5%. Power for CN/R is up by 2-3% compared to cnv8. Also we've added some user requested features like colors and support for ssl pool connections.
|
|
|
|
Team Red Miner v0.3.10 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.3.10 - Slight performace improvement for Vegas on lyra2rev3
- Pool stratum protocol work-arounds for some pools, fixing duplicate share error.
- Changed handling of unrecognized pool rpcs to be ignored instead of causing a reconnect.
- Fix for duplicate shares on 480/580/Vega56 cards with lyra2rev3.
Most of the changes in this release are fixes for various issues people ran into with lyra2rev3. Issues seen with p2pool and bitpoolmining should now be resolved. There was also a small performance improvement for Vegas in this version Edit: For those of you running with p2pool (or coinotron), you may need to add the following option to your command line: --pool_no_ensub
|
|
|
|
Perfect,
my first test with same OC than Cryptonightv8, Rx 580 8Gb armor = 49.94Mh/s and 136W (!)
Any advice for OC setting on rx580 ?
Thank you
Nice! 50Mh/s is pretty good for a 580 Lyra2rev3 does not use much memory bandwidth, so you should try to push up core clock for more perf and lower mem clock to lower power usage. Unfortunately there's no single best OC setting as all the different types of cards behave differently. |
|
|
|
Can you give us an exemple of config file for lyra2v3 i cannot get it work.
Thank you
I assume you're running on windows, try something like the following with all of the <pool_*> fields replaced with your pool's info: teamredminer.exe -a lyra2rev3 -o stratum+tcp://<pool_address>:<pool_port> -u <pool_username> -p <pool_password> |
|
|
|
todxx , does this update include/works on Nicehash too ? Recently they added Lyra2Rev3 too .
I have not tested on NH directly, but it should work just fine unless they've done something special for lyra2rev3. |
|
|
|
Team Red Miner v0.3.9 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.3.9 - Added support for lyra2rev3 on amdgpu-pro and windows. ROCm support coming in later version.
- Fixed API bug with not reporting dead GPUs
Lyra2rev3 performance and power usage is looking good compared to other miners! Let us know what numbers you guys get!
|
|
|
|
New AMD gpu drivers are out and with so many new things I just gotta use them. So far mining speed on teamred seems to be a bit better and now one can undervolt well enough without registery powertables.. Not sure if the combination of new drivers + teamred or just teamred but whole system seems to be laggy while mining. It wasn't before  Probably need new CN-values. Release notes https://www.amd.com/en/support/kb/release-notes/rn-rad-win-18-12-2Download as usual. Sapphire Pulse Vega 56 & Cryptonight V8 algo. i can verify the lagginess with teamread and 18.12.2. drivers with my vega56/64. hashrate is higher without having to mess with powertables, but there's a substantial lag on the system now. Can you elaborate a bit more on your setup? Are you running the cards with risers? I just ran my Vega 64 LC on 18.12.2 and did not have any problems. i7-5930k, one vega56 pciex16 slot with monitor connected, two vega56 on risers, one vega64 on riser... all set to 14+14, win10x64 My system is similar except for the risers, so that's something to look into. If you have a chance, could you try to run the miner on each card individually to see if the lag issue is caused by a particular card or set of cards? |
|
|
|
|
Show Posts
