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

[TheHarbinger]

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.

[DeathAndTaxes]

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.

More specifically the DISPLAY DRIVERS are user mode drivers (in WinXP they were kernel mode drivers).  When user switches they are shutdown.  When new user logs in they are started up under the new user.  No drivers = no access to GPUs.  There is no work around that can be done by the developer or end user.  For stability reasons display drivers are now user mode (as of Windows Vista) and that will never change going forward.  There are advantages like having a driver crash and you just get "AMD Catalyst stopped respond, driver restarted" message instead of a BSOD.  Also crashing applications like games are more likely to crash back to the desktop then halt the entire system.

[kano]

...

Luke-jr's name is in the code and the AUTHORS file - he added his name after I did, but 'above' mine coz I guess he felt he was more important

I've left it in that order but in the hope that one day I could make this comment ... which I just did

Anyway, on the subject of accepting code - yep even Luke-jr's code gets accepted.
However, like my code, it gets vetted by ckolivas before it goes in.

The problematic things he seems to like to do are related to changing the way things look because he wants it to look different - and they have been rejected in the past.
Otherwise, I think most of his code changes have gone in.

Anyone who uses a BFL (or even an Icarus) is using the code that Luke-jr wrote.
Icarus code was based on the BFL code, a lot was rewritten due to the different way they work and then other changes have happened to the Icarus code since then (hmm I should add my latest LP Icarus change to the BFL code whenever I get around to sending a pull request ...)

OK, I take that back.
After spending some time arguing with luke-jr about bugs in his pull requests that he wouldn't listen to
I'll say there are issues with accepting his code.

In the past he hasn't tested (or even compiled) some of the changes he requested, I know he doesn't test run the code on windows by his own admission, and having to argue with him about why a code bug is a bug is a complete PITA.
(and then have him say that it's my bug because I have a similar code change (written better) that I know has the bug that I haven't sent the code to be added - because I know it's a bug and haven't worked out the fix yet in my unsent code - is even more annoying )

He likes to label a piece of text displayed by cgminer as a bug if it isn't what he wants (that one will probably be in the next release)
But a real code bug that he put in as a pull request - he thinks that's not possible.
(until later he sees exactly what I've told him is already on his own screen - he just didn't test it properly)

I like working on the API (and Icarus.c) coz noone else is messing with it or making stupid changes to it (and also the donations for the API are high compared to other donations so far - in real terms they are not a lot - but compared to other stuff around here, they are good) but there are a lot of changes that I see luke-jr now trying to push on those two and I don't trust his code ethic (or his code)

I'm sure this will not affect anyone, but I'll take a break from the code for a day?, week?, month? and see how this latest set of changes mess things up ... or wait for them to disappear.

I don't have any control at all over the cgminer code, that's all ckolivas' decisions, so it shouldn't matter to anyone anyway.

[Luke-Jr]

In the past he hasn't tested (or even compiled) some of the changes he requested,

Kinda hard to test GPU mining when I didn't have any working GPUs; I think I did the best reasonably expected given those circumstances. That's solved now (I have 1 working GPU, and another on the way).

having to argue with him about why a code bug is a bug is a complete PITA.

I added work-restart support to the Icarus driver, and you started demanding I had to refactor the (admittedly broken-by-design) internal structure that it used. Just because I'm touching a piece of code doesn't mean I want to refactor the existing code it's using (and when/if I do, it certainly doesn't belong in the same commit). As I told you, I wanted to talk to Con before changing it, since I wasn't very familiar with it. As it turns out, this particular code goes back to Jeff Garzik and cpuminer, and Con seems fine with the refactor you suggested.

But a real code bug that he put in as a pull request - he thinks that's not possible.
(until later he sees exactly what I've told him is already on his own screen - he just didn't test it properly)

Sorry, I had no reason to expect that fixing the hashrate measurement in the Icarus driver would somehow break the actual share-finding. It was a subtle bug, one you admit would only be noticable after hours of mining with it.

I'm sure this will not affect anyone, but I'll take a break from the code for a day?, week?, month? and see how this latest set of changes mess things up ... or wait for them to disappear.

I finished writing that JSON API refactoring I proposed to you, and was kindof hoping you could look it over and see why I think it's a good idea. Feel free to take your time; it'll just be sitting there waiting for your input when you get back, not merged until you give it a thumbs up.

[dietwice]

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?

[-ck]

No

[Krak]

Are there any downsides to running 1 thread per GPU on a normal pool? Every time I try enabling that second thread, my hashrate drops severely and my system becomes really slow.

[-ck]

Are there any downsides to running 1 thread per GPU on a normal pool? Every time I try enabling that second thread, my hashrate drops severely and my system becomes really slow.

It usually adds only a small amount to the hashrate in the order of 1-3% depending on device.

[ShadesOfMarble]

What went wrong here?

[craked5]

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.

[Krak]

Are there any downsides to running 1 thread per GPU on a normal pool? Every time I try enabling that second thread, my hashrate drops severely and my system becomes really slow.

It usually adds only a small amount to the hashrate in the order of 1-3% depending on device.

Alright. Do you maybe know why it's doing that? I know I used to use 2 threads back when I was on Windows and it ran just fine. Also it seems to be just the display GPU that suffers, but being on dynamic intensity, it's supposed to set itself to 1 thread anyway, right?

[-ck]

Are there any downsides to running 1 thread per GPU on a normal pool? Every time I try enabling that second thread, my hashrate drops severely and my system becomes really slow.

It usually adds only a small amount to the hashrate in the order of 1-3% depending on device.

Alright. Do you maybe know why it's doing that? I know I used to use 2 threads back when I was on Windows and it ran just fine. Also it seems to be just the display GPU that suffers, but being on dynamic intensity, it's supposed to set itself to 1 thread anyway, right?

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.

[-ck]

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).

[Krak]

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 ).

Also, what intensity is usually recommended for 6870s?

[jjiimm_64]

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

[P4man]

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

[The00Dustin]

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.

[jjiimm_64]

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

[jjiimm_64]

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.

[sharky112065]

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.