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

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: ?? on ??

con, kano

Have you guys considered web user interface instead of console?
You are already providing a lot of the info via APIs so the switch
from console to http/html might not be that hard to do.

I'm not adding interfaces to the main cgminer code any more. As others have suggested, cgminer is for the engine side of things, not the interface side. The current interface is "enough" and the API makes it easy to add whatever interface you like. I'm not an interface designer.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: cablepair on March 07, 2012, 03:17:05 PM

its not in the latest windows version, I have a linux binary from the git with it compiled in to show temps but it wasnt compiled with openGL - so I cant run the Bitforce on the same machine as GPUs which I need to do in this situation.

I'll be releasing a new version with the most minor of changes once my own mining rig is back online again. Smoked a PSU so I can't test anything yet again.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: cablepair on March 05, 2012, 09:20:16 PM

ckvolias:using latest cgminer 2.3.1-2 win7 64x

after awhile I loose temps and fan speed displays both on screen and from API - a cgminer reboot fixes the issue

Windows driver ATI Display Library fsckage. I can't do anything about it. Does restarting cgminer fix it or rebooting the machine fix it? I could probably try working around the former by detecting "losing adl support" and re-initialising it.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: localhost on March 09, 2012, 07:02:42 AM

There you go:

Code:

cgminer -n[2012-03-09 12:59:20] CL Platform 0 version: OpenCL 1.1 AMD-APP (898.1)
[2012-03-09 12:59:20] Platform 0 devices: 2

AMD APP 898.1 is the sdk 2.6 that is distributed with catalyst driver 12.2 on 64 bit windows so that explains your slowdown. You've already figured out a workaround.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: fabrizziop on March 07, 2012, 10:18:27 AM

I don't know why did I miss this miner earlier, I started to use, it's very practical, now I don't have to use clocktweak and 4 phoenix miners. And, it's even giving me 20 MH/s more per card with 12.1 than phoenix with 12.1. I think this gem needs more advertising to newbies.

Thanks

Enjoy. What sort of advertising exactly could I possibly do to promote it?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: The00Dustin on March 09, 2012, 08:47:19 AM

Quote from: localhost on March 09, 2012, 08:34:59 AM

Hm, alright, thanks for all this information. I grabbed the old phatk110817.cl and phatk110817Cypressbitalignv2w128long4.bin from my cgminer 2.0.6, renamed them to phatk120223.cl and phatk120223Cypressv2w128l4.bin and this did restore my hashrate.

Judging from their date, they were built either under Catalyst 11.9 or 11.10. Should I expect any additional benefit from messing with my drivers as you describe? The changelog doesn't seem to mention performance improvements, "just" tons of features, bugfixes, and tweaks for newest GPUs.

I'm surprised that worked, actually. At some point on 2.3.0 or 2.3.1, someone tried that and it didn't work at all. I thought ck subsequentsy posted that the old binaries weren't compatible with 2.3 and that was why he did the minor vesion change from 2.2.x. I guess somewhere along the way to 2.3.1-2 he did some major reverting.

Exactly. In version 2.3.1-2 the phatk kernel is identical to the much older "good" phatk kernel that was used for months; only with the new version number.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: coblee on March 08, 2012, 06:30:52 PM

any plans to support the x6500 fpgas?

Alas no one has said they're working on support and no one has sent me one to work on to provide support. So that would be a no.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Hawkix on March 08, 2012, 02:55:09 PM

I have not checked the source code, but it seems that CGMINER keeps getting work from all defined pools, regardless if it mines on them or not. I am on very slow line (GPRS), so this hogs it the line a lot. Can it be run in "no poll" mode, just being switched on failure of primary pool?

BTW, i already use --failover-only, but it has no effect on amount of work being downloaded.

This is a gross exaggeration. It asks for precisely one work item (about 100 bytes) from pools that are not in use with --failover-only when starting up to see if those pools are alive and then never communicates with them again unless your primary pool fails. If you are having network trouble then almost certainly the problem is the rate the requests are sent out rather than the total amount of requests because often multiple requests are sent at exactly the same time. Try --net-delay to cope with that.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: coblee on March 09, 2012, 01:10:55 PM

