Pages:
Author

Topic: T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 23. (Read 175016 times)

full member
Activity: 1226
Merit: 209
Actual h\r on pool side is indeed 50% of reported.



It's a known problem that only occurs when mining on nanopool, we're looking into it. Mining on other pools is unaffected.
as follows, up to 50% of the rejects on nicehash

Which version? If 0.21.2, could you upload the log file?
Code:
20210709 19:49:34.171[784846.400] -OUT-> {"id":216934401,"method":"mining.submit","params":["*************.*************","00000000db3e4a50","33dd6bb444","00000000","108a8e33dd6bb444"],"worker":"Farm2"}
20210709 19:49:34.327[784846.552] <-IN-66-0 {"id":216934401,"result":false,"error":[1,"Share above target."]}
20210709 19:49:34.437[784846.656] [FAIL] 1158/1163 - Share above target., 255ms ... GPU #1
20210709 19:49:34.437[784846.660] autolykos.eu-north.nicehash.com:3390 asks job 00000000db3e4a50 for block 528488
20210709 19:49:40.614[784852.835] -OUT-> {"id":218581763,"method":"mining.submit","params":["*************.****************","00000000db3e4a50","9a584ea21c","00000000","108a8e9a584ea21c"],"worker":"Farm2"}
20210709 19:49:40.802[784853.032] <-IN-66-0 {"id":218581763,"result":false,"error":[1,"Share above target."]}
20210709 19:49:40.864[784853.093] [FAIL] 1158/1164 - Share above target., 257ms ... GPU #3
20210709 19:49:40.864[784853.096] autolykos.eu-north.nicehash.com:3390 asks job 00000000db3e4a50 for block 528488
20210709 19:49:41.722[784853.954] <-IN-229-0 {"id":null,"method":"mining.notify","params":["00000000db3e4a51",528488,"b7de423bd2296543770a31e637a70b4782fc01d9dd52211e3a06ff4e53e7f58d","","",2,"41157205394722105456231126733432809649589828953424482219666653390575","",false]}
20210709 19:49:41.816[784854.038] GOT NEW WORK job_id=00000000db3e4a51, old: job_id=00000000db3e4a50
20210709 19:49:41.909[784854.129] WARN: New iteration find nonces for device [ID=1, GPU #1]: job_id=00000000db3e4a51
20210709 19:49:41.909[784854.129] WARN: New iteration find nonces for device [ID=4, GPU #4]: job_id=00000000db3e4a51
20210709 19:49:41.909[784854.129] WARN: New iteration find nonces for device [ID=2, GPU #2]: job_id=00000000db3e4a51
20210709 19:49:41.909[784854.129] WARN: New iteration find nonces for device [ID=3, GPU #3]: job_id=00000000db3e4a51
20210709 19:49:41.940[784854.173] WARN: New iteration find nonces for device [ID=0, GPU #0]: job_id=00000000db3e4a51
20210709 19:49:53.594[784865.814] -OUT-> {"id":221904387,"method":"mining.submit","params":["*************.****************","00000000db3e4a51","99beb24d00","00000000","108a8e99beb24d00"],"worker":"Farm2"}
20210709 19:49:53.734[784865.965] <-IN-66-0 {"id":221904387,"result":false,"error":[1,"Share above target."]}
20210709 19:49:53.828[784866.057] [FAIL] 1158/1165 - Share above target., 243ms ... GPU #3
20210709 19:49:53.828[784866.061] autolykos.eu-north.nicehash.com:3390 asks job 00000000db3e4a51 for block 528488
20210709 19:49:55.512[784867.734] -OUT-> {"id":222395649,"method":"mining.submit","params":["*************.*************","00000000db3e4a51","335e6ed01c","00000000","108a8e335e6ed01c"],"worker":"Farm2"}
20210709 19:49:55.653[784867.886] <-IN-66-0 {"id":222395649,"result":false,"error":[1,"Share above target."]}
20210709 19:49:55.762[784867.995] [FAIL] 1158/1166 - Share above target., 261ms ... GPU #1
20210709 19:49:55.778[784867.999] autolykos.eu-north.nicehash.com:3390 asks job 00000000db3e4a51 for block 528488

newbie
Activity: 1
Merit: 0
hello i got this error when t-rex restarted

ernel: [61101.636943][T24530] mpool_observer[24530]: segfault at a3 ip 000000000050a9ed sp 00007f4c26ffc4d0 error 4 in t-rex[400000+1891000]
Jul 10 10:40:15 kelinci kernel: [61101.636955][T24530] Code: c4 30 5b 5d 41 5c 41 5d 41 5e c3 66 90 4c 8d 77 30 89 4c 24 0c 89 34 24 4c 89 f7 e8 ed bf ef ff 48 8b 3b 8b 34 24 8b 4c 24 0c <80> bf a3 00 00 00 00 49 89 f9 0f 85 8b 00 00 00 84 c9 0f 84 26 01
Jul 10 10:40:19 kelinci kernel: [61105.043536][T25366] DTS: killing sk:00000000a8226e9c (127.0.0.1:58186 -> 127.0.0.1:4059) state 6
Jul 10 10:40:19 kelinci kernel: [61105.043539][T25366] DTS: killing sk:00000000556a53a0 (127.0.0.1:58190 -> 127.0.0.1:4059) state 6
Jul 10 10:40:19 kelinci kernel: [61105.043540][T25366] DTS: killing sk:00000000f6e6380a (127.0.0.1:58174 -> 127.0.0.1:4059) state 6
Jul 10 10:40:19 kelinci kernel: [61105.043542][T25366] DTS: killing sk:000000001330665f (127.0.0.1:58182 -> 127.0.0.1:4059) state 6
Jul 10 10:40:19 kelinci kernel: [61105.043543][T25366] DTS: killing sk:00000000faa6e06d (127.0.0.1:58178 -> 127.0.0.1:4059) state 6

can anyone help me pls
member
Activity: 283
Merit: 63
Actual h\r on pool side is indeed 50% of reported.



It's a known problem that only occurs when mining on nanopool, we're looking into it. Mining on other pools is unaffected.
as follows, up to 50% of the rejects on nicehash

Which version? If 0.21.2, could you upload the log file?
full member
Activity: 1226
Merit: 209
Actual h\r on pool side is indeed 50% of reported.



It's a known problem that only occurs when mining on nanopool, we're looking into it. Mining on other pools is unaffected.
as follows, up to 50% of the rejects on nicehash
newbie
Activity: 1
Merit: 0
I would like to request a feature which would enable me to schedule times when a miner has to pause and take a break and when to resume work. PhoenixMiner offers something like this with its 'pauseAt' and 'resumeAt' arguments. Since mining hardware is running 24/7 it would be nice to let it rest and cool down every once in a while.

P.S. I am aware that Windows users can setup a scheduled task that would send requests to HTTP API http://127.0.0.1:4067/control?pause=true and http://127.0.0.1:4067/control?pause=fals, but still it would be nice to have that build into a miner.
member
Activity: 283
Merit: 63
Actual h\r on pool side is indeed 50% of reported.



It's a known problem that only occurs when mining on nanopool, we're looking into it. Mining on other pools is unaffected.
jr. member
Activity: 312
Merit: 2
Actual h\r on pool side is indeed 50% of reported.

jr. member
Activity: 312
Merit: 2
What the hell is wrong with fan control on pascals? It would spin fans to 90%+ for quite some time before settle down. No such thing was on 0.20.4 version when i mined MTP, now I found out u can mine EGRO and tried latest version and got this.... Well, eventually it got ok, but at some point fan control got cards 10C° below tt.

PS oh, and T-rex is more power consuming than NBminer a little bit. Reported h\r is the same.

PSS after 40minutes it does not look good on the pools side, it's like 50% of h\r I had with NBminer. I'll mine for at least 3 hours with 1 rig though just to be sure...
member
Activity: 66
Merit: 45
Where can I read about the changes in version 0.21?
I see that new protocols have been added
https://github.com/trexminer/T-Rex/releases/  
Code:
Add autolykos2 algorithm for ERGO mining (dev fee 2%)
at the moment there are many rejected shares with a low difficulty mark


Could you please run 0.21.2 with "--protocol-dump --log-path trex.log" parameters and post the log file if it happens again? Thanks.
in version 21.2 there are very few errors, this is probably a normal state
member
Activity: 283
Merit: 63
Where can I read about the changes in version 0.21?
I see that new protocols have been added
https://github.com/trexminer/T-Rex/releases/  
Code:
Add autolykos2 algorithm for ERGO mining (dev fee 2%)
at the moment there are many rejected shares with a low difficulty mark


Could you please run 0.21.2 with "--protocol-dump --log-path trex.log" parameters and post the log file if it happens again? Thanks.
member
Activity: 66
Merit: 45
Where can I read about the changes in version 0.21?
I see that new protocols have been added
https://github.com/trexminer/T-Rex/releases/   
Code:
Add autolykos2 algorithm for ERGO mining (dev fee 2%)
at the moment there are many rejected shares with a low difficulty mark
jr. member
Activity: 152
Merit: 3
Where can I read about the changes in version 0.21?
I see that new protocols have been added
https://github.com/trexminer/T-Rex/releases/  

Quote
Quote
Add autolykos2 algorithm for ERGO mining (dev fee 2%).
we always take minors for cash cows ... as they say in my country.

there is other software with 1.25% or 1.50% that works fine.
legendary
Activity: 3164
Merit: 1003
Where can I read about the changes in version 0.21?
I see that new protocols have been added
https://github.com/trexminer/T-Rex/releases/  

EDIT: You can read it here.
member
Activity: 66
Merit: 45
Where can I read about the changes in version 0.21?
I see that new protocols have been added
newbie
Activity: 24
Merit: 1
Is there a way to monitor t-rex using claymore ethman console?, phoenixminer and teamredminer can but this one is not working
newbie
Activity: 2
Merit: 0
I ran 2 x 3080 on minerstat
set absolute core clock at 1060 , memclock +1200 the galax is working fine but my MSI gaming Z Trio doesnt seem to lock the core clock . any advice?
newbie
Activity: 19
Merit: 0
install 466.55 now it's fine!
thx!
full member
Activity: 1125
Merit: 136
same here , High CPU usage 37.6% !

using latest NVIDIA driver 471.11 and Win 11,  [turning off --validate-shares or --cpu-priority 1] dose not help in my case., is there any other solution ?
 


I am having problem with one of miners. It is W10 1903, 2x1070 Nvidia with latest drivers. Cpu usage is locked on 100% on miner Huh I downloaded today latest miner for rvn fork ..

For comparison of cpu usage, Driver 436.02 vs Driver 430.64 took a few days to identify that new drivers were overloading cpu.

Driver 436.02


Driver 430.64


Obviously its a driver issue so use an older driver.
newbie
Activity: 19
Merit: 0
same here , High CPU usage 37.6% !

using latest NVIDIA driver 471.11 and Win 11,  [turning off --validate-shares or --cpu-priority 1] dose not help in my case., is there any other solution ?
 


I am having problem with one of miners. It is W10 1903, 2x1070 Nvidia with latest drivers. Cpu usage is locked on 100% on miner Huh I downloaded today latest miner for rvn fork ..

For comparison of cpu usage, Driver 436.02 vs Driver 430.64 took a few days to identify that new drivers were overloading cpu.

Driver 436.02
https://i.postimg.cc/bJ5NF0HM/99.jpg

Driver 430.64
https://i.postimg.cc/7LY2FV0Y/7.jpg
full member
Activity: 1281
Merit: 141
Hi CPU load in Task Manager 39%  anyone knows how to fix it? is it normal?

Can try turning off --validate-shares or --cpu-priority 1

Pages:
Jump to: