Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 400. (Read 5806004 times)
March 08, 2013, 12:24:49 AM
what is the difference between win32.zip version and cgminer-2.11.1-x86_64-built.tar.lrz
March 07, 2013, 05:54:02 PM
I am using cgminer 2.10.4 for Litecoin mining. win7x64. AMD 7970. various versions of Catalyst (12.10, ... , 13.1, 13.2)
On https://github.com/litecoin-project/litecoin/wiki/Mining-hardware-comparison there's a 7970 with 682 kHash/s
clock: 1000MHz, mem clock: 1600MHz
command line args are: --shaders 2048 --thread-concurrency 8192 -I 13 -g 2 -w 256
I'm not getting more than 550 kHash/s with the exact same settings.
Is 682 a typo (-> 582) - or is it really possible?
I'd say it's unlikely, but I don't really play with scrypt much any more. Perhaps you just need more system ram.On https://github.com/litecoin-project/litecoin/wiki/Mining-hardware-comparison there's a 7970 with 682 kHash/s
clock: 1000MHz, mem clock: 1600MHz
command line args are: --shaders 2048 --thread-concurrency 8192 -I 13 -g 2 -w 256
I'm not getting more than 550 kHash/s with the exact same settings.
Is 682 a typo (-> 582) - or is it really possible?
How much would I need for 2 x 7970 ?
March 07, 2013, 05:46:18 PM
I am using cgminer 2.10.4 for Litecoin mining. win7x64. AMD 7970. various versions of Catalyst (12.10, ... , 13.1, 13.2)
On https://github.com/litecoin-project/litecoin/wiki/Mining-hardware-comparison there's a 7970 with 682 kHash/s
clock: 1000MHz, mem clock: 1600MHz
command line args are: --shaders 2048 --thread-concurrency 8192 -I 13 -g 2 -w 256
I'm not getting more than 550 kHash/s with the exact same settings.
Is 682 a typo (-> 582) - or is it really possible?
I'd say it's unlikely, but I don't really play with scrypt much any more. Perhaps you just need more system ram.On https://github.com/litecoin-project/litecoin/wiki/Mining-hardware-comparison there's a 7970 with 682 kHash/s
clock: 1000MHz, mem clock: 1600MHz
command line args are: --shaders 2048 --thread-concurrency 8192 -I 13 -g 2 -w 256
I'm not getting more than 550 kHash/s with the exact same settings.
Is 682 a typo (-> 582) - or is it really possible?
How much would I need for 2 x 7970 ?
March 07, 2013, 05:33:27 PM
I am using cgminer 2.10.4 for Litecoin mining. win7x64. AMD 7970. various versions of Catalyst (12.10, ... , 13.1, 13.2)
On https://github.com/litecoin-project/litecoin/wiki/Mining-hardware-comparison there's a 7970 with 682 kHash/s
clock: 1000MHz, mem clock: 1600MHz
command line args are: --shaders 2048 --thread-concurrency 8192 -I 13 -g 2 -w 256
I'm not getting more than 550 kHash/s with the exact same settings.
Is 682 a typo (-> 582) - or is it really possible?
I'd say it's unlikely, but I don't really play with scrypt much any more. Perhaps you just need more system ram. On https://github.com/litecoin-project/litecoin/wiki/Mining-hardware-comparison there's a 7970 with 682 kHash/s
clock: 1000MHz, mem clock: 1600MHz
command line args are: --shaders 2048 --thread-concurrency 8192 -I 13 -g 2 -w 256
I'm not getting more than 550 kHash/s with the exact same settings.
Is 682 a typo (-> 582) - or is it really possible?
March 07, 2013, 05:30:24 PM
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
--hotplug 0 will only stop it finding new devices when you plug them in.
I've decided on how to handle this already but not implemented it yet.
I'll move it further up the todo list
In the mean time, if you start the cgminer that uses the FPGAs first (with -G), then start the GPU cgminer 2nd with --hotplug 0 then the GPU miner won't pick them up at startup or later via hotplug.
March 07, 2013, 03:22:27 PM
I am using cgminer 2.10.4 for Litecoin mining. win7x64. AMD 7970. various versions of Catalyst (12.10, ... , 13.1, 13.2)
On https://github.com/litecoin-project/litecoin/wiki/Mining-hardware-comparison there's a 7970 with 682 kHash/s
clock: 1000MHz, mem clock: 1600MHz
command line args are: --shaders 2048 --thread-concurrency 8192 -I 13 -g 2 -w 256
I'm not getting more than 550 kHash/s with the exact same settings.
Is 682 a typo (-> 582) - or is it really possible?
On https://github.com/litecoin-project/litecoin/wiki/Mining-hardware-comparison there's a 7970 with 682 kHash/s
clock: 1000MHz, mem clock: 1600MHz
command line args are: --shaders 2048 --thread-concurrency 8192 -I 13 -g 2 -w 256
I'm not getting more than 550 kHash/s with the exact same settings.
Is 682 a typo (-> 582) - or is it really possible?
March 07, 2013, 03:03:53 PM
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.
Heh whoops, I just got a crash so it's not quite there yet 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.
March 07, 2013, 02:59:06 PM
My kids have just reached an age where they're quoting this too so it's very topical. Thanks
March 07, 2013, 02:52:54 PM
Quote
[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?[2013-03-07 17:55:32] SOLVED 1 BLOCK!
March 07, 2013, 01:31:49 PM
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. 
March 07, 2013, 01:28:27 PM
Quote
[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?[2013-03-07 17:55:32] SOLVED 1 BLOCK!
What's your Best share: ?
March 07, 2013, 12:59:35 PM
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
March 07, 2013, 12:55:12 PM
March 07, 2013, 12:33:23 PM
Quote
[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?[2013-03-07 17:55:32] SOLVED 1 BLOCK!
March 07, 2013, 12:19:12 PM
Quote
[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? [2013-03-07 17:55:32] SOLVED 1 BLOCK!
March 07, 2013, 12:05:51 PM
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.
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!
March 07, 2013, 11:41:48 AM
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?
Yes. What pool and protocol? Some pools have been really struggling of late so it's the likely culprit.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
.....
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 ***
March 07, 2013, 09:30:52 AM
March 07, 2013, 09:26:44 AM
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
March 07, 2013, 09:15:22 AM
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?
Jump to: