123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926 |
- SUPPORTED DEVICES
- Currently supported devices include:
- - Antminer U1/U2/U2+/U3 USB
- - Antminer S1
- - ASICMINER block erupters
- - ASICMINER Tube/Prisma
- - Avalon (including BitBurner and Klondike)
- - Avalon2/3
- - Avalon4/4.1/6
- - Avalon7
- - Avalon8
- - BFx2 USB
- - Butterfly Labs SC 65/28nm range
- - BF1 (bitfury) USB (red and blue)
- - BlackArrow Bitfury
- - BlackArrow Minion
- - Bi*fury USB
- - Cointerra
- - Compac bitshopperde and GekkoScience
- - Halong Dragonmint T1
- - Hashfast Babyjet and Sierra
- - Hashratio
- - Hexfury USB
- - KnCminer Mercury, Saturn and Jupiter
- - Nanofury USB
- - Other bitfury USB devices
- - Onestring miner USB
- - Rockminer R-Box/RK-Box/T1/New R-Box
- - Spondoolies SP10, SP30
- No COM ports on windows or TTY devices will be used by cgminer as it
- communicates directly with them via USB so it is normal for them to not exist or
- be disconnected when cgminer is running.
- The BFL devices should come up as one of the following:
- BAJ: BFL ASIC Jalapeño
- BAL: BFL ASIC Little Single
- BAS: BFL ASIC Single
- BAM: BFL ASIC Minirig
- BMA: BFL Monarch
- BFL devices need the
- Avalon will come up as AVA.
- Avalon devices need the
- Avalon2/3 will come up as AV2.
- Avalon2/3 devices need the
- Avalon4/4.1 will come up as AV4, Please use the MM version to distinguish.
- Avalon6 will come up as AV6.
- Avalon4/4.1/6 devies need the
- Avalon7 will come up as AV7.
- Avalon8 will come up as AV8.
- Klondike will come up as KLN.
- Klondike devices need the
- ASICMINER block erupters will come up as AMU.
- ASICMINER devices need the
- Also note that the AMU is managed by the Icarus driver which is detailed
- in the FPGA-README. Configuring them uses the same mechanism as outlined
- below for getting started with USB ASICs.
- ASICMINER BlockErupter Tube/Prisma will come up as BET.
- ASICMINER Tube/Prisma devices need the
- compiling cgminer. This driver is apparently BROKEN and the original contributor
- has not submitted fixes.
- BlackArrow Bitfury devices
- BlackArrow Bitfury devices need the
- The current BlackArrow Bitfury devices are similar to the Bitfury GPIO mining
- boards, with both V1 and V2 controllers, and come up as BaB.
- BlackArrow Minion devices
- BlackArrow Minion devices need the
- cgminer.
- BlackArrow Minion devices are SPI/GPIO mining devices and come up as MBA
- BITFURY devices
- Bitfury devices need the
- Currently the BPMC/BGMC BF1 devices AKA redfury/bluefury are supported and
- come up as BF1, along with the Bi*fury USB devices which come up as BXF.
- Nanofury devices come up as NF1. BFx2 devices come up as BXM.
- Bitfury USB devices are also set up as per the USB ASICs below.
- COINTERRA devices
- Cointerra devices need the
- Cointerra devices come up as CTA devices and currently take only hidden command
- line arguments for power settings.
- Cointerra USB devices are set up as per the USB ASIC instructions below.
- Compac devices
- Compac devices need the
- bitshopperde come up as BSC and GekkoScience as GSC
- HALONG devices
- HALONG Dragonmint T1 devices will come up as DT1.
- Halong devices need the
- HASHFAST devices
- Hashfast devices need the
- All current HFA devices are supported and are recognised with the name HFA
- in the
- they are and give them the following names:
- HFB: Hashfast Babyjet
- HFS: Hashfast Sierra
- HFA: Hashfast non standard (eg. a Babyjet with an added board, Habanero)
- HASHRATIO devices
- Hashratio devices need the
- ANTMINER U1/U2+/U3 devices
- Antminer devices need the
- Currently the U1/2/3 USB sticks are supported and come up as the following
- devices:
- ANU: Antminer U1/U2/U2+
- AU3: Antminer U3
- They are also set up as per the USB ASICs below.
- ANTMINER S1 devices
- Antminer S1 devices need the
- They are custom OpenWRT linux devices
- They are recognised with the name ANT
- BITMINE A1 devices
- Bitmine A1 devices need the
- Rockminer R*Box
- Rockminer R*Box devices need the
- They appear with the following names:
- LIN: R-Box
- LIR: New R-Box
- GETTING STARTED WITH USB ASICS
- Unlike other software, cgminer uses direct USB communication instead of the
- ancient serial USB communication to be much faster, more reliable and use a
- lot less CPU. For this reason, setting up for mining with cgminer on these
- devices requires different drivers.
- WINDOWS:
- On windows, the direct USB support requires the installation of a WinUSB
- driver (NOT the ftdi_sio driver), and attach it to the chosen USB device.
- When configuring your device, plug it in and wait for windows to attempt to
- install a driver on its own. It may think it has succeeded or failed but wait
- for it to finish regardless. This is NOT the driver you want installed. At this
- point you need to associate your device with the WinUSB driver. The easiest
- way to do this is to use the zadig utility which you must right click on and
- run as administrator. Then once you plug in your device you can choose the
- "list all devices" from the "option" menu and you should be able to see the
- device as something like: "BitFORCE SHA256 SC". Choose the install or replace
- driver option and select WinUSB. You can either google for zadig or download
- it from the cgminer directory in the DOWNLOADS link above.
- When you first switch a device over to WinUSB with zadig and it shows that
- correctly on the left of the zadig window, but it still gives permission
- errors, you may need to unplug the USB miner and then plug it back in. Some
- users may need to reboot at this point.
- LINUX:
- On linux, the direct USB support requires no drivers at all. However due to
- permissions issues, you may not be able to mine directly on the devices as a
- regular user without giving the user access to the device or by mining as
- root (administrator). In order to give your regular user access, you can make
- him a member of the plugdev group with the following commands:
- sudo usermod -G plugdev -a `whoami`
- If your distribution does not have the plugdev group you can create it with:
- sudo groupadd plugdev
- In order for the BFL devices to instantly be owned by the plugdev group and
- accessible by anyone from the plugdev group you can copy the file
- "01-cgminer.rules" from the cgminer archive into the /etc/udev/rules.d
- directory with the following command:
- sudo cp 01-cgminer.rules /etc/udev/rules.d/
- After this you can either manually restart udev and re-login, or more easily
- just reboot.
- OSX:
- On OSX, like Linux, no drivers need to be installed. However some devices
- like the bitfury USB sticks automatically load a driver thinking they're a
- modem and the driver needs to be unloaded for cgminer to work:
- sudo kextunload -b com.apple.driver.AppleUSBCDC
- sudo kextunload -b com.apple.driver.AppleUSBCDCACMData
- There may be a limit to the number of USB devices that you are allowed to start.
- The following set of commands, followed by a reboot will increase that:
- sudo su
- touch /etc/sysctl.conf
- echo kern.sysv.semume=100 >> /etc/sysctl.conf
- chown root:wheel /etc/sysctl.conf
- chmod 0644 /etc/sysctl.conf
- Some devices need superuser access to mine on them so cgminer may need to
- be started with sudo
- i.e.:
- sudo cgminer <insert commands here>
- ASIC SPECIFIC COMMANDS
- ANTMINER S1 DEVICES
- The Antminer S1 device comes with its own operating system and a preinstalled
- version of cgminer as part of the flash firmware. No configuration should be
- necessary.
- ANTMINER U1/2/3 DEVICES
- By default, Antminer U1 devices run at a clockspeed of 200. This command allows
- you to specify a chosen frequency to attempt to run all ANU devices at. Cgminer
- will try to find the nearest frequency the device supports and will report if
- the frequency is not exactly as requested. Note that cgminer reports hashrate
- ONLY FROM VALID HASHES so if you increase the frequency but your hashrate does
- not increase or it decreases and hardware errors start showing up, you have
- overclocked it too much. In the worst case scenario it will fail to start at too
- high a speed. Most will run happily up to 250.
- ASICMINER BlockErupter Tube/Prisma DEVICES
- Default clockspeed for Tube/Prisma is 240MHz. This command allows to set clockspeed
- of on board BE200 chips in range from 200MHz to 320MHz. For Tube devices, you can
- try overclocking to 270MHz or even higher, but NOT recommended for Prisma devices.
- If you notice hash rate drops or board fails to start, restart cgminer with lower
- clockspeed.
- AVALON AND BITBURNER DEVICES
- Currently all known Avalon devices come with their own operating system and
- a preinstalled version of cgminer as part of the flash firmware, based on the
- most current cgminer version so no configuration should be necessary. It is
- possible to plug a USB cable from a PC into the Avalon device and mine using
- cgminer as per any other device. It will autodetect and hotplug using default
- options. You can customise the avalon behaviour by using the avalon-options
- command, and adjust its fan control-temperature relationship with avalon-temp.
- By default the avalon will also cut off when its temperature reaches 60
- degrees.
- All current BitBurner devices (BitBurner X, BitBurner XX and BitBurner Fury)
- emulate Avalon devices, whether or not they use Avalon chips.
- Avalon commands:
- Avalon auto will enable dynamic overclocking gradually increasing and
- decreasing the frequency till the highest hashrate that keeps hardware errors
- under 2% is achieved. This WILL run your avalon beyond its normal specification
- so the usual warnings apply. When avalon-auto is enabled, the avalon-options
- for frequency and timeout are used as the starting point only.
- eg:
- By default the avalon fans will be adjusted to maintain a target temperature
- over a range from 20 to 100% fanspeed. avalon-fan allows you to limit the
- range of fanspeeds to a single value or a range of values.
- eg:
- In combination with the avalon-auto command, the avalon-freq command allows you
- to limit the range of frequencies which auto will adjust to.
- eg:
- This will adjust fanspeed to keep the temperature at or slightly below 55.
- If you wish the fans to run at maximum speed, setting the target temperature
- very low such as 0 will achieve this. This option can be added to the "More
- options" entry in the web interface if you do not have a direct way of setting
- it.
- eg:
- This will cut off the avalon should it get up to 65 degrees and will then
- re-enable it when it gets to the target temperature as specified by avalon-temp.
- eg:
- The values are baud : miners : asic count : timeout : frequency : technology.
- Baud:
- The device is pretty much hard coded to emulate 115200 baud so you shouldn't
- change this.
- Miners:
- Most Avalons are 3 module devices, which come to 24 miners. 4 module devices
- would use 32 here.
- For BitBurner X and BitBurner XX devices you should use twice the number of
- boards in the stack. e.g. for a two-board stack you would use 4. For
- BitBurner Fury devices you should use the total number of BitFury chips in the
- stack (i.e. 16 times the number of boards). e.g. for a two-board stack you
- would use 32.
- Asic count:
- Virtually all have 10, so don't change this. BitBurner devices use 10 here
- even if the boards have some other number of ASICs.
- Timeout:
- This is how long the device will work on a work item before accepting new work
- to replace it. It should be changed according to the frequency (last setting).
- It is possible to set this a little lower if you are trying to tune for short
- block mining (eg p2pool) but much lower and the device will start creating
- duplicate shares.
- A value of 'd' means cgminer will calculate it for you based on the frequency
- and is highly recommended.
- Sample settings for valid different frequencies (last 3 values) for 110nm AVAs:
- 34:375:110 *
- 36:350:110 *
- 43:300:110
- 45:282:110 (default)
- 50:256:110
- Note that setting a value with an asterisk next to it will be using your
- avalon outside its spec and you do so at your own risk.
- For 55nm AVAs, the usual values are 8:1500
- Frequency:
- This is the clock speed of the devices. For Avalon 110nm devices, values from
- 256 upwards are valid with the default being 282 and the maximum practical
- being approximately 350. For 55nm devices values from 1000-2000 are valid with
- 1500 being the default.
- Technology:
- What sized technology ASICs are in use in the avalon, choices are 55 or 110,
- corresponding to the nm technology chips in use.
- The default frequency for BitBurner X and BitBurner XX boards is 282. The
- default frequency for BitBurner Fury boards is 256. Overclocking is
- possible - please consult the product documentation and/or manufacturer for
- information on safe values. Values outside this range are used at your own
- risk. Underclocking is also possible, at least with the X and XX boards.
- eg:
- This option takes the same format as
- will be used for BitBurner Fury boards in preference to the values specified
- in
- controlled by the values used in
- a detailed description of the fields.
- This option is particularly useful when using a mixture of different BitBurner
- devices as BitBurner Fury devices generally require significantly different
- clock frequencies from Avalon-based devices. This option is only available
- for boards with recent firmware that are recognized by cgminer as BBF.
- eg:
- Sets the core voltage for the BitBurner Fury boards. The default value is
- 900. Overvolting is possible - please consult the product documentation
- and/or manufaturer about the safe range of values. Values outside this range
- are used at your own risk.
- This option is only available for boards with recent firmware that are
- recognized by cgminer as BBF. For boards recognized as BTB, see
- eg:
- Sets the core voltage for the Avalon-based BitBurner X and BitBurner XX
- boards. The default value is 1200. Overvolting and undervolting is
- possible - please consult the product documentation and/or the manufacturer
- for information about the safe range. Values outside this range are used at
- your own risk.
- Older BitBurner Fury firmware emulates a BitBurner XX board and is identified
- by cgminer as BTB. On these devices,
- the voltage of the BitBurner Fury board. The actual core voltage will be
- 300mV less than the requested voltage, so to run a BitBurner Fury board at
- 950mV use
- corresponds to the default core voltage of 900mV.
- If you use the full curses based interface with Avalons you will get this
- information:
- AVA 0: 22/ 46C 2400R
- The values are:
- ambient temp / highest device temp lowest detected ASIC cooling fan RPM.
- Use the API for more detailed information than this.
- Avalon2 Devices
- Avalon4 Devices
- Avalon7 Devices
- Avalon8 Devices
- BFLSC Devices
- This will allow you to change or disable the default temperature where cgminer
- throttles BFLSC devices by allowing them to temporarily go idle.
- BITFURY Devices
- In combination with the dynamic clocking on Bi*fury devices, this sets the
- highest bit target that cgminer will aim for.
- Cgminer uses dynamic clocking on Bi*fury devices to try and maintain the
- temperature just below an optimal target. This option allows you to change the
- target temperature. When actively cooled below this, the devices will run at
- maximum speed.
- Choose the overclocking bits for BFx2 devices.
- Cgminer by default sets the clockspeed on nanofury devices to the highest that
- is still within USB2 spec. This value allows you to alter the clockspeed, with
- ~54 being the optimal but requiring a higher power or USB3 port.
- Cointerra Devices
- These are undocumented.
- Drillbit Systems Devices
- * int/ext defines the clock source - default int. Not all boards support ext.
- * clock_divider must be 1 or 2 with a default of 1. Bitfury only,
- ignored on Avalon.
- * clock is in MHz, on Drillbit range 80-250 with a default of 200,
- recommended maximum 230. On Avalon range 500-1000 with a
- recommended maximum of 800.
- * voltage is ASIC core voltage in millivolts, available values vary per board but
- default is 850 and the recommended maximum is 950 (Bitfury) and 1000 (Avalon.)
- If supported by firmware and device, this feature allows cgminer to
- automatically tweak each ASIC's clock rate up and down in to achieve
- optimal performance.
- * every - only required param, check each ASIC after each block of
- this many work units. Recommended value 100.
- * gooderr - the "Good" threshold is when less hardware errors than
- this per "every" work units, the clock rate will be increased.
- Default value 1.
- * baderr - the "Bad" threshold is when more hardware errors than
- this per "every" work units, the clock rate will be decreased.
- Default value 3.
- * maxerr - the "Max" threshold is when more hardware errors than
- this per "every" work units (including pre-empting before
- "every" work units is up), the clock rate will be decreased and
- will not be increased again past this point. Default value 10.
- BlackArrow Bitfury devices
- Any option left blank or starting with 'd' will use the default setting
- If there are not enough options, then the remaining will be left at their
- default value
- Max:Def:Min are the chip speed limits to allow, ranging from 52 to 57
- Up:Down are the HW error % used to tune the chip speed
- Up means if the HW error % is less than up, over a 5 minute period,
- then increase the chip speed
- Down means if the HW error % is greater than down, over 5 minutes,
- then decrease the chip speed
- Hz is the SPI clock speed to use
- Delay is the us delay used between bytes for the SPI I/O - default 0
- Trf is the us delay used between sends for the SPI I/O - default 0
- Hashfast devices
- This will change the initialisation clock speed on all attached hfa devices.
- Note that if instability is detected by cgminer and the device has to undergo
- a reset, cgminer will lower the clockspeed on resetting it each time till the
- value returns to the default of 550.
- If you overclock your hashfast device with
- it failing to return hashes, it will restart it at a lower clock speed if
- possible. Changing this value will allow you to choose how much it will lower
- the clock speed or to disable this function entirely.
- This changes the range of fanspeeds used on hashfast devices with firmware that
- supports it. Note that the fanspeed will dynamically change to try and maintain
- a target temperature with
- disabled, the fanspeed will remain static.
- eg:
- Cgminer will temporarily stop sending hashfast devices work once this
- temperature is reached. Note that with the water cooling in these devices,
- temperature recovery is likely to be very quick and the device will start
- hashing again after only a very brief period.
- On hashfast devices with firmware that supports dynamic fanspeed and die speeds,
- cgminer will try to maintain temperature according to this target by adjusting
- fanspeed and then if need be, throttle speeds on a die-by-die basis. Disabling
- this feature will leave a constant fanspeed and die speed but will not disable
- the temp-overheat feature.
- This command allows you to specify the unique name stored in nvram on a single
- hashfast device. This name can be queried from the API stats command and comes
- up as "op name". Discrete names are used by cgminer to try to maintain settings
- across restarts, unplugs/hotplugs and so on. If this command is used by itself,
- the name will be given to the first hashfast device it encounters and then
- cgminer will proceed to go back to regular mining. If you have multiple devices,
- it is best to discretely choose the device you wish to use with the
- command. For example
- 'lsusb' on linux shows the following devices (297c:0001 is a hfa device):
- Bus 001 Device 079: ID 297c:0001
- Bus 004 Device 042: ID 297c:0001
- If you wished to name the second device Slug you would add the commands:
-
- Newer firmwares on hashfast devices dynamically disable cores that generate
- invalid data. This command will disable this feature where possible.
- This command allows you to set options for each discrete hashfast device by
- its name (if the firmware has naming support, i.e. version 0.3+). Currently
- this takes as option the clock speed alone or clock speed and voltage,
- although future options may be added.
- e.g.:
- Would set a device named rabbit to clock speed 650 MHz using default voltage
- and the one named turtle to 550 MHz using a voltage of 800 mv. Starting the
- device at a speed where it is most stable will give more reliable hashrates
- long term and prevent it interacting with other devices, rather than depending
- on the clockdown feature in cgminer.
- Note: Setting voltage cause a board reset and hotplug event on cgminer startup.
- Other undocumented hashfast command line options are for development purposes
- only at this stage and serve no useful purpose to end users.
- Hashratio Devices
- Bitmine A1 Devices
- ref_clk: reference clock in kHz (default: 16000)
- sys_clk: target system clock in kHz to be set in PLL (default: 250000)
- spi_clk: SPI clock in kHz (default: 800)
- max_chip: [debug/testing] limit chip chain
- Set 0 for fields you want to keep untouched to default, e.g.
- to only set SPI clock to 400kHz
- Rockminer R-Box Devices
- Note that only a limited range is likely to be accepted (usually 200-290)
- This code is provided entirely free of charge by the programmer in his spare
- time so donations would be greatly appreciated. Please consider donating to the
- address below.
- Con Kolivas <kernel@kolivas.org>
- 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ
|