Windows 1.8.0 CUSA X11EXO #37
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I am pritty much no longer maintaining this repository, Your pull request will stand as-is for others to see, but There are forks from various active developers who Christian 2016-06-16 7:10 GMT+02:00 jaredkaragen [email protected]:
|
|
Okie; I guess at some point I'll have to download the source and ability to compile and just get it done myself :) Thanks for the prompt reply. I'll see if the fork dev will make the change before I try the other approach. -Alan Sent from my iPhone
|
optimized for the 9xx and more recent, same results on the 750 Ti + restore second nonce support not present in nicehash published version Better on linux at least...
seems better on windows and a bit easier to read...
these informations are shown with ccminer -D -n
boost clocks and the thermal limit are shared with afterburner beware with your settings, not as safe as application clocks! Note: both nvapi and nvml are now used on windows x64 Signed-off-by: Tanguy Pruvot <[email protected]>
also add perf stats api, unsure what it is exactly..
cuda 6.5 one seems to crash on pascal or report invalid mem sizes
seen on yiimp benchs, PNY duplicate could be for usb keys only
also query the led level and fix OV delta output note: the Gigabyte 1080 G1 seems not compatible with the current nvapi
you can now use --led=0xFF00FF to change the color/level (windows only) for non-rvb standard nvidia devices, you can use a level value (0 to 100) ps: i really need to find how to turn them off on linux, not found yet...
and rename RVB to RGB, french typo...
disabled by default, require --led=100 on nvidia compatible devices Gigabyte RGB led hack is not perfect for the moment, can fail and require a reboot.
sample usage if GPU #0 is RVB and GPU #1 a generic led: ccminer --led=0x00ff00,100,mining to put the led on while the gpus are scanning
rewrote almost properly ;)
1 MH/s reached on the 1070 ...
no weird protocol or reversed endian like sia...
mostly imported from opensourced vertcoin-miner with a few fixes
remove outdated sentences with typos
Fix for block reorg on alternate block being promoted to accepted block.
does not support equihash, wildkeccak, scrypt and cryptonight (outdated anyway)
removed outdated comment about installing gcc 5... it confuses the rare people reading the install man page
* Init docker build * Set workdir before switching branches * nvidia drivers * ldconfig * Actions can't run as no GPU * Docker prune * Disk space docker pull parttimelegend/ccminer
tpruvot
force-pushed
the
linux
branch
2 times, most recently
from
1cccfa7 to
edc45ba
Compare
tpruvot
force-pushed
the
linux
branch
4 times, most recently
from
90f8f1b to
288ba23
Compare
tpruvot
force-pushed
the
linux
branch
3 times, most recently
from
79355c5 to
d3ccae5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am wondering if the pre-compiled X11EVO windows [and other] release[s] can be changed to accommodate larger passwords.
The main DEV version is correct, but the X11EVO release does not have the ability to accept passwords >100 chars without truncating it shortly thereafter. This is a necessary modification for our yiimp pool, as algo normalization is done through the password string, and it gets rather lengthy with as many algos as our pool has. I'm not sure why this release doesn't have the increased password size like the 1.8.0 dev version has for several prior versions.
Thanks for your time!