@ -19,7 +19,7 @@ The best solution for this is to use a tool called Zadig to set the driver:
@@ -19,7 +19,7 @@ The best solution for this is to use a tool called Zadig to set the driver:
This allows you set the driver for the device to be WinUSB which is usually
required to make it work if you're having problems
With Zaidg, you may need to run it as administrator and if your device is
With Zadig, you may need to run it as administrator and if your device is
plugged in but you cannot see it, use the Menu: Options -> List All Devices
You must also make sure you are using the latest libusb-1.0.dll supplied
@ -437,7 +437,10 @@ Work Utility (WU) value will confirm you are not generating garbage. You
@@ -437,7 +437,10 @@ Work Utility (WU) value will confirm you are not generating garbage. You
should be getting about .9WU per kHash. If not, then try decreasing your
intensity, do not increase the number of gpu-threads, and consider adding
system RAM to match your GPU ram. You may also be using a bad combination
of driver and/or SDK.
of driver and/or SDK. If you are getting a lot more HW errors with the
current version of cgminer but were not on an older version, chances are that
the older version simply wasn't reporting them so going back to and older
version is not a real solution.
Q: Scrypt fails to initialise the kernel every time?
A: Your parameters are too high. Don't add GPU threads, don't set intensity
@ -462,6 +465,11 @@ Q: I change my GPU engine/memory/voltage and cgminer reports back no change?
@@ -462,6 +465,11 @@ Q: I change my GPU engine/memory/voltage and cgminer reports back no change?
A: Cgminer asks the GPU using the ATI Display Library to change settings, but
the driver and hardware are free to do what it wants with that query, including
ignoring it. Some GPUs are locked with one or more of those properties as well.
The most common of these is that many GPUs only allow a fixed difference
between the engine clock speed and the memory clock speed (such as the memory
being no lower than the engine - 150). Other 3rd party tools have unofficial
data on these devices on windows and can get the memory clock speed down
further but cgminer does not have access to these means.
Q: I have multiple GPUs and although many devices show up, it appears to be
working only on one GPU splitting it up.
@ -483,6 +491,9 @@ A: No. The software is unchanged regardless of which driver/SDK/ADL_SDK version
@@ -483,6 +491,9 @@ A: No. The software is unchanged regardless of which driver/SDK/ADL_SDK version
you are running. However if you change SDKs you should delete any generated
.bin files for them to be recreated with the new SDK.
Q: I do not want cgminer to modify my engine/clock/fanspeed?
A: Cgminer only modifies values if you tell it to via some parameters.
SEE ALSO ASIC-README, FGPA-README, GPU-README AND SCRYPT-README FOR MORE
INFORMATION ON EACH.
SEE ALSO API-README, ASIC-README, FGPA-README, GPU-README AND SCRYPT-README FOR
MORE INFORMATION ON EACH.
---
@ -117,7 +117,6 @@ CGMiner specific configuration options:
@@ -117,7 +117,6 @@ CGMiner specific configuration options:
--enable-avalon Compile support for Avalon (default disabled)
--enable-scrypt Compile support for scrypt litecoin mining (default disabled)
--without-curses Compile support for curses TUI (default enabled)
--without-libudev Autodetect FPGAs using libudev (default enabled)
Basic *nix build instructions:
To actually build:
@ -234,10 +233,17 @@ See SCRYPT-README for more information regarding litecoin mining.
@@ -234,10 +233,17 @@ See SCRYPT-README for more information regarding litecoin mining.
Cgminer will automatically find all of your BFL ASIC, BitForce FPGAs,
ModMiner FPGAs, Icarus bitstream FPGAs or Ztex FPGAs
--avalon-options (See ASIC-README)
--bfl-range Use nonce range on bitforce devices if supported
--icarus-options <arg> Set specific FPGA board configurations - one set of values for all or comma separated
--icarus-timing <arg> Set how the Icarus timing is calculated - one setting/value for all or comma separated
--usb <arg> USB device selection (See below)
--usb-dump (See FPGA-README)
The --usb option can restrict how many BFL ASIC, BitForce FPGAs,
Cgminer will automatically find all of your Avalon ASIC, BFL ASIC, BitForce
FPGAs, Icarus bitstream FPGAs, ModMiner FPGAs, or Ztex FPGAs
The --usb option can restrict how many Avalon, BFL ASIC, BitForce FPGAs,
ModMiner FPGAs or Icarus bitstream FPGAs it finds:
--usb 1:2,1:3,1:4,1:*
@ -288,7 +294,8 @@ If one of the 10 devices stops working, hotplug - if enabled, as is default
@@ -288,7 +294,8 @@ If one of the 10 devices stops working, hotplug - if enabled, as is default
--usb :0 will disable all USB I/O other than to initialise libusb
For other FPGA details see the FPGA-README
For more ASIC details see the ASIC-README
For more FPGA details see the FPGA-README
---
@ -518,6 +525,10 @@ A: No, cgminer keeps a database of the block it's working on to ensure it does
@@ -518,6 +525,10 @@ A: No, cgminer keeps a database of the block it's working on to ensure it does
not work on stale blocks, and having different blocks from two networks would
make it invalidate the work from each other.
Q: Can I configure cgminer to mine with different login credentials or pools
for each separate device?
A: No.
Q: Can I put multiple pools in the config file?
A: Yes, check the example.conf file. Alternatively, set up everything either on
the command line or via the menu after startup and choose settings->write
@ -679,6 +690,11 @@ every time cgminer looks for new hardware to hotplug it it can cause these
@@ -679,6 +690,11 @@ every time cgminer looks for new hardware to hotplug it it can cause these
sorts of problems. You can disable hotplug with:
--hotplug 0
Q: Can I use a proxy?
A: Proxies only work with the getwork and GBT protocols using the --proxy
command. If you wish to use a proxy with stratum, people have supported
success with various 3rd party tools like proxifier.
---
This code is provided entirely free of charge by the programmer in his spare