OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[planman]

Hello  

I was wondering if anyone could help me trouble shoot some trouble I am having with (I think) a cgminer mapping issue.

[SNIP]

You are having multiple problems. Does the 5970 work or are you another hopeful that bought a dead GPU? Most of these are way beyond working status thanks to being abused by miners. Do you have enough system ram to scrypt mine on that many GPUs? Did you read the EXTENSIVE section on using --gpu-map in the readme?

Hello Ckolivas,,

I tested the 5970 in a new Gigabyte motherboard about 2 hours ago after I did the post. Using CGMINER 2.10.5 the card ran about 350 khash/gpu. There was trouble with one of the GPUs running very hot. I solved the heat problem by installing fresh CPU grease, cleaning the lint out of the fins, and adding a 90mm HP server case fan that blow serious air (140 CFM). The card itself appears to be in good shape, it runs.

The system I am running has 4GB ram.

I spent about 4 hours reading through your readme file today. I run 11 cards in my rigs and have printed copies of your readme file on the wall. I have also been through almost every page of this and several other threads. I take notes and change a single setting at a time to better understand what is happening. I also run a watt meter and check voltages and power draws in the rails using a meter.

I understand the --gpu-platform command. I use the --gpu-platform command to run the radion 5380 card that is working. I have problems when I swap out the 5830 card and install the 5970.

I agree with you that it might be faster/easier/cheaper to use a pair of 5850's in place of a 5970. I did a google search, read the readme file again, and searched the support thread but did not locate my situation. I figured if I posted perhaps someone else might understand better than I do what is going. I thought it was kind of a cool technical problem to learn from. I did not mean to waste your time or appear helpless. I want to make it work!

Can you give me a quick clue as to the problems you see? I have done all I can think to do with --gpu-platform, the -d switch, and --gpu-map

I will share the solution, document it as best I can, and try to grow the knowledge base.

(Or I will just use it as a space heater)

Thank you,

[1714234830]

1714234830

[-ck]

have printed copies of your readme file on the wall.

I like your style.

Can you give me a quick clue as to the problems you see? I have done all I can think to do with --gpu-platform, the -d switch, and --gpu-map

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.

[Radacoin]

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?

[nitrox]

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 :

Code:

 [2013-03-07 11:50:19] Rejected 51eafd38 Diff 3/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non
.....
 [2013-03-07 11:50:42] Rejected b1ac8474 Diff 1/1 GPU 1 pool 0 ((-2, u'Share is above target 
.....
 [2013-03-07 11:50:19] Rejected 51eafd38 Diff 3/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....
 [2013-03-07 11:50:42] Rejected b1ac8474 Diff 1/1 GPU 1 pool 0 ((-2, u'Share is above target 
.....
 [2013-03-07 11:52:54] Rejected 6ae3257b Diff 2/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....
 [2013-03-07 11:54:10] Rejected 04dead4d Diff 52/1 GPU 0 pool 0 ((-2, u'Share is above target 
.....
 [2013-03-07 11:58:58] Rejected d5ec96b4 Diff 1/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....
 [2013-03-07 12:04:15] Rejected efedb124 Diff 1/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....
 [2013-03-07 12:17:34] Rejected 0638fb44 Diff 41/1 GPU 0 pool 0 ((-2, u'Incorrect size of ext 
.....
 [2013-03-07 12:33:23] Rejected 1fb0a7ca Diff 8/1 GPU 1 pool 0 ((-2, u'Incorrect size of ext 
 .....
[2013-03-07 12:34:55] Rejected 588fdf7c Diff 2/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....
 [2013-03-07 12:38:54] Rejected 28a8a413 Diff 6/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....
 [2013-03-07 11:52:54] Rejected 6ae3257b Diff 2/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....
 [2013-03-07 11:54:10] Rejected 04dead4d Diff 52/1 GPU 0 pool 0 ((-2, u'Share is above target 
.....
 [2013-03-07 11:58:58] Rejected d5ec96b4 Diff 1/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....
 [2013-03-07 12:04:15] Rejected efedb124 Diff 1/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....
 [2013-03-07 12:17:34] Rejected 0638fb44 Diff 41/1 GPU 0 pool 0 ((-2, u'Incorrect size of ext 
.....
 [2013-03-07 12:33:23] Rejected 1fb0a7ca Diff 8/1 GPU 1 pool 0 ((-2, u'Incorrect size of ext 
.....
 [2013-03-07 12:34:55] Rejected 588fdf7c Diff 2/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....
 [2013-03-07 12:38:54] Rejected 28a8a413 Diff 6/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non 
.....

should I be worried about this messages?

[-ck]

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 :

Code:

 [2013-03-07 11:50:19] Rejected 51eafd38 Diff 3/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non
.....

should I be worried about this messages?

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

[kano]

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?

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

[-ck]

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

[rkozola]

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?

[PatMan]

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?

--hotplug 0

[PatMan]

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

Great work guys, this has cured my usb issues - many thanks!

Kano, I used your Xubuntu binary 2.11.0a with this latest release and everything seems fine - is this ok do you think? I can live with the wrong release version being displayed.....lol

[planman]

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 :

Code:

 [2013-03-07 11:50:19] Rejected 51eafd38 Diff 3/1 GPU 1 pool 0 ((-2, u'Duplicate share', Non
.....

should I be worried about this messages?

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

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 ***

 

[Aseras]

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.

Awesome thanks!

[ewibit]

[2013-03-07 17:55:32] Pool: http://xxx:yyy                   
[2013-03-07 17:55:32] SOLVED 1 BLOCK! 

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

[K1773R]

[2013-03-07 17:55:32] Pool: http://xxx:yyy                    
[2013-03-07 17:55:32] SOLVED 1 BLOCK!  

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

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

[crazyates]

[rkozola]

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?

--hotplug 0

tried that and still had the same problem

[os2sam]

[2013-03-07 17:55:32] Pool: http://xxx:yyy                   
[2013-03-07 17:55:32] SOLVED 1 BLOCK! 

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

What's your Best share: ?

[BitMinerN8]

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.

[-ck]

[2013-03-07 17:55:32] Pool: http://xxx:yyy                   
[2013-03-07 17:55:32] SOLVED 1 BLOCK! 

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

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.

[-ck]

LOL.

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