Topic: T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 20. (Read 175016 times)
Is there anyway to mine ravencoin on 3070ti and mine ETH with 1660s using Trex miner in hiveOS at the same time? I can't find a way around this and it's been days, I had to find another motherboard and separated the 3070ti from the 1660s to mine kawpow algorithm separately
Developers you did well really, nothing to add
But I strongly recommend reduce fee to 0.65% or close
Because have miner same Hashrate with T-rex and same wattage with T-rex
but they have less fee than T-rex so they have 1 more point less fee
maybe not notice for small miners but still 1 more point better
just my opinion ,
But I strongly recommend reduce fee to 0.65% or close
Because have miner same Hashrate with T-rex and same wattage with T-rex
but they have less fee than T-rex so they have 1 more point less fee
maybe not notice for small miners but still 1 more point better
just my opinion ,
Hi trex team, I would like to know if you are already working on trying to unlock LHR, at least partially, or is this not in the plans?
Can someone help me figure out the configuration to get T-Rex to run with the json file? like can someone provide their start up and just remove your wallet ect? I've been trying for awhile and not getting anywhere. I want to be able to make changes in the api and have it save to my config.
Does the --validate-shares command not work when mining ERGO? It doesn't show the difficulty of the submitted shares while on ERGO like it does on ETH.
It doesn't. We'll fix it in the next version. Does the --validate-shares command not work when mining ERGO? It doesn't show the difficulty of the submitted shares while on ERGO like it does on ETH.
no juste intensity work
Does the --validate-shares command not work when mining ERGO? It doesn't show the difficulty of the submitted shares while on ERGO like it does on ETH.
I wish it was possible to put an argument to decide what time the next card will start.
Example: --gpu-init-mode 60, it would be for GPU 1 to start 60 seconds after GPU 0 and so on.
It would help in my region not to pay an energy tariff when the miner is initiated by the high demand requested in the network. With the non-peak because they would start separately, in the current one it still generates the tariff.
About DEV FREE, I'll get another log and check again, if I find any discrepancies I'll post it here for you to look at too, thanks for the clarification.
Example: --gpu-init-mode 60, it would be for GPU 1 to start 60 seconds after GPU 0 and so on.
It would help in my region not to pay an energy tariff when the miner is initiated by the high demand requested in the network. With the non-peak because they would start separately, in the current one it still generates the tariff.
About DEV FREE, I'll get another log and check again, if I find any discrepancies I'll post it here for you to look at too, thanks for the clarification.
hello your miner is not running on leafpool.com
Hi. Apparently it's the share validation functionality that's broken, we'll look into it. Remove "--validate-shares" parameter and try again, it should be mining just fine.
Hello. I'm trying to mine Raven with octopus algorithm, but i'm having errors like "invalid stoll argument" or "failed to ethproxy-subscribe on stratum". Especially first one more often.
I'm seeing 64-65 mh/s with my RTX 3070 TI in this algorithm but it does not give any shares at all. Just idling.
Is it possible to use octopus algorithm for RVN with Tirex?
I'm seeing 64-65 mh/s with my RTX 3070 TI in this algorithm but it does not give any shares at all. Just idling.
Is it possible to use octopus algorithm for RVN with Tirex?
Hi. No, mining RVN is only possible using kawpow algorithm. Octopus is used by CFX.
Good morning, I would like two requests, 1st I would like to implement the option to decide the time the card will be applied in the sequential command --gpu-init-mode, 2nd implement a time counter and share the dev free, currently I walk suspicious of the % charged by the miner, I took a log and calculated, by time and share, the value was greater than 1%. version used 0.21.6
Hi.
Quote
implement the option to decide the time the card will be applied in the sequential command --gpu-init-mode
Could you clarify what you mean by that?Quote
suspicious of the % charged by the miner, I took a log and calculated, by time and share, the value was greater than 1%
It can only be greater than 1% for the first dev fee session (this is done so that people don't abuse it by restarting the miner every N minutes to avoid mining dev fee). Please share the log file where there are at least two dev fee sessions and we'll have a look. I'm pretty sure "dev fee time / miner uptime" is going to be 1%, this was tested extensively and has been working without issues since 2018.Quote from: trexminer
hello your miner is not running on leafpool.comCode:
20210818 15:04:24.306[830562.239] T-Rex NVIDIA GPU miner v0.21.6 - [Windows]
20210818 15:04:24.307[830562.239] r.3ea03a096378
20210818 15:04:24.307[830562.239]
20210818 15:04:24.312[830562.244] NVIDIA Driver v471.11
20210818 15:04:24.312[830562.244] CUDA devices available: 1
20210818 15:04:24.312[830562.245]
20210818 15:04:24.312[830562.245] WARN: DevFee 2% (autolykos2)
20210818 15:04:24.312[830562.245]
20210818 15:04:24.312[830562.245] URL : stratum+ssl://ergo-eu.leafpool.com:2288
20210818 15:04:24.312[830562.245] USER: ***
20210818 15:04:24.312[830562.245] PASS: x
20210818 15:04:24.313[830562.245] WRK : nikqz
20210818 15:04:24.313[830562.245]
20210818 15:04:24.313[830562.245] WARN: Temperature limit is activated. Limit is set to 65C.
20210818 15:04:24.313[830562.245]
20210818 15:04:24.313[830562.245] WARN: Built-in watchdog has been disabled!
20210818 15:04:24.315[830562.248] mtype [00.01.00]: [0], mem 0 (15)
20210818 15:04:24.316[830562.249] mmaker[00.01.00]: [0], mem 10 (10)
20210818 15:04:24.316[830562.249] Starting on: ergo-eu.leafpool.com:2288
20210818 15:04:24.317[830562.249] [submit_work_thread] start
20210818 15:04:24.317[830562.249] [get_stratum_work_thread] start
20210818 15:04:24.317[830562.249] [asio_thread_func] start
20210818 15:04:24.332[830562.265] Connecting to: ergo-eu.leafpool.com:2288, ip: 155.94.210.149
20210818 15:04:24.381[830562.313] ApiServer: HTTP server started on 127.0.0.1:4067
20210818 15:04:24.383[830562.316] ---------------------------------------------------
20210818 15:04:24.384[830562.316] For control navigate to: http://127.0.0.1:4067/trex
20210818 15:04:24.384[830562.316] ---------------------------------------------------
20210818 15:04:24.384[830562.316] ApiServer: Telnet server started on 127.0.0.1:4068
20210818 15:04:24.506[830562.438] -OUT-> {"id":1,"method":"mining.subscribe","params":["t-rex/0.21.6"]}
20210818 15:04:24.557[830562.489] <-IN-47-0 {"id":1,"error":null,"result":[null,"d725",6]}
20210818 15:04:24.557[830562.489] Extranonce is set to: d725
20210818 15:04:24.557[830562.489] -OUT-> {"id":3,"method":"mining.authorize","params":["***","x"],"worker":"nikqz"}
20210818 15:04:24.557[830562.489] Authorizing...
20210818 15:04:24.575[830562.508] mclock=800MHz for [0]
20210818 15:04:24.581[830562.513] pl=62% for [0]
20210818 15:04:24.581[830562.514] GPU #0(000100): Palit NVIDIA GeForce RTX 3080 Ti, intensity 25, auto-fan (memory) 80C, mclock 800MHz, pl 62%
20210818 15:04:24.607[830562.540] <-IN-36-0 {"id":3,"error":null,"result":true}
20210818 15:04:24.608[830562.540] Authorized successfully.
20210818 15:04:24.608[830562.540] -OUT-> {"id":2,"method":"mining.extranonce.subscribe","params":[]}
20210818 15:04:24.608[830562.540] ergo-eu.leafpool.com:2288 asks job for block 0
20210818 15:04:24.657[830562.589] <-IN-58-215 {"id":null,"method":"mining.set_difficulty","params":[1]}
20210818 15:04:24.657[830562.590] ergo-eu.leafpool.com:2288 asks job for block 0
20210818 15:04:24.658[830562.590] <-IN-215-0 {"id":null,"method":"mining.notify","params":["bbf",557159,"a26c024b7bba1ec2fcd48c5b1873301ae3b0c78ebe0835fd2852cce68db07494","","",2,"26959535291011309493156476344723991336010898738574164086137773096960","",true]}
20210818 15:04:24.658[830562.590] GOT NEW WORK job_id=bbf, old: job_id=
20210818 15:04:24.658[830562.590] autolykos2 block: 557159, diff: 4.29 G
20210818 15:04:24.658[830562.590] WARN: New iteration find nonces for device [ID=0, GPU #0]: job_id=bbf
20210818 15:04:24.661[830562.594] GPU #0: allocated memory for the dataset, memory left: 8.84 GB
20210818 15:04:24.707[830562.639] <-IN-59-0 {"id":2,"result":false,"error":[20,"Not supported.",null]}
20210818 15:04:24.708[830562.640] ergo-eu.leafpool.com:2288 asks job bbf for block 557159
20210818 15:04:25.884[830563.816] GPU #0: dataset generated for block 557159 [time: 1223 ms]
20210818 15:04:34.317[830572.249] GPU #0: auto-fan activated, target memory temperature 80C, [0% - 60%]
20210818 15:04:34.318[830572.251] auto-fan for [0]: memory temperature: 70C, target: 80C, delta: -15.0%
20210818 15:04:34.323[830572.256] fan=42% for [0]
20210818 15:04:37.887[830575.819] WARN: GPU #0: result for 0xd725cf0636e45835 does not validate on CPU!
20210818 15:04:37.888[830575.820] [INVL] 0/1 - share validation failed ... GPU #0
20210818 15:04:44.324[830582.257] auto-fan for [0]: memory temperature: 68C, target: 80C, delta: -13.6%
20210818 15:04:44.326[830582.258] fan=43% for [0]
20210818 15:04:54.332[830592.264] auto-fan for [0]: memory temperature: 74C, target: 80C, delta: 7.2%
20210818 15:04:54.333[830592.265] fan=60% for [0]
20210818 15:04:57.785[830595.718] WARN: GPU #0: result for 0xd725cf0720b04de0 does not validate on CPU!
20210818 15:04:57.786[830595.718] [INVL] 0/2 - share validation failed ... GPU #0
20210818 15:05:04.338[830602.270] auto-fan for [0]: memory temperature: 74C, target: 80C, delta: -4.8%
20210818 15:05:04.339[830602.271] fan=55% for [0]
20210818 15:05:14.344[830612.276] auto-fan for [0]: memory temperature: 76C, target: 80C, delta: 0.8%
20210818 15:05:14.345[830612.278] fan=56% for [0]
20210818 15:05:18.104[830616.036] WARN: GPU #0: result for 0xd725cf0859b7e904 does not validate on CPU!
20210818 15:05:18.104[830616.037] [INVL] 0/3 - share validation failed ... GPU #0
20210818 15:05:20.657[830618.589] WARN: GPU #0: result for 0xd725cf0881a1cf70 does not validate on CPU!
20210818 15:05:20.658[830618.590] [INVL] 0/4 - share validation failed ... GPU #0
20210818 15:05:24.348[830622.280] auto-fan for [0]: memory temperature: 76C, target: 80C, delta: -3.2%
20210818 15:05:24.349[830622.282] fan=53% for [0]
-------20210818 15:05:25.111[830623.044] --------
Mining at ergo-eu.leafpool.com:2288, diff: 4.29 G
GPU #0: Palit NVIDIA RTX 3080 Ti - 225.39 MH/s, [T:56/76C, P:211W, F:56%, E:1.09MH/W], 0/4 R:0% I:100%
Shares/min: 0
Uptime: 1 min | Algo: autolykos2 | T-Rex v0.21.6
20210818 15:05:25.511[830623.443] WARN: GPU #0: result for 0xd725cf08ccd05a06 does not validate on CPU!
20210818 15:05:25.511[830623.444] [INVL] 0/5 - share validation failed ... GPU #0
20210818 15:05:27.067[830624.999] WARN: GPU #0: result for 0xd725cf08e65c4418 does not validate on CPU!
20210818 15:05:27.068[830625.000] [INVL] 0/6 - share validation failed ... GPU #0
20210818 15:05:34.353[830632.285] auto-fan for [0]: memory temperature: 76C, target: 80C, delta: -3.2%
20210818 15:05:34.354[830632.287] fan=50% for [0]
20210818 15:05:43.280[830641.212] WARN: shutdown t-rex, got Ctrl+C from console
Hello. I'm trying to mine Raven with octopus algorithm, but i'm having errors like "invalid stoll argument" or "failed to ethproxy-subscribe on stratum". Especially first one more often.
I'm seeing 64-65 mh/s with my RTX 3070 TI in this algorithm but it does not give any shares at all. Just idling.
Is it possible to use octopus algorithm for RVN with Tirex?
I'm seeing 64-65 mh/s with my RTX 3070 TI in this algorithm but it does not give any shares at all. Just idling.
Is it possible to use octopus algorithm for RVN with Tirex?
...2nd implement a time counter and share the dev free, currently I walk suspicious of the % charged by the miner, I took a log and calculated, by time and share, the value was greater than 1%. version used 0.21.6
I second this proposition. Would be more transparent if we can have more clarity about the dev fee mechanism. I've never tracked it but if what said the prvious commentator is confirmed something has to be done. hope T-rex dev will do something to prove his good faith about this matter
Good morning, I would like two requests, 1st I would like to implement the option to decide the time the card will be applied in the sequential command --gpu-init-mode, 2nd implement a time counter and share the dev free, currently I walk suspicious of the % charged by the miner, I took a log and calculated, by time and share, the value was greater than 1%. version used 0.21.6
i noticed a little more stability on the rigs...
the temperature drop also helped
time will tell
the temperature drop also helped
time will tell
I don't understand why but version 21.5 is giving me a lot of rejects and GPU crashes mining ETH. I went back to 21.4
I haven't tried 21.6 but I'm not willing to right now.
I haven't tried 21.6 but I'm not willing to right now.
trexminer
Hello.
When you add support to monitor hash, temp... using claymore ethman ?
Thanks.
Hello.
When you add support to monitor hash, temp... using claymore ethman ?
Thanks.
I didnt post that link for you or anyone to actualy use it, I meant to say that only there more precise hashrate can be seen now.
No, efficiency is not properly calculated - that's one problem. Second power consumption is not avg. over time, but current. Actual 2h avg. power consumption for gpu1 is 198.34wt according to HWinfo. So best(and only) way is to go to http://192.168.0.101:3333/summary. There hashrate(minute or instant) is what it is supposed to bee: ~4205kh/s
Doesnt matter a tuning improvement would still be reflected regardless of which data set you use…which was your actual request.
But you dont seem to understand that or that Internal network links are internal.
Enjoy chasing that windmill Mr. Quixote.
Jump to: