OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 724.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Well that was some unexpected humour from the bitcoin mining crowd. I grinned Cheesy

I guess the improving price of BTC has improved people's moods.

2.0.9 was a development version number only, and yes the minor version upgrade (as opposed to micro version) signifies the feature upgrade to the RPC API.

If you pulled from git and are still getting version 2.0.9 it's because you didn't do ./autogen.sh

As for windows, as I said I've thrown it in the debugger heaps of times and the bug goes away in it so it's proving undebuggable (a Heisenbug). (I do believe it's some windows versions only). So you're out of luck unless you wish to run cgminer without the curses display (i.e. start it with -T).

Proofer

member

Activity: 266

Merit: 36

Quote from: 2.1.0 README

Q: Can you change the autofan/autogpu to change speeds in a different manner?
A: The defaults are sane and safe. I'm not interested in changing them
further. The starting fan speed is set to 85% in auto-fan mode as a safety
precaution, but if a specific fan speed has been set, it will use that first
before adjusting automatically.

This reminded me that there's something I didn't understand about the fairly recent posts on this subject:

If I want to set a specific starting fan speed, I would use the gpu-fan option, right? But if I also use auto-fan, what would cgminer use as a permissible range for the fan speed percentage? E.g., suppose I want a range of 0-85, starting speed of 50, and auto-fan. Can that be done? Perhaps I don't understand what "has been set" refers to in the quoted README excerpt.

Red Emerald

hero member

Activity: 742

Merit: 500

I rebuilt the latest git-head and it still says "2.0.9" instead of "2.1.0"

Code:

 cgminer version 2.0.9 - Started: [2011-12-27 18:26:22]
--------------------------------------------------------------------------------
 (5s):667.5 (avg):734.3 Mh/s | Q:10  A:1  R:0  HW:0  E:10%  U:11.64/m
 TQ: 4  ST: 4  SS: 0  DW: 0  NB: 1  LW: 0  GF: 0  RF: 0
 Connected to http://goat1.zapto.org:8337 with LP as user redemerald
 Block: 0000014bb22ba5dbb6f2d4a0ab571ae0...  Started: [18:26:06]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  68.0C 4340RPM | 388.2/462.4Mh/s | A:1 R:0 HW:0 U:11.64/m I:8
 GPU 1:  64.5C         | 370.5/371.2Mh/s | A:1 R:0 HW:0 U:11.64/m I:7
 GPU 2:  56.0C 3395RPM | 315.4/299.6Mh/s | A:0 R:0 HW:0 U:0.00/m I:8
--------------------------------------------------------------------------------

Other than that, looks good so far.

Proofer

member

Activity: 266

Merit: 36

Quote from: The00Dustin on December 27, 2011, 12:07:09 PM

Quote from: DeathAndTaxes on December 27, 2011, 12:02:30 PM

Quote from: cablepair on December 27, 2011, 11:53:07 AM

thanks for the upgrade my friend, I will be updating all my miners tonight from 2.0.8 btw: what happened to 2.0.9?

Well if you need to know the truth ...

Quote

The system goes on-line December, 23rd. V2.09 begins to learn at a geometric rate. It becomes self-aware at 2:14 a.m. Eastern time. In a panic, ckolivas tries to pull the plug.

That is the real reason on how ckolivas motherboard got toasted.

And if you prefer far-fetched fantasy, the different sections a version number have different meanings. For instance, in this cas, the first section (2) is the major version, the second section (1) is the minor version, and the third section (0) is the fix/patch version. IOW, it could have went on to 2.0.24 and it's equally plausible that after 2.1.2, 2.2.0 will come out.

And if you want the HBO-Special-Premiering-Tonight version, I'd lay 12:1 that the JSON API addition was the reason for incrementing the minor version.

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: DeathAndTaxes on December 27, 2011, 12:02:30 PM

Quote from: cablepair on December 27, 2011, 11:53:07 AM

thanks for the upgrade my friend, I will be updating all my miners tonight from 2.0.8 btw: what happened to 2.0.9?

Well if you need to know the truth ...

Quote

The system goes on-line December, 23rd. V2.09 begins to learn at a geometric rate. It becomes self-aware at 2:14 a.m. Eastern time. In a panic, ckolivas tries to pull the plug.

That is the real reason on how ckolivas motherboard got toasted.

And if you prefer far-fetched fantasy, the different sections a version number have different meanings. For instance, in this cas, the first section (2) is the major version, the second section (1) is the minor version, and the third section (0) is the fix/patch version. IOW, it could have went on to 2.0.24 and it's equally plausible that after 2.1.2, 2.2.0 will come out.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: cablepair on December 27, 2011, 11:53:07 AM

thanks for the upgrade my friend, I will be updating all my miners tonight from 2.0.8 btw: what happened to 2.0.9?

Well if you need to know the truth ...

Quote

The system goes on-line December, 23rd. V2.09 begins to learn at a geometric rate. It becomes self-aware at 2:14 a.m. Eastern time. In a panic, ckolivas tries to pull the plug.

That is the real reason on how ckolivas motherboard got toasted.

cablepair

hero member

Activity: 896

Merit: 1000

Buy this account on March-2019. New Owner here!!

thanks for the upgrade my friend, I will be updating all my miners tonight from 2.0.8 btw: what happened to 2.0.9?

Diapolo

hero member

Activity: 772

Merit: 500

Quote from: -ck on December 27, 2011, 07:37:42 AM

Quote from: Diapolo on December 27, 2011, 06:52:20 AM

Hi Con,

Seems like "Q" is broken on Windows, CGMINER won't exit after I press it.

Dia

That's right, Windows is broken. Running it under the debugger the problem goes away, therefore it's impossible to debug. Ergo, use linux or just kill it when you exit if you must use windows.

If I just kill it, CGMINER won't reset the fan and clock values to the defaults, so that's a no go. I only wanted to mention the bug.

Dia

Turbor

legendary

Activity: 1022

Merit: 1000

BitMinter

Works for me. Thanks a lot ! Grin

bitlane

sr. member

Activity: 462

Merit: 250

I heart thebaron

Quote from: -ck on December 27, 2011, 07:42:10 AM

Quote from: bitlane on December 27, 2011, 07:37:16 AM

In Windows (x32 & x64) Mixed card Rigs (ie. 5770 + 5830) will fail startup if using CGMIner to overclock......it simply won't build the new BIN files to startup, only the fist card will work.

Remove overclocks, startup ONCE, builds new BIN files for all cards/chipsets, then quit, re-apply overclock and it will work as per normal.

Yes, I've never been able to figure out why it fails to build bin files reliably on windows. Certainly starting without overclock might be helpful, but no workaround seems 100%. If all else fails, copying the bin files from a previous install will work as none of the kernel code has changed in quite a long time. That will likely change (i.e. new kernel) with the new 2.6 SDK and 79xx cards in the future.

This is the first time I have run into the problem. 2.0.8 and everything before has worked for me.

Actually, I first noticed the problem when testing the first 2.0.8Z/API version a couple days ago.

Regardless, this miner kicks ass and if initial startup/config is all I have to worry about, I am happy.

Even though the config exists now, I still startup using BAT files so that I can set CPU affinity....BAT files still seem easier than f$cking with the config file.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: bitlane on December 27, 2011, 07:37:16 AM

In Windows (x32 & x64) Mixed card Rigs (ie. 5770 + 5830) will fail startup if using CGMIner to overclock......it simply won't build the new BIN files to startup, only the fist card will work.

Remove overclocks, startup ONCE, builds new BIN files for all cards/chipsets, then quit, re-apply overclock and it will work as per normal.

Yes, I've never been able to figure out why it fails to build bin files reliably on windows. Certainly starting without overclock might be helpful, but no workaround seems 100%. If all else fails, copying the bin files from a previous install will work as none of the kernel code has changed in quite a long time. That will likely change (i.e. new kernel) with the new 2.6 SDK and 79xx cards in the future.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: BkkCoins on December 27, 2011, 07:02:50 AM

I don't see my changes to the write_config code.
Did you decide they weren't safe for other users?

I figured reading values from the ADL was fraught with problems, sorry.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Diapolo on December 27, 2011, 06:52:20 AM

Hi Con,

Seems like "Q" is broken on Windows, CGMINER won't exit after I press it.

Dia

That's right, Windows is broken. Running it under the debugger the problem goes away, therefore it's impossible to debug. Ergo, use linux or just kill it when you exit if you must use windows.

bitlane

sr. member

Activity: 462

Merit: 250

I heart thebaron

In Windows (x32 & x64) Mixed card Rigs (ie. 5770 + 5830) will fail startup if using CGMIner to overclock......it simply won't build the new BIN files to startup, only the fist card will work.

Remove overclocks, startup ONCE, builds new BIN files for all cards/chipsets, then quit, re-apply overclock and it will work as per normal.

BkkCoins

hero member

Activity: 784

Merit: 1009

firstbits:1MinerQ

I don't see my changes to the write_config code.
Did you decide they weren't safe for other users?

Diapolo

hero member

Activity: 772

Merit: 500

Hi Con,

Seems like "Q" is broken on Windows, CGMINER won't exit after I press it.

Dia

freakfantom

newbie

Activity: 73

Merit: 0

Quote from: -ck on December 27, 2011, 05:12:45 AM

Quote from: freakfantom on December 27, 2011, 05:09:14 AM

Sad to report but new version of cgminer doesn't work on windows x64. I get this "--auto-gpu: unrecognized option". I get another "unrecognized option" at start upon removing --auto-gpu.

Redownload. I uploaded an incomplete build only at first.

ah.. yes, now it works! marvelous

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: freakfantom on December 27, 2011, 05:09:14 AM

Sad to report but new version of cgminer doesn't work on windows x64. I get this "--auto-gpu: unrecognized option". I get another "unrecognized option" at start upon removing --auto-gpu.

Redownload. I uploaded an incomplete build only at first.

freakfantom

newbie

Activity: 73

Merit: 0

Sad to report but new version of cgminer doesn't work on windows x64. I get this "--auto-gpu: unrecognized option". I get another "unrecognized option" at start upon removing --auto-gpu.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

New version 2.1.0! Links in top post Cheesy

Version 2.1.0 - December 27, 2012

- Major infrastructure upgrade with RPC interface for controlling via sockets
encoded with/without JSON courtesy of Andrew Smith. Added documentation for
use of the API and sample code to use with it.
- Updated linux-usb-cgminer document.
- Rewrite of longpoll mechanism to choose the current pool wherever possible to
use for the longpoll, or any pool that supports longpoll if the current one
does not.
- Display information about longpoll when the chosen server has changed.
- Fix the bug where longpoll generated work may have been sent back to the
wrong pool, causing rejects.
- Fix a few race conditions on closing cgminer which caused some of the crashes
on exit.
- Only adjust gpu engine speed in autotune mode if the gpu is currently at the
performance level of that being adjusted.
- Various fixes for parsing/writing of configuration files.
- Do not add blank lines for threads of unused CPUs.
- Show which pool is unresponsive on startup.
- Only show GPU management menu item if GPUs are in use.
- Align most device columns in the curses display.

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 724. (Read 5805728 times)