OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.10.0

[intron]

- Hexfury USB sticks should now be detected and come up as HXF instead of BXF.

Thanks!

[1495798343]

1495798343

[os2sam]

New release: 4.2.3, 3rd April 2014

- Added a --widescreen option by request which does not toggle and shows all information. This can be enabled/disabled via the display menu.

Perfect.  How wide is that?  I have my width set to 90 and it seems to display everything.

[os2sam]

New release: 4.2.3, 3rd April 2014



- Solo miners can now add their own signature of up to 32 characters to the coinbase with the --btc-sig option.

Great! Thanks.

It appears that spaces aren't allowed.  Are there any other characters that aren't allowed, that you may know of?

[-ck]

New release: 4.2.3, 3rd April 2014

- Added a --widescreen option by request which does not toggle and shows all information. This can be enabled/disabled via the display menu.

Perfect.  How wide is that?  I have my width set to 90 and it seems to display everything.

Will go up to 100.

New release: 4.2.3, 3rd April 2014



- Solo miners can now add their own signature of up to 32 characters to the coinbase with the --btc-sig option.

Great! Thanks.

It appears that spaces aren't allowed.  Are there any other characters that aren't allowed, that you may know of?

Spaces are allowed, you just have to quote the signature.

[IYFTech]

Love that widescreen option......

[os2sam]

New release: 4.2.3, 3rd April 2014



- Solo miners can now add their own signature of up to 32 characters to the coinbase with the --btc-sig option.

Great! Thanks.

It appears that spaces aren't allowed.  Are there any other characters that aren't allowed, that you may know of?

Spaces are allowed, you just have to quote the signature.

Good info.  Thanks

The --btc-sig was missed in the readme altogether.

[-ck]

New release: 4.2.3, 3rd April 2014



- Solo miners can now add their own signature of up to 32 characters to the coinbase with the --btc-sig option.

Great! Thanks.

It appears that spaces aren't allowed.  Are there any other characters that aren't allowed, that you may know of?

Spaces are allowed, you just have to quote the signature.

Good info.  Thanks

The --btc-sig was missed in the readme altogether.

Yeah sorry I realised after I had already put together the release. Oh and you can use any characters you like provided it's all quoted.

[Trongersoll]

New release: 4.2.3, 3rd April 2014



- Solo miners can now add their own signature of up to 32 characters to the coinbase with the --btc-sig option.

Great! Thanks.

It appears that spaces aren't allowed.  Are there any other characters that aren't allowed, that you may know of?

Spaces are allowed, you just have to quote the signature.

Good info.  Thanks

The --btc-sig was missed in the readme altogether.

Sounds like it is time for me to set up a solo miner. I'm totally about getting my name all over the internet.

[-ck]

Sounds like it is time for me to set up a solo miner. I'm totally about getting my name all over the internet.

I recommend any miner who has a full bitcoind running somewhere on their lan should have solo mining as their last backup anyway, in case every single pool you are mining on falls over for whatever reason. It's good security for you and the network.

[loshia]

Con,
I found two cosmetic bugs in cgminer-api

static void disablepool(struct io_data *io_data, __maybe_unused SOCKE
.........
   pool->enabled = POOL_DISABLED;
   enabled_pools--;


 

And same in enablepool

b]enabled_pools++;[/b]




Thanks

PS:What about my previous question about stale_work
      work->job_id = strdup(pool->gbt_workid);

and checking it's job_id

In general there is no code when gbt work becomes stale.

Thanks

[-ck]

Con,

I am looking at stale_work() code. I am wandering if work gets stale in solo and gbt also?

if (pool->gbt_workid)
      work->job_id = strdup(pool->gbt_workid);
Shall job_id be checked inside stale_work code. For stratum it is considered as stale if there is no share but for gbt and solo?
Thanks

There are enough checks to determine if work is stale with gbt solo/pool already.

[loshia]

Con,

I am looking at stale_work() code. I am wandering if work gets stale in solo and gbt also?

if (pool->gbt_workid)
      work->job_id = strdup(pool->gbt_workid);
Shall job_id be checked inside stale_work code. For stratum it is considered as stale if there is no share but for gbt and solo?
Thanks

There are enough checks to determine if work is stale with gbt solo/pool already.

Thanks,
Can you give me some hints what to look for in the code i am carious

Thanks

[-ck]

Con,

I am looking at stale_work() code. I am wandering if work gets stale in solo and gbt also?

if (pool->gbt_workid)
      work->job_id = strdup(pool->gbt_workid);
Shall job_id be checked inside stale_work code. For stratum it is considered as stale if there is no share but for gbt and solo?
Thanks

There are enough checks to determine if work is stale with gbt solo/pool already.

Thanks,
Can you give me some hints what to look for in the code i am carious

Thanks

work_block is enough to pick up if we're working on the same block. work_id is used only for pooled gbt mining (not solo) to tell the pool which gbt update it came from (and is optional at the pool end).

[loshia]

Con,

I am looking at stale_work() code. I am wandering if work gets stale in solo and gbt also?

if (pool->gbt_workid)
      work->job_id = strdup(pool->gbt_workid);
Shall job_id be checked inside stale_work code. For stratum it is considered as stale if there is no share but for gbt and solo?
Thanks

There are enough checks to determine if work is stale with gbt solo/pool already.

Thanks,
Can you give me some hints what to look for in the code i am carious

Thanks

work_block is enough to pick up if we're working on the same block. work_id is used only for pooled gbt mining (not solo) to tell the pool which gbt update it came from (and is optional at the pool end).

Thank You

[shortpocket]

could anybody be so kind and give step by step instruction on how to get 4.2.2 working on linux (ubuntu)?

From reading the first post in this thread, you learn you have to do this:

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

If you have 32-bit Ubuntu, download the file cgminer-4.2.2.tar.bz2.
If you have 64-bit Ubuntu, download the file cgminer-4.2.2-x86_64-built.tar.bz2

Either way, unzip the file you downloaded.  Then run the executable you just unzipped, follow the prompts to set up your first pool, plug in your devices, and poof, you're mining.  (I also suggest, after you configure your pool and other settings, that you save a config file using the in-program menus and prompts.)

For anything more specific than that, you'll have to ask a clearer question.

ok iĺl be more specific...

last time i had cgminer running it was 3.7 i think through the console/terminal so i dont know wich executionable you are talking about.. if you could be so kind and tell me i would apreciate it.
i need to get cgminer running now, as i have just received a package.

[linuxdoctor]

The following code snippet appears in cgminer.c from the latest (April 4, 2014) git clone.

Code:

   3073         } else {
   3074                 char *hexstr;
   3075
   3076                 endian_flip128(work->data, work->data);
   3077
   3078                 /* build hex string */
   3079                 hexstr = bin2hex(work->data, 118);
   3080                 s = strdup("{\"method\": \"getwork\", \"params\": [ \"");
   3081                 s = realloc_strcat(s, hexstr);
   3082                 s = realloc_strcat(s, "\" ], \"id\":1}");
   3083                 free(hexstr);
   3084         }

Question: in line 3079 why is the data length being passed to bin2hex()  set to 118? Should this not be 'sizeof(work->data)', that is to say, 256 bytes?

[-ck]

The following code snippet appears in cgminer.c from the latest (April 4, 2014) git clone.

Code:

   3073         } else {
   3074                 char *hexstr;
   3075
   3076                 endian_flip128(work->data, work->data);
   3077
   3078                 /* build hex string */
   3079                 hexstr = bin2hex(work->data, 118);
   3080                 s = strdup("{\"method\": \"getwork\", \"params\": [ \"");
   3081                 s = realloc_strcat(s, hexstr);
   3082                 s = realloc_strcat(s, "\" ], \"id\":1}");
   3083                 free(hexstr);
   3084         }

Question: in line 3079 why is the data length being passed to bin2hex()  set to 118? Should this not be 'sizeof(work->data)', that is to say, 256 bytes?

No because only those variables are actually the work payload which becomes the result. Other data in the work struct are private.

[KyrosKrane]

could anybody be so kind and give step by step instruction on how to get 4.2.2 working on linux (ubuntu)?

From reading the first post in this thread, you learn you have to do this:

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

If you have 32-bit Ubuntu, download the file cgminer-4.2.2.tar.bz2.
If you have 64-bit Ubuntu, download the file cgminer-4.2.2-x86_64-built.tar.bz2

Either way, unzip the file you downloaded.  Then run the executable you just unzipped, follow the prompts to set up your first pool, plug in your devices, and poof, you're mining.  (I also suggest, after you configure your pool and other settings, that you save a config file using the in-program menus and prompts.)

For anything more specific than that, you'll have to ask a clearer question.

ok iĺl be more specific...

last time i had cgminer running it was 3.7 i think through the console/terminal so i dont know wich executionable you are talking about.. if you could be so kind and tell me i would apreciate it.
i need to get cgminer running now, as i have just received a package.

