Hero Circle Shape
Hero Moon Shape
Hero Right Shape
imtoken下载网址|cgminer挖以太坊

imtoken下载网址|cgminer挖以太坊

  • 作者: imtoken下载网址
  • 2024-03-12 19:33:29

GitHub - bitmaintech/cgminer: ASIC / FPGA / GPU miner in c for bitcoin and litecoin

GitHub - bitmaintech/cgminer: ASIC / FPGA / GPU miner in c for bitcoin and litecoin

Skip to content

Toggle navigation

Sign in

Product

Actions

Automate any workflow

Packages

Host and manage packages

Security

Find and fix vulnerabilities

Codespaces

Instant dev environments

Copilot

Write better code with AI

Code review

Manage code changes

Issues

Plan and track work

Discussions

Collaborate outside of code

Explore

All features

Documentation

GitHub Skills

Blog

Solutions

For

Enterprise

Teams

Startups

Education

By Solution

CI/CD & Automation

DevOps

DevSecOps

Resources

Learning Pathways

White papers, Ebooks, Webinars

Customer Stories

Partners

Open Source

GitHub Sponsors

Fund open source developers

The ReadME Project

GitHub community articles

Repositories

Topics

Trending

Collections

Pricing

Search or jump to...

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Cancel

Submit feedback

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Cancel

Create saved search

Sign in

Sign up

You signed in with another tab or window. Reload to refresh your session.

You signed out in another tab or window. Reload to refresh your session.

You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

bitmaintech

/

cgminer

Public

forked from ckolivas/cgminer

Notifications

Fork

48

Star

87

ASIC / FPGA / GPU miner in c for bitcoin and litecoin

ck.kolivas.org/apps/cgminer

License

Unknown, GPL-3.0 licenses found

Licenses found

Unknown

LICENSE

GPL-3.0

COPYING

87

stars

2.3k

forks

Branches

Tags

Activity

Star

Notifications

Code

Pull requests

2

Actions

Projects

0

Security

Insights

Additional navigation options

Code

Pull requests

Actions

Projects

Security

Insights

bitmaintech/cgminer

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

 masterBranchesTagsGo to fileCode  Folders and filesNameNameLast commit messageLast commit dateLatest commit History4,997 Commitsbitstreamsbitstreams  ccanccan  compatcompat  liblib  m4m4  .gitignore.gitignore  01-cgminer.rules01-cgminer.rules  A1-board-selector-CCD.cA1-board-selector-CCD.c  A1-board-selector-CCR.cA1-board-selector-CCR.c  A1-board-selector.hA1-board-selector.h  A1-common.hA1-common.h  A1-desk-board-selector.cA1-desk-board-selector.c  A1-trimpot-mcp4x.cA1-trimpot-mcp4x.c  A1-trimpot-mcp4x.hA1-trimpot-mcp4x.h  API-READMEAPI-README  API.classAPI.class  API.javaAPI.java  ASIC-READMEASIC-README  AUTHORSAUTHORS  COPYINGCOPYING  ChangeLogChangeLog  FPGA-READMEFPGA-README  LICENSELICENSE  MCast.classMCast.class  MCast.javaMCast.java  Makefile.amMakefile.am  NEWSNEWS  READMEREADME  api-example.capi-example.c  api-example.phpapi-example.php  api-example.pyapi-example.py  api-example.rbapi-example.rb  api.capi.c  arg-nonnull.harg-nonnull.h  autogen.shautogen.sh  bench_block.hbench_block.h  bitforce-firmware-flash.cbitforce-firmware-flash.c  bitmain-readme.txtbitmain-readme.txt  c++defs.hc++defs.h  cgminer.ccgminer.c  compat.hcompat.h  configure.acconfigure.ac  crc.hcrc.h  crc16.ccrc16.c  driver-SPI-bitmine-A1.cdriver-SPI-bitmine-A1.c  driver-avalon.cdriver-avalon.c  driver-avalon.hdriver-avalon.h  driver-avalon2.cdriver-avalon2.c  driver-avalon2.hdriver-avalon2.h  driver-avalon4.cdriver-avalon4.c  driver-avalon4.hdriver-avalon4.h  driver-bab.cdriver-bab.c  driver-bflsc.cdriver-bflsc.c  driver-bflsc.hdriver-bflsc.h  driver-bitforce.cdriver-bitforce.c  driver-bitfury.cdriver-bitfury.c  driver-bitfury.hdriver-bitfury.h  driver-bitmain.cdriver-bitmain.c  driver-bitmain.hdriver-bitmain.h  driver-blockerupter.cdriver-blockerupter.c  driver-blockerupter.hdriver-blockerupter.h  driver-bmsc.cdriver-bmsc.c  driver-cointerra.cdriver-cointerra.c  driver-cointerra.hdriver-cointerra.h  driver-drillbit.cdriver-drillbit.c  driver-drillbit.hdriver-drillbit.h  driver-hashfast.cdriver-hashfast.c  driver-hashfast.hdriver-hashfast.h  driver-hashratio.cdriver-hashratio.c  driver-hashratio.hdriver-hashratio.h  driver-icarus.cdriver-icarus.c  driver-klondike.cdriver-klondike.c  driver-knc.cdriver-knc.c  driver-minion.cdriver-minion.c  driver-modminer.cdriver-modminer.c  driver-spondoolies-sp10-p.cdriver-spondoolies-sp10-p.c  driver-spondoolies-sp10-p.hdriver-spondoolies-sp10-p.h  driver-spondoolies-sp10.cdriver-spondoolies-sp10.c  driver-spondoolies-sp10.hdriver-spondoolies-sp10.h  driver-spondoolies-sp30-p.cdriver-spondoolies-sp30-p.c  driver-spondoolies-sp30-p.hdriver-spondoolies-sp30-p.h  driver-spondoolies-sp30.cdriver-spondoolies-sp30.c  driver-spondoolies-sp30.hdriver-spondoolies-sp30.h  elist.helist.h  example.confexample.conf  fpgautils.cfpgautils.c  fpgautils.hfpgautils.h  hexdump.chexdump.c  hf_protocol.hhf_protocol.h  hf_protocol_be.hhf_protocol_be.h  i2c-context.ci2c-context.c  i2c-context.hi2c-context.h  klist.cklist.c  klist.hklist.h  knc-asic.cknc-asic.c  knc-asic.hknc-asic.h  knc-transport-spi.cknc-transport-spi.c  knc-transport.hknc-transport.h  libbitfury.clibbitfury.c  libbitfury.hlibbitfury.h  View all filesRepository files navigationREADMELicenseGPL-3.0 licenseThis is a multi-threaded multi-pool FPGA and ASIC miner for bitcoin.

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

15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ

NOTE: This code is licensed under the GPLv3. This means that the source to any

modifications you make to this code MUST be provided by law if you distribute

modified binaries. See COPYING for details.

DOWNLOADS:

http://ck.kolivas.org/apps/cgminer

GIT TREE:

https://github.com/ckolivas/cgminer

Support thread:

http://bitcointalk.org/index.php?topic=28402.0

IRC Channel:

irc://irc.freenode.net/cgminer

SEE ALSO API-README, ASIC-README and FGPA-README FOR MORE INFORMATION ON EACH.

---

EXECUTIVE SUMMARY ON USAGE:

Single pool:

cgminer -o http://pool:port -u username -p password

Multiple pools:

cgminer -o http://pool1:port -u pool1username -p pool1password -o http://pool2:port -u pool2usernmae -p pool2password

Single pool with a standard http proxy:

cgminer -o "http:proxy:port|http://pool:port" -u username -p password

Single pool with a socks5 proxy:

cgminer -o "socks5:proxy:port|http://pool:port" -u username -p password

Single pool with stratum protocol support:

cgminer -o stratum+tcp://pool:port -u username -p password

Solo mining to local bitcoind:

cgminer -o http://localhost:8332 -u username -p password --btc-address 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ

The list of proxy types are:

http: standard http 1.1 proxy

http0: http 1.0 proxy

socks4: socks4 proxy

socks5: socks5 proxy

socks4a: socks4a proxy

socks5h: socks5 proxy using a hostname

If you compile cgminer with a version of CURL before 7.19.4 then some of the above will

not be available. All are available since CURL version 7.19.4

If you specify the --socks-proxy option to cgminer, it will only be applied to all pools

that don't specify their own proxy setting like above

After saving configuration from the menu, you do not need to give cgminer any

arguments and it will load your configuration.

Any configuration file may also contain a single

"include" : "filename"

to recursively include another configuration file.

Writing the configuration will save all settings from all files in the output.

---

BUILDING CGMINER FOR YOURSELF

DEPENDENCIES:

Mandatory:

pkg-config http://www.freedesktop.org/wiki/Software/pkg-config

libtool http://www.gnu.org/software/libtool/

Optional:

curl dev library http://curl.haxx.se/libcurl/

(libcurl4-openssl-dev - Must tell configure --disable-libcurl otherwise

it will attempt to compile it in)

curses dev library

(libncurses5-dev or libpdcurses on WIN32 for text user interface)

libudev dev library (libudev-dev)

(This is only required for USB device support and is linux only)

If building from git:

autoconf

automake

If building on Red Hat:

sudo yum install autoconf automake autoreconf libtool openssl-compat-bitcoin-devel.x86_64 \

curl libcurl libcurl-devel openssh

If building on Ubuntu:

sudo apt-get install build-essential autoconf automake libtool pkg-config \

libcurl3-dev libudev-dev

CGMiner specific configuration options:

--enable-bmsc Compile support for BitMain Single Chain(default disabled)

--enable-bitmain Compile support for BitMain Multi Chain(default disabled)

--enable-avalon Compile support for Avalon (default disabled)

--enable-avalon2 Compile support for Avalon2 (default disabled)

--enable-avalon4 Compile support for Avalon4 (default disabled)

--enable-bab Compile support for BlackArrow Bitfury (default

disabled)

--enable-bflsc Compile support for BFL ASICs (default disabled)

--enable-bitforce Compile support for BitForce FPGAs (default

disabled)

--enable-bitfury Compile support for BitFury ASICs (default disabled)

--enable-bitmine_A1 Compile support for Bitmine.ch A1 ASICs (default

disabled)

--enable-blockerupter Compile support for ASICMINER BlockErupter Tube/Prisma

(default disabled)

--enable-cointerra Compile support for Cointerra ASICs (default disabled)

--enable-drillbit Compile support for Drillbit BitFury ASICs (default

disabled)

--enable-hashfast Compile support for Hashfast (default disabled)

--enable-icarus Compile support for Icarus (default disabled)

--enable-klondike Compile support for Klondike (default disabled)

--enable-knc Compile support for KnC miners (default disabled)

--enable-minion Compile support for Minion BlackArrow ASIC (default

disabled)

--enable-modminer Compile support for ModMiner FPGAs(default disabled)

--enable-sp10 Compile support for Spondoolies SP10 (default

disabled)

--enable-sp30 Compile support for Spondoolies SP30 (default

disabled)

--disable-libcurl Disable building with libcurl for getwork and GBT

support

--without-curses Compile support for curses TUI (default enabled)

--with-system-libusb Compile against dynamic system libusb (default use

included static libusb)

Basic *nix build instructions:

To actually build:

./autogen.sh # only needed if building from git repo

CFLAGS="-O2 -Wall -march=native" ./configure

make

No installation is necessary. You may run cgminer from the build

directory directly, but you may do make install if you wish to install

cgminer to a system location or location you specified.

Building for windows:

It is actually easiest to build a windows binary using cross compilation tools

provided by "mxe" available at http://mxe.cc/ (use the 32 bit one!)

Once you have followed the instructions for building mxe:

export PATH=(path/to/mxe)/usr/bin/:$PATH

CFLAGS="-O2 -Wall -W -march=i686" ./configure --host=i686-pc-mingw32

make

Native WIN32 build instructions: see windows-build.txt but these instructions

are now hopelessly out of date.

---

Usage instructions: Run "cgminer --help" to see options:

Usage: cgminer [-DdElmpPQqUsTouOchnV]

Options for both config file and command line:

--anu-freq Set AntminerU1/2 frequency in MHz, range 125-500 (default: 250.0)

--api-allow Allow API access only to the given list of [G:]IP[/Prefix] addresses[/subnets]

--api-description Description placed in the API status header, default: cgminer version

--api-groups API one letter groups G:cmd:cmd[,P:cmd:*...] defining the cmds a groups can use

--api-listen Enable API, default: disabled

--api-mcast Enable API Multicast listener, default: disabled

--api-mcast-addr API Multicast listen address

--api-mcast-code Code expected in the API Multicast message, don't use '-'

--api-mcast-des Description appended to the API Multicast reply, default: ''

--api-mcast-port API Multicast listen port (default: 4028)

--api-network Allow API (if enabled) to listen on/for any address, default: only 127.0.0.1

--api-port Port number of miner API (default: 4028)

--au3-freq Set AntminerU3 frequency in MHz, range 100-250 (default: 225.0)

--au3-volt Set AntminerU3 voltage in mv, range 725-850, 0 to not set (default: 750)

--avalon-auto Adjust avalon overclock frequency dynamically for best hashrate

--avalon-cutoff Set avalon overheat cut off temperature (default: 60)

--avalon-fan Set fanspeed percentage for avalon, single value or range (default: 20-100)

--avalon-freq Set frequency range for avalon-auto, single value or range

--avalon-options Set avalon options baud:miners:asic:timeout:freq:tech

--avalon-temp Set avalon target temperature (default: 50)

--avalon2-freq Set frequency range for Avalon2, single value or range

--avalon2-voltage Set Avalon2 core voltage, in millivolts

--avalon2-fan Set Avalon2 target fan speed

--avalon2-cutoff Set Avalon2 overheat cut off temperature (default: 88)

--avalon2-fixed-speed Set Avalon2 fan to fixed speed

--avalon4-automatic-voltage Automatic adjust voltage base on module DH

--avalon4-voltage Set Avalon4 core voltage, in millivolts, step: 125

--avalon4-freq Set frequency for Avalon4, 1 to 3 values, example: 445:385:370

--avalon4-fan Set Avalon4 target fan speed range

--avalon4-temp Set Avalon4 target temperature (default: 42)

--avalon4-cutoff Set Avalon4 overheat cut off temperature (default: 65)

--avalon4-polling-delay Set Avalon4 polling delay value (ms) (default: 20)

--avalon4-ntime-offset Set Avalon4 MM ntime rolling max offset (default: 4)

--avalon4-aucspeed Set Avalon4 AUC IIC bus speed (default: 400000)

--avalon4-aucxdelay Set Avalon4 AUC IIC xfer read delay, 4800 ~= 1ms (default: 9600)

--bab-options Set BaB options max:def:min:up:down:hz:delay:trf

--balance Change multipool strategy from failover to even share balance

--benchfile Run cgminer in benchmark mode using a work file - produces no shares

--benchfile-display Display each benchfile nonce found

--benchmark Run cgminer in benchmark mode - produces no shares

--bet-clk Set clockspeed of ASICMINER Tube/Prisma to (arg+1)*10MHz (default: 23)

--bfl-range Use nonce range on bitforce devices if supported

--bflsc-overheat Set overheat temperature where BFLSC devices throttle, 0 to disable (default: 85)

--bitburner-fury-voltage Set BitBurner Fury core voltage, in millivolts

--bitburner-fury-options Override avalon-options for BitBurner Fury boards baud:miners:asic:timeout:freq

--bitburner-voltage Set BitBurner (Avalon) core voltage, in millivolts

--bitmain-auto Adjust bitmain overclock frequency dynamically for best hashrate

--bitmain-cutoff Set bitmain overheat cut off temperature

--bitmain-fan Set fanspeed percentage for bitmain, single value or range (default: 20-100)

--bitmain-freq Set frequency range for bitmain-auto, single value or range

--bitmain-hwerror Set bitmain device detect hardware error

--bitmain-options Set bitmain options baud:miners:asic:timeout:freq

--bitmain-temp Set bitmain target temperature

--bxf-bits Set max BXF/HXF bits for overclocking (default: 54)

--bxf-temp-target Set target temperature for BXF/HXF devices (default: 82)

--bxm-bits Set BXM bits for overclocking (default: 54)

--btc-address Set bitcoin target address when solo mining to bitcoind

--btc-sig Set signature to add to coinbase when solo mining (optional)

--compact Use compact display without per device statistics

--debug|-D Enable debug output

--disable-rejecting Automatically disable pools that continually reject shares

--drillbit-options Set drillbit options :clock[:clock_divider][:voltage]

--expiry|-E Upper bound on how many seconds after getting work we consider a share from it stale (default: 120)

--failover-only Don't leak work to backup pools when primary pool is lagging

--fix-protocol Do not redirect to a different getwork protocol (eg. stratum)

--hfa-hash-clock Set hashfast clock speed (default: 550)

--hfa-fail-drop Set how many MHz to drop clockspeed each failure on an overlocked hashfast device (default: 10)

--hfa-fan Set fanspeed percentage for hashfast, single value or range (default: 10-85)

--hfa-name Set a unique name for a single hashfast device specified with --usb or the first device found

--hfa-noshed Disable hashfast dynamic core disabling feature

--hfa-options Set hashfast options name:clock (comma separated)

--hfa-temp-overheat Set the hashfast overheat throttling temperature (default: 95)

--hfa-temp-target Set the hashfast target temperature (0 to disable) (default: 88)

--hro-freq Set the hashratio clock frequency (default: 280)

--hotplug Seconds between hotplug checks (0 means never check)

--klondike-options Set klondike options clock:temptarget

--load-balance Change multipool strategy from failover to quota based balance

--log|-l Interval in seconds between log output (default: 5)

--lowmem Minimise caching of shares for low memory applications

--minion-chipreport Seconds to report chip 5min hashrate, range 0-100 (default: 0=disabled)

--minion-freq Set minion chip frequencies in MHz, single value or comma list, range 100-1400 (default: 1200)

--minion-freqchange Millisecond total time to do frequency changes (default: 1000)

--minion-freqpercent Percentage to use when starting up a chip (default: 70%)

--minion-idlecount Report when IdleCount is >0 or changes

--minion-ledcount Turn off led when more than this many chips below the ledlimit (default: 0)

--minion-ledlimit Turn off led when chips GHs are below this (default: 90)

--minion-noautofreq Disable automatic frequency adjustment

--minion-overheat Enable directly halting any chip when the status exceeds 100C

--minion-spidelay Add a delay in microseconds after each SPI I/O

--minion-spireset SPI regular reset: iNNN for I/O count or sNNN for seconds - 0 means none

--minion-spisleep Sleep time in milliseconds when doing an SPI reset

--minion-temp Set minion chip temperature threshold, single value or comma list, range 120-160 (default: 135C)

--monitor|-m Use custom pipe cmd for output messages

--nfu-bits Set nanofury bits for overclocking, range 32-63 (default: 50)

--net-delay Impose small delays in networking to not overload slow routers

--no-submit-stale Don't submit shares if they are detected as stale

--osm-led-mode Set LED mode for OneStringMiner devices (default: 4)

--pass|-p Password for bitcoin JSON-RPC server

--per-device-stats Force verbose mode and output per-device statistics

--protocol-dump|-P Verbose dump of protocol-level activities

--queue|-Q Minimum number of work items to have queued (0+) (default: 1)

--quiet|-q Disable logging output, display status and errors

--quota|-U quota;URL combination for server with load-balance strategy quotas

--real-quiet Disable all output

--rock-freq Set RockMiner frequency in MHz, range 200-400 (default: 270)

--rotate Change multipool strategy from failover to regularly rotate at N minutes (default: 0)

--round-robin Change multipool strategy from failover to round robin on failure

--scan-time|-s Upper bound on time spent scanning current work, in seconds (default: -1)

