|
0.8.0 - WOW
good job-
more HR - lower power consumption-
test on vega56 nitro and vega 56 ref and vega 64LE.
thx
|
|
|
|
Hey guys,
There are some days that I´m trying to reach a stable config for my RX Vega 56 MSI Air Boost, Hynix memory (blower), the most stable results is in Simplemining OS, but the results are pretty much the same in the MMP OS (lately I faced some drivers errors in the second one, [amdgpu yada-yada-yada]).
46.65 MH/s, 322 accepted shares and 8 hw errors until now. Team Red Miner. 47MH/s at pool.
If I go mV down, even only 10mV, it gets a lot hw errors. If I go only 5 MHz mem up, it gets a lot of errors. The same thing for --rcdwr, for 17 and down that, a lot of errors too.
Core 1050@900mV, mem 900. 137 W in software, 180W at the wall. 90% fan and mem working about 74ºC.
amdmemorytweak --i 1 --cl 18 --ras 23 --rcdrd 18 --rcdwr 11 --rc 34 --rp 13 --rrds 3 --rrdl 4 --rtp 6 --faw 12 --cwl 7 --wtrs 4 --wtrl 4 --wr 11 --rfc 164 --REF 17000
Anyone that faced some similar problems or similar hardware that could help me with this? Thanks a lot!
Hi, having similar issues, having 3x Sapphire Nitro+ (Hynix) in a rig where I've successfully ran 9xRX570 before without any issues. I was able to successfully OC memories to 960MHz, 930MHz and 950Mhz but I haven't used any mem strapping, just increased REF to 65535 and I got around 44MH/s. When I tried to mimic your settings on my cards, 2 of them got only 41MH/s and third one (after cca 30s) crashed. I'm not an expert on tuning memory straps but have tried all different will-work-for-sure-on-your-Vega56-Hynix settings and none of them worked for me. try this WinAMDTweak.exe --RAS 26 --rp 14 --rc 35 --rfc 170 --rrds 4 --rrdl 5 --rcdrd 19 --rcdwr 7 --REF 15600 i have vega56 nitro+ hynix and this is middle setings. 45-46MH. 6*vega56 use 1100W on the wall.  if you wona beter HR just use 1100 -1200 GPU clock and give more power etc 900mv |
|
|
|
[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. not NH. NH have 2-3% reject with identical error. i dont konow what pool is this. this is rentals rig and user use pool but i not see wich pool. but i see this error code 23 and on ethermine and nanopool. 0,5-1% |
|
|
|
|
[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
|
|
|
|
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. thx ... |
|
|
|
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 |
|
|
|
thx advance for explanation for efficency, any idea how much vega hashrate for chikwa2?
vega 56 etc 36-39kh |
|
|
|
i have issue rig stil mining but ethermine status 0 mhs reported sometimes in 2-3days mining, randomly happen
share continue nothing change but reported hashrate gone and avegare & current status slowly downturn, seems weird, no error happening on console/miner
right now i tried different dns, something weird happen lately
this happen atleast when defi craze start, at first september, i.m using 0.6.1 btw, skipped 0.7.9 cause using 2% more power consumption
any idea new version trm will come out?
TRM 0.7.15
https://github.com/todxx/teamredminer/tree/5a7ce1ec7fbfda947de3d267979b536ffc6fd99bwhy not see this version on first page on this topic? i see 0.7.9 last version. My apologies. I've been slacking a bit on updating the main page. It is now up to date.  thx |
|
|
|
i have issue rig stil mining but ethermine status 0 mhs reported sometimes in 2-3days mining, randomly happen
share continue nothing change but reported hashrate gone and avegare & current status slowly downturn, seems weird, no error happening on console/miner
right now i tried different dns, something weird happen lately
this happen atleast when defi craze start, at first september, i.m using 0.6.1 btw, skipped 0.7.9 cause using 2% more power consumption
any idea new version trm will come out?
TRM 0.7.15
https://github.com/todxx/teamredminer/tree/5a7ce1ec7fbfda947de3d267979b536ffc6fd99bwhy not see this version on first page on this topic? i see 0.7.9 last version. |
|
|
|
Hi Guys,
I was browsing posts in topic and I am interested into how ppl get these 900w with 6 vegas?
My setup is 5x vegas64 (samsung) flashed to 56
I got 273MH/s with 985 watts from the wall using wattmeter this is around 54.5mh/s from the card. So where is the trick?
Cheers
real? and you wont better? this is verx nice HR for this power. Send 1 SS for this Hr and pls send your setings. Owerdrive and Tweak. thx |
|
|
|
I use teamredminer 0.7.9 for mining using 3 vega 56 gpus. I get this command always.. Please someone help...
And one GPU mostly gets off even for different miners.. Please someone help. Thanks in advance
GPU 1: detected DEAD ..... No restart script configured, will continue mining.
Please use command line argument --watchdog_script to handle dead GPUs.
i see this message on 1 GPU(vega56 hynix) on rig. to low MV on memory. try 900mv and see. after work godown to 890mv and go down to 880 .... my other GPU use 850-860mv and work but 1 GPU work only with 890mv without this message. if use watchdog_script rig go restart miner and work again. use this command and create restart.bat teamredminer.exe -a ethash -o stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -u WALETADRES -p PASS -d 0,1,2,3,4,5 --eth_config A896 --bus_reorder --watchdog_script=restart.batin restart. bat write this: echo. timeout 6 taskkill /F /IM "teamredminer.exe" timeout 3 start "start.bat" " start.bat" echo. timeout 5 exit |
|
|
|
That's what I did, it's not working
teamredminer.exe -a ethash -o stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -u 3***********************P -p x -d 0,
Whether I set -d 0, or any other number, the miner crash starts.
dont use -d 0 and miner start with all card or if you use command is -d 0 without , if use 2 card command is -d 0,1 or -d 3,5 etc miner with 6 card teamredminer.exe -a ethash -o stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -u WALETADRES -p PASS -d 0,1,2,3,4,5 --eth_config A896 --bus_reorder --watchdog_script=restart-eth.bat |
|
|
|
|
TRM suport new tube?
Algo: cuckaroo29b (c29b)
BitTubeCash pool started, network will start around 29th of July when BitTube reach block 654000
As there are no guarantee exchanges will support deposits in Tube3 chain after the fork. New bittubecash pool will be opened instead, new algo will be Cuckaroo29b, Tube4 will be new chain with new wallet addresses.
|
|
|
|
haven, win7, rx460, rx550
0.5.9 updated to 0.7.7
different rigs freeze at the start, video driver crashes, statistics are displayed in parts.
on the old version everything worked fine
Hmm. I’m guessing now, but one big thing that has changed is various upgrades to the ADL library handling to read clocks/temps on win. Win7 isn’t officially supported, we do zero testing there. However, try disabling it as a test with —no_gpu_monitor. after a few days, I did not notice any hang-ups at startup and drivers crashing. although on the first day three rigs were fully launched after 3-4 attempts But statistics output works strange. printed on the screen for a long time, in parts (line by line) a rig with RX550 is displayed correctly, at once but on rigs with RX460 (RX560) it is incorrect. all information can be displayed in 2-3 minutes it often happens that the speed of some video cards is indicated unrealistic - 5000kh/s, 1600kh/s etchttp://www.screencapture.ru/file/955b4F99tried it —no_gpu_monitor no changes your TWEAK is so high and card blocked... vega56 have etc 2k HR but i see 4khr and after 20sec rig i reset. to high tweak. |
|
|
|
haven, win7, rx460, rx550
0.5.9 updated to 0.7.7
different rigs freeze at the start, video driver crashes, statistics are displayed in parts.
on the old version everything worked fine
Hmm. I’m guessing now, but one big thing that has changed is various upgrades to the ADL library handling to read clocks/temps on win. Win7 isn’t officially supported, we do zero testing there. However, try disabling it as a test with —no_gpu_monitor. win10 oprekinliteplus + driver 20.4.2 - vega 56(hynix and samsung) vega 64LE 2 rig 10 card all work fine with haven |
|
|
|
Team Red Miner v0.7.7 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.7.7 - Added support for Nimiq (dumb mode only).
- Integrated a Nimiq node.js network proxy into the miner.
- Fixed Nimiq bug that could lose shares, especially against lower vardiff pools.
- Fixed Nimiq bug that could cause duplicate shares on startup for low-diff pools.
- Fixed regression bug for ethash Nicehash, correct stratum mode now used again.
We now support Nimiq! any news about haven fork support? It has been released on github. Todxx will post here shortly. THX |
|
|
|
Haven Offshore fork will happen at block 640640 (20th of July around 15:00 UTC)
TRM suport this?
Need a new release, will work on it tonight. NICe thx |
|
|
|
|
Haven Offshore fork will happen at block 640640 (20th of July around 15:00 UTC)
TRM suport this?
|
|
|
|
Please Vega 56 users, could you tell me your HR with CN heavy / Haven / Tube algo(s) ?
Thx in advance.
Yeah I try to run conservatively as in not going for max hash but best power efficiency: TUBE = 1.35 kH/s pool side for 160w at the wall tube-haven-heavy give 2000+HR on any vega (56 or 64) and use etc 150W per cards etc: 1 rig 6*vega56hynix = 960W at the wall = 12200kh etc 1 rig 4*vega56 samsung = 720W at the wall 8700kh etc Nice which clocks do you use? mem core volts? mem 900-920mhz 862mv (hynix) mem 1098-1100mhz 862mv (samsung) gpu 1440mhz 807mv u must use AMD tweek for this HR. read this topis for vega tweak https://bitcointalk.org/index.php?topic=5123724.1080etc amd tweek : for tube with vega56 @vega 64 bios (samsung)- WinAMDTweak.exe --i 0,1,2,3 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 246 --FAW 14 |
|
|
|
|
Show Posts
