Author

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

hero member
Activity: 490
Merit: 501
...
heh, we are talking bitcoin GPU mining. If a good  video card can give 600+Mhs ( like a 7850), then a small rig churning 10Mhs isn't all that impressive. I'm not sure what you consider "low megahashes". everything is relative.
Wow - that's overclocked Smiley

Apparently you can get ~370MH/s out of a 7850 but I'd wonder how long it would last ...

my bad, that's a 100Mhs card, i got confused. I haven't had the chance to memorize the entire Hardware comparison chart yet. i occasionally get things mixed up.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
...
heh, we are talking bitcoin GPU mining. If a good  video card can give 600+Mhs ( like a 7850), then a small rig churning 10Mhs isn't all that impressive. I'm not sure what you consider "low megahashes". everything is relative.
Wow - that's overclocked Smiley

Apparently you can get ~370MH/s out of a 7850 but I'd wonder how long it would last ...
hero member
Activity: 490
Merit: 501

well, the intensity was set a -1 on the little machine that i am playing with. moving it to 5 raised the hash rate from 6Mhash to 10Mhash. moving it to 6 looked like it  caused the rate to drop a little, so 5 it is.

10Mhash/s? how do you get the Mhash ? ty

Did i mislabel? isn't Mhs, Mega Hashes? I've only been into this for about 2 weeks so it would be easy for me to mispeak.
eee, stop and reload..
you are talking litecoin? you are talking GPU mining?
may i ask how a tiny rig gives you Mega Hash/s? the top listed here is 7970(x2) in low megashas/s...
// i'm obviously missing something obvious. sorry about it.


heh, we are talking bitcoin GPU mining. If a good  video card can give 600+Mhs ( like a 7850), then a small rig churning 10Mhs isn't all that impressive. I'm not sure what you consider "low megahashes". everything is relative.
newbie
Activity: 42
Merit: 0
Someone please help me, I just built a small rig and got a Gigabyte 7950 in it.
I use all the settings suggested for varying hash rates on the charts and I cannot get it to work.

First off if I change the Memory clock either in the CGminer window or in the .bat and load it, my screen goes black and it all just locks up and I have to reset my PC, every single time.
Also, I cannot raise the thread concurrency beyond like 10600, it just gives me the GPU/thread disabling kernel error message, even though I did the "auto tune" test and it suggested 22400, I have no idea why, do I need more RAM possibly?

The only way I can get it to work now is leave everything default (1000/1250clock) and just put the intensity at 18....but it gets too damn hot, its open case with a bunch of exhaust fans, Its around 85-90 C right now depending if I just Accepted a share, it gets hotter, and this is only at a K/hash rate of like 570-600, can anyone help why my card is getting so damn hot?? and all my other issues Sad I tried 20 first and it got up to 95 and just shut the card off similar to how it reacts when I increase the mem clock....

25 LTC to anyone or a group of you guys that help me solve this problem

Also in my pool it says I am only getting 46 k/hash on the card
Please please someone help me out here, btw I have 2 gigs of system RAM.
Also when I launch CUDAminer, cause I want to use my 570 (which is the primary card) to mine as well, it takes away from CGminer and my hash and everything starts going down. Why is that? I could have sworn you could run both programs at the same time to mine both cards, help pl0x!
hero member
Activity: 810
Merit: 1000
After 9 months mining, I fried a 6770 and 2 * PSUs. The 6770 has no physical signs however when mining it was reporting sick/dead after 10~20minutes for about 3 weeks. The PSU blew so I replaced it then it blew too so I ripped out the sick 6770, added a new PSU and things have booted up OK except for....I can no longer mine!

Upon starting up CGMiner reports that a card is already overtemp yet I am monitoring the card temp using a 3rd party which has it as 40ish degrees C when idling.

Ideas on how to fix...?
At a wild guess - your config file may still be setup to include the other card?
(and thus the GPU settings are going to the wrong devices?)

I deleted the 2nd cards Intensity rating from the config and boot shortcut...hmmm...will go back and have a look at removing all the secondary settings within the config files...

If it works...some compensating BTC or LTC will be shelled out
newbie
Activity: 41
Merit: 0

well, the intensity was set a -1 on the little machine that i am playing with. moving it to 5 raised the hash rate from 6Mhash to 10Mhash. moving it to 6 looked like it  caused the rate to drop a little, so 5 it is.

10Mhash/s? how do you get the Mhash ? ty

Did i mislabel? isn't Mhs, Mega Hashes? I've only been into this for about 2 weeks so it would be easy for me to mispeak.
eee, stop and reload..
you are talking litecoin? you are talking GPU mining?
may i ask how a tiny rig gives you Mega Hash/s? the top listed here is 7970(x2) in low megashas/s...
// i'm obviously missing something obvious. sorry about it.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
After 9 months mining, I fried a 6770 and 2 * PSUs. The 6770 has no physical signs however when mining it was reporting sick/dead after 10~20minutes for about 3 weeks. The PSU blew so I replaced it then it blew too so I ripped out the sick 6770, added a new PSU and things have booted up OK except for....I can no longer mine!

Upon starting up CGMiner reports that a card is already overtemp yet I am monitoring the card temp using a 3rd party which has it as 40ish degrees C when idling.

Ideas on how to fix...?
At a wild guess - your config file may still be setup to include the other card?
(and thus the GPU settings are going to the wrong devices?)
newbie
Activity: 42
Merit: 0
Someone please help me, I just built a small rig and got a Gigabyte 7950 in it.
I use all the settings suggested for varying hash rates on the charts and I cannot get it to work.

First off if I change the Memory clock either in the CGminer window or in the .bat and load it, my screen goes black and it all just locks up and I have to reset my PC, every single time.
Also, I cannot raise the thread concurrency beyond like 10600, it just gives me the GPU/thread disabling kernel error message, even though I did the "auto tune" test and it suggested 22400, I have no idea why, do I need more RAM possibly?

The only way I can get it to work now is leave everything default (1000/1250clock) and just put the intensity at 18....but it gets too damn hot, its open case with a bunch of exhaust fans, Its around 85-90 C right now depending if I just Accepted a share, it gets hotter, and this is only at a K/hash rate of like 570-600, can anyone help why my card is getting so damn hot?? and all my other issues Sad I tried 20 first and it got up to 95 and just shut the card off similar to how it reacts when I increase the mem clock....

25 LTC to anyone or a group of you guys that help me solve this problem

Also in my pool it says I am only getting 46 k/hash on the card
hero member
Activity: 810
Merit: 1000
After 9 months mining, I fried a 6770 and 2 * PSUs. The 6770 has no physical signs however when mining it was reporting sick/dead after 10~20minutes for about 3 weeks. The PSU blew so I replaced it then it blew too so I ripped out the sick 6770, added a new PSU and things have booted up OK except for....I can no longer mine!

Upon starting up CGMiner reports that a card is already overtemp yet I am monitoring the card temp using a 3rd party which has it as 40ish degrees C when idling.

Ideas on how to fix...?
member
Activity: 112
Merit: 10
I have a question, if someone maybe can answer.  I wouldn't not have thought this a valid question, but have run into it myself.  

--How does "System RAM" connect / associate with "GPU RAM" and "TC" in CGminer?

Example similar to what I ran into;

System mining LTC with 1024mb system ram, with say a TC- 10752
Change
System mining LTC with 512mb system ram, with same TC - 10752  <<eNDRangeKernel)

Anyone have thoughts on how / why / what is making the connection with system ram?  Thanks in advance for any help.




The problem is with OpenCL being unable to allocate the gpu memory on a system with less system memory than it wants to allocate.

I'm not sure if there is any way to work around that, other than to add more memory to the system.
sr. member
Activity: 258
Merit: 250
So im trying to build the cgminer-3.1.0-windows and i have been following the directions in the windows-build.txt.
I have done everything up until the step * Build cgminer.exe *.

When i try to run autoreconf -fvi in the MINGW32 prompt it gives me the error autoreconf-2.68: 'configure.ac' or 'configure.in' is required.
Yes i did change the working directory to my cgminer-3.1.0-windows folder.

Im positive that i have done every step correctly.. I will attempt to redo it all just to be sure its not me, but does anyone else know whats going on with this error that prevents me from building this thing already? haha

Please and thank you!
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4

Hi,

i recently did some solomining and got several hints regarding the expiry setting.

As i tried to understand what the function of this settings are i checked the rm:

Quote
--expiry|-E    Upper bound on how many seconds after getting work we consider a share from it stale (default: 120)

But some questions still remain:

Am i right that a expiry setting of 5 would stop the work on the current block after 5s and switch to the next block?

And why would i want to stop the miner working on a block?

Greetings

ImI

You aren't stopping work on a block.
You are stopping work on a work item.
sr. member
Activity: 322
Merit: 250


3.1.0 - "nogpu" version

Platform:
Win 7 64 bit


After approx. 3-6 hours the following behavior occurs.


1.  Increasingly frequent "Unable to read temperature."  Or something like that.  BFL unit in question still hashing away.

2.  Not long after 1. cgminer stops processing work.  "JSON stratum auth failed (no reason)" messages.  Have to Q out, restart to hash again.


The stratum auth failure message occurs with or without cgminer continuing to process work.  So, pool seems available - just some quirky problem.


full member
Activity: 238
Merit: 100
I have a question, if someone maybe can answer.  I wouldn't not have thought this a valid question, but have run into it myself.  

--How does "System RAM" connect / associate with "GPU RAM" and "TC" in CGminer?

Example similar to what I ran into;

System mining LTC with 1024mb system ram, with say a TC- 10752
Change
System mining LTC with 512mb system ram, with same TC - 10752  <<eNDRangeKernel)

Anyone have thoughts on how / why / what is making the connection with system ram?  Thanks in advance for any help.


ImI
legendary
Activity: 1946
Merit: 1019

Hi,

i recently did some solomining and got several hints regarding the expiry setting.

As i tried to understand what the function of this settings are i checked the rm:

Quote
--expiry|-E    Upper bound on how many seconds after getting work we consider a share from it stale (default: 120)

But some questions still remain:

Am i right that a expiry setting of 5 would stop the work on the current block after 5s and switch to the next block?

And why would i want to stop the miner working on a block?

Greetings

ImI



newbie
Activity: 24
Merit: 0
That's like going back to how we mined bitcoins >2 years ago before pools and longpoll. The answer is set the scantime as low as you can before the hashrate drops. If you're solo mining, something like 5s is usual for sha coins. However it can be slow to return results for scrypt so you'll have to experiment.

Thank you for the advice. I have two more questions:

1. I don't see a reduction in the displayed hash rate when I decrease scan-time. Is the displayed hash rate reliable at very low scan-time?

2. Is scan-time=0 a valid setting? According to the README, scan-time is an "Upper bound on time spent scanning current work, in seconds", so it sounds like 0 wouldn't make sense. However, it appears to work, and I found that scan-time=0 allows cgminer to detect new blocks slightly more quickly than scan-time=1. At this moment there are ~5 CNC blocks per minute so every second of stale work counts. I'm solo-mining and I haven't mined a block since I changed to scan-time=0, so I can't tell whether it's truly working.
member
Activity: 80
Merit: 10
Hi,

A number of us are getting CGminer lockups following stratum connection interrupted issues:
https://bitcointalksearch.org/topic/cgminer-stratum-connection-to-pool-0-interrupted-issue-188533

The pool never fails over, and cgminer stops hashing and becomes unresponsive to keyboard input.

Any fix or workaround for this issue?

legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
...
Heheh I'm a bit embarresed right now. Sorry. Was just tired and a bit frustrated after trying to configure something that's a little above my skill level. Everything's working fine now though, which is pretty rewarding.
But just in case you didn't get what I meant the first time ...
Explanation of the error message you got and where to find details about tuning scrypt.
legendary
Activity: 1274
Merit: 1050
New question : CG miner reports that difficulty is set to 526k. This seems overmuch as the current difficulty of CHNcoin is 8. How do i change this ?


CGMiner reports what the network is saying.  If it says 526k, then it's 526k.  Are you sure you're on the right pool/network?

M
.. and in case he are mixing coin pools ... read the first 3 lines of the README Smiley

It's funny you've quoted README's two times now without solving anything, kind of like you're telling me to RTFM while actually you don't really know what you're talking about.

Here's the answer https://bitcointalksearch.org/topic/m.2030732

still puzzled by your avatar though

I guess someone could make youtube video reading the FAQ and Readme's to you so you wouldn't have to actually RTFM for yourself.

Reading The Fine (or other term) Manual may be more productive than telling one of the author's of the software "actually you don't really know what you're talking about. ".

Just sayin,
Sam

Heheh I'm a bit embarresed right now. Sorry. Was just tired and a bit frustrated after trying to configure something that's a little above my skill level. Everything's working fine now though, which is pretty rewarding.
sr. member
Activity: 252
Merit: 250
Jump to: