OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 595.

jddebug

sr. member

Activity: 446

Merit: 250

Quote from: DeathAndTaxes on April 24, 2012, 12:07:15 PM

You likely updated your SDK at some point in the past.
cgminer will cache the compiled kernel hiding the change in performance.
new version of cgminer has no cached kernel so it compiles under new SDK and performance drops.

To confirm:
a) make backup of .bin files in old cgminer directory
b) delete .bin files in old cgminer directory.
c) start cgminer and it will recreate bin files using new SDK.
d) compare performance to "new" cgminer.

Is there a "best" SDK to be using for mining?

DeathAndTaxes

donator

Activity: 1218

Merit: 1080

Gerald Davis

You likely updated your SDK at some point in the past.
cgminer will cache the compiled kernel (bin files) hiding the change in performance.
new version of cgminer has no cached kernel (bin files) so it compiles under new SDK and performance drops.

To confirm:
a) make backup of .bin files in old cgminer directory
b) delete .bin files in old cgminer directory.
c) start cgminer and it will recreate bin files using new SDK.
d) compare performance to "new" cgminer.

Fiyasko

legendary

Activity: 1428

Merit: 1001

Okey Dokey Lokey

So i've been HAPPILY using cgminer version 2.1.2 with No issues, And i wonder this.
I have 1x6990 2x6870 1x5830 1x5770
If i update will i notice Obvious changes? Such as higher hashrates?

Woah what the fuck 30mh/core slower??!?!! what the hell!
Here is my gaming system with the dual 6870's

Code:

 cgminer version 2.3.3 - Started: [2012-04-24 09:51:27]
--------------------------------------------------------------------------------
 (5s):556.9 (avg):538.2 Mh/s | Q:22  A:15  R:0  HW:0  E:68%  U:8.88/m
 TQ: 1  ST: 2  SS: 0  DW: 1  NB: 2  LW: 0  GF: 0  RF: 0
 Connected to http://pit.deepbit.net:8332 with LP as user *************
 Block: 000009d3c3bee3207dee653e3729bc4e...  Started: [09:51:38]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  74.0C  50%    | 278.0/282.8Mh/s | A:8 R:0 HW:0 U:4.74/m I: 3
 GPU 1:  79.0C  78%    | 278.8/276.0Mh/s | A:9 R:0 HW:0 U:5.33/m I: 3
--------------------------------------------------------------------------------

[2012-04-24 09:52:25] Accepted 00000000.8e56b448.21c0d788 GPU 1 thread 3
[2012-04-24 09:52:27] Accepted 00000000.19c8c4e1.1cfeeeb6 GPU 0 thread 1
[2012-04-24 09:52:32] Accepted 00000000.3ef81cef.66d7bf19 GPU 1 thread 3
[2012-04-24 09:52:36] Accepted 00000000.f375494f.61edeffd GPU 0 thread 1
[2012-04-24 09:53:01] Accepted 00000000.5360ca14.bbe6e9e9 GPU 0 thread 1
[2012-04-24 09:53:02] Accepted 00000000.a2bca0ff.1d014d8c GPU 1 thread 3
[2012-04-24 09:53:08] Accepted 00000000.8ca2ef3d.c819dd63 GPU 1 thread 2
[2012-04-24 09:53:09] Accepted 00000000.fe8c9ea7.a8bb18d8 GPU 1 thread 2
[2012-04-24 09:53:10] Accepted 00000000.5ae48698.4f8fa217 GPU 1 thread 2
[2012-04-24 09:53:10] Accepted 00000000.09e180b8.c099ef9d GPU 1 thread 3
[2012-04-24 09:53:10] Accepted 00000000.7bb4c2f6.b2e10aa9 GPU 1 thread 3
[2012-04-24 09:53:13] Accepted 00000000.5c3b0577.74747a36 GPU 1 thread 2

^^^Newer
v v vOlder

Code:

 cgminer version 2.1.2 - Started: [2012-04-24 09:54:18]