I thought it was clear - "run the executable you just unzipped". The executable is cgminer - it's just zipped up for faster download. Once you unzip it, you just run it, like any other Linux program.  Either type in the name from the command line, or double click the file if you're using a GUI.  If you want to control how it runs, check the readme file and set the command line parameters the way you want them, or configure them in the program and write the config file using the built in function.

I'm sorry, but I'm honestly not sure how to be any clearer. If you don't know how to run a program in your preferred operating system, then you need to spend some time learning how to do that along with other basic tasks, like how to safely boot and shut down the PC, or how to log on and log off, or how to save your documents for later use.

[Zich]

ok iĺl be more specific...

last time i had cgminer running it was 3.7 i think through the console/terminal so i dont know wich executionable you are talking about.. if you could be so kind and tell me i would apreciate it.
i need to get cgminer running now, as i have just received a package.

Make sure the following package already installed on your ubuntu system

Code:

1. sudo apt-get update
2. sudo apt-get upgrade
3. sudo apt-get install libudev-dev libusb-1.0-0-dev libfox-1.6-dev
4. sudo apt-get install autotools-dev autoconf automake libcurl3-dev
5. sudo apt-get install libtool libncurses-dev yasm
6. sudo apt-get install curl libcurl4-openssl-dev libjansson-dev screen
7. sudo apt-get install pkg-config uthash-dev make git-core

Download & compile cgminer 4.2.3, no need to install.

Code:

1. sudo git clone https://github.com/ckolivas/cgminer.git
2. sudo mv cgminer cgminer-4.2.3
3. cd cgminer-4.2.3
4. sudo ./autogen.sh --enable-ants1 --enable-avalon --enable-bitfury
5. sudo make

Step number 4  use additional option to enable specific device. Add the option based on available devices.

Code:

 --enable-ants1          Compile support for Antminer S1 Bitmain (default  disabled)
  --enable-avalon         Compile support for Avalon (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-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-knc            Compile support for KnC miners (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)

To run, go to cgminer-4.2.3 folder.

Code:

sudo ./cgminer

To use cgminer-api, you need to compile it first

Code:

sudo gcc api-example.c -Icompat/jansson-2.5 -Icompat/libusb-1.0/libusb -o cgminer-api

To run

Code:

cgminer-api stats

Code:

cgminer-api pools

Code:

cgminer-api summary

Code:

cgminer-api devs

[jomant]

ok iĺl be more specific...

last time i had cgminer running it was 3.7 i think through the console/terminal so i dont know wich executionable you are talking about.. if you could be so kind and tell me i would apreciate it.
i need to get cgminer running now, as i have just received a package.

Make sure the following package already installed on your ubuntu system

Code:

1. sudo apt-get update
2. sudo apt-get upgrade
3. sudo apt-get install libudev-dev libusb-1.0-0-dev libfox-1.6-dev
4. sudo apt-get install autotools-dev autoconf automake libcurl3-dev
5. sudo apt-get install libtool libncurses-dev yasm
6. sudo apt-get install curl libcurl4-openssl-dev libjansson-dev screen
7. sudo apt-get install pkg-config uthash-dev make git-core

Download & compile cgminer 4.2.3, no need to install.

Code:

1. sudo git clone https://github.com/ckolivas/cgminer.git
2. sudo mv cgminer cgminer-4.2.3
3. cd cgminer-4.2.3
4. sudo ./autogen.sh --enable-ants1 --enable-avalon --enable-bitfury
5. sudo make

Step number 4  use additional option to enable specific device. Add the option based on available devices.

Code:

 --enable-ants1          Compile support for Antminer S1 Bitmain (default  disabled)
  --enable-avalon         Compile support for Avalon (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-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-knc            Compile support for KnC miners (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)

To run, go to cgminer-4.2.3 folder.

Code:

sudo ./cgminer

To use cgminer-api, you need to compile it first

Code:

sudo gcc api-example.c -Icompat/jansson-2.5 -Icompat/libusb-1.0/libusb -o cgminer-api

To run

Code:

cgminer-api stats

Code:

cgminer-api pools

Code:

cgminer-api summary

Code:

cgminer-api devs

Are those steps apply for the Raspberry pi as well. I was looking for a detailed Installation instruction like this a page before and ended up with backing up my previews version 1.8 or so. I am mining on 2GH/s with a Antminer U2 with a 14% error rate.