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

[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.

[1675866827]

1675866827

[1675866827]

1675866827

[1675866827]

1675866827

[1675866827]

1675866827

[kano]

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

https://github.com/ckolivas/cgminer/blob/master/README

... that's why it's called ... README ...

[-ck]

New release: 4.2.3, 3rd April 2014


Human readable changelog:

- During network outages the devices hashrate would appear static, this has been fixed.
- Did a major rewrite of the code that writes and parses the config files. Now if you choose [W]rite from the [ S]ettings menu it should write most of the options you've given on the command line. Some options were never written correctly and many weren't written at all previously.
- Changed the toggling display to sit on the most important screen and not toggle by default, but it can be re-enabled via the [D]isplay menu.
- The hashrate line for per-device also includes the Work Utility at the end now instead of the alternate screen to better fit within 80 columns.
- Added a --widescreen option by request which does not toggle and shows all information. This can be enabled/disabled via the display menu.
- The --device and --remove-disabled commands have been removed. They are a hangover from the GPU days and choosing devices with this command does not give any meaningfully reliable way of choosing devices.
- Added checking for any number of chips on bi*fury (BXF) devices and added the extra output in the API for them.
- Hexfury USB sticks should now be detected and come up as HXF instead of BXF.
- BXF bits can now be configured on the command line in case people wish to push the maximum for hardware modded devices (normally 54).
- Solo miners can now add their own signature of up to 32 characters to the coinbase with the --btc-sig option.
- miner.php updates.
- Fixed getwork share submission which was broken for the rare pools remaining that still use it.
- Other low level bugfixes/improvements.


Full changelog:

- Decay the per device hashrates when only the watchdog is calling the hashmeter
- Fix parsing of config files failing on custom parsing
- Allow an arbitrary number of chips in the BXF driver, showing results from
each chip in the API and identify the hexfury, naming it HXF
- Disable toggling display by default and offer a --widescreen option to have
all the information on an extra wide display.
- Use OPT_WITH_CBARG for all custom parsing functions to allow their values to
be written generically when writing the config file from the menu.
- Provide a ccan variant OPT_WITH_CBARG that assigns the arguments passed as a
string and then performs the callback function on the string.
- Define strings to store special option parsing parameters leaving no
OPT_WITH_ARG missing args
- Correct the writing of special case options to the config file
- Provide support for writing anu freq from menu write option
- Update to diver-avalon2.c
- Generalise a lot more of the command line options simplifying the write config
function and making it write far more values unaided
- Use the general opt_set_charp functions for setting api parameters
- Json escape any strings written to the config file
- Store standard charp options when writing config files
- Add support for all the integer range options when writing the config file
from the menu
- Remove the --device and --remove-disabled options which don't work in a
meaningful way any more
- Make the bxf bits configurable on the command line
- Provide a --btc-sig option to optionally add a custom signature to the solo
mining coinbsae
- Compact gbt solo extra data and store the length, allowing it to be variable,
leaving room for a signature
- miner.php - Kano summary Pool Acc/Rej should be only work submitted
- miner.php add best share and gen formatting for pool summary
- miner.php - remove BGEN/GEN eval() errors from the web log
- miner.php allow optional fields when gen is disabled
- miner.php dont format missing gen fields
- miner.php make Summary a custompage
- miner.php allow uers and system lists of customsummarypages and add more
examples
- Fix getwork share submission
- Cosmetic fix to udev rules
- Put WU on the hashrate status to compact lines further
- miner.php show api/rig errors at the top of a customsummarypage

[intron]

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

Thanks!

[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.