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

Heh whoops, I just got a crash so it's not quite there yet  

LOL.

My kids have just reached an age where they're quoting this too so it's very topical.  Thanks 

That's the main network difficulty it uses to calculate, btc, so it's the real thing. Your best share should show you something real big.

I don't know if this unique to my rig (7 BFL's on an Atom ITX running Ubuntu 12.10 Server) but I have been using the same steps to git clone and compile going back many versions. Never any issues. Starting today with 2.11.1 when I would start my same cgminer script I have been using it would say "./cgminer: -S: unrecognized option". I removed the "-S auto" from my script and all is good. Just passing the info in case anyone runs into it.

What's your Best share: ?

tried that and still had the same problem

1 BTC Block, u dont know if the Pool does MM (Merged Mining) or not, atleast not @ the protocol level.

does this mean solved 1 BTC Block or may it be a NMC Block?

Awesome thanks!

Hello Ckolivas,

Thanks for the redirect.

I went over the GPU device issues section and did not locate anything I have not tried yet.

I know I am using the correct platform number (--gpu-platform 1) and the -d 0 and -d 1 switches are correct.

In any case, some problems are not cost effective to solve. You seem to have your hands full with the 2.11.1 release and nobody else has yet surfaced with an answer.

So here is how I solved it:

I set the 5970 card in a newer motherboard, went back to cgminer 2.10.5, pointed it at coinotron, and started mining PPC at speeds of about 750+ and 71 degrees.

I will trade the PPC for LTC and in the end we will have the litecoins I was trying to produce. I will run 5830's in the older motherboard.

*** Problem solved ***

 

--hotplug 0

I have a system that utilizes both gpus and fpgas and I want to run one cgminer instance for gpus and another for fpgas.  Starting in 2.11.0 with the new usb subsystem, I am unable to start an instance of cgminer for just the gpus.  Whenever I try to start the instance for gpus only, cgminer displays "MTX: BitForce USB failed to get cgminer-usb..." and exits.  Is there any way to disable the usb detection like how "-S noauto" used to work?

New release: v2.11.1, March 7th 2013

Keep building on the changes required for BFL SC when it comes out, adding new features and fixing bugs with the new 2.11 branch... This is still the unstable development version but is proving quite stable for my testing so far.


Human readable changelog:

Faster startup now when pools are slow, connecting to the first pool available!
Fixed some stratum bugs which would lead to weird disconnects when pools were slow.
Improved the mining resume support for stratum.
Added the show message feature of stratum (which I don't believe any pool uses yet?).
Lots of other minor stratum fixes and improvements.
Added the --hotplug (time) feature if you have hardware that has random stalls every time the usb devices are probed (default is 5 seconds).
Extra API features.
Random bugfixes.


Full changelog:

- Shorten the time before keepalive probes are sent out and how frequently
they're sent with stratum curls.
- Only set stratum auth once to prevent multiple threads being started.
- Display select return value on select fail in stratum thread.
- Clear the socket of anything in the receive buffer if we're going to retry
connecting.
- Allow pools to be resuscitated on first startup by the watchpool thread.
- Check all pools simultaneously at startup switching to the first alive one to
speed up startup.
- Clear just the socket buffer when we don't care what is left in a stratum
socket.
- Clear the stratum socket whenever we are closing it since the buffer is going
to be reused.
- Do not continue work from a stratum pool where the connection has been
interrupted.
- Reset stratum_notify flag on suspend_stratum as well.
- Close any sockets opened if we fail to initiate stratum but have opened the
socket.
- Close any existing stratum socket if we are attempting to restart stratum so
the pool knows the connection has gone.
- Show mechanism of stratum interruption if select times out.
- Make stratum connection interrupted message higher priority to be visible at
normal logging levels.
- Implement client.show_message support for stratum.
- API add 'Network Difficulty' to 'coin'
- Setup BFLSC support
- API use control_lock when switching pools
- Make sure to retry only once with noresume support for stratum.
- Instead of keeping track of when the last work item was generated to keep
stratum connections open, keep them open if any shares have been submitted
awaiting a response.
- usbutils.c copy full size to 'Last Command'
- configure - set USE_USBUTILS when usbutils is required and use it in the code
- Clear last pool work on switching pools if the current pool supports local
work generation or we are in failover only mode.
- make rw locks: mining_thr_lock and devices_lock
- Release MMQ device only once (not 4 times)
- api.c fix MSG overlap
- Hotplug - allow setting interval via --hotplug or API
- curses - fix - put a dev_width inside #ifdef
- usb_cleanup() use correct locking mechanism
- Implement and use usb_cleanup() on shutdown or restart
- miner.php report 'Last Valid Work' as time before request
- API - return Last Valid Work
- api -> drv
- ZTX bug set missing drv_id

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

Yes. What pool and protocol? Some pools have been really struggling of late so it's the likely culprit.

hi,
i look at my log for cgminer 2.11.0 ( win7 x64 ; GPU drv - 12.6 ; SDK 2.8 )
and i see something strange :
should I be worried about this messages?

I used cgminer since a long time to mine BTC.

Now I'd like to mine some LTC. I use Windows7 and a pair of 7970s.

What's the correct command line to use cgminer to mine LTC?

I like your style.
Search for "GPU DEVICE ISSUES and use of --gpu-map" in you README poster. I can't tell exactly how to set it up for you without access to your machine but that is where your remaining issues lie I believe.