Topic: A real discussion about 100% unlock (Read 176 times)
Bump
Ok I'm gonna start off by saying I've read about this on trex miners GitHub. https://github.com/trexminer/T-Rex/issues/991
That is the discussion there. I want to talk about what it takes to induce a invalid share with each type of lhr card and what clocks were used. Leave no details unturned. My thoughts are this and I'm no coder by any means but maybe this can be a start to getting Fhr on our cards and giving Nvidia the middle finger. The discussion about this for the people who don't go read the GitHub discussion is after one or more invalid shares the card will unlock and stay unlocked until a computer restart. I would assume if we could get some concrete nbers and whatnot maybe something could be coded to try automate the invalid shares to get it to full hash rate. So go and read the discussion, try it out for yourself and let's get some numbers down on paper.
I personally have been trying 3060 be cards but have been having a problem getting invalids. Others have done 3060ti and 3070
That is the discussion there. I want to talk about what it takes to induce a invalid share with each type of lhr card and what clocks were used. Leave no details unturned. My thoughts are this and I'm no coder by any means but maybe this can be a start to getting Fhr on our cards and giving Nvidia the middle finger. The discussion about this for the people who don't go read the GitHub discussion is after one or more invalid shares the card will unlock and stay unlocked until a computer restart. I would assume if we could get some concrete nbers and whatnot maybe something could be coded to try automate the invalid shares to get it to full hash rate. So go and read the discussion, try it out for yourself and let's get some numbers down on paper.
I personally have been trying 3060 be cards but have been having a problem getting invalids. Others have done 3060ti and 3070
Jump to: