alucard20724
|
|
June 08, 2019, 07:27:23 AM |
|
Team Red Miner v0.5.1 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.5.1 - Added better support for CN intensities 16*15, use --allow_large_alloc under Linux.
- Added --no_ntime_roll for mining x16rt on e.g. bsod.pw.
- Added Tonga device recognition.
- Better error reporting for pool communication issues.
This release addresses a few minor issues people have reported in the v0.5.0 release. and just when i was about to post results with my vega VII for cnr for v0.5.0 release 3.33k for cnr with 13*13:AAA per vega VII under win10x64 with 19.5.2 drivers with both air cooled and water cooled cards.
|
|
|
|
|
|
|
You can see the statistics of your reports to moderators on the "Report to moderator" pages.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
ggarbi
Jr. Member
Offline
Activity: 43
Merit: 1
|
|
June 08, 2019, 02:56:47 PM |
|
Hey all. I have problem with my 7x xfx vega 64 rig. Im using 1050 mem 1175 core clocks and registery edited my rig and using 19.4.1 driver. When i mine one of my gpus going down (lights off but still working but not mining) im using 14*14:aaa It is happening after a day or two after i run Team red miner (using 0.5.0)
|
|
|
|
Vampire_sumy
Member
Offline
Activity: 110
Merit: 10
|
|
June 10, 2019, 07:57:03 AM |
|
I am sorry, but i have to ask you again - do you plan to add cn_gpu algo to the trm (ryo coin) ?
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
June 10, 2019, 09:06:18 AM |
|
Hey all. I have problem with my 7x xfx vega 64 rig. Im using 1050 mem 1175 core clocks and registery edited my rig and using 19.4.1 driver. When i mine one of my gpus going down (lights off but still working but not mining) im using 14*14:aaa It is happening after a day or two after i run Team red miner (using 0.5.0)
Hi! Is it always the same gpu? Have you tried reducing clocks/increasing voltage just a little for that gpu?
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
June 10, 2019, 09:11:17 AM |
|
I am sorry, but i have to ask you again - do you plan to add cn_gpu algo to the trm (ryo coin) ?
Hi! Sorry, forgot to reply the last time! Right now we’ll look at other algos rather than more CN variants. We might return to variants like conceal and cn_gpu after that.
|
|
|
|
Iamtutut
|
|
June 10, 2019, 10:25:23 AM |
|
I am sorry, but i have to ask you again - do you plan to add cn_gpu algo to the trm (ryo coin) ?
Hi! Sorry, forgot to reply the last time! Right now we’ll look at other algos rather than more CN variants. We might return to variants like conceal and cn_gpu after that. I see argon2id getting more and more interest, I think you really should consider it. There's even a bounty to develop a argon2id GPU miner (TRTL community).
|
|
|
|
Rakly3
Newbie
Offline
Activity: 45
Merit: 0
|
|
June 10, 2019, 01:24:07 PM |
|
How, if possible, can I run autotune with only X*Y ? (thus no X-Y, X+Y)
thanks! ilovetrm
|
|
|
|
Beruang123
Newbie
Offline
Activity: 10
Merit: 0
|
|
June 10, 2019, 01:36:39 PM |
|
Hey all. I have problem with my 7x xfx vega 64 rig. Im using 1050 mem 1175 core clocks and registery edited my rig and using 19.4.1 driver. When i mine one of my gpus going down (lights off but still working but not mining) im using 14*14:aaa It is happening after a day or two after i run Team red miner (using 0.5.0)
Hi! Is it always the same gpu? Have you tried reducing clocks/increasing voltage just a little for that gpu? I have the same issue with 2 of my rigs, and always happen with GPU 4. Tried lower the clocks and increase the voltage but same error occured. Cannot mine for 24 hours without error
|
|
|
|
ggarbi
Jr. Member
Offline
Activity: 43
Merit: 1
|
|
June 10, 2019, 03:38:56 PM |
|
Hey all. I have problem with my 7x xfx vega 64 rig. Im using 1050 mem 1175 core clocks and registery edited my rig and using 19.4.1 driver. When i mine one of my gpus going down (lights off but still working but not mining) im using 14*14:aaa It is happening after a day or two after i run Team red miner (using 0.5.0)
Hi! Is it always the same gpu? Have you tried reducing clocks/increasing voltage just a little for that gpu? I have the same issue with 2 of my rigs, and always happen with GPU 4. Tried lower the clocks and increase the voltage but same error occured. Cannot mine for 24 hours without error Yeah its happening to me too. Always one gpu making all rig crashed (rest of gpus working with all lights up but one of them working lights off and ofc,not mining)
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
June 10, 2019, 04:53:13 PM |
|
Hey all. I have problem with my 7x xfx vega 64 rig. Im using 1050 mem 1175 core clocks and registery edited my rig and using 19.4.1 driver. When i mine one of my gpus going down (lights off but still working but not mining) im using 14*14:aaa It is happening after a day or two after i run Team red miner (using 0.5.0)
Hi! Is it always the same gpu? Have you tried reducing clocks/increasing voltage just a little for that gpu? I have the same issue with 2 of my rigs, and always happen with GPU 4. Tried lower the clocks and increase the voltage but same error occured. Cannot mine for 24 hours without error Yeah its happening to me too. Always one gpu making all rig crashed (rest of gpus working with all lights up but one of them working lights off and ofc,not mining) Hmm. A little weird this one. Is this for CN/r or some other algo? Or any algo? Does running an older version solve the problem, ie you can run stable for a long time? We have one small bugfix on the way out, can’t really see that it would be the issue here though, but who knows.
|
|
|
|
Duck Hellen
Newbie
Offline
Activity: 1
Merit: 0
|
|
June 10, 2019, 05:38:08 PM Last edit: June 10, 2019, 05:59:33 PM by Duck Hellen |
|
I managed to solve today "one card crashing issue" on windows 10 Looks like compute mode switch is broken either : by tool that can enable/disable compute mode , and by swiching it manually in amd "control center" give me same result. So too gets cards too work i need to be in "graphic mode"... But in registry editor : Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318} You can see your cards 0001 0002 etc... and there is "blokchain support setting" or something like that " with "0 value" I think that it is new name of "compute mode" after swichng it to "1 value" everefing still works fine im on 19.6.1 driver
|
|
|
|
Rakly3
Newbie
Offline
Activity: 45
Merit: 0
|
|
June 10, 2019, 05:48:23 PM |
|
I managed to solve today "one card crashing issue" on windows 10 Looks like compute mode switch is broken either by script and by swiching it manually in amd "control center" give me same result. So too gets cards too work i need to be in "graphic mode"... But in registry editor : Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318} You can see your cards 0001 0002 etc... and there is "blokchain support setting" or something like that " with "0 value" I think that it is new name of "compute mode" after swichng it to "1 value" everefing still works fine im on 19.6.1 driver I just uninstalled all the AMD software and kept the drivers + a tool that can enable/disable compute mode. Card behaves now. IMO it's wattman causing much of system instabilities. Even if you never 'turned it on', it is still being used. The "blockchain support" is just the new feature AMD put in to switch memory timings 0 = auto 1 = level 1 2 = level 2 What the timings are, pfft I dunno. I don't see anything different using my tools. But it does affect hashrate a little.
|
|
|
|
SamAlackass
Newbie
Offline
Activity: 27
Merit: 1
|
|
June 10, 2019, 08:07:36 PM |
|
What tool are you using to set compute mode?
|
|
|
|
Beruang123
Newbie
Offline
Activity: 10
Merit: 0
|
|
June 11, 2019, 01:22:09 AM |
|
Hey all. I have problem with my 7x xfx vega 64 rig. Im using 1050 mem 1175 core clocks and registery edited my rig and using 19.4.1 driver. When i mine one of my gpus going down (lights off but still working but not mining) im using 14*14:aaa It is happening after a day or two after i run Team red miner (using 0.5.0)
Hi! Is it always the same gpu? Have you tried reducing clocks/increasing voltage just a little for that gpu? I have the same issue with 2 of my rigs, and always happen with GPU 4. Tried lower the clocks and increase the voltage but same error occured. Cannot mine for 24 hours without error Yeah its happening to me too. Always one gpu making all rig crashed (rest of gpus working with all lights up but one of them working lights off and ofc,not mining) Hmm. A little weird this one. Is this for CN/r or some other algo? Or any algo? Does running an older version solve the problem, ie you can run stable for a long time? We have one small bugfix on the way out, can’t really see that it would be the issue here though, but who knows. I am mining cn_saber, tried both 5.0 version and 5.1 version, all have the same result.... error with GPU no 4
|
|
|
|
|
Ngenah Euy
Jr. Member
Offline
Activity: 207
Merit: 5
|
|
June 11, 2019, 06:17:42 AM |
|
how to select certain GPUs in rigs? thanks
|
|
|
|
grimskal
Newbie
Offline
Activity: 6
Merit: 0
|
|
June 11, 2019, 09:02:41 AM |
|
how to select certain GPUs in rigs? thanks
teamredminer.exe --help -d, --devices=DEVLIST Sets gpu devices to use from detected list. DEVLIST should be a comma- separated list of device indices, e.g. -d 0,1,2,4. If not specified, all devices on the platform(s) will be used. NOTE: if using --bus_reorder, the indices used are after reordering. Use --list_devices to show indices.
|
|
|
|
SamAlackass
Newbie
Offline
Activity: 27
Merit: 1
|
|
June 11, 2019, 11:24:23 AM |
|
Thank you for the link! I can't believe it never came up before.
|
|
|
|
migo77
Newbie
Offline
Activity: 23
Merit: 1
|
|
June 11, 2019, 01:52:14 PM |
|
2 kerney666
Hi, my rig can't run longer then 1-2 hours on v 0.4.5 and newer. One GPU hangs (this is from 0.5.1 after autoconfig):
[2019-06-10 21:22:55] GPU 0 [57C, fan 87%] cnr: 2.486kh/s, avg 2.477kh/s, pool 2.709kh/s a:46 r:0 hw:0 [2019-06-10 21:22:55] GPU 1 [58C, fan 85%] cnr: 2.490kh/s, avg 2.482kh/s, pool 1.261kh/s a:22 r:0 hw:0 [2019-06-10 21:22:55] GPU 2 [56C, fan 86%] cnr: 2.486kh/s, avg 2.478kh/s, pool 2.969kh/s a:51 r:0 hw:1 [2019-06-10 21:22:55] GPU 3 [63C, fan 87%] cnr: 2.480kh/s, avg 2.468kh/s, pool 2.377kh/s a:42 r:0 hw:0 [2019-06-10 21:22:55] GPU 4 [45C, fan 90%] cnr: 2.483kh/s, avg 2.471kh/s, pool 2.737kh/s a:47 r:0 hw:3 [2019-06-10 21:22:55] Total cnr: 12.42kh/s, avg 12.38kh/s, pool 12.05kh/s a:208 r:0 hw:4 [2019-06-10 21:23:05] GPU 4: detected DEAD (11:00.0), will execute restart script watchdog.sh
but v0.4.4 with exactly same config can run for weeks:
[2019-06-10 19:40:27] Stats Uptime: 13 days, 12:58:15 [2019-06-10 19:40:27] GPU 0 [59C, fan 87%] cnr: 2.471kh/s, avg 2.470kh/s, pool 2.340kh/s a:7780 r:0 hw:17 [2019-06-10 19:40:27] GPU 1 [60C, fan 85%] cnr: 2.474kh/s, avg 2.473kh/s, pool 2.423kh/s a:8057 r:0 hw:39 [2019-06-10 19:40:27] GPU 2 [57C, fan 86%] cnr: 2.471kh/s, avg 2.471kh/s, pool 2.337kh/s a:7768 r:0 hw:106 [2019-06-10 19:40:27] GPU 3 [63C, fan 87%] cnr: 2.464kh/s, avg 2.464kh/s, pool 2.381kh/s a:7917 r:0 hw:73 [2019-06-10 19:40:27] GPU 4 [55C, fan 88%] cnr: 2.470kh/s, avg 2.468kh/s, pool 2.259kh/s a:7519 r:0 hw:321 [2019-06-10 19:40:27] Total cnr: 12.35kh/s, avg 12.35kh/s, pool 11.74kh/s a:39041 r:0 hw:556 [2019-06-10 19:40:39] Pool pool.supportxmr.com received new job. (job_id: +kOSIEF95a5dlkxX6slHR0EW+l34)
I know, I'm pushing hard on limit, but what changed in TR miner 0.4.5 that causes this instability? With 0.4.4 and older was this rig rock stable. OS is Linux & amd18.3 drivers.
Thank you for answer,
Migo
|
|
|
|
Iamtutut
|
|
June 11, 2019, 02:14:03 PM |
|
Very impressive upgrade, a few extra hundred hashes with Turtlecoin and very good implementation of CN Heavy algos.
Excellent work, kudos to the devs.
The tuning mode is amazing, now on a few algos I have the same hashrate than when I had bios mods on my GPUs. To achieve such speeds, I use the AMD memory timings tool.
|
|
|
|
|