--------------------------------------------------------------------------------
 (5s):627.4 (avg):623.3 Mh/s | Q:13  A:15  R:0  HW:0  E:115%  U:12.83/m
 TQ: 2  ST: 1  SS: 0  DW: 0  NB: 1  LW: 0  GF: 0  RF: 0
 Connected to http://pit.deepbit.net:8332 with LP as user ***************
 Block: 000009d3c3bee3207dee653e3729bc4e...  Started: [09:54:18]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  75.0C  50%    | 316.0/324.7Mh/s | A:9 R:0 HW:0 U:  7.70/m I: 3
 GPU 1:  79.0C  82%    | 316.2/323.4Mh/s | A:6 R:0 HW:0 U:  5.13/m I: 3
--------------------------------------------------------------------------------

[2012-04-24 09:54:31] Accepted 00000000.d27e0e14.ac2a2dc5 GPU 1 thread 3
[2012-04-24 09:54:37] Accepted 00000000.95685005.07737480 GPU 0 thread 2
[2012-04-24 09:54:38] Accepted 00000000.0c81d27b.62f4eefc GPU 1 thread 3
[2012-04-24 09:54:38] Accepted 00000000.7b58cf89.ad70a24a GPU 0 thread 0
[2012-04-24 09:54:42] Accepted 00000000.14fa51cb.f938df0b GPU 1 thread 3
[2012-04-24 09:54:49] Accepted 00000000.d99bba9d.757eb820 GPU 0 thread 0
[2012-04-24 09:54:53] Accepted 00000000.ae7d0bc0.2caa74d1 GPU 1 thread 3
[2012-04-24 09:54:57] Accepted 00000000.aaf638c5.55ca044b GPU 0 thread 0
[2012-04-24 09:54:57] Accepted 00000000.0456264a.112018e7 GPU 0 thread 0
[2012-04-24 09:55:01] Accepted 00000000.23f02532.2b4aaf5a GPU 1 thread 3
[2012-04-24 09:55:04] Accepted 00000000.37fe79d5.b1743c5b GPU 0 thread 0
[2012-04-24 09:55:14] Accepted 00000000.70255cd6.7b516e40 GPU 0 thread 2

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: ?? on ??

For those of you who want to build their own Windows version that works with Icarus, you might want to get icarus.c from my site:

http://www.petermoss.com/cgminer-wdog/my-cgminer-modifications/

I've been running it for a while now, it seems to work well. I get ~400 Mh/s, 5.30-5.35 shares/min.

Heh you can't actually get 400MH/s unless you use a faster bitstream.
The device can only max out at 380MH/s with the standard bitstream.

I did use your code as a basis for the windows additions I did - serial initialisation - (I just minimised it as much as possible)
You'll see your name is in a comment above that code in driver-icarus.c in the git
The next release (the current git) works on windows.

There's still 2 things that certainly need to (must) be done to driver-icarus.c but they probably wont be there until after the release.
The hash rate (luke-jr found the simple fix for that) is wrong (and wrong in your one also)
That and a USB/UART problem that happens on some machines (I've not yet had it happen on 2 linux computers that have run for days or even weeks)
I'm trying an overnight windows test on another computer to see if I can have it happen

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: ?? on ??

For those of you who want to build their own Windows version that works with Icarus, you might want to get icarus.c from my site:

http://www.petermoss.com/cgminer-wdog/my-cgminer-modifications/

I've been running it for a while now, it seems to work well. I get ~400 Mh/s, 5.30-5.35 shares/min.

What commit was this based on?

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: Epoch on April 23, 2012, 11:40:46 PM

...
It then mines with 7 Singles (COM3-COM9) but doesn't use COM10-COM12). Why is cgminer detecting an Icarus product on COM10-COM12? I have no Icarus, only BFL.
...

It actually says it didn't detect an Icarus if you read again

However, the Icarus code reports if it attempted and succeeded or failed.
In this case the 3 ports that BFL didn't succeed with were passed on to Icarus to try,
and as it said "Icarus Detect: Failed to open COM1x"

Aside: The next version of the code should actually work with Icarus on windows ...
I get the impression few if any have had it work in the past with Icarus on windows.
My pull request (that hopefully will go in) includes changes based on the suggestions by af_newbie and that made my pull request work fine on windows (that I delayed for a few weeks for that very reason, I hadn't tested it on windows)
It also works wonders for anyone with lots of Icarus devices (even on linux) the current code takes something like almost a minute to check 10 (I'm not sure of the exact figure), but the new one takes at most a little over 0.1s per device

Epoch

legendary

Activity: 922

Merit: 1003

Quote from: Luke-Jr on April 23, 2012, 11:46:29 PM

Quote from: Epoch on April 23, 2012, 11:40:46 PM

Might it have something to do with the fact that in COM has 2 digits instead of 1? Has anyone else run into this issue?

Yes. You need to use the full path if it's more than 1 digit.

Code:

cgminer -S \\.\COM10

That did the trick. Thanks, Luke!

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Epoch on April 23, 2012, 11:40:46 PM

Might it have something to do with the fact that in COM has 2 digits instead of 1? Has anyone else run into this issue?

Yes. You need to use the full path if it's more than 1 digit.

Code:

cgminer -S \\.\COM10

Epoch

legendary

Activity: 922

Merit: 1003

I've run into a problem running 10 BFL Singles with cgminer 2.3.3 (Windows 7 32-bit). My Singles are assigned to COM ports COM3-COM12 inclusive. I use the following command line:

Code:

cgminer -o http://pool -u  -p  --disable-gpu -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9 -S COM10 -S COM11 -S COM12

cgminer reports this error:

Code:

[2012-04-23 22:54:00] Started cgminer 2.3.3
[2012-04-23 22:54:00] Icarus Detect: Failed to open COM10
[2012-04-23 22:54:00] Icarus Detect: Failed to open COM11
[2012-04-23 22:54:00] Icarus Detect: Failed to open COM12

It then mines with 7 Singles (COM3-COM9) but doesn't use COM10-COM12). Why is cgminer detecting an Icarus product on COM10-COM12? I have no Icarus, only BFL.

I then tried Ufasoft, and Ufasoft detects and uses all 10 Singles without any issue. Cgminer, however, seems to have trouble with COM10, COM11, and COM12. Might it have something to do with the fact that in COM has 2 digits instead of 1? Has anyone else run into this issue?

If I simplify the command line to only the following:

Code:

cgminer -o http://pool -u  -p  --disable-gpu -S COM10 -S COM11 -S COM12

cgminer comes back with "all devices disabled, cannot mine!" (after the 'Icarus Detect: Failed to open COM10' messages).

Any ideas? Cgmine doesn't seem to be happy with COM10-COM12 but is perfectly happy with COM3-COM9.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: jjiimm_64 on April 22, 2012, 05:56:32 PM

Quote from: kano on April 22, 2012, 04:09:49 PM

...

But why would you upgraded to an old version?

my bad for not keeping with the all the versions.

still I am wondering why a command that used to work with the api, does not work with 2.2.6.

WARN: '{"command":"summary"}' returned nothing

Either you don't have access to the API since you haven't granted access or you mistyped it.

If you didn't mistype that, then if you use your original cgminer API settings then that command will work.

The access control changed so that if you didn't modify your cgminer options, you would still have read access, but no write/priviledged access.

As I stated at the time - it was a security fix.
Granting access to destroy your rig or steal your hashes by default seemed like a bad idea.
You now have to choose to let people destroy it or steal hashes (the 'W:' prefix)

I'll waste my time posting the relevant RPC API contents of the README since you didn't read it all:

Quote

RPC API

If you start cgminer with the "--api-listen" option, it will listen on a simple TCP/IP socket for single string API requests from the same machine running cgminer and reply with a string and then close the socket each time
If you add the "--api-network" option, it will accept API requests from any network attached computer.

You can only access the comands that reply with data in this mode.
By default, you cannot access any privileged command that affects the miner -
you will receive an access denied status message see --api-allow below.

You can specify IP addresses/prefixes that are only allowed to access the API with the "--api-allow" option e.g. --api-allow W:192.168.0.1,10.0.0/24 will allow 192.168.0.1 or any address matching 10.0.0.*, but nothing else
IP addresses are automatically padded with extra '.0's as needed
Without a /prefix is the same as specifying /32
0/0 means all IP addresses.
The 'W:' on the front gives that address/subnet privileged access to commands that modify cgminer.
Without it those commands return an access denied status.
Privileged access is checked in the order the IP addresses were supplied to "--api-allow"
The first match determines the privilege level.
Using the "--api-allow" option overides the "--api-network" option if they are both specified
With "--api-allow", 127.0.0.1 is not by default given access unless specified

See that last line ...

If you don't run the current version, you can read the NEWS to work out when different options were added.

jjiimm_64

legendary

Activity: 1876

Merit: 1000

Quote from: kano on April 22, 2012, 04:09:49 PM

Quote from: jjiimm_64 on April 22, 2012, 01:54:36 PM

Quote from: The00Dustin on April 22, 2012, 01:47:31 PM

Quote from: P4man on April 22, 2012, 01:39:41 PM

Is 0/0 a valid IP range?
If you want local access, try

Code:

W:192.168.1.0/24

Assuming your lan uses 192.168.1.x

It sounds like it used to work, so I'm assuming the goal is to allow all IPs. If so, I would try something like 172.0.0.1/0 (since it seems to be checking the address format), and if all addresses is not the goal, another important piece of information might be that 127.0.0.1/32 would be localhost only.

this is in the readme at git:

Without a /prefix is the same as specifying /32
0/0 means all IP addresses.

You caused your own problem.

Let me reword what you said for you:

"I upgraded to an old version that doesn't support 0/0
The current version does support 0/0
Why doesn't the old version magically have the 0/0 code in it that was written after it?"

The problem is you didn't upgrade to the version that supports 0/0 ...
If you upgrade to before a version that supports something ... ... it means it wont work ... ...

If you read the NEWS file it will tell you which version added the code that supports 0/0

But why would you upgraded to an old version?

my bad for not keeping with the all the versions.

still I am wondering why a command that used to work with the api, does not work with 2.2.6.

WARN: '{"command":"summary"}' returned nothing

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: jjiimm_64 on April 22, 2012, 01:54:36 PM

Quote from: The00Dustin on April 22, 2012, 01:47:31 PM

Quote from: P4man on April 22, 2012, 01:39:41 PM

Is 0/0 a valid IP range?
If you want local access, try

Code:

W:192.168.1.0/24

Assuming your lan uses 192.168.1.x

It sounds like it used to work, so I'm assuming the goal is to allow all IPs. If so, I would try something like 172.0.0.1/0 (since it seems to be checking the address format), and if all addresses is not the goal, another important piece of information might be that 127.0.0.1/32 would be localhost only.

this is in the readme at git:

Without a /prefix is the same as specifying /32
0/0 means all IP addresses.

You caused your own problem.

Let me reword what you said for you:

"I upgraded to an old version that doesn't support 0/0
The current version does support 0/0
Why doesn't the old version magically have the 0/0 code in it that was written after it?"

The problem is you didn't upgrade to the version that supports 0/0 ...
If you upgrade to before a version that supports something ... ... it means it wont work ... ...

If you read the NEWS file it will tell you which version added the code that supports 0/0

But why would you upgraded to an old version?

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: dietwice on April 21, 2012, 11:11:03 PM

Quote from: TheHarbinger on April 21, 2012, 10:06:51 AM

Quote from: dietwice on April 21, 2012, 03:32:04 AM

Quote from: -ck on April 20, 2012, 11:58:11 PM

Quote from: dietwice on April 20, 2012, 11:40:33 PM

Both 2.3.2 and 2.3.3 windows versions stop working on user switching.
2.3.1 works well.
Win7 x64, SDK 2.6.

User switching?... What on earth has the cgminer version got to do with that?

I don't know O_o.
But when I return back to the user running cgminer I see that no more shares were submitted since I switched out.
It just staying still.

This is a Windows 7 issue, it has nothing to do with cgminer. W7 doesn't operate the same as XP did, anything that the user has running is suspended when that user is logged out or another user is switched to. In XP you could continue to have programs running with a logged out user, not in Win 7.

No, Win7 doesn't suspend tasks of inactive user.
It does make something weird with drivers when switching between users but again it isn't full termination or suspend.
Anyway 2.3.1 have enough luck to work well behind the scene and behave alive when I switch to the user where It runs.

I wonder if something was changed between 2.3.1-2 and 2.3.2 and caused such behavior?

Didn't Ckolivas change it in 2.3.2 to restart ADL if it stopped and in 2.3.2 changed it to just restart cgminer if ADL stopped working? When you log out or switch users, Catalyst stops running thus no ADL.

jjiimm_64

legendary

Activity: 1876

Merit: 1000

Quote from: The00Dustin on April 22, 2012, 01:47:31 PM

Quote from: P4man on April 22, 2012, 01:39:41 PM

Is 0/0 a valid IP range?
If you want local access, try

Code:

W:192.168.1.0/24

Assuming your lan uses 192.168.1.x

It sounds like it used to work, so I'm assuming the goal is to allow all IPs. If so, I would try something like 172.0.0.1/0 (since it seems to be checking the address format), and if all addresses is not the goal, another important piece of information might be that 127.0.0.1/32 would be localhost only.

this is in the readme at git:

Without a /prefix is the same as specifying /32
0/0 means all IP addresses.

jjiimm_64

legendary

Activity: 1876

Merit: 1000

Quote from: P4man on April 22, 2012, 01:39:41 PM

Is 0/0 a valid IP range?
If you want local access, try

Code:

W:192.168.1.0/24

Assuming your lan uses 192.168.1.x

thank you sir...

now we get this from my old api call: arrrgggg...

Code:

WARN: '{"command":"summary"}' returned nothing

this is why i loath to 'upgrade' anything...

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: P4man on April 22, 2012, 01:39:41 PM

Is 0/0 a valid IP range?
If you want local access, try

Code:

W:192.168.1.0/24

Assuming your lan uses 192.168.1.x

It sounds like it used to work, so I'm assuming the goal is to allow all IPs. If so, I would try something like 172.0.0.1/0 (since it seems to be checking the address format), and if all addresses is not the goal, another important piece of information might be that 127.0.0.1/32 would be localhost only.

P4man

hero member

Activity: 518

Merit: 500

Is 0/0 a valid IP range?
If you want local access, try

Code:

W:192.168.1.0/24

Assuming your lan uses 192.168.1.x

jjiimm_64

legendary

Activity: 1876

Merit: 1000

I know this is a busy thread, i try not to post unless needed...

I upgraded one of my rigs from 2.2.1 to 2.2.6. I am having trouble with the API calls now.

this is my conf snippet

Code:


"api-listen" : true,
"api-network" : true,
"api-port" : "4028",
"api-allow" : "W:0/0",

but this is what I get when I start cgminer:

Code:

  API not running (no valid IPs specified) - API will not be available

help

Krak

hero member

Activity: 591

Merit: 500

Quote from: -ck on April 22, 2012, 11:40:35 AM

No idea

Only time someone reported something along these lines they discovered the display GPU wasn't actually the one they thought it was in cgminer. The GPU numbers don't always make sense and are just whatever OpenCL tells cgminer.

Well I know I have the right one; my top (display) GPU's fan always runs a couple hundred RPM faster than my second one. I've tested it quite a bit with different settings on each (and I think I would probably be able to tell if my display GPU was running at 8 intensity Tongue

).

Also, what intensity is usually recommended for 6870s?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: craked5 on April 22, 2012, 10:47:49 AM

Hey guys! i add a 5870 and a 5830 running perfectly on cgminer, but when i added a 5750 via a x1 extender cable cgminer crashes everytime i try to open it. I tryed doing no overclocking to the cards etc etc and nothing works. Some help please!

after that error msg cgminer crashes.

Try deleting any .bin files you have in the cgminer directory and starting again. If that fails, try specifying a different worksize for the 57x0 to the 58x0 (eg -w 256,256,128 if the 5750 is last).

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