When I run cgminer with 6 GPUs, 3-4 of them end up in the DEAD state after a while. Anyone know why that happens or how I can debug it? Quitting cgminer and restarting it fixes things.

Reduce your clocks. Dead = GPU crashed. cgminer miner tends to drive GPU harder at a given Mhz than other miners. Try backing your clocks off by 5Mhz or so.

coblee

donator

Activity: 1654

Merit: 1354

Creator of Litecoin. Cryptocurrency enthusiast.

When I run cgminer with 6 GPUs, 3-4 of them end up in the DEAD state after a while. Anyone know why that happens or how I can debug it? Quitting cgminer and restarting it fixes things.

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: localhost on March 09, 2012, 08:55:21 AM

Quote from: The00Dustin on March 09, 2012, 08:47:19 AM

EDIT: Also, with Cypress and phatk, I am under the impression that SDK 2.1 is better when the GPU memory is underclocked. You might want to dowload phatk120223Cypressv2w128l4.bin from http://ck.kolivas.org/apps/cgminer/bins/2.1/ and try out the SDK 2.1 binary that is actually compiled in 2.3.1-2.

Just tried it, doesn't work (error 42, then recompiles the slower new version over it)

Weird! I guess he did do some major backtracking by 2.3.1-2, and that kernel must have been compiled in 2.3.0-1. I do wonder why mine is working, though, pretty sure I didn't delete the kernel after I upgraded to 2.3.1-2 from 2.3.0-1. Oh well, you've got your system working well enough to make you happy, right?

localhost

sr. member

Activity: 392

Merit: 250

Quote from: sharky112065 on March 09, 2012, 10:09:03 AM

I get 442 Mh/s on my 5870's clocked at 970/170 on 2.5 (793.1). So 2.5 does just fine at lower mem clock settings (yes verified by GPUz).

I'm getting 396MH/s @890/300 currently - 333MH/s @750/300 on the other one (underclocked for silence), about 2% slower clock for clock. Tried setting the RAM @170, lost about 10% hashrate. I guess I'll have to play with the drivers a bit some time then (next time I upgrade cgminer I suppose Cheesy

). Not that urgent though, given the small speed difference.

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: localhost on March 09, 2012, 08:34:59 AM

Hm, alright, thanks for all this information. I grabbed the old phatk110817.cl and phatk110817Cypressbitalignv2w128long4.bin from my cgminer 2.0.6, renamed them to phatk120223.cl and phatk120223Cypressv2w128l4.bin and this did restore my hashrate.

Judging from their date, they were built either under Catalyst 11.9 or 11.10. Should I expect any additional benefit from messing with my drivers as you describe? The changelog doesn't seem to mention performance improvements, "just" tons of features, bugfixes, and tweaks for newest GPUs.

Well you need to get rid of that AMD-APP Run-time (2.6) and go to 2.5 or you will always have to be copying and renaming bin files every time you switch to a newer version of cgminer. Follow step 2.

I get 442 Mh/s on my 5870's clocked at 970/170 on 2.5 (793.1). So 2.5 does just fine at lower mem clock settings (yes verified by GPUz).

localhost

sr. member

Activity: 392

Merit: 250

Quote from: The00Dustin on March 09, 2012, 08:47:19 AM

I'm surprised that worked, actually.

Yeah, I wasn't really expecting it to work either, but I thought this was worth trying since I've got some stuff running that I can't really interrupt right now. Working and looking good, although I'm not using "advanced" features such as overclocking/fan control/etc - the only thing I configure from cgminer, apart from the proxy now, is the intensity.

Quote from: The00Dustin on March 09, 2012, 08:47:19 AM

EDIT2: The .cl file isn't used when you have a .bin file, you probably sohuldn't have overwritten it with the older one, but if you never change settings, it won't matter.

