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

Heh - timed that well (badly)
I tried to upload 2.10.1a at the same time you posted ... then spent a while messing around creating a new git cgminer-binaries
The download section no longer allows uploading new content and github will be deleting it in 90 days

cut/paste ...

2.10.1
An Xubuntu 11.04 x86_64 executable is in my github called cgminer-2.10.1a
https://github.com/kanoi/cgminer-binaries
(it also works on Fedora 16 and 17)

Yes I had to create a seperate git for the binaries since github has disabled the download feature

To get the binary simply:
wget https://github.com/kanoi/cgminer-binaries/raw/master/cgminer-2.10.1a
chmod +x cgminer-2.10.1a
md5sum cgminer-2.10.1a
f81c40434b1a88a8c5f437033e3e640e  cgminer-2.10.1a

For anyone who didn't realise, it's just the executable file to put in place of 'cgminer'
Nothing else needs changing
First get and extract the full binary release from ckolivas and then copy my file in place of 'cgminer'

No problems so far (50 minutes) on my GPU, MMQ or 'BFL+2xICA'

Since I'm no longer GPU mining, I just run it for a while on my single 6950 to see what happens

BFL+ICAs (1.6GH/s) on OzCoin Stratum with fixed 8 diff
MMQ (795MH/s) on OzCoin Stratum with fixed 8 diff

The same configure options as cvolivas' binary version
In case anyone was wondering:
CFLAGS="-O2 -W -Wall" ./autogen.sh --enable-icarus --enable-bitforce --enable-ztex --enable-modminer --enable-scrypt
make clean
make

Perfect - thanks Kano. Sorted.

https://bitcointalksearch.org/topic/m.1180029

Also it failed to failback.  us1 came back last night, but as of this morning cgminer is still mining on us2 (even though the pool management screen shows all pools as alive).  I thought that in the default failover policy it was supposed to failback to a pool higher up the list, once it's been stable for a little while?

roy

Sorry for posting here, I haven't found the Stratum thread yet (the search leads me to the wrong results), but thank you both for the tip.
I'm already digging into it.

As ckolivas said, there's no compilation involved. Please follow instructions from https://github.com/slush0/stratum-mining-proxy , it should work even on dd-wrt (it requires only python 2.6/2.7).

Sorry for OT.

This is not the right place. Check the stratum thread. And the proxy is in python so needs no compiling, just python.

I don't know if this is the right place to ask this, but has anyone tried to compile the stratum proxy for dd-wrt?
Is it possible?
How could I setup the compile environment?

Thank you all in advance.

New version: 2.10.1, 14th December 2012

Mainly to try and fix the windows+stratum disconnect bug.


Human readable changelog:

Converted the curl code that was where all the crashing on windows was occurring into the raw code equivalents. Hopefully this quashes the crashes with stratum on various flavours of windows.
Ztex and MMQ updates.
Miner.php updates
New API features and code improvements.


Full changelog:

- Check for EWOULDBLOCK when supported in send and recv as well.
- Use the raw send() command instead of curl_easy_send since curl raw socket
usage introduces random bugs on windows.
- Use raw recv() command in place of curl_easy_recv since the curl
implementation introduces random bugs on windows builds when the recv fails.
- miner.php when displaying a single rig, add prev/next rig buttons if they
exist, next to refresh
- miner.php allow custom page joins for STATS
- API show if pool has GBT (so people know not to use that pool)
- miner.php - include windows easyphp link
- driver-ztex: use the correct size for the swap array
- API stats - display pool byte transfer stats
- Pool store data transfer stats
- README ModMiner dependency
- Benchmark incorrect work size
- ChangeLog refer to NEWS
- MMQ handle over temp differently and hash longer
- driver-ztex: search the complete noncerange based on the actual speed
- README - update ModMiner details
- API-README update
- api use a dynamic io buffer, truncated before it reaches the current ~64k
limit

I'm running cgminer 2.10.0 with us.eclipsemc.com:3333 instead of adding server numbers like us1.eclipsemc.com:3333 on Win7...I see less disconnects this way.

Despite the windows+stratum bugs that people are still encountering with 2.10.0, they are no worse than with 2.9.7, and no real showstopper bugs have shown up on 2.10.0 apart from lots of leaking shares when the primary pool is getwork without rolltime (which pools are still that bad!?). So despite the fact that windows+stratum disconnect is still problematic, I am going to raise the status of 2.10.0 to stable since it is no worse than the 2.9 branch. The substantial changes in 2.10 were all actually in the scheduling of work and there has not been a significant bug there as far as I can tell.

I will continue to pursue these windows bugs till no one is mining on windows any more... uh I mean till hopefully I can find wtf is uniquely wrong on windows. I'm so annoyed that 99% of my debugging effort is now directed to windows specific issues that I find myself wishing that I had made cgminer linux only. I could probably develop cgminer much faster if it was possible to drop windows support. Of course that's crazy talk...

EDIT: Note I will likely be releasing 2.10.1 shortly anyway.

Coincidence related to something else maybe like a driver change. The GPU code hasn't been touched in any significant way in many months.

The only openCL implementation for nvidia devices is through the cuda driver, meaning it goes cgminer->opencl->cuda->GPU. There is no way to do native cgminer->cuda->GPU. It's not at all worth it since the performance is identical, and they earn no money and GPU mining is on the way out. Throw me 1000 BTC and I'll make you a native cuda version, but it's not going to be of any advantage.

That's correct.

Which is good because that's what it's supposed to be. Performance with current hardware (i.e. no asics) should have maximised with stratum support already. The changes in 2.10 are for the future.

You only get a windows+stratum crash after 2.8.7?

Performance for me exactly like 2.9.x versions.

normal, its linux

Sorry, I had a brain error when typing that, but I am indeed using http://api.bitcoin.cz:8332 (which auto-upgrades to Stratum anyway)

I'll switch to the using the stratum+tcp URL if that's prefered.

roy