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

Gosh guys, Do we Not have a donation address for ckolivas? When there was the change from 2.7->2.8 and we got that Totally Uneccesary "Best Share" stat, I'd of set my donation to 1% for two days.
I really think that CGminer should have a Prompt of "Could you please help the developer by enabling .001% hashrate donation? There are no side affects"

Seriously, Back when CGminer prompted for "donation set to 0%, Please consider atleast 0.00x% :"(" it made me want to donate, Im sure that if Ckolivas Gets SOMETHING for doing all this work, Then he'll continue the work.

What would you all do if CGminer just Stopped being updated? For awhile we would all be just fine, But imagine if it was discontinued Before stratum, Or even before LongPolling
Just donate!

You've got my vote to remove GBT support.  Just because it's available doesn't mean it has to be implemented.  That's how the marketplace works. 

M

That's what I like to hear.

Do be careful though. That poison known as GBT may strike with unexpected bugs if one of your backup pools uses GBT.

Best current compromise is to use as many stratum pools as possible with their direct addresses and add --fix-protocol in case one of your backup pool uses GBT.

Bottom line: I really regret even implementing GBT for cgminer, as it was a lot of work, introduced a new set of bugs, and has earned me zero donations despite a lot of work. I'm seriously considering just disabling or even backing out GBT support.

Yay the 2.9.4 works great with stratum and eclipse!

Hashpower has LP again!

Everything is working as expected.

the problem was "device" : "0", and 1 and 2 .. listed at the end of the .conf file   Removed all "device" : .. lines and all runs fine now   Thanks

Well, you still need to set up all of your configuration in the conf file too...

-- Smoov

Im on it, I'll edit with news soon   thanks

edit 1 : All GPU are OFF when starting cgminer with -c doom.conf  :/

this rig have 4 GPU and 1 FPGA, only FPGA runs on start now !!

On Win7, I have several different shortcuts set up, which loads up different conf files depending on what I want to mine.

The only command line option is similar to "-c cgminer(BTC).conf", with all of my other options in the conf file.

Give that -c flag a shot?

-- Smoov

cgminer.conf edited manually, have change Engine and Memory parameters and it does'nt apply on loading CGMINER  :S
Dont want to use your precious time CKOLIVAS, was in hope someone else could help.. you have done so much work with CgMiner !

Edit : I'll try setting my Engine and Memory clock in the commandline that start CGMINER = Issue sould be relsoved 

Thank you very much for your very nice miner, by far my favorite !

It saves command line parameters, not things you change later on.

I've searched the forum and this thread and could not find an answer..

Settings/Write Config ENTER to default cgminer.conf did not save engine and memory clock settings.

Each time I restart CGMINER I need to set memory and GPU clocks.

I'm using an old version (2.7.5) maybe this is an issue that have already been adressed.
I've also tried to edit manualy the cgminer.conf file, not effective.

Sorry for maybe noob question, I've search for an answer before asking !

Thanks anyone for your time.

Thanks for the info.  That machine is just an old MB with a card plugged in. I guess I need to drag a monitor over to it and upgrade it.  My other rigs are running 2.7.6 with no problems. My GPU days are numbered anyway...

Quick question @ckolivas

Just flashed over to check that all miner are up - saw this...




What is "Harmful miner version detect" - using 2.6.1 on bitminter?

I run Linux 10.10, don't have any backup pools, don't usually upgrade anything, because my rigs just mine continuously with no problems.

I probably do.  I don't know which ones use GBT and which ones don't.

M

Did you have a GBT pool as a backup somewhere? I think there's a crash unique to pools that send GBT info. If so, --fix-protocol should prevent it, so you'll have to specify the stratum pools' urls/ports directly.

alas, 2.9.4 crashed on me today on my windows 8 box while pointing to oz.  11 hours before I got home from my day job.

I'm going to try --verbose and see if it stops doing that.

M

It looks like stratum backup pools aren't detected as alive when specified with a stratum+tcp:// URL (though, strangely, they work fine if you put in an http:// URL pointing to the stratum port).

At least with EMC.

ETA, unless I don't understand what a stratum URL is supposed to look like.

With the default (failover) strategy, if I specify my pools as follows then only whichever pool I put first is detected as alive (and if that's down it *doesn't* failover).

stratum+tcp://us1.eclipsemc.com:3333
stratum+tcp://us2.eclipsemc.com:3333
stratum+tcp://us3.eclipsemc.com:3333

If I specify them as follows then it connects with stratum, detects all pools live, and failover seems to work:

http://us1.eclipsemc.com:3333
http://us2.eclipsemc.com:3333
http://us3.eclipsemc.com:3333

ETA again: Although to be fair some of the evidence that lead me to the above conclusion was collected from a version of git master HEAD somewhere between 2.9.3 and 2.9.4.  But I'm certainly seeing backup pools report as down in 2.9.4 - can't say for sure that failover is actually not working.

FFSake can you stop with the FUD - Eligius and Bitminter are not decentralized - learn English, not whatever warped, deluded, zealot language you use.

There is a perfectly simple reason to use p2pool and not go anywhere near ANY centralised GBT pool like Eligius or Bitminter and that is the 2 orders of magnitude larger amount of data GBT transfers across the internet to your miner compared to the old getwork or new stratum pool protocol.
Even a bitcoin dev has said that the GBT data design is not designed for a WAN (or even a LAN)
... as per my Issue I raised on the bitcoin code (where you sneaked in your botnet support into bitcoind/GBT)
https://github.com/bitcoin/bitcoin/issues/1985
I also do not understand why you supported botnets on Eligius and now added support of them into bitcoind that everyone now has in their bitcoind

Bitminter and Eligius ARE centralised - there is one place that controls all the work - the pool - just like every other non-p2pool pool does.
On Eligius GBT, the centralised pool decides what is valid work and what is not valid work.
On p2pool it is the p2peers that decide ... and if suddenly half the peers decide one type of work is valid and the other half decide a different type of work is valid, you will then get 2 p2pools running with 2 different sharechains
Be it half the miners or just one miner, the miner can keep mining no matter what it decides is valid - each sharechain is simply the list of p2pool miners that agree in it's contents ... and that is by definition decentralised.

None of those (AFAIK) support decentralized mining, though. Nor is it really practical as GBT's bandwidth use is absurd with p2pool's 10 second blocks.
There's no reason to prefer p2pool over Eligius or Bitminter anyway, so long as you're decentralized mining.