--sched-start Set a time of day in HH:MM to start mining (a once off without a stop time)

--sched-stop Set a time of day in HH:MM to stop mining (will quit without a start time)

--sharelog Append share log to file

--shares Quit after mining N shares (default: unlimited)

--socks-proxy Set socks4 proxy (host:port)

--suggest-diff Suggest miner difficulty for pool to user (default: none)

--syslog Use system log for output messages (default: standard error)

--temp-cutoff Temperature where a device will be automatically disabled, one value or comma separated list (default: 95)

--text-only|-T Disable ncurses formatted screen output

--url|-o URL for bitcoin JSON-RPC server

--usb USB device selection

--user|-u Username for bitcoin JSON-RPC server

--userpass|-O Username:Password pair for bitcoin JSON-RPC server

--verbose Log verbose output to stderr as well as status output

--widescreen Use extra wide display without toggling

--worktime Display extra work time debug information

Options for command line only:

--config|-c Load a JSON-format configuration file

See example.conf for an example configuration.

--default-config Specify the filename of the default config file

Loaded at start and used when saving without a name.

--help|-h Print this message

--ndevs|-n Display all USB devices and exit

--version|-V Display version and exit

Silent USB device (ASIC and FPGA) options:

--icarus-options Set specific FPGA board configurations - one set of values for all or comma separated

--icarus-timing Set how the Icarus timing is calculated - one setting/value for all or comma separated

--usb-dump (See FPGA-README)

See FGPA-README or ASIC-README for more information regarding these.

ASIC only options:

--anu-freq Set AntminerU1/2 frequency in MHz, range 125-500 (default: 250.0)

--au3-freq Set AntminerU3 frequency in MHz, range 100-250 (default: 225.0)

--au3-volt Set AntminerU3 voltage in mv, range 725-850, 0 to not set (default: 750)

--avalon-auto Adjust avalon overclock frequency dynamically for best hashrate

--avalon-cutoff Set avalon overheat cut off temperature (default: 60)

--avalon-fan Set fanspeed percentage for avalon, single value or range (default: 20-100)

--avalon-freq Set frequency range for avalon-auto, single value or range

--avalon-options Set avalon options baud:miners:asic:timeout:freq:tech

--avalon-temp Set avalon target temperature (default: 50)

--avalon2-freq Set frequency range for Avalon2, single value or range

--avalon2-voltage Set Avalon2 core voltage, in millivolts

--avalon2-fan Set Avalon2 target fan speed

--avalon2-cutoff Set Avalon2 overheat cut off temperature (default: 88)

--avalon2-fixed-speed Set Avalon2 fan to fixed speed

--avalon4-automatic-voltage Automatic adjust voltage base on module DH

--avalon4-voltage Set Avalon4 core voltage, in millivolts, step: 125

--avalon4-freq Set frequency for Avalon4, 1 to 3 values, example: 445:385:370

--avalon4-fan Set Avalon4 target fan speed range

--avalon4-temp Set Avalon4 target temperature (default: 42)

--avalon4-cutoff Set Avalon4 overheat cut off temperature (default: 65)

--avalon4-polling-delay Set Avalon4 polling delay value (ms) (default: 20)

--avalon4-ntime-offset Set Avalon4 MM ntime rolling max offset (default: 4)

--avalon4-aucspeed Set Avalon4 AUC IIC bus speed (default: 400000)

--avalon4-aucxdelay Set Avalon4 AUC IIC xfer read delay, 4800 ~= 1ms (default: 9600)

--bab-options Set BaB options max:def:min:up:down:hz:delay:trf

--bflsc-overheat Set overheat temperature where BFLSC devices throttle, 0 to disable (default: 90)

--bitburner-fury-options Override avalon-options for BitBurner Fury boards baud:miners:asic:timeout:freq

--bitburner-fury-voltage Set BitBurner Fury core voltage, in millivolts

--bitburner-voltage Set BitBurner (Avalon) core voltage, in millivolts

--bitmine-a1-options :::

--bxf-temp-target Set target temperature for BXF devices (default: 82)

--bxm-bits Set BXM bits for overclocking (default: 50)

--hfa-hash-clock Set hashfast clock speed (default: 550)

--hfa-fail-drop Set how many MHz to drop clockspeed each failure on an overlocked hashfast device (default: 10)

--hfa-fan Set fanspeed percentage for hashfast, single value or range (default: 10-85)

--hfa-name Set a unique name for a single hashfast device specified with --usb or the first device found

--hfa-noshed Disable hashfast dynamic core disabling feature

--hfa-temp-overheat Set the hashfast overheat throttling temperature (default: 95)

--hfa-temp-target Set the hashfast target temperature (0 to disable) (default: 88)

--hro-freq Set the hashratio clock frequency (default: 280)

--klondike-options Set klondike options clock:temptarget

--rock-freq Set RockMiner frequency in MHz, range 125-500 (default: 270)

See ASIC-README for more information regarding these.

FPGA only options:

--bfl-range Use nonce range on bitforce devices if supported

See FGPA-README for more information regarding this.

Cgminer should automatically find all of your Avalon ASIC, BFL ASIC, BitForce

FPGAs, Icarus bitstream FPGAs, Klondike ASIC, ASICMINER usb block erupters,

KnC ASICs, BaB ASICs, Hashfast ASICs, ModMiner FPGAs, BPMC/BGMC BF1 USB ASICs,

Bi*fury USB ASICs, Onestring miner USB ASICs, Hexfury USB ASICs, Nanofury USB

ASICs, Antminer U1/U2/U2+ U3 USB ASICs, Cointerra devices, BFx2 USB ASICs,

Rockminer R-Box/RK-Box/T1 USB ASICs, Avalon2/3/4 USB ASICs and Hashratio USB

ASICs.

---

SETTING UP USB DEVICES

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:

The short version:

sudo cp 01-cgminer.rules /etc/udev/rules.d/

The long version:

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 USB 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

---

Advanced USB options:

The --usb option can restrict how many USB devices are found:

--usb 1:2,1:3,1:4,1:*

or

--usb BAS:1,BFL:1,MMQ:0,ICA:0,KLN:0

or

--usb :10

You can only use one of the above 3

The first version

--usb 1:2,1:3,1:4,1:*

allows you to select which devices to mine on with a list of USB

bus_number:device_address

All other USB devices will be ignored

Hotplug will also only look at the devices matching the list specified and

find nothing new if they are all in use

You can specify just the USB bus_number to find all devices like 1:*

which means any devices on USB bus_number 1

This is useful if you unplug a device then plug it back in the same port,

it usually reappears with the same bus_number but a different device_address

You can see the list of all USB devices on linux with 'sudo lsusb'

Cgminer will list the recognised USB devices

with the '-n' option or the

'--usb-dump 0' option

The '--usb-dump N' option with a value of N greater than 0 will dump a lot

of details about each recognised USB device

If you wish to see all USB devices, include the --usb-list-all option

The second version

--usb BAS:1,BFL:1,MMQ:0,ICA:0,KLN:0

allows you to specify how many devices to choose based on each device

driver cgminer has - the current USB drivers are:

AVA, BAS, BFL, BF1, DRB, HFA, ICA, KLN and MMQ.

N.B. you can only specify which device driver to limit, not the type of

each device, e.g. with BAS:n you can limit how many BFL ASIC devices will

be checked, but you cannot limit the number of each type of BFL ASIC

Also note that the MMQ count is the number of MMQ backplanes you have

not the number of MMQ FPGAs

The third version

--usb :10

means only use a maximum of 10 devices of any supported USB devices

Once cgminer has 10 devices it will not configure any more and hotplug will

not scan for any more

If one of the 10 devices stops working, hotplug - if enabled, as is default

- will scan normally again until it has 10 devices

--usb :0 will disable all USB I/O other than to initialise libusb

---

WHILE RUNNING:

The following options are available while running with a single keypress:

[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit

U gives you:

[S]ummary of device information

[E]nable device

[D]isable device

[U]nplug to allow hotplug restart

[R]eset device USB

[L]ist all known devices

[B]lacklist current device from current instance of cgminer

[W]hitelist previously blacklisted device

[H]otplug interval (0 to disable)

P gives you:

Current pool management strategy: Failover

[F]ailover only disabled

[A]dd pool [R]emove pool [D]isable pool [E]nable pool

[C]hange management strategy [S]witch pool [I]nformation

S gives you:

[Q]ueue: 1

[S]cantime: 60

[E]xpiry: 120

[W]rite config file

[C]gminer restart

D gives you:

[N]ormal [C]lear [S]ilent mode (disable all output)

[D]ebug:off

[P]er-device:off

[Q]uiet:off

[V]erbose:off

[R]PC debug:off

[W]orkTime details:off

co[M]pact: off

[T]oggle status switching:enabled

[Z]ero statistics

[L]og interval:5

Q quits the application.

The running log shows output like this:

[2013-11-09 11:04:41] Accepted 01b3bde7 Diff 150/128 AVA 1 pool 0

[2013-11-09 11:04:49] Accepted 015df995 Diff 187/128 AVA 1 pool 0

[2013-11-09 11:04:50] Accepted 01163b68 Diff 236/128 AVA 1 pool 0

[2013-11-09 11:04:53] Accepted 9f745840 Diff 411/128 BAS 1 pool 0

The 8 byte hex value are the 1st nonzero bytes of the share being submitted to

the pool. The 2 diff values are the actual difficulty target that share reached

followed by the difficulty target the pool is currently asking for.

---

Also many issues and FAQs are covered in the forum thread

dedicated to this program,

http://forum.bitcoin.org/index.php?topic=28402.0

DISPLAY:

The display is roughly split into two portions, the top status window and the

bottom scrolling log window.

STATUS WINDOW

The status window is split into overall status and per device status.

Overall status:

The output line shows the following:

(5s):2.469T (1m):2.677T (5m):2.040T (15m):1.014T (avg):2.733Th/s

These are exponentially decaying average hashrates over 5s/1m/5m/15m and an

average since the start.

Followed by:

A:290391 R:5101 HW:145 WU:37610.4/m

Each column is as follows:

A: The total difficulty of Accepted shares

R: The total difficulty of Rejected shares

HW: The number of HardWare errors

WU: The Work Utility defined as the number of diff1 shares work / minute

(accepted or rejected).

alternating with:

ST: 22 SS: 0 NB: 2 LW: 356090 GF: 0 RF: 0

ST is STaged work items (ready to use).

SS is Stale Shares discarded (detected and not submitted so don't count as rejects)

NB is New Blocks detected on the network

LW is Locally generated Work items

GF is Getwork Fail Occasions (server slow to provide work)

RF is Remote Fail occasions (server slow to accept work)

Followed by:

Connected to pool.com diff 3.45K with stratum as user me

The diff shown is the current vardiff requested by the pool currently being

mined at.

Followed by:

Block: ca0d237f... Diff:5.01G Started: [00:14:27] Best share: 1.18M

This shows a short stretch about the current block, when the new block started,

and the all time best difficulty share you've found since starting cgminer

this time.

Per device status:

6: HFS Random : 645MHz 85C 13% 0.79V | 2.152T / 1.351Th/s

Each column is as follows:

Temperature (if supported)

Fanspeed (if supported)

Voltage (if supported)

A 5 second exponentially decaying average hash rate

An all time average hash rate

alternating with

6: HFS Random : 645MHz 86C 13% 0.80V | A:290348 R:1067 HW:88 WU:18901.8/m

The total difficulty of accepted shares

The total difficulty of rejected shares

The number of hardware erorrs

The work utility defined as the number of diff1 shares work / minute

LOG WINDOW

All running information is shown here, usually share submission results and

block update notifications, along with device messages and warnings.

[2014-03-29 00:24:09] Accepted 1397768d Diff 3.35K/2727 HFS 0 pool 0

[2014-03-29 00:24:13] Stratum from pool 0 detected new block

---

MULTIPOOL

FAILOVER STRATEGIES WITH MULTIPOOL:

A number of different strategies for dealing with multipool setups are

available. Each has their advantages and disadvantages so multiple strategies

are available by user choice, as per the following list:

FAILOVER:

The default strategy is failover. This means that if you input a number of

pools, it will try to use them as a priority list, moving away from the 1st

to the 2nd, 2nd to 3rd and so on. If any of the earlier pools recover, it will

move back to the higher priority ones.

ROUND ROBIN:

This strategy only moves from one pool to the next when the current one falls

idle and makes no attempt to move otherwise.

ROTATE:

This strategy moves at user-defined intervals from one active pool to the next,

skipping pools that are idle.

LOAD BALANCE:

This strategy sends work to all the pools on a quota basis. By default, all

pools are allocated equal quotas unless specified with --quota. This

apportioning of work is based on work handed out, not shares returned so is

independent of difficulty targets or rejected shares. While a pool is disabled

or dead, its quota is dropped until it is re-enabled. Quotas are forward

looking, so if the quota is changed on the fly, it only affects future work.

If all pools are set to zero quota or all pools with quota are dead, it will

fall back to a failover mode. See quota below for more information.

The failover-only flag has special meaning in combination with load-balance

mode and it will distribute quota back to priority pool 0 from any pools that

are unable to provide work for any reason so as to maintain quota ratios

between the rest of the pools.

BALANCE:

This strategy monitors the amount of difficulty 1 shares solved for each pool

and uses it to try to end up doing the same amount of work for all pools.

---

QUOTAS

The load-balance multipool strategy works off a quota based scheduler. The

quotas handed out by default are equal, but the user is allowed to specify any

arbitrary ratio of quotas. For example, if all the quota values add up to 100,

each quota value will be a percentage, but if 2 pools are specified and pool0

is given a quota of 1 and pool1 is given a quota of 9, pool0 will get 10% of

the work and pool1 will get 90%. Quotas can be changed on the fly by the API,

and do not act retrospectively. Setting a quota to zero will effectively

disable that pool unless all other pools are disabled or dead. In that

scenario, load-balance falls back to regular failover priority-based strategy.

While a pool is dead, it loses its quota and no attempt is made to catch up

when it comes back to life.

To specify quotas on the command line, pools should be specified with a

semicolon separated --quota(or -U) entry instead of --url. Pools specified with

--url are given a nominal quota value of 1 and entries can be mixed.

For example:

--url poola:porta -u usernamea -p passa --quota "2;poolb:portb" -u usernameb -p passb

Will give poola 1/3 of the work and poolb 2/3 of the work.

Writing configuration files with quotas is likewise supported. To use the above

quotas in a configuration file they would be specified thus:

"pools" : [

{

"url" : "poola:porta",

"user" : "usernamea",

"pass" : "passa"

},

{

"quota" : "2;poolb:portb",

"user" : "usernameb",

"pass" : "passb"

}

]

---

SOLO MINING

Solo mining can be done efficiently as a single pool entry or a backup to

any other pooled mining and it is recommended everyone have solo mining set up

as their final backup in case all their other pools are DDoSed/down for the

security of the network. To enable solo mining, one must be running a local

bitcoind/bitcoin-qt or have one they have rpc access to. To do this, edit your

bitcoind configuration file (bitcoin.conf) with the following extra lines,

using your choice of username and password:

rpcuser=username

rpcpassword=password

Restart bitcoind, then start cgminer, pointing to the bitcoind and choose a

btc address with the following options, altering to suit their setup:

cgminer -o http://localhost:8332 -u username -p password --btc-address 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ

Note the http:// is mandatory for solo mining.

---

LOGGING

cgminer will log to stderr if it detects stderr is being redirected to a file.

To enable logging simply add 2>logfile.txt to your command line and logfile.txt

will contain the logged output at the log level you specify (normal, verbose,

debug etc.)

In other words if you would normally use:

./cgminer -o xxx -u yyy -p zzz

if you use

./cgminer -o xxx -u yyy -p zzz 2>logfile.txt

it will log to a file called logfile.txt and otherwise work the same.

There is also the -m option on linux which will spawn a command of your choice

and pipe the output directly to that command.

The WorkTime details 'debug' option adds details on the end of each line

displayed for Accepted or Rejected work done. An example would be:

<-00000059.ed4834a3 M:X D:1.0 G:17:02:38:0.405 C:1.855 (2.995) W:3.440 (0.000) S:0.461 R:17:02:47

The first 2 hex codes are the previous block hash, the rest are reported in

seconds unless stated otherwise:

The previous hash is followed by the getwork mode used M:X where X is one of

P:Pool, T:Test Pool, L:LP or B:Benchmark,

then D:d.ddd is the difficulty required to get a share from the work,

then G:hh:mm:ss:n.nnn, which is when the getwork or LP was sent to the pool and

the n.nnn is how long it took to reply,

followed by 'O' on it's own if it is an original getwork, or 'C:n.nnn' if it was

a clone with n.nnn stating how long after the work was recieved that it was cloned,

(m.mmm) is how long from when the original work was received until work started,

W:n.nnn is how long the work took to process until it was ready to submit,

(m.mmm) is how long from ready to submit to actually doing the submit, this is

usually 0.000 unless there was a problem with submitting the work,

S:n.nnn is how long it took to submit the completed work and await the reply,

R:hh:mm:ss is the actual time the work submit reply was received

If you start cgminer with the --sharelog option, you can get detailed

information for each share found. The argument to the option may be "-" for

standard output (not advisable with the ncurses UI), any valid positive number

for that file descriptor, or a filename.

To log share data to a file named "share.log", you can use either:

./cgminer --sharelog 50 -o xxx -u yyy -p zzz 50>share.log

./cgminer --sharelog share.log -o xxx -u yyy -p zzz

For every share found, data will be logged in a CSV (Comma Separated Value)

format:

timestamp,disposition,target,pool,dev,thr,sharehash,sharedata

For example (this is wrapped, but it's all on one line for real):

1335313090,reject,

ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000,

http://localhost:8337,ASC0,0,

6f983c918f3299b58febf95ec4d0c7094ed634bc13754553ec34fc3800000000,

00000001a0980aff4ce4a96d53f4b89a2d5f0e765c978640fe24372a000001c5

000000004a4366808f81d44f26df3d69d7dc4b3473385930462d9ab707b50498

f681634a4f1f63d01a0cd43fb338000000000080000000000000000000000000

0000000000000000000000000000000000000000000000000000000080020000

---

BENCHMARK

The --benchmark option hashes a single fixed work item over and over and does

not submit shares to any pools.

The --benchfile option hashes the work given in the file supplied.

The format of the work file is:

version,merkleroot,prevhash,diffbits,noncetime

Any empty line or any line starting with '#' or '/' is ignored.

When it reaches the end of the file it continues back at the top.

The format of the data items matches the byte ordering and format of the

the bitcoind getblock RPC output.

An example file containing bitcoin block #1 would be:

# Block 1

1,0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd512098,00000000001

9d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f,1d00ffff,1231469665

However, the work data should be one line without the linebreak in the middle

If you use --benchfile , then --benchfile-display will output a log line,

for each nonce found, showing the nonce value in decimal and hex and the work

used to find it in hex.

---

RPC API

For RPC API details see the API-README file

---

FAQ

Q: Help, I've started cgminer and everything reads zero!?

A: Welcome to bitcoin mining. Your computer by itself cannot mine bitcoin no

matter how powerful it is. You have to purchase dedicated mining hardware

called ASICs to plug into your computer. See Q regarding ASICs below.

Q: I have multiple USB stick devices but I can't get them all to work at once?

A: Very few USB hubs deliver the promised power required to run as many devices

as they fit if all of them draw power from USB.

Q: I've plugged my devices into my USB hub but nothing shows up?

A: RPis and Windows have incomplete or non-standard USB3 support so they may

never work. It may be possible to get a USB3 hub to work by plugging it into

a USB2 hub. When choosing a hub, USB2 hubs are preferable whenever possible

due to better support all round.

Q: Can I mine on servers from different networks (eg xxxcoin and bitcoin) at

the same time?

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

config file and the file will be loaded one each startup.

Q: The build fails with gcc is unable to build a binary.

A: Remove the "-march=native" component of your CFLAGS as your version of gcc

does not support it. Also -O2 is capital o 2, not zero 2.

Q: Can you implement feature X?

A: I can, but time is limited, and people who donate are more likely to get

their feature requests implemented.

Q: Work keeps going to my backup pool even though my primary pool hasn't

failed?

A: Cgminer checks for conditions where the primary pool is lagging and will

pass some work to the backup servers under those conditions. The reason for

doing this is to try its absolute best to keep the devices working on something

useful and not risk idle periods. You can disable this behaviour with the

option --failover-only.

Q: Is this a virus?

A: Cgminer is being packaged with other trojan scripts and some antivirus

software is falsely accusing cgminer.exe as being the actual virus, rather

than whatever it is being packaged with. If you installed cgminer yourself,

then you do not have a virus on your computer. Complain to your antivirus

software company. They seem to be flagging even source code now from cgminer

as viruses, even though text source files can't do anything by themself.

Q: Can you modify the display to include more of one thing in the output and

less of another, or can you change the quiet mode or can you add yet another

output mode?

A: Everyone will always have their own view of what's important to monitor.

The defaults are very sane and I have very little interest in changing this

any further. There is far more detail in the API output than can be reasonably

displayed on the small console window, and using an external interface such

as miner.php is much more useful for setups with many devices.

Q: What are the best parameters to pass for X pool/hardware/device.

A: Virtually always, the DEFAULT parameters give the best results. Most user

defined settings lead to worse performance.

Q: What happened to CPU and GPU mining?

A: Their efficiency makes them irrelevant in the bitcoin mining world today

and the author has no interest in supporting alternative coins that are better

mined by these devices.

Q: GUI version?

A: No. The RPC interface makes it possible for someone else to write one

though.

Q: I'm having an issue. What debugging information should I provide?

A: Start cgminer with your regular commands and add -D -T --verbose and provide

the full startup output and a summary of your hardware and operating system.

Q: Why don't you provide win64 builds?

A: Win32 builds work everywhere and there is precisely zero advantage to a

64 bit build on windows.

Q: Is it faster to mine on windows or linux?

A: It makes no difference in terms of performance. It comes down to choice of

operating system for their various features and your comfort level. However

linux is the primary development platform and is virtually guaranteed to be

more stable.

Q: My network gets slower and slower and then dies for a minute?

A; Try the --net-delay option if you are on a getwork or GBT server. This does

nothing with stratum mining.

Q: How do I tune for p2pool?

A: It is also recommended to use --failover-only since the work is effectively

like a different block chain, and not enabling --no-submit-stale. If mining with

a BFL (fpga) minirig, it is worth adding the --bfl-range option.

Q: I run PHP on windows to access the API with the example miner.php. Why does

it fail when php is installed properly but I only get errors about Sockets not

working in the logs?

A: http://us.php.net/manual/en/sockets.installation.php

Q: What is a PGA?

A: Cgminer supports 3 FPGAs: BitForce, Icarus and ModMiner.

They are Field-Programmable Gate Arrays that have been programmed to do Bitcoin

mining. Since the acronym needs to be only 3 characters, the "Field-" part has

been skipped.

Q: What is an ASIC?

A: They are Application Specify Integrated Circuit devices and provide the

highest performance per unit power due to being dedicated to only one purpose.

They are the only meaningful way to mine bitcoin today.

Q: What is stratum and how do I use it?

A: Stratum is a protocol designed for pooled mining in such a way as to

minimise the amount of network communications, yet scale to hardware of any

speed. With versions of cgminer 2.8.0+, if a pool has stratum support, cgminer

will automatically detect it and switch to the support as advertised if it can.

If you input the stratum port directly into your configuration, or use the

special prefix "stratum+tcp://" instead of "http://", cgminer will ONLY try to

use stratum protocol mining. The advantages of stratum to the miner are no

delays in getting more work for the miner, less rejects across block changes,

and far less network communications for the same amount of mining hashrate. If

you do NOT wish cgminer to automatically switch to stratum protocol even if it

is detected, add the --fix-protocol option.

Q: Why don't the statistics add up: Accepted, Rejected, Stale, Hardware Errors,

Diff1 Work, etc. when mining greater than 1 difficulty shares?

A: As an example, if you look at 'Difficulty Accepted' in the RPC API, the number

of difficulty shares accepted does not usually exactly equal the amount of work

done to find them. If you are mining at 8 difficulty, then you would expect on

average to find one 8 difficulty share, per 8 single difficulty shares found.

However, the number is actually random and converges over time, it is an average,

not an exact value, thus you may find more or less than the expected average.

Q: My keyboard input momentarily pauses or repeats keys every so often on

windows while mining?

A: The USB implementation on windows can be very flaky on some hardware and

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: What should my Work Utility (WU) be?

A: Work utility is the product of hashrate * luck and only stabilises over a

very long period of time. Assuming all your work is valid work, bitcoin mining

should produce a work utility of approximately 1 per 71.6MH. This means at

5GH you should have a WU of 5000 / 71.6 or ~ 69. You cannot make your machine

do "better WU" than this - it is luck related. However you can make it much

worse if your machine produces a lot of hardware errors producing invalid work.

Q: What should I build in for a generic distribution binary?

A: There are a number of drivers that expect to be used on dedicated standalone

hardware. That said, the drivers that are designed to work generically with

USB on any hardware are the following:

--enable-avalon

--enable-avalon2

--enable-avalon4

--enable-bflsc

--enable-bitfury

--enable-blockerupter

--enable-cointerra

--enable-drillbit

--enable-hashfast

--enable-hashratio

--enable-icarus

--enable-klondike

---

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

15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ

About

ASIC / FPGA / GPU miner in c for bitcoin and litecoin

ck.kolivas.org/apps/cgminer

Resources

Readme

License

Unknown, GPL-3.0 licenses found

Licenses found

Unknown

LICENSE

GPL-3.0

COPYING

Activity

Custom properties

Stars

87

stars

Watchers

27

watching

Forks

48

forks

Report repository

Releases

139

tags

Packages

0

No packages published

Languages

C

93.6%

C++

3.5%

PHP

2.5%

Java

0.3%

Python

0.1%

Shell

0.0%

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms

Privacy

Security

Status

Docs

Contact

Manage cookies

Do not share my personal information

You can’t perform that action at this time.

下载 CGMiner 3.7.2 - ASIC、GPU 和 FPGA 矿工 [2022]

下载 CGMiner 3.7.2 - ASIC、GPU 和 FPGA 矿工 [2022]

CGMiner

快速入门

我的平衡

Toggle search

切换菜单

en

ru

es

zh

Contents

Toggle menu

Latest stable version

3.7.2

4.12

下载 CGMiner 3.7.2 - ASIC、GPU 和 FPGA 矿工 [2022]

少于 1 分钟读完

在本页上

Get started with CGMiner

Version: 3.7.2

File: *cgminer.exe,

SHA256: 417b22681a716e2481fde1fcaed96d66a5716a188186a4ae765d558d4a7ec2f5

(Download for Linux)

Download Now (Windows x64)

(mirror)

新的 CGMiner 旧版本已准备就绪。

你可以从这里下载 CGMiner 3.7.2:

Download Now

Download (mirror)

在存档中,您将找到包含安装说明的文件 README.txt。

确保将池和钱包地址替换为您在所有文件中使用的地址。

更新时间: 01.02.2022

Download now

Latest version is 3.7.2

File: *cgminer.exe,

SHA256: 417b22681a716e2481fde1fcaed96d66a5716a188186a4ae765d558d4a7ec2f5

Based on 3,400+ reviews

Download (windows)

Download (linux)

猜您还喜欢

CGMiner: 变更日志和发行说明

少于 1 分钟读完

发行说明是随软件产品分发的文档

CGMiner - 命令行参数和选项

少于 1 分钟读完

您必须优化您的 cgminer.conf 和 cgminer.bat 文件,以生成特定硬件装备支持的吞吐量和散列的最佳组合。

CGMiner Setup Guide [2023]

少于 1 分钟读完

You can use this list as a reference for all Launch Parameters supported by CGMiner.

分享

Twitter

Facebook

LinkedIn

向前

向后

CGMiner Community

irc

GitHub

Bitcointalk

Awesome Miner

Ethoprotocol

Hive OS

RaveOS

PiMP OS

Minerstat

SimpleMining OS

Note, when downloading the CGMiner, Windows may issue a warning, but if you used CGMiner download link you can ignore this.

Disclaimer: This isn't an official CGMiner's site. No binary files were affected.

All rights belong to their respective owners.

Back to top

© 2023 CGMiner.

About |

Russian version: Switch Language |

Cookie Policy |

Privacy Policy

Powered by

五分钟,开启比特币挖矿之旅! - 知乎

五分钟,开启比特币挖矿之旅! - 知乎首发于云体验师切换模式写文章登录/注册五分钟,开启比特币挖矿之旅!奉孝翼德​对未知世界留有敬畏之心挖矿其实很简单,只需要:一台有计算能力的联网设备和一个小小的挖矿软件。设备可以是:一台笔记本电脑,一块装着FPGA的主板都可以。挖矿软件,以最有影响力的比特币来说,常见的有以下几个:CGMiner:CGMiner支持命令行方式,因为是C语言写的,所以效率比较好,跨平台也非常好。虽说是跨平台的,但是在我的Windows10上安装失败了,系统提示有毒,可能是因为别人修改了什么被病毒库发现了吧,还是推荐在Linux上运行CGMiner,为了简便起见,这次体验就选一个难度其实奇低的吧。Bitminter:Java写的跨平台的工具,有图形化界面,但是限定了只能用特定的矿池。此外还有BFGMiner,这个不支持GPU,无法发挥我GTX1070的威力,也放弃了。EasyMiner,有图形化界面,但是太丑了,而且,也会惹到防病毒软件,想想也是放弃了,唯一推荐的是这个叫NiceHash的软件,界面美观,适合有美学修养的爱好者体验。官网(https://www.nicehash.com/)软件实际截图很好看吧不仅美观,它支持CPU,ASIC当然还有GPU,而且是AMD和NVIDIA的GPU都支持,软件操作感觉也很不错。软件选好了,我来介绍一下我的电脑配置吧,2016年买的i76700K CPU+16GB RAM+GTX 1070显卡,还过得去。软硬件都有了,现在开始挖矿吧?等等……这时候要准备一个钱包,比特币钱包提供一串地址,唯一的地址,就靠这个地址记录你的比特币,丢了就真的丢了。然后,你需要选择一个矿池。当然,你也可以选择Solo挖,就是不做矿池公认,自己干,但是自己需要解决很多问题,比如安全问题,风险比较大,建议还是找个包工头(Pool)一起挖,旱涝保收,也不怕故障丢成果,也不怕黑客给你添乱,这些麻烦事儿都交给池主吧。当然,你得交保护费。我们先注册登录,登录后的Dashboard如下图。点击Wallet钱包选项,里面就有一串地址,如下图所示,一串以3或者1开头的字符串:Yourbtc address。你可以把这串地址复制出来,粘贴到软件里,也可以注册第三方的Wallet(钱包来用)。UseBTC Address,我用的是后者。我是在Coinbase上注册的,不考虑别的原因,纯粹为了测试起见,选择了Coinbase(Coinbase不支持中国地区用户买,限制中国用户交易)。选择自己找的钱包或者直接用NiceHash提供的钱包选矿池。NiceHash提供了矿池,挖矿的时候你可以直接用。另外,作为买家的话,你可以自己添加矿池。Stratum列表中有很多可选项如果你就是挖矿的话,用NiceHash的你可以暂时跳过选池子的问题,NiceHash自带池子。你也可以看看配置栏里的东西,有点迫不及待的朋友可以之间点击Start了,点了之后,马上就可以进入正式的Benchmark过程了。为了测试一下你机器的水平吧,过程中会相应的做一些优化。Benchmark如果能顺利走完,就可以开始挖矿了。挖矿对计算能力要求还是很高的,如果机器不太行的话,这次挖矿之旅可能就到此为止了。挖矿ing图中预估了一天挖矿的产出,这个是波动的数字,因为BTC也在波动,计算力也在波动。当你的BTC足够支付手续费的时候,你就可以考虑出售了。NiceHash更牛的地方是,这里就支持交易。更多内容自己挖掘吧,考虑到现在的行情,我还是让我的显卡歇一歇吧。https://miner.nicehash.com/祝大家挖的愉快,不用交电费发布于 2018-09-06 08:59比特币 (Bitcoin)挖矿挖矿机​赞同 22​​6 条评论​分享​喜欢​收藏​申请转载​文章被以下专栏收录云体验师科技爱好者,IT科技八卦党(公号:云体

CGMiner Setup Guide [2023]

CGMiner Setup Guide [2023]

CGMiner

快速入门

我的平衡

Toggle search

切换菜单

en

ru

es

zh

Contents

Toggle menu

Setup

Command Line Arguments

Changelog

CGMiner Setup Guide

少于 1 分钟读完

在本页上

You can use this list as a reference for all Launch Parameters supported by CGMiner.

You can download CGMiner 3.7.2 from here:

Download Now

Download (mirror)

CGMiner 有一个命令行界面。 对于最小配置,请在 .bat 文件中输入:

CGMiner -a [挖矿算法] -o [矿池服务器] -u [用户名或钱包地址]

例子:

cgminer -o http://pool:port -u wallet_address -p password

获取钱包最简单的方法是在 Huobi 或 Binance。

有关配置选项的完整列表,请运行:

CGMiner --help

Linux:

Under Linux you need to replace cgminer.exe with ./cgminer in the command-line examples below.

The software supports the following algorithms:

Scrypt

SHA-256

NeoScrypt

CryptoNight

更新时间: 28.03.2023

Download now

Latest version is 3.7.2

File: *cgminer.exe,

SHA256: 417b22681a716e2481fde1fcaed96d66a5716a188186a4ae765d558d4a7ec2f5

Based on 3,400+ reviews

Download (windows)

Download (linux)

猜您还喜欢

下载 CGMiner 3.7.2 - ASIC、GPU 和 FPGA 矿工 [2022]

少于 1 分钟读完

Get started with CGMiner

Version: 3.7.2

File: *cgminer.exe,

SHA256: 417b22681a716e2481fde1fcaed96d66a5716a188186a4ae765d558d4a7ec2f5

(Down...

CGMiner: 变更日志和发行说明

少于 1 分钟读完

发行说明是随软件产品分发的文档

CGMiner - 命令行参数和选项

少于 1 分钟读完

您必须优化您的 cgminer.conf 和 cgminer.bat 文件,以生成特定硬件装备支持的吞吐量和散列的最佳组合。

分享

Twitter

Facebook

LinkedIn

向前

向后

CGMiner Community

irc

GitHub

Bitcointalk

Awesome Miner

Ethoprotocol

Hive OS

RaveOS

PiMP OS

Minerstat

SimpleMining OS

Note, when downloading the CGMiner, Windows may issue a warning, but if you used CGMiner download link you can ignore this.

Disclaimer: This isn't an official CGMiner's site. No binary files were affected.

All rights belong to their respective owners.

Back to top

© 2023 CGMiner.

About |

Russian version: Switch Language |

Cookie Policy |

Privacy Policy

Powered by

How to Mine Bitcoins With a GPU Using CGMiner Without Stress

How to Mine Bitcoins With a GPU Using CGMiner Without Stress

Skip to content

SunTrust Blog

Home

Travel

Technology

Lifestyle

Privacy Policy

Search

SunTrust Blog

Toggle Menu

Finance

How to Mine Bitcoins With a GPU Using CGMiner Without Stress

ByLucas TMLT

December 10, 2020July 12, 2022

Reading Time: 9 minutes

– GPU Using CGMiner –

Mine Bitcoins With a GPU Using CGMiner: The following article is a comprehensive guide on GPU mining from planning through execution. It will cover not just the technical setup but the decision making and process regarding profitability and long term gains.

READ ALSO:

Ibuypower 9200 I7-8700K Gaming PC Review 2020

The Four Basic Functions of a Computer Uses & Advantages Seen

40 Advantages & Disadvantages of Technology in Education Reviewed

Amish Miracle Heater Review 2020: How Good Can it Be?

What is Bitcoin

Bitcoin is a digital currency created in January 2009 following the housing market crash. It follows the ideas set out in a whitepaper by the mysterious and pseudonymous Satoshi Nakamoto.

The identity of the person or persons who created the technology is still a mystery. Bitcoin offers the promise of lower transaction fees than traditional online payment mechanisms and is operated by a decentralized authority, unlike government-issued currencies.

There are no physical bitcoins, only balances kept on a public ledger that everyone has transparent access to, that along with all Bitcoin transactions is verified by a massive amount of computing power.

Bitcoins are not issued or backed by any banks or governments, nor are individual bitcoins valuable as a commodity.

How are Bitcoins Mined

Mining is a process of adding transaction records to Bitcoin’s public ledger, called the Blockchain. It exists so that every transaction can be confirmed, and every single user of the network can access this ledger.

It is also used to distinguish legitimate Bitcoin transactions from attempts at re-spending money that has already been spent somewhere else.

Essentially, miners are serving the Bitcoin community by confirming every transaction and making sure that every single one of them is legitimate. Every time a new block is ‘sealed off’, a miner gets a reward. As of October 2017, the bounty stands at 12.5 Bitcoins per block.

The rate at which new coins appear resembles the rate at which commodities like gold are mined from the ground. Hence why the process is called ‘mining’.

Hardware Used for Mining

CPU Mining

Early Bitcoin client versions allowed users to use their CPUs to mine. The advent of GPU mining made CPU mining financially unwise as the hashrate of the network grew to such a degree that the number of bitcoins produced by CPU mining became lower than the cost of power to operate a CPU.

The option was therefore removed from the core Bitcoin client’s user interface.

GPU Mining

GPU Mining is drastically faster and more efficient than CPU mining. See the main article: Why a GPU mines faster than a CPU. A variety of popular mining rigs have been documented.

FPGA Mining

FPGA mining is a very efficient and fast way to mine, comparable to GPU mining and drastically outperforming CPU mining. FPGAs typically consume very small amounts of power with relatively high hash ratings, making them more viable and efficient than GPU mining.

See Mining Hardware Comparison for FPGA hardware specifications and statistics.

Whats is a GPU

Graphics processing technology has evolved to deliver unique benefits in the world of computing. The latest graphics processing units (GPUs) unlock new possibilities in gaming, content creation, machine learning, and more.

Designed for parallel processing, the GPU is used in a wide range of applications, including graphics and video rendering.

Although they’re best known for their capabilities in gaming, GPUs are becoming more popular for use in creative production and artificial intelligence (AI).

Why Mine Using a GPU

GPU mining is the second step in the mining evolution (first there was CPU mining); it’s very useful in the process of understanding mining.

We strongly believe that every miner should try mining with a GPU to experience how changing different options affects the speed and efficiency of GPU mining. Most likely, you already have a GPU in your desktop machine.

In the process of setting up the software, you will learn all the little tricks that are applicable to your hardware. You will also learn how the GPU compares to more advanced hardware, such as FPGAs and ASICs.

How Mine Using a GPU

What to Buy         

To build a GPU mining rig, you will need to purchase several hardware components. Start by deciding how many GPUs you would like your mining rig to have.

If only two, any regular desktop PC case will do. If more, then you’ll need a special mining case, such as this aluminum stackable open mining case for up to 8 GPUs.

The best GPUs for mining in terms of value are the AMD RX 480 and the Nvidia GTX 1070 Founders Edition.

Again, use the online mining calculator recommended above to calculate which of the two GPUs is more profitable for your cryptocurrency of choice.

You’ll also need a motherboard with enough PCI Express connectors for all your GPUs. There are now special mining motherboards, such as the ASRock H110 Pro BTC+ (up to 13 GPUs) or the ASUS B250

Mining Expert (up to 19 GPUs), but you can also use a regular desktop motherboard, such as the ASUS PRIME Z270-A.

The PSU of choice for most miners is the EVGA 1000 GQ, which is an 80 PLUS Gold certified power supply with heavy-duty protections and a large and quiet fan with fluid dynamic bearings.

Other hardware components, such as the CPU and RAM, are not too important, and you shouldn’t feel bad if you decide to save money on them.

Any modern Intel Pentium CPU, such as the G4560, should work fine. Just make sure that it’s compatible with your motherboard.

How to Start

With your GPU mining rig ready to go, we recommend you buy and set up the ethOS 64-bit Linux mining distribution, which supports Ethereum, Zcash, Monero, and other GPU-minable coins.

Of course, you can get by without a specialized mining operating system, but we guarantee that ethOS will pay for itself multiple times in the long run.

ethOS supports up to 16 AMD RX or Nvidia GPUs, it can automatically assign an IP address and hostname, has built-in GPU overheat protection, and features automatic reporting, and remote configuration.

Above all, is extremely lightweight and works with all CPUs made in the last 5 generations on only 2 GB of RAM.

What is CGMiner

CGMiner is an ASIC, GPU, and FPGA miner that is maintained as an open-source product and works on platforms including Windows, Linux, and macOS.

CGMiner is extremely flexible platform-wise and can work with a variety of hardware miners, and GPUs, including the CUDA and NVIDIA platforms.

How to Mine with CGMiner

Create an Online Bitcoin Wallet

Blockchain allows you to create a free, and secure wallet that provides many useful features.

Blockchain.info is a great place to create a free online Bitcoin wallet.

Blockchain will generate a password recovery mnemonic, be sure to store this somewhere safe in case you ever need to recover access to your wallet.

It’s important to use a very secure password for the wallet. If anyone were to gain access to your wallet they could quickly steal all of the coins inside.

Find Your Bitcoin Wallet Address

After creating the account log into the wallet using the identifier and password. The address of the wallet can be found on the main wallet home tab.

The address consists of 27-34 alphanumeric characters. This address is what you will provide to people so they can send you payments using Bitcoins.

Once you have a wallet you can give out your address so people can send you Bitcoins!

Join a Bitcoin Mining Pool

Solo mining requires an incredible amount of processing power which most people don’t have access to.

Pooled mining allows miners to group up to solve blocks and earn Bitcoins together. Each miner that joins the pool earns shares for the work they contribute.

Each time the pool finds a block (currently worth 12.5 BTC) the Bitcoins earned are divided among the users in the pool based on how many shares they earned in the particular round.

 

There are many different mining pools you can join, each pool has it’s own pros and cons. As you learn more about Bitcoins you will be able to make a more educated decision of which pool is best for you.

I recommend joining AntPool because it has some great features and is very easy to use.

Creating an Account at AntPool

The process for joining most Bitcoin mining pools is very similar but in this guide, I’ll show you how to start mining with AntPool.

The first step in joining the pool is to register for a new account.

Create a Subaccount

After registering with AntPool you will need to create a sub-account and associate a Bitcoin wallet. Payments will be sent from the pool to this wallet address once the payment threshold has been reached.

After logging in click on the settings like to create a new sub-account. Once you’ve created a sub-account click the edit link to add your Bitcoin wallet address.

The changes to your account will need to be confirmed by responding to the email sent from AntPool.

Creating a Worker

Next, you need to set up a worker, click on the dashboard tab then workers. You will need one worker account for each copy of CGMiner you intend to run.

Creating an AntPool worker.

Download and Configure CGMiner

At this point, you should have a Bitcoin wallet that is now associated with the AntPool worker. This means you are finally ready to start actually mining for Bitcoins!

Cgminer version 3.7.2 is the latest version with GPU support. Versions later than 3.7.2 do not support GPUs (only ASICs).

Extract the Contents of the Zipfile

After downloading the compressed zip file open the archive. You can use 7zip to extract the contents of the file. Inside the archive you’ll find a folder called cgminer-3.7.2-windows.

Move this folder to C:\ and rename it to cgminer.

You should end up a with a folder called c:\cgminer , the contents should like like the image below.

Edit the CGMiner.conf File

Next you need to enter the pool settings into the cgminer.conf file contained inside the c:\cgminer directory where you extracted the files.

Edit the existing cgminer.conf file and modify the pools section as shown below. Replace subaccount.worker with the name of your own sub account and worker you created in the AntPool dashboard.

Remove the extra pool sections unless you intend to add configure multiple pools.

Launching CGMiner

Once the config file has been modified you are ready to start mining for Bitcoins using CGMiner. Double click on cgminer.exe to start the miner.

If your configuration is correct CGMiner launch, connect to the mining pool, and start mining for Bitcoins.

Each of the GPUs detected by CGMiner will be listed in the second section below the summary. The current hash rate for each card will be displayed in Mh/s (Mega hashes per second).

CGMiner in operation mining for Bitcoins.

CGMiner in operation mining for Bitcoins.

Troubleshooting CGMiner

If you’re unable to get CGMiner working here are some common things you should check first.

Install the latest version of the video card drivers

Try launching cgminer directly from the command prompt instead o to check for error messages.

Double-check the worker’s name entered in the commoner.conf file.

We hope this article was useful and educative, do well to share these messages with friends and loved ones. If you have a question, kindly drop your comments below.

Share this:FacebookXLike this:Like Loading...

Post navigation

Previous

PreviousList of 50 Cute and Catchy Diner Names you Can UseNextContinue

How to Ensure Safety on Letgo While Buying and Selling Used Stuff

Similar Posts

Credit Card | Finance

Walmart Cashback Limit 2021: Paying With Credit and Debit Card

Read More Walmart Cashback Limit 2021: Paying With Credit and Debit CardContinue

Blog | Finance

What are the Transfer Limits of U.S Banks for 2021?

Read More What are the Transfer Limits of U.S Banks for 2021?Continue

Business | Credit Card | Finance

How to Cancel a PayPal Payment Mistakenly Sent to the Wrong Person

Read More How to Cancel a PayPal Payment Mistakenly Sent to the Wrong PersonContinue

Blog | Finance

MoneyMutual: Services Offered by Money Mutual Review 2021

Read More MoneyMutual: Services Offered by Money Mutual Review 2021Continue

Business | Finance

How to Value a Business & Common Mistakes to Avoid

Read More How to Value a Business & Common Mistakes to AvoidContinue

Credit Card | Finance

Can You Buy a Car With a Credit Card? Everything You Need To Know

Read More Can You Buy a Car With a Credit Card? Everything You Need To KnowContinue

Leave a Reply Cancel replyYour email address will not be published. Required fields are marked *Comment *Name *

Email *

Website

Save my name, email, and website in this browser for the next time I comment.

Notify me of follow-up comments by email. Notify me of new posts by email.

Δ

© TMLT Innovative Hub

Home

Travel

Technology

Lifestyle

Privacy Policy

Toggle Menu Close

Search for:

Search

%d

Download the latest version CGMiner (3.7.2) - AMD+NVIDIA [2022]

Download the latest version CGMiner (3.7.2) - AMD+NVIDIA [2022]

CGMiner

Quick Start

Download

Toggle search

Toggle menu

en

ru

es

zh

Contents

Toggle menu

Latest stable version

3.7.2

4.12

Download newest Version of CGMiner - 3.7.2

less than 1 minute read

On this page

Get started with CGMiner

Latest version is 3.7.2

SHA256: 417b22681a716e2481fde1fcaed96d66a5716a188186a4ae765d558d4a7ec2f5 *cgminer3.7.2.exe

(Download for Linux)

Download Now (Windows x64)

(mirror)

The new CGMiner stable version is ready.

You can download CGMiner 3.7.2 from here:

Download Now

Download (mirror)

Inside the archive you will find a file README.txt with installation instructions.

Make sure to replace the pool and wallet address by what you’re using in all files.

Updated: 29.04.2022

Download now

Latest version is 3.7.2

File: *cgminer.exe,

SHA256: 417b22681a716e2481fde1fcaed96d66a5716a188186a4ae765d558d4a7ec2f5

Based on 3,400+ reviews

Download (windows)

Download (linux)

You may also enjoy

Download CGMiner 4.12 - ASIC, GPU and FPGA Miner [2022]

1 minute read

Get started with CGMiner

Version: 4.12

File: *cgminer.exe,

SHA256: c57cfadb4a6b8af18bb83248e5244992a0e1dd3617b254f68df9a6c97261c953

(Downl...

Download CGMiner 3.7.2 - ASIC, GPU and FPGA Miner [2022]

less than 1 minute read

Get started with CGMiner

Version: 3.7.2

File: *cgminer.exe,

SHA256: 417b22681a716e2481fde1fcaed96d66a5716a188186a4ae765d558d4a7ec2f5

(Down...

CGMiner Setup Guide [2023]

1 minute read

You can use this list as a reference for all Launch Parameters supported by CGMiner.

CGMiner: Changelog and Release notes

1 minute read

Release notes are documents that are distributed with software products

Share on

Twitter

Facebook

LinkedIn

Previous

Next

CGMiner Community

irc

GitHub

Bitcointalk

Awesome Miner

Ethoprotocol

Hive OS

RaveOS

PiMP OS

Minerstat

SimpleMining OS

Note, when downloading the CGMiner, Windows may issue a warning, but if you used CGMiner download link you can ignore this.

Disclaimer: This isn't an official CGMiner's site. No binary files were affected.

All rights belong to their respective owners.

Back to top

© 2023 CGMiner.

About |

Russian version: Switch Language |

Cookie Policy |

Privacy Policy

Powered by

Releases · CGMinerGit/CGMiner · GitHub

Releases · CGMinerGit/CGMiner · GitHub

Skip to content

Toggle navigation

Sign in

Product

Actions

Automate any workflow

Packages

Host and manage packages

Security

Find and fix vulnerabilities

Codespaces

Instant dev environments

Copilot

Write better code with AI

Code review

Manage code changes

Issues

Plan and track work

Discussions

Collaborate outside of code

Explore

All features

Documentation

GitHub Skills

Blog

Solutions

For

Enterprise

Teams

Startups

Education

By Solution

CI/CD & Automation

DevOps

DevSecOps

Resources

Learning Pathways

White papers, Ebooks, Webinars

Customer Stories

Partners

Open Source

GitHub Sponsors

Fund open source developers

The ReadME Project

GitHub community articles

Repositories

Topics

Trending

Collections

Pricing

Search or jump to...

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Cancel

Submit feedback

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Cancel

Create saved search

Sign in

Sign up

You signed in with another tab or window. Reload to refresh your session.

You signed out in another tab or window. Reload to refresh your session.

You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

CGMinerGit

/

CGMiner

Public

forked from ckolivas/cgminer

Notifications

Fork

3

Star

5

Code

Pull requests

0

Actions

Projects

0

Security

Insights

Additional navigation options

Code

Pull requests

Actions

Projects

Security

Insights

Releases: CGMinerGit/CGMiner

Releases

Tags

Releases · CGMinerGit/CGMiner

CGminer 4.12.0 GekkoScience Compac, 2pac & Newpack BM1384 & CompacF

29 Apr 13:20

CGMinerGit

4.12.0

b8491c6

This commit was created on GitHub.com and signed with GitHub’s verified signature.

The key has expired.

GPG key ID: 4AEE18F83AFDEB23

Expired

Learn about vigilant mode.

Compare

Choose a tag to compare

View all tags

CGminer 4.12.0 GekkoScience Compac, 2pac & Newpack BM1384 & CompacF

Latest

Latest

This is cgminer 4.12.0 with support for GekkoScience Compac, CompacF, 2pac.

This software is forked from cgminer 4.11.1 original from ckolivas.

Then i added v.thoang gekko drivers

I also adapted this code to my own material / miners / computer (you can refer to original documentation to docs/README)

Assets

4

All reactions

Cgminer 4.11.1 with GekkoScience Compac

29 Apr 13:07

CGMinerGit

v4.11.1

d6faaf0

Compare

Choose a tag to compare

View all tags

Cgminer 4.11.1 with GekkoScience Compac

Cgminer-gekko.zip => only gekko usb

Cgminer-gekko-all-usb.zip => all usb included in cgminer 4.10

Assets

3

All reactions

CGMiner 4.3.5

29 Apr 13:01

CGMinerGit

v4.3.5

1afa194

Compare

Choose a tag to compare

View all tags

CGMiner 4.3.5

v4.3.5

Add cointerra driver to news

Assets

3

All reactions

CGMiner 4.1.0

29 Apr 13:02

CGMinerGit

v4.1.0

50b3b76

Compare

Choose a tag to compare

View all tags

CGMiner 4.1.0

v4.1.0

Minor documentation updates.

Assets

3

All reactions

CGMiner 3.7.2

29 Apr 13:03

CGMinerGit

v3.7.2

829f068

Compare

Choose a tag to compare

View all tags

CGMiner 3.7.2

v3.7.2

Bump version to 3.7.2

Assets

3

All reactions

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms

Privacy

Security

Status

Docs

Contact

Manage cookies

Do not share my personal information

You can’t perform that action at this time.

Attention Required! | Cloudflare

Attention Required! | Cloudflare

Please enable cookies.

Sorry, you have been blocked

You are unable to access block.cc

Why have I been blocked?

This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.

What can I do to resolve this?

You can email the site owner to let them know you were blocked. Please include what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page.

Cloudflare Ray ID: 8633782a2e3885a3

Your IP:

Click to reveal

49.157.13.121

Performance & security by Cloudflare

最全Cgminer比特币挖矿使用教程详解_蜜蜂查

最全Cgminer比特币挖矿使用教程详解_蜜蜂查

为积极响应中国政府监管政策要求,自2021年9月28日起,蜜蜂查block.cc停止为中国大陆用户提供相关服务。蜜蜂查block.cc致力于遵循各国法律法规合法运营,感谢您的支持与理解! 币种: -- 交易所: -- 总成交额(24h): -- 总市值: --

USD 首页币种交易所快讯公告资讯更多 研报问答日历专栏排行榜最新收录微博Twitter区块链百科 商业API APP 登录 / 注册 首页 百科 最全Cgminer比特币挖矿使用教程详解 最全Cgminer比特币挖矿使用教程详解 yoyo 2022.09.20 22:36 在下七彩神仙鱼看到新手,还有部分老手不太会用CGminer挖矿,特出此教程和大家交流一下CG相关设置,如有不对之处,还望大家指正1、前期准备1)CG软件下载绝版CG 2.3.4 WIN32CG所有版本:点我2)驱动和SDK的选择驱动建议5、6系选用11.11或11.12和12.1(也可使用11.X不过CPU会满载),7系卡使用12.3或最新驱动,。驱动请去驱动之家下载。11.12win7 32位驱动地址部分驱动已集成SDK,可以直接挖矿。没有集成的,SDK下载地址2、中期配置CG可采用配置文件配置,一次配置终身使用,可谓简单易行稳定。上图左边为配置文件,右边为主程序文件,在配置完成后,双击打开EXE即可挖矿,也已把exe的快捷方式放在开始菜单启动文件夹下,即可实现开机自动挖矿。用记事本新建一个TXT文件,按下面配置完成后,另存为cgminer.conf配置文件中标点符号全文为英文字符,切记。1)矿池配置 pools : [{ url : http://mine3.btcguild.com:8332 , user : tu , pass : -1 },{ url : http://mmpool.bitparking.com:15098 , user : tudou , pass : -1 },{ url : pool.maxbtc.com:8332/ , user : maomao00079-1 , pass : doP31V60 }]复制代码每一个{}间为一个矿池服务器地址以及对于的账号和密码,不同矿池间用英文逗号隔开。可以添加多个矿池,一旦矿池发生矿难,可以自动使用下一个矿池挖矿,一旦恢复采用优先级最高的挖矿。2)核心参数下面以双显卡为例说明一下: intensity : 9,9 , intensity 指显卡工作优先级 6是一般,D是自动,数字越高优先级越高 ,接显示器的设为6 其他的设为9-14.通过调节优先级可以是先GPU满载和不满载工作。 vectors : 2,2 , worksize : 128,128 ,工作空间 kernel : phatk,phatk ,CG采用diablo poclbm, phatk,diakgcn四种内核,不同内核在不同系统、驱动、SDK速度会有所差异,差异一般在10M-70M之间。按前期准备配置时,建议采用diablo,phatk内核或者diakgcn gpu-engine : 0-800,0-800 ,指显卡工作频率 也就是超频 0是默认频率 数值是设定频率gpu-fan : 85,85 ,显卡风扇转速,此为固定转速,建议自行尝试设置,只要能压住温度就行。 gpu-memdiff : 0,0 ,默认就行 gpu-powertune : 0,0 , 为AMD powertune 技术,5970和6990支持设为20,其他设为0。 gpu-vddc : 0,0 ,显卡电压,超频一般伴随着电压的调节,不过只有做工过硬的显卡可以加压。0是默认,一次加减0.001V,降低电压降低功耗和温度。 temp-cutoff : 90,90 ,显卡停止工作温度,另外CG中显示的温度是核心温度而非供电温度,两者之间有一定的差距。 temp-overheat : 80,80 ,显卡过热温度 temp-target : 72,72 ,显卡目标温度。以上参数后面的数值根据显卡的多少改变数值的多少。例如:单卡 gpu-engine : 0, ,双卡 gpu-engine : 0,0 ,三卡 gpu-engine : 0,0,0 ,四卡三卡 gpu-engine : 0,0,0,0 ,以此类推。3)其余参数其余参数一般不变,如下 api-port : 4028 , expiry : 120 , failover-only :true, gpu-dyninterval : 7 , gpu-platform : 0 , gpu-threads : 2 , log : 5 , queue : 1 , retry-pause : 5 , scan-time : 60 , temp-hysteresis : 3 , shares : 0 , kernel-path : /usr/local/bin }单卡cgminer.conf文件http://dl.dbank.com/c0cvbadz6l请自行修改3、后期调试后期主要调接GPU核心频率、电压,风扇转速,内核版本。重新设置后打开CG运行3分钟左右,待速度稳定后,通过对比速度,来选择相应的参数。

来源: 蜜蜂查 新闻资讯 免责声明:蜜蜂查作为区块链行情资讯平台,仅提供数据追踪和整理,网站内所有内容均不代表蜜蜂查平台观点,且不构成任何投资建议。请用户谨慎防范以“虚拟货币”“区块链”等名义进行的非法集资。 更多精彩内容 Android版下载 iPhone 版下载 扫描二维码,查询更多行情 蜜蜂查服务 币种交易所IEO项目区块日历7 X 24快讯公告专栏资讯排行榜百科指南币种收录交易所收录常见问题开放API隐私政策 热门链接 比特币比特币价格比特币新闻比特币交易比特币走势比特币行情 联系我们 微信公众号 官方客服 收录申请 商务合作 喜马拉雅 热门币种: 比特币BTC币以太坊以太币ETH币EOS币USDT币BNB币币安币LTC币莱特币XRP币瑞波币XLM币恒星币波场TRX币BCH币比特币现金ADA币艾达币LEO币Bitfinex平台币XTZ币Tezos代币ATOM币Cosmos代币XMR币门罗币OKBOKex平台币HT币Huobi平台币Link币Chainlink代币ALGO币Algorand代币NEO币ETC币以太坊经典HEDG币IOTA币埃欧塔SHARD币DASH币达世币ONT币本体网络XT币 蜜蜂查 Copyright © 2024 京ICP备18055546号-2