From SolidCoin Wiki
Reaper is the first OpenCL GPU miner for SolidCoin 2.0, coded by mtrlt, currently in an early stage of development. It is open source and licensed under the GPL 3.0.
Reaper works well on both ATI and Nvidia GPUs. Although ATI GPUs appear to be more efficient, many types of GPU remain untested. Users are encouraged to experiment with the software and try to attain the best hash rate they can and post their results on the official SolidCoin forum so they can be included in the Mining Hardware Performance page.
As well as supporting GPU mining, Reaper can be configured to mine with the CPU as well. Enabling CPU mining does not normally have an impact on GPU mining hash rates.
The newest version is currently v13 beta 4.
v13 beta 4:
- Fixed some linux bugs
- Added long polling
v13 beta 3:
- Fixed compiling for Tahiti (79xx), and probably many other cards too
- Using Catalyst 12.2 or newer is now recommended
v13 beta 2:
- LTC and BTC GPU mining
- SLC GPU mining +100% speed
- SLC CPU mining 64-bit +60%, 32-bit +100%
- Mining speed 1-2% faster
- Linux compiling easier
- Can put the host/port/user/pass info to the config too
- long_polling [yes/no]
- include [filename]
- proxy [address]
- Mining is now about 20% faster
- CMake build system
- Send correct user agent
- Time between getworks from 2s to 20s
- max aggression target from 500ms to 320ms
- Windows build from curl 7.21.4 to 7.22.0
- Fixed random startup crashes
- Kernels for nvidia and hd4xxx compatibility
- Share the read pad between threads on the same GPU
How to use
Put your connection info to the config file like this:
Or use from the command line, syntax:
reaper <host> <port> <user> <pass> [config_filename]
The default configuration file name is reaper.conf which should be located in the same directory as the executable. The available configuration options are:
Used to specify on how many threads you want to mine on your CPU(s).
Recommended value: Number of logical cores. For example, if you have a quad core CPU set this to 4. If you have a quad core with Hyper Threading, set it to 8.
Used to specify which GPU devices reaper should use. For example, if a user had 4 GPUs, inserting the following lines into the conf:
would make Reaper use devices 0 and 2, and leave devices 1 and 3 free. If there are no device lines in the config, Reaper will attempt to use all available GPUs.
Used to specify a different kernel for a specific device. Example:
would make device 1 use "anotherkernel.cl". If a device-specific kernel is not specified, the default kernel is used.
How many threads serve each GPU. Different types of GPU may benefit from a higher or lower number, but 2 is optimal in most cases.
Recommended values: 1, 2 or 4
How much work is pushed onto the GPU at a time. Higher values for Aggression typically produce higher hash rates. Experiment with different values to find the best setting for your system.
From v10 onwards, there is a "maximum aggression" setting. It automatically sets the aggression to an optimal value. It's useful for dedicated mining machines. It is enabled like this:
aggression max instead of a number.
Recommended values: max for dedicated miners, otherwise over 10
The size of the work sent to the GPU thread. Experiment with different values to find the fastest hash rate for your setup. 128 seems to be optimal for most setups.
Recommended values: 32, 64, 128, 256
What kernel to use if not overridden by device[num].kernel. The default is reaper.cl.
Recommended value: reaper.cl
Whether to save binaries after compiling. With this option enabled, subsequent start-ups are faster. If this option is enabled, remember to delete the binaries when updating drivers.
Recommended value: yes
Select which OpenCL platform to use. For example the AMD one is called "AMD Accelerated Parallel Processing". The NVIDIA one is "CUDA something". Usually platform number 0 is the one you want.
Recommended value: 0
Whether to enable the "Graceful Shutdown" option. When this is enabled, users can press "Q" then "Enter" to shut down Reaper gracefully.
Recommended value: yes
In v11, the following options were added:
Whether to enable the experimental long polling support.
Recommended value: yes
You can now configure the server's info in the config file instead of having to use command line arguments.
Proxy information such as: socks4://user:pass@proxyaddr:port
Loads a config file and overwrites the current settings with its settings.
Kernel build not successful: -46
This bug seems to occur on systems with multiple GPUs. The best available workaround is to try repeatedly until the error goes away.
Windows reports MSVCP100.DLL missing
Install the Microsoft Visual C++ 2010 Redistributable Package