Those cards are meant to be used for gaming, not mining.
|
|
|
you can't know on which pool and which port will claymore devfee mine, until it starts mining. Only way to have total control over the connections it makes would be to make a wrapper around the app, which detects outgoing connections and ..does stuff... But your tool is good for eth only mining on default devfee pools.
|
|
|
As a solution you can modify your hosts file in Windows or /etc/hosts in Linux and redirect DNS to only one pool you wish, so miner will think it connects to random pools, but actually it will mine at one pool to your wallet.
Can you please share your /etc/hosts file ? How do you re-write the port number so they all connect to ethermine on 4444 for example ? Boom, there's the point. You can't redirect ports with hosts file.
|
|
|
just a question: what happens when i mine an eth fork, and have to enable -allcoins ?
|
|
|
I'm not, just sayin, you are not forced to use ssl with his miner.
|
|
|
no, you don't have to use the ssl, so then it's not encrypted
|
|
|
This guy probably had a weak pass at MPH, autopayout set too high (hey, why would you keep 5 ETH on your pool) , so he has to blame something/someone for his own stupidity.
|
|
|
He probably misses 1500-2000
|
|
|
DevFee is eth only, in solo & dual mode. Only difference is 1% solo, 2% dual.
|
|
|
I already asked about 20 pages ago, but here it goes again, cause i did not get an answer: can pool job timeout be changed? Now it's 15 minutes, can it be set to less?
|
|
|
and then you need to go to the padding between the legacy VBIOS & the UEFI one, and remove enough such that the VBIOS image remains the same size
There are very rare bioses where it (remove part of the padding) is not possible. so how do you add anything extra in those kind of bioses?
|
|
|
a guy with 50ghs just flew in on ubiq
|
|
|
Hello how i can check if i have dual bios in my gpu ? and how to check what memory i have ?
dual bios gpus have a hardware switch on the card, and the answer to 2 is gpu-z.
|
|
|
This is because it has no init regulator object in its VoltageObjectInfo table - and he said he doesn't plan to add support for inserting offsets, so god knows he wouldn't support inserting entire voltage objects.
Niko and you pointed out a few things, and since you were right, no one has to be affraid, i won't add anything "spectacular" to the tool
|
|
|
After gpu or mem freq change you have to save bios then re-open it. Until then voltage stuff is disabled Until V2.62 the offset had to be on a "expected place" in VOI, but now i changed that and it finds it on any place , if it exists in the VOI. Maybe this way a few more cards will be capable of changing vddc
|
|
|
|