search

trexminer / T-Rex

T-Rex NVIDIA GPU miner with web control monitoring page
2.64k stars 439 forks source link

T-Rex 0.25.15 really drops the hashrate of LHR cards a lot!!! #1289

Open mikaljan opened 2 years ago

mikaljan commented 2 years ago

I've noticed on my RTX3080TI rig, on T-Rex 0.25.12, the hashrate used to be around 90MH/s, now it's around 65~70MH/s, on T-Rex 0.25.15. This is all in HiveOS btw.

I've gone back to T-Rex 0.25.12 and everything is back to normal again, I think the new version is screwed up somewhere!

Synergyst commented 2 years ago

What driver version are you using?

Had you reviewed the log file for LHR lock detections? You can run the following while getting the LHR drops to check: grep detect /var/log/miner/t-rex/t-rex.log && echo 'Locks detected..' || echo 'No locks detected, great!'

If you have any locks then reduce your memory overclock values for any of the affected cards.

mikaljan commented 2 years ago

I'm using 470.82.00 on HiveOS, because I'm using RebTech all in one motherboard, which does not work with driver newer than 470.82.00. An option should be added to preserve the 0.25.12 method in dealing with LHR cards.

What driver version are you using?

Had you reviewed the log file for LHR lock detections? You can run the following while getting the LHR drops to check: grep detect /var/log/miner/t-rex/t-rex.log && echo 'Locks detected..' || echo 'No locks detected, great!'

If you have any locks then reduce your memory overclock values for any of the affected cards.

— Reply to this email directly, view it on GitHub https://github.com/trexminer/T-Rex/issues/1289#issuecomment-1120002411, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJC2JFMMLO24SEAGWSKIHLVIWBSRANCNFSM5VJGSU2A . You are receiving this because you authored the thread.Message ID: @.***>

Synergyst commented 2 years ago

Ahh, that's your issue then..

The new unlocker requires a driver newer than that, more specifically 510.xx

mikaljan commented 2 years ago

I'm sure there are many people that can't use the latest driver, maybe T-Rex can detect the driver version and if it's older ones just retain the unlock method suitable for older drivers?

or an option to use method that's compatible with older drivers, don't abandon a group of users that can't use the newer driver.

Ahh, that's your issue then..

The new unlocker requires a driver newer than that, more specifically 510.xx

— Reply to this email directly, view it on GitHub https://github.com/trexminer/T-Rex/issues/1289#issuecomment-1120012298, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJC2JERMZBQT5RCNDY32GTVIWDSVANCNFSM5VJGSU2A . You are receiving this because you authored the thread.Message ID: @.***>

mikaljan commented 2 years ago

Upon upgrading, or using the latest HiveOS image and flash it onto SSD drive, it will generate a "nvtool error (12)" message inside HiveOS. The new driver won't be loaded thus making GPUs inoperable.

Screenshot 2022-05-11 010736

On Tue, May 10, 2022 at 4:03 AM TwistedMetalHead @.***> wrote:

Hi, can you please explain how is your motherboard related to the driver version? I thought you can just update drivers through HiveOS to 510 and they are stored on the SSD.

— Reply to this email directly, view it on GitHub https://github.com/trexminer/T-Rex/issues/1289#issuecomment-1121521500, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJC2JC4FGPARYQ2XNXIGSLVJFVQRANCNFSM5VJGSU2A . You are receiving this because you authored the thread.Message ID: @.***>