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

I guess you didn't read my original post where I told about the lack of GPU clockspeed control when I run CGMiner as other user, which does make it totally hidden but causes this bug. If your registry solution does allow CGMiner to be run without trayicon or cmd window and have it's GPU clockspeed control working please post it right here.

I'm just wondering if this issue is something on windows permissions (that other account is admin and UAC is off) or did I really find a fancy bug in here.

You can use GUIminer to launch cgminer in tray.
If you want start it totally "hidden" you can run it from registry, google it

Thanks, it works 

Performance with thread concurrency 16384 seems to be on par with 8192 on my system. Higher values are a no go (system unresponsive).

I tryied without OC - didn't help (

I'll have a look at that, thanks.

Still looking for a "official" solutions so cgminer could be launched with task scheduler as another user and thus not showing any window or tray icon. Having a clean desktop is crucial in my situation.

Back your OC off some. That's why your driver is failing.

Hello guys!
I have a problem with cgminer 2.10.5

Sometime when I run  cgminer I see "Display driver has stopped working and has recovered"  after that gpu1 doesn't work sick or dead
I use next settings for cgminer  -I 9 -w 128 -g 2
If cgminer run ok without error he can mine one day or one hour and then I see error
http://dl.dropbox.com/u/38228438/1.png

my configuration
7970x2 - 12.7. beta
mothermoard asus M3A - AMD 770 / SB600 chipset
2gb memory
cpu amd 6000
 

Try the program TrayIt!
http://trayit.en.softonic.com/

First I have to say this is a totally awesome miner. Thank you for putting such an incredible effort into it.

I think I came across some sort of a bug when I'm running cgminer through windows task scheduler as other user than the one who's currently logged in to the computer. My goal is to run cgminer in the backround without visible window. Everything else works just fine but cgminer seems not to be able to change my cards clocks and fan speeds if it's launched that way. This is bothering me because I would like to use that --auto-gpu function to lower the gpu clocks during the soon coming hot summer days when room temperature goes too high.

My system is Win7 x64, 2x7970, Catalyst 13.1.

Are you aware of this issue and more inportantly is there any solution available to it? Thanks!

For scrypt mining on windows with high thread concurrencies, see "How to raise "Maximum buffer memory" in cgminer 2.11.3 ":

http://forum.litecoin.net/index.php/topic,1420.0.html

Summary:

thx for reply ckolivas - maybe its completly diferent i have no idea, but i just check on gpu-z sensors tab and it works fine i can switch user and come back and its still working, so maybe there is some trick - anyway i can live with --compact feature

http://i.imgur.com/RqvqpQz.png

at 1000mhz core, changing memory from 1500 to 1200 I just lose 1Kh/s, 1100 takes me down 7Kh/s
Changing the core speed has a direct influence on hashrate

Yuk. That sounds like completely no fun whatsoever.....

Count me in on that anti bounty.......

I have received some further donations for scrypt, so I will briefly outline how to get the best hashrate for a 7970 as I understand it, that should work for any hardware combo.

EDIT: Preliminary actions:
On linux run this command:
export GPU_MAX_ALLOC_PERCENT=100
or on windows this:
setx GPU_MAX_ALLOC_PERCENT 100
in the same console/bash/dos prompt/bat file/whatever you want to call it,
before running cgminer.

First, find the highest thread concurrency that you can start it at. They should all start at 8192 but some will go up to 3 times that. Don't go too high on the intensity while testing and don't change gpu threads. If you cannot go above 8192, don't fret as you can still get a high hashrate.

Delete any .bin files so you're starting from scratch and see what bins get generated.

First try without any thread concurrency or even shaders, as cgminer will try to find an optimal value
cgminer -I 13

If that starts mining, see what bin was generated, it is likely the largest meaningful TC you can set.
Starting it on mine I get:
scrypt130302Tahitiglg2tc22392w64l8.bin

See tc22392 that's telling you what thread concurrency it was. It should start without TC parameters, but you never know. So if it doesn't, start with --thread-concurrency 8192 and add 2048 to it at a time till you find the highest value it will start successfully at.

Then start overclocking the eyeballs off your memory, as 7970s are exquisitely sensitive to memory speed and amazingly overclockable but please make sure it keeps adequately cooled with --auto-fan! Do it while it's running from the GPU menu. Go up by 25 at a time every 30 seconds or so until your GPU crashes. Then reboot and start it 25 lower as a rough start. Mine runs stable at 1900 memory without overvolting. Overvolting is the only thing that can actually damage your GPU so I wouldn't recommend it at all.

Then once you find the maximum memory clock speed, you need to find the sweet spot engine clock speed that matches it. It's a fine line where one more MHz will make the hashrate drop by 20%. It's somewhere in the .57 - 0.6 ratio range. Start your engine clock speed at half your memory clock speed and then increase it by 5 at a time. The hashrate should climb a little each rise in engine speed and then suddenly drop above a certain value. Decrease it by 1 then until you find it climbs dramatically. If your engine clock speed cannot get that high without crashing the GPU, you will have to use a lower memclock.

Then, and only then, bother trying to increase intensity further.

My final settings were:
--gpu-engine 1157  --gpu-memclock 1900 -I 20
for a hashrate of 725kH.

Note I did not bother setting a thread concurrency. Once you have the magic endpoint, look at what tc was chosen by the bin file generated and then hard code that in next time (eg --thread-concurrency 22336) as slight changes in thread concurrency will happen every time if you don't specify one, and the tc to clock ratios are critical!

Good luck, and if this doesn't work for you, well same old magic discussion applies, I cannot debug every hardware combo out there.

Your numbers will be your numbers depending on your hardware combination and OS, so don't expect to get exactly the same results!

Maybe we should have an anti-bounty and match whatever funds to drop support? (Obvious Troll is Obvious)

Maybe the bounty should be started on this forum, again.
Graet ?

I'd love to say I'll make it 100 times faster but realistically no, just that I'll maintain support for it and keep the code in line with btc mining and fix any unique scrypt bugs instead of letting it rot in hell which is what I'm tempted to do. It's no secret I find the scrypt code annoying and difficult to support because of its non-deterministic behaviour. I'm not against alternative cryptocurrencies or LTC per se, it's just that I primarily care about BTC. There already have been very big scrypt updates behind the scenes in cgminer the last 6 months and no one gave a rat's arse till they abandoned GPU mining on BTC. As I've said elsewhere, I got a big donation to add scrypt support to cgminer originally, and then in the 6 months since then got a sum total of 3.6LTC in donations until a week ago. I'm only giving it some foreground attention now because of the recent donations. The fact is I have to hold onto a GPU to even try and keep support for it when I was planning on selling all of them (I've sold 3 of my 4 GPUs).  Yes, I can be "paid to care", I admit it. Keep the donations coming and I'll even stop complaining about it (as much)  

See this litecoin thread for a failed attempt to start a "bounty" as such.
http://forum.litecoin.net/index.php?topic=1389

Gee, thanks. I hadn't thought of that. 

HOW?

Hey Con,

In the case where we get the right amount of donations, do you envision many more improvements that could be done for Scrypt support? I think that with the current state of the mining market, a big Scrypt update could rally many people for donations.

GPU monitoring requires  constant same-user access to the values. This is a known OS limitation and there is no workaround if you are switching users.