Kept a backup anyway

Quote from: The00Dustin on March 09, 2012, 08:47:19 AM

EDIT: Also, with Cypress and phatk, I am under the impression that SDK 2.1 is better when the GPU memory is underclocked. You might want to dowload phatk120223Cypressv2w128l4.bin from http://ck.kolivas.org/apps/cgminer/bins/2.1/ and try out the SDK 2.1 binary that is actually compiled in 2.3.1-2.

Just tried it, doesn't work (error 42, then recompiles the slower new version over it)

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: localhost on March 09, 2012, 08:34:59 AM

Hm, alright, thanks for all this information. I grabbed the old phatk110817.cl and phatk110817Cypressbitalignv2w128long4.bin from my cgminer 2.0.6, renamed them to phatk120223.cl and phatk120223Cypressv2w128l4.bin and this did restore my hashrate.

Judging from their date, they were built either under Catalyst 11.9 or 11.10. Should I expect any additional benefit from messing with my drivers as you describe? The changelog doesn't seem to mention performance improvements, "just" tons of features, bugfixes, and tweaks for newest GPUs.

I'm surprised that worked, actually. At some point on 2.3.0 or 2.3.1, someone tried that and it didn't work at all. I thought ck subsequentsy posted that the old binaries weren't compatible with 2.3 and that was why he did the minor vesion change from 2.2.x. I guess somewhere along the way to 2.3.1-2 he did some major reverting.

EDIT: Also, with Cypress and phatk, I am under the impression that SDK 2.1 is better when the GPU memory is underclocked. You might want to dowload phatk120223Cypressv2w128l4.bin from http://ck.kolivas.org/apps/cgminer/bins/2.1/ and try out the SDK 2.1 binary that is actually compiled in 2.3.1-2.

EDIT2: The .cl file isn't used when you have a .bin file, you probably sohuldn't have overwritten it with the older one, but if you never change settings, it won't matter.

localhost

sr. member

Activity: 392

Merit: 250

Hm, alright, thanks for all this information. I grabbed the old phatk110817.cl and phatk110817Cypressbitalignv2w128long4.bin from my cgminer 2.0.6, renamed them to phatk120223.cl and phatk120223Cypressv2w128l4.bin and this did restore my hashrate.

Judging from their date, they were built either under Catalyst 11.9 or 11.10. Should I expect any additional benefit from messing with my drivers as you describe? The changelog doesn't seem to mention performance improvements, "just" tons of features, bugfixes, and tweaks for newest GPUs.

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: localhost on March 09, 2012, 07:02:42 AM

Quote from: kano on March 09, 2012, 06:45:46 AM

I should say quite a lot more than that.
Post it all.
Also in the cgminer directory in a command prompt: dir/a *.bin

Woops, I ran it on version 2.0.6 instead of 2.3.1, that's why. There you go:

Code:

>cgminer -n
[2012-03-09 12:59:20] CL Platform 0 vendor: Advanced Micro Devices, Inc.
[2012-03-09 12:59:20] CL Platform 0 name: AMD Accelerated Parallel Processing
[2012-03-09 12:59:20] CL Platform 0 version: OpenCL 1.1 AMD-APP (898.1)
[2012-03-09 12:59:20] Platform 0 devices: 2
[2012-03-09 12:59:20] GPU 0 ATI Radeon HD 5800 Series hardware monitoring enable
d
[2012-03-09 12:59:20] GPU 1 ATI Radeon HD 5800 Series hardware monitoring enable
d
[2012-03-09 12:59:20] 2 GPU devices max detected

Code:

>dir/a *.bin
 Volume in drive E is xxxx
 Volume Serial Number is xxxxx

 Directory of E:\xxx\cgminer-2.3.1-2

2012-03-07  16:53           751,168 phatk120223Cypressv2w128l4.bin
               1 File(s)        751,168 bytes
               0 Dir(s)  198,869,528,576 bytes free

Edit: actually, on cgminer 2.0.6 I'm even ~730MH/s right now

I believe you may be on 2.6 AMD APP (898.1). I think you want 2.5 (793.1). The reason 2.0.6 is still probably working at the correct hash rate is because you still have the bins that were created prior to upgrading your driver (which sneaks the newer APP in). If you were to delete your .bin files in your 2.0.6 directory I'm betting that your hash rate will drop as well.

The following was posted in an earlier post...

1) Run Catalyst 12.1 installer -> Custom install -> Unselect All button -> Select GPU Driver only -> Next... Untill it's installed
2) Run Catalyst 11.11 installer -> Custom install -> Unselect All button -> Select SDK Runtime only -> Next... Untill it's installed (2.5.793.1)
3) Done!

That should give you a driver without the 100% CPU bug and the last version of SDK 2.5 runtime.

Note: I had to also install catalyst when I did step 1 to get the temp and fan monitoring in cgminer.

Don't forget to remove every thing first.

In the future when upgrading your driver, uncheck all check boxes and recheck the driver and catalyst. (custom install)

localhost

sr. member

Activity: 392

Merit: 250

Quote from: kano on March 09, 2012, 06:45:46 AM

I should say quite a lot more than that.
Post it all.
Also in the cgminer directory in a command prompt: dir/a *.bin

Woops, I ran it on version 2.0.6 instead of 2.3.1, that's why. There you go:

Code:

>cgminer -n
[2012-03-09 12:59:20] CL Platform 0 vendor: Advanced Micro Devices, Inc.
[2012-03-09 12:59:20] CL Platform 0 name: AMD Accelerated Parallel Processing
[2012-03-09 12:59:20] CL Platform 0 version: OpenCL 1.1 AMD-APP (898.1)
[2012-03-09 12:59:20] Platform 0 devices: 2
[2012-03-09 12:59:20] GPU 0 ATI Radeon HD 5800 Series hardware monitoring enable
d
[2012-03-09 12:59:20] GPU 1 ATI Radeon HD 5800 Series hardware monitoring enable
d
[2012-03-09 12:59:20] 2 GPU devices max detected

Code:

>dir/a *.bin
 Volume in drive E is xxxx
 Volume Serial Number is xxxxx

 Directory of E:\xxx\cgminer-2.3.1-2

2012-03-07  16:53           751,168 phatk120223Cypressv2w128l4.bin
               1 File(s)        751,168 bytes
               0 Dir(s)  198,869,528,576 bytes free

Edit: actually, on cgminer 2.0.6 I'm even ~730MH/s right now

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: localhost on March 09, 2012, 06:43:53 AM

Quote from: Vbs on March 09, 2012, 04:48:48 AM

Have you updated drivers/sdk on that machine since you first started 2.0.6? If you did, you are probably using SDK 2.6 now...

I've kept my drivers updated, but I haven't upgraded since I switched from 2.0.6 to 2.3.1. To be sure (Catalyst 12.2 was indeed released not long before I switched from 2.0.6 to 2.3.1), I just relaunched 2.0.6 right now: I'm still getting around 710MH/s

@kano: was "cgminer -n" for me? (it just tells me I have 2 GPUs - that's correct I have 2 5870s)

I should say quite a lot more than that.
Post it all.
Also in the cgminer directory in a command prompt: dir/a *.bin

localhost

sr. member

Activity: 392

Merit: 250

Quote from: Vbs on March 09, 2012, 04:48:48 AM

Have you updated drivers/sdk on that machine since you first started 2.0.6? If you did, you are probably using SDK 2.6 now...

I've kept my drivers updated, but I haven't upgraded since I switched from 2.0.6 to 2.3.1. To be sure (Catalyst 12.2 was indeed released not long before I switched from 2.0.6 to 2.3.1), I just relaunched 2.0.6 right now: I'm still getting around 710MH/s

@kano: was "cgminer -n" for me? (it just tells me I have 2 GPUs - that's correct I have 2 5870s)

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