This is caused by time shifts (notice the time went backwards at "13:44:22 WARN: WATCHDOG: T-Rex has a problem with GPU, terminating..."). We already have a fix for it, will be available in the next version.
Ok, thanks, there is another problem on one of my rigs: 18:01:32 ethash epoch: 414, block: 12420254, diff: 4.29 G
18:01:39 [ OK ] 7/7 - 191.21 MH/s, 38ms ... GPU #2
18:01:42 [ OK ] 8/8 - 191.21 MH/s, 38ms ... GPU #5
18:01:43 ethash epoch: 414, block: 12420255, diff: 4.29 G
18:02:00 WARN: GPU #3: EVGA GeForce GTX 1080 Ti is idle, last activity was 34 secs ago
18:02:03 ethash epoch: 414, block: 12420256, diff: 4.29 G
18:02:05 WARN: GPU #3: EVGA GeForce GTX 1080 Ti is idle, last activity was 39 secs ago
18:02:10 WARN: GPU #3: EVGA GeForce GTX 1080 Ti is idle, last activity was 44 secs ago
18:02:15 WARN: GPU #3: EVGA GeForce GTX 1080 Ti is idle, last activity was 49 secs ago
18:02:20 WARN: GPU #3: EVGA GeForce GTX 1080 Ti is idle, last activity was 54 secs ago
18:02:25 WARN: GPU #3: EVGA GeForce GTX 1080 Ti is idle, last activity was 1 min ago
18:02:26 WARN: WATCHDOG: T-Rex has a problem with GPU, terminating...
18:02:26 WARN: WATCHDOG: recovering T-Rex
18:02:30 T-Rex NVIDIA GPU miner v0.20.3 - [Windows]
18:02:30 r.555472ba6b21 This card keeps idling after start\restart(if something crashes), then when miner restarts because of idling it's not happening again until restart for any other reason(like crash of any card). I've tried replacing raiser, didn't help. Thing is it's only happening when mining eth on T-rex, if I use other miners - no such problem. Also if I mine FIRO with T-rex there is no such problem. ps it never happened on 0.19.xx versions(or prior) btw. |
|
|
|
13:43:55 [ OK ] 1287/1289 - 280.32 MH/s, 47ms ... GPU #2
13:44:00 ethash epoch: 413, block: 12419148, diff: 4.29 G
13:44:03 ethash epoch: 413, block: 12419149, diff: 4.29 G
13:44:08 ethash epoch: 413, block: 12419150, diff: 4.29 G
13:44:12 ethash epoch: 413, block: 12419151, diff: 4.29 G
13:44:30 ethash epoch: 413, block: 12419152, diff: 4.29 G
13:44:22 WARN: WATCHDOG: T-Rex has a problem with GPU, terminating...
13:44:23 WARN: WATCHDOG: recovering T-Rex
13:44:26 T-Rex NVIDIA GPU miner v0.20.3 - [Windows]
T-rex keeps restarting/crashing from time to time without telling what card is causing this, why?  |
|
|
|
When are gonna fix(hide) fan adjustment reports? Logs are insanely big and impossible to navigate. (T-Rex 0.20.3)  |
|
|
|
No.. the cards and the Miner report 304.
But the real average 24h shown in the pool is just 295.
And that‘s the case for weeks now.
So wehre are the missing 9 mhs?
Fees?
On ETH I never got h\r on the pool side close to what miner says cards are giving me(excluding 2% of fees) with t-rex. It is usually -5% or more. |
|
|
|
|
T-rex does not report actual h\r based on shares you submitted, only what cards report. And it doesn't include fees obviously. It reports shares per minute only. If 295 is what t-rex says you have, than its you supposed hashrate. If 295 is what your pool says then it's what you actually have(all fees included).
|
|
|
|
20:11:00 WARN: GPU #4: EVGA GeForce GTX 1080 Ti is idle, last activity was 34 secs ago
20:11:02 ethash epoch: 411, block: 12330196, diff: 4.00 G
20:11:05 WARN: GPU #4: EVGA GeForce GTX 1080 Ti is idle, last activity was 39 secs ago Happened first time today - whats this? Card just stop working and miner won't restart it. Had to closer miner and relaunch.... |
|
|
|
Thanks. That was a test version, the official release won't be spamming like that.
Yeah? Cos 0.20.3 does spam fan adjustments exactly like that test version)) Note: fan speeds are limited to [5%; 95%] range in auto-fan mode. Most of pascals' fans can't spin properly at 5%, you should lower minimum limit to 0 so they won't go crazy spinning/stopping when below target temp.... ps there is also hashrate fluctuations when mining FIRO(dunno, mb when mining any other algo as well - I'm just mining FIRO now). There hasn't been any and so often as now in 0.20.3   pps also shares-per-card now shown only for current session, if miner restarts only total shares at top would remain, per card will start from 0 again. It wasn't like that in previous versions and I think its preferable cos you can compare how card performs with other cards. Ofc there is a "summary" but its not that handy as when you can just see this data on the main page. |
|
|
|
Hi, it does work now, but miner reports every fan adjustment which is super annoying...  |
|
|
|
(Windows) Add experimental support of "auto-fan" feature: miner adjusts GPU fan speed to maintain a predefined GPU core temperature, see --fan for details Target temp doesn't work on pascals, why no mention of incompatibility? |
|
|
|
|
Is it possible to reset(restart) a single GPU while still mining to regenerate dag, like you can do in Phoenix miner? If not please implement!
|
|
|
|
|
Hm, i set mt 1 to test mining MTP, but if any mt parameter is set I can't change intensity through web interface, it remains same as in config forever.
ps This disappointing bug aside this update is quite good cos unlike ethpill --mt 1(only tried 1 so far) affects 1070 as well. Still even 1080Ti got better hashrate with mt 1 than with pill and mt-0. Lets hope OC will remain stable!
|
|
|
|
|
Why -eres command doesn't do anything (1070\1080ti rigs)?
|
|
|
|
As long as there are no competitive miners fees like this will exist  |
|
|
|
That Fury X. not Fury NANO. Fury X hug power consume.
What do u mean? In the article there is ASUS Fury(neither X nor Nano). Though Nano should be have same exact performance as Fury X unless u make it throttle, which is impossible with most of algos if u tune it. Since properly tuned Fury x shouldn't be exceeding 180Wt Nano shouldn't have any throttling as well. |
|
|
|
Just seeing first result in benchmark list makes me cry: 29.8mhs@170Watts on ETH)))) I had that hash rate @140-145Wt(975Mhz core) with my cards. Or it could be 30.8mhs @1000Mhz@155Wt. And unlike pascal it newer dropped with DAG grow) In most of Fury mining videos they even have 250+Wt... some miners. My h\rs in some other algos were: lyra2v3 58mhs@150-155Wt, cryptonightR 880hs@120Wt |
|
|
|
|
No miner developing team makes optimizations for Fiji. They used to be on pair with gtx1070 in h\r(though with 20% more power consumtions) 2 years ago, but since then they have fallen behind significantly in newer algos, some times they even can't mine some at all(and not cos of 4gb, "AMD" simply don't support them). So, I've sold my last R9 Fury this summer realizing developers won't bother to make optimizations for them ever again.
|
|
|
|
|
Why -eres doesn't work with GTX1080ti? Miner refuses to allocate more memory than current DAG size. No such thing with GTX1070...
|
|
|
|
|
corsar71 Если лог включен, то клей пишет в свою же папку.
|
|
|
|
Хм, из-под NHML nbminer создает api через 127.0.0.1+порт, поменять через доп параметры на 0.0.0.0 нельзя - он не видит хешрейт. Как сделать что бы по ip локалки открывался мониторинг? ps кстати, на Gminer1.74 следующая проблема: после имени рига NHML еще что-то дописывает: +----------------------------------------------------------------+
| GMiner v1.74 |
+----------------------------------------------------------------+
Algorithm: Cuckatoo31
Stratum server #1:
host: grincuckatoo31.eu.nicehash.com:3372
user: 3oOpqd2em7NrwkCLrbmRh1qqwdXh48J.Rig1$0-ddxCfqy1rVu+67l8JgD6wA
password: x |
|
|
|
|
Does -eres work for nvidia cards? Cos no matter what value I enter I always see same dag-size generated...
|
|
|
|
|
Show Posts
