No, nvidia and amd need 2 instances with different  gpu-platform values.

It's only a postulated cause for instability, but probably >=7.25 which have the keepalive features.

Did you do a proper reconfigure of xorg.conf?


Did you export your display variable after xorg is started before mining?

Indeed, many pools moving back to 0.7 was a terrible blow for the progress all the devs have been working hard to achieve.

I see DB upgrading their bitcoind at last, so I doubt they will be holding people back, even with people running unattended ancient versions of mining software (still find it funny people mine at one pool without a single backup even now...).

It works on 12.04 as well. I can't attest to its stability as such though.

Want to make a poll to determine that?

I am tentatively elevating the status of 2.11.2 to stable.

It is worth reminding people that on windows+fpgas you will need to install a winusb driver as it says in the fpga readme compared to running versions of cgminer <2.11 which used the old serial interface.

It is also worth mentioning that stability seems to be compromised when built with an older version of libcurl.

The alt cryptocurrency subforum didn't seem to do so well either. They seemed to be very happy about it, not realising the irony that the purpose for alt cryptocurrencies were to push development ideas, yet it was their stagnancy on old bitcoin code that protected them from such a problem. Go figure.

BTCGuild's stratum ignores the password anyway so I've just been using x as the password.

Let no one say that pooled mining is bad for bitcoin now, given how quickly the pool operators corrected this potential disaster and coordinated its recovery... It would have taken a lot longer for thousands of solo miners to have corrected it.

Holy crap 

For what it's worth, I've moved my mining to this pool for now. Eleuthria you need to add a donation% option to allow us to donate above the usual pool fee.

Use the --gpu-platform option in cgminer. You need to be running 2 instances of cgminer, one for nvidia devices and one for amd devices.

Be wary of FUD 

迷い猫オーバーラン!

If they specify the stratum protocol as stratum+tcp:// it will continue to try to connect to stratum indefinitely. The problem is many people don't specify that or even specify http:// and cgminer does its best to guess what it should be.

The benefits? Realistically: many sleepless nights, headaches, heartaches, trolling, frustration, loss of money and the very slim chance of making a profit...

I wouldn't have said this 6 months ago, but right now I think there is room for more pools with the hashrate jump and the new technical challenges of keeping up with the hardware revolution. That said, the effort required to get up to speed as a meaningful alternative pool is massive and requires a lot of know how of both regular server and networking scalability issues, as well as unique bitcoin mining and its protocol scalability issues.

The 2 usual reasons for this are: Mixed versions of different driver files installed, and virus software interfering.

New version: 2.11.2, 9th March 2013

Keep on quashing bugs in 2.11 series and developing further, hopefully a stable release soonish (this one if we're lucky!).


Human readable changelog:

Numerous fixes to the parallel pool test startup code which should work robustly now, including fixes for crashes and failure to fall back to pools when they come back to life.
Ability to start work on a backup pool much sooner once a stratum pool gets an interrupted connection.
Hopefully fixes for API related crashes.
Fixed a memory leak with GPU share submission.
More named threads on operating systems that support them.
Make AMD APP SDK 2.8 GPUs use diablo kernel for non-Tahiti chipsets.
Fixed an ancient bug where if you have multiple OpenCL platforms installed (eg Intel and AMD) with no devices on the highest numbered one, cgminer would refuse to work on any devices.


Full changelog:

- Whitelist AMD APP SDK 2.8 for diablo kernel.
- Cope with the highest opencl platform not having usable devices.
- Fix memory leak with share submission on GPU work structures as discovered by
twobitcoins.
- usb_cleanup() without locking.
- Use curl_easy_cleanup to close any open stratum sockets. (Spotted by luke-Jr)
- Show pool number in switch message
- Don't start testing any pools with the watchpool thread if any of the test
threads are still active.
- Set sockd to false should curl setup fail on stratum.
- Close any open sockets when reusing a curl handle and reopen the socket
whenever we're retrying stratum.
- Set pool died on failed testing to allow idle flag and time to be set.
- Remove unused pthread_t typedefs from struct pool.
- Perform pool_resus on all pools that are found alive with the test pool
threads.
- Use pool_unworkable in select_balanced as well.
- Differentiate pool_unusable from pool_unworkable.
- Keep a connection open on higher priority stratum pools to fail back to them.
- Rename threads according to what pool they're associated with as well.
- Set the wrong bool in pool_active
- Start the stratum thread only if we successfully init and authorise it,
otherwise unset the init flag.
- Make the initialisation of the stratum thread more robust allowing the
watchpool thread safe access to it after the stratum thread is started.
- API no longer ignore send() status
- API make the main socket non-static