ASIC-README 8.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231
  1. SUPPORTED DEVICES
  2. Currently supported devices include the Avalon (including BitBurner), the
  3. Butterfly Labs SC range of devices, the ASICMINER block erupters and the BPMC
  4. BF1 (bitfury) USB devices. No COM ports on windows or TTY devices will be used
  5. by cgminer as it communicates directly with them via USB so it is normal for
  6. them to not exist or be disconnected when cgminer is running.
  7. The BFL devices should come up as one of the following:
  8. BAJ: BFL ASIC Jalapeño
  9. BAL: BFL ASIC Little Single
  10. BAS: BFL ASIC Single
  11. BAM: BFL ASIC Minirig
  12. BFL devices need the --enable-bflsc option when compiling cgminer yourself.
  13. Avalon will come up as AVA.
  14. Avalon devices need the --enable-avalon option when compiling cgminer.
  15. ASICMINER block erupters will come up as AMU.
  16. ASICMINER devices need the --enable-icarus option when compiling cgminer.
  17. Also note that the AMU is managed by the Icarus driver which is detailed
  18. in the FPGA-README. Configuring them uses the same mechanism as outlined
  19. below for getting started with butterfly labs ASICs.
  20. BITFURY devices
  21. Bitfury devices need the --enable-bitfury option when compiling cgminer.
  22. Currently only the BPMC BF1 devices AKA redfury/bluefury are supported and
  23. come up as BF1. There are no options available for them. Bitfury device are
  24. also set up as per the butterfly labs ASICs below.
  25. GETTING STARTED WITH BUTTERFLY LABS ASICS
  26. Unlike other software, cgminer uses direct USB communication instead of the
  27. ancient serial USB communication to be much faster, more reliable and use a
  28. lot less CPU. For this reason, setting up for mining with cgminer on these
  29. devices requires different drivers.
  30. WINDOWS:
  31. On windows, the direct USB support requires the installation of a WinUSB
  32. driver (NOT the ftdi_sio driver), and attach it to the Butterfly labs device.
  33. The easiest way to do this is to use the zadig utility which will install the
  34. drivers for you and then once you plug in your device you can choose the
  35. "list all devices" from the "option" menu and you should be able to see the
  36. device as something like: "BitFORCE SHA256 SC". Choose the install or replace
  37. driver option and select WinUSB. You can either google for zadig or download
  38. it from the cgminer directory in the DOWNLOADS link above.
  39. When you first switch a device over to WinUSB with zadig and it shows that
  40. correctly on the left of the zadig window, but it still gives permission
  41. errors, you may need to unplug the USB miner and then plug it back in. Some
  42. users may need to reboot at this point.
  43. LINUX:
  44. On linux, the direct USB support requires no drivers at all. However due to
  45. permissions issues, you may not be able to mine directly on the devices as a
  46. regular user without giving the user access to the device or by mining as
  47. root (administrator). In order to give your regular user access, you can make
  48. him a member of the plugdev group with the following commands:
  49. sudo usermod -G plugdev -a `whoami`
  50. If your distribution does not have the plugdev group you can create it with:
  51. sudo groupadd plugdev
  52. In order for the BFL devices to instantly be owned by the plugdev group and
  53. accessible by anyone from the plugdev group you can copy the file
  54. "01-cgminer.rules" from the cgminer archive into the /etc/udev/rules.d
  55. directory with the following command:
  56. sudo cp 01-cgminer.rules /etc/udev/rules.d/
  57. After this you can either manually restart udev and re-login, or more easily
  58. just reboot.
  59. ASIC SPECIFIC COMMANDS
  60. --avalon-auto Adjust avalon overclock frequency dynamically for best hashrate
  61. --avalon-cutoff <arg> Set avalon overheat cut off temperature (default: 60)
  62. --avalon-fan <arg> Set fanspeed percentage for avalon, single value or range (default: 20-100)
  63. --avalon-freq <arg> Set frequency range for avalon-auto, single value or range
  64. --avalon-options <arg> Set avalon options baud:miners:asic:timeout:freq
  65. --avalon-temp <arg> Set avalon target temperature (default: 50)
  66. --bflsc-overheat <arg> Set overheat temperature where BFLSC devices throttle, 0 to disable (default: 90)
  67. --bitburner-voltage <arg> Set BitBurner core voltage, in millivolts
  68. AVALON DEVICES
  69. Currently all known Avalon devices come with their own operating system and
  70. a preinstalled version of cgminer as part of the flash firmware, based on the
  71. most current cgminer version so no configuration should be necessary. It is
  72. possible to plug a USB cable from a PC into the Avalon device and mine using
  73. cgminer as per any other device. It will autodetect and hotplug using default
  74. options. You can customise the avalon behaviour by using the avalon-options
  75. command, and adjust its fan control-temperature relationship with avalon-temp.
  76. By default the avalon will also cut off when its temperature reaches 60
  77. degrees.
  78. Avalon commands:
  79. --avalon-auto Adjust avalon overclock frequency dynamically for best hashrate
  80. --avalon-cutoff <arg> Set avalon overheat cut off temperature (default: 60)
  81. --avalon-fan <arg> Set fanspeed percentage for avalon, single value or range (default: 20-100)
  82. --avalon-freq <arg> Set frequency range for avalon-auto, single value or range
  83. --avalon-options <arg> Set avalon options baud:miners:asic:timeout:freq
  84. --avalon-temp <arg> Set avalon target temperature (default: 50)
  85. --bitburner-voltage <arg> Set BitBurner core voltage, in millivolts
  86. Avalon auto will enable dynamic overclocking gradually increasing and
  87. decreasing the frequency till the highest hashrate that keeps hardware errors
  88. under 2% is achieved. This WILL run your avalon beyond its normal specification
  89. so the usual warnings apply. When avalon-auto is enabled, the avalon-options
  90. for frequency and timeout are used as the starting point only.
  91. eg:
  92. --avalon-fan 50
  93. --avalon-fan 40-80
  94. By default the avalon fans will be adjusted to maintain a target temperature
  95. over a range from 20 to 100% fanspeed. avalon-fan allows you to limit the
  96. range of fanspeeds to a single value or a range of values.
  97. eg:
  98. --avalon-freq 300-350
  99. In combination with the avalon-auto command, the avalon-freq command allows you
  100. to limit the range of frequencies which auto will adjust to.
  101. eg:
  102. --avalon-temp 55
  103. This will adjust fanspeed to keep the temperature at or slightly below 55.
  104. If you wish the fans to run at maximum speed, setting the target temperature
  105. very low such as 0 will achieve this. This option can be added to the "More
  106. options" entry in the web interface if you do not have a direct way of setting
  107. it.
  108. eg:
  109. --avalon-cutoff 65
  110. This will cut off the avalon should it get up to 65 degrees and will then
  111. re-enable it when it gets to the target temperature as specified by avalon-temp.
  112. eg:
  113. --avalon-options 115200:24:10:45:282
  114. The values are baud : miners : asic count : timeout : frequency.
  115. Baud:
  116. The device is pretty much hard coded to emulate 115200 baud so you shouldn't
  117. change this.
  118. Miners:
  119. Most Avalons are 3 module devices, which come to 24 miners. 4 module devices
  120. would use 32 here.
  121. Asic count:
  122. Virtually all have 10, so don't change this.
  123. Timeout:
  124. This is how long the device will work on a work item before accepting new work
  125. to replace it. It should be changed according to the frequency (last setting).
  126. It is possible to set this a little lower if you are trying to tune for short
  127. block mining (eg p2pool) but much lower and the device will start creating
  128. duplicate shares.
  129. A value of 'd' means cgminer will calculate it for you based on the frequency
  130. Sample settings for valid different frequencies (last 2 values):
  131. 34:375 *
  132. 36:350 *
  133. 39:325 *
  134. 43:300
  135. 45:282 (default)
  136. 47:270
  137. 50:256
  138. Frequency:
  139. This is the clock speed of the devices. Only specific values work, 256, 270,
  140. 282 (default), 300, 325, 350 and 375.
  141. Note that setting a value with an asterisk next to it will be using your
  142. avalon outside its spec and you do so at your own risk.
  143. eg:
  144. --bitburner-voltage <arg> Set BitBurner core voltage, in millivolts
  145. Self evident.
  146. If you use the full curses based interface with Avalons you will get this
  147. information:
  148. AVA 0: 22/ 46C 2400R
  149. The values are:
  150. ambient temp / highest device temp lowest detected ASIC cooling fan RPM.
  151. Use the API for more detailed information than this.
  152. BFLSC Devices
  153. --bflsc-overheat <arg> Set overheat temperature where BFLSC devices throttle, 0 to disable (default: 90)
  154. This will allow you to change or disable the default temperature where cgminer
  155. throttles BFLSC devices by allowing them to temporarily go idle.
  156. ---
  157. This code is provided entirely free of charge by the programmer in his spare
  158. time so donations would be greatly appreciated. Please consider donating to the
  159. address below.
  160. Con Kolivas <kernel@kolivas.org>
  161. 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