Hmm what do the 58xx report their name as? Cypress? It sounds like cgminer should default them to worksize 256 instead of 128. Would that be a fair assessment?
I think we should leave it default 128 as I found that works pretty good as it is.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 651. (Read 5805546 times)
February 16, 2012, 05:49:35 AM
I think we should leave it default 128 as I found that works pretty good as it is.
February 16, 2012, 05:47:46 AM
Hmm what do the 58xx report their name as? Cypress? It sounds like cgminer should default them to worksize 256 instead of 128. Would that be a fair assessment?
February 16, 2012, 05:45:24 AM
Quote from: DeathAndTaxes
You can install driver & SDK independently.
So you can install driver 11.12 to get the no CPU bug and then SDK 2.1 to maximize performance of 5000 series cards. Be sure to delete any existing bins and run cgminer to compile bins with SDK 2.1.
So you can install driver 11.12 to get the no CPU bug and then SDK 2.1 to maximize performance of 5000 series cards. Be sure to delete any existing bins and run cgminer to compile bins with SDK 2.1.
Know how to do this on Linux ?
Or shall I just stick with 11.6 and 2.1 ?
Have you tested the difference between 2.4 and 2.1 on your 5970s ? Is it really that much better compared with 2.4/2.5 ?
I have 5870s only.
Thanks !
For my 5850's I'm getting ~400MH/s (Core ~975, Mem 150MHz) with 12.1 driver and SDK 2.5.793.1 (comes with the 11.11 driver), with phatk kernel, vectors 2, worksize 256 and intensity 9. It's much faster for me than SDK 2.1 and poclbm, especially because you can clock down ram so much and bump gpu core speed.
February 16, 2012, 05:34:35 AM
Quote
I make the Icarus work with cgminer. why I do this, because cgminer is pure C. since I will try to run cgminer in a home router like TP-LINK WR1043ND(400Mhz. 32MB memory. 8MB flash). python miner needs much space. for example it's needs about ~10MB under OpenWrt. so for those
kind of device I would like using cgminer.
kind of device I would like using cgminer.
Yeah. That would be quite neat !
I also hate all that python BS and the reason I switched to cgminer in the first place. Python is for lazy programmers who can't code properly IMHO.
February 16, 2012, 05:04:58 AM
February 16, 2012, 02:51:19 AM
With Diapolo's help we finally got the diakgcn kernel working on cgminer. I've just committed code to the git tree which makes it work. Alas at the same engine and clock speeds on the 7970, diakgcn gives me 699 MHash while my customised kernel gives me 717 MHash. But now that it's working, he may be able to tweak it further...
February 15, 2012, 11:34:19 PM
Is there some way I'm not aware of (and I went back and re-read the latest docs) to set GPU core/RAM clocks on exit?
I can mine at a much higher clock/much lower memory, than I choose to game.. and if I forget to go back and reset it each time I close the miner, my desktop machine will hang..
I realize it's a small thing, but just wondering if there's a way to set it?
February 15, 2012, 11:30:52 PM
Is there some way I'm not aware of (and I went back and re-read the latest docs) to set GPU core/RAM clocks on exit?
I can mine at a much higher clock/much lower memory, than I choose to game.. and if I forget to go back and reset it each time I close the miner, my desktop machine will hang..
I realize it's a small thing, but just wondering if there's a way to set it?
February 15, 2012, 11:28:34 PM
But it was working perfectly on a previous version of cgminer... or maybe it was the driver changes to 11.12 and sdk 2.1 that caused this..? brb, downloading old cgminer version to find out.
Never blame the new version of cgminer. ALWAYS blame something else first. 
Like it might work in 11.6 and then got broken in 11.11 or something. 
February 15, 2012, 10:33:37 PM
But it was working perfectly on a previous version of cgminer... or maybe it was the driver changes to 11.12 and sdk 2.1 that caused this..? brb, downloading old cgminer version to find out.
Never blame the new version of cgminer. ALWAYS blame something else first. February 15, 2012, 10:29:03 PM
But it was working perfectly on a previous version of cgminer... or maybe it was the driver changes to 11.12 and sdk 2.1 that caused this..? brb, downloading old cgminer version to find out.
Never blame the new version of cgminer. ALWAYS blame something else first. February 15, 2012, 10:28:09 PM
Update on 7970 performance.
I did a little calculation to see how my 7970 is performing with the latest cgminer.
Clock per clock it is precisely 1/3 faster than the 6970 running at the equivalent clock speed.
What's hilarious about this is that the number of stream processors is precisely 1/3 more than the 6970 (2048 vs 1536). This is despite the 6970 running on phatk on sdk 2.5 and 7970 running on my customised poclbm on sdk 2.6. As I said before, at least on the 6970 which I don't grossly underclock the memory (only -125) I'm getting slightly better performance on poclbm with 2.6 now than phatk with 2.5.
So in terms of raw performance, I think the current cgminer release and kernel is doing pretty good.
Alas none of the magic GCN changes that aren't just more processors appear to have been exploited, and every thread I've read on suggestions to exploit them on these forums has only led to worse performance, often disastrously worse.
I did a little calculation to see how my 7970 is performing with the latest cgminer.
Clock per clock it is precisely 1/3 faster than the 6970 running at the equivalent clock speed.
What's hilarious about this is that the number of stream processors is precisely 1/3 more than the 6970 (2048 vs 1536). This is despite the 6970 running on phatk on sdk 2.5 and 7970 running on my customised poclbm on sdk 2.6. As I said before, at least on the 6970 which I don't grossly underclock the memory (only -125) I'm getting slightly better performance on poclbm with 2.6 now than phatk with 2.5.
So in terms of raw performance, I think the current cgminer release and kernel is doing pretty good.
Alas none of the magic GCN changes that aren't just more processors appear to have been exploited, and every thread I've read on suggestions to exploit them on these forums has only led to worse performance, often disastrously worse.
February 15, 2012, 10:24:57 PM
Well I wondered that, but I thought that newer drivers refused to support older SDKs. I guess I'll try it again soon.
I don't think so but with so many combinations of hardware, OS, drivers, and SDK YMMV.
That is suspiciously similar to stock, wonder if OC settings aren't being applied by cgminer? brb checking
EDIT: When I hit G then C then 0 and enter then E and typed 950 and hit enter and then Y, cgminer told me that the driver accepted the voltages, but that I should "check the values below". It didn't seem to actually OC the cards.
EDIT: Damn, 2.2.3 (which was working fine before) is doing the same thing. wtf
February 15, 2012, 10:23:26 PM
Well I wondered that, but I thought that newer drivers refused to support older SDKs. I guess I'll try it again soon.
I don't think so but with so many combinations of hardware, OS, drivers, and SDK YMMV.
That is suspiciously similar to stock, wonder if OC settings aren't being applied by cgminer? brb checking
EDIT: When I hit G then C then 0 and enter then E and typed 950 and hit enter and then Y, cgminer told me that the driver accepted the voltages, but that I should "check the values below". It didn't seem to actually OC the cards.
February 15, 2012, 10:13:53 PM
Well I wondered that, but I thought that newer drivers refused to support older SDKs. I guess I'll try it again soon.
I don't think so but with so many combinations of hardware, OS, drivers, and SDK YMMV.
That is suspiciously similar to stock, wonder if OC settings aren't being applied by cgminer? brb checking
EDIT: When I hit G then C then 0 and enter then E and typed 950 and hit enter and then Y, cgminer told me that the driver accepted the voltages, but that I should "check the values below". It didn't seem to actually OC the cards.
February 15, 2012, 09:19:18 PM
On Linux: when you install 2.6 you should do it manually.
Thanks for the heads up, that isn't the only danger with relying on the crappy installation script.
ATI always sucked where any coding was involved and AMD just kept ATI staff...
February 15, 2012, 09:05:02 PM
On Linux: when you install 2.6 you should do it manually.
It copies 2 libraries over the OS installed ones if you do it with the ATI install script.
Everything else is the similar to the cgminer README
(so is easy as long as you understand how to extract tgz files ...)
The 2 OS libraries are: libaticalcl.so libaticalrt.so
So you need to save the old links (e.g. rename them: mv libaticalcl.so libaticalcl.so.old )
If you don't want to try mess with removing and reinstalling the fglrx packages later to go back to an earlier 2.x
Hmm maybe I'll write up the steps to go forward AND back later ...
It copies 2 libraries over the OS installed ones if you do it with the ATI install script.
Everything else is the similar to the cgminer README
(so is easy as long as you understand how to extract tgz files ...)
The 2 OS libraries are: libaticalcl.so libaticalrt.so
So you need to save the old links (e.g. rename them: mv libaticalcl.so libaticalcl.so.old )
If you don't want to try mess with removing and reinstalling the fglrx packages later to go back to an earlier 2.x
Hmm maybe I'll write up the steps to go forward AND back later ...
February 15, 2012, 06:46:50 PM
Quote from: DeathAndTaxes
You can install driver & SDK independently.
So you can install driver 11.12 to get the no CPU bug and then SDK 2.1 to maximize performance of 5000 series cards. Be sure to delete any existing bins and run cgminer to compile bins with SDK 2.1.
So you can install driver 11.12 to get the no CPU bug and then SDK 2.1 to maximize performance of 5000 series cards. Be sure to delete any existing bins and run cgminer to compile bins with SDK 2.1.
Know how to do this on Linux ?
Or shall I just stick with 11.6 and 2.1 ?
Have you tested the difference between 2.4 and 2.1 on your 5970s ? Is it really that much better compared with 2.4/2.5 ?
I have 5870s only.
Thanks !
February 15, 2012, 06:42:44 PM
Well I wondered that, but I thought that newer drivers refused to support older SDKs. I guess I'll try it again soon.
I don't think so but with so many combinations of hardware, OS, drivers, and SDK YMMV.
February 15, 2012, 06:35:54 PM
Damn, I thought that was the version that removed that necessity. I'll try something newer I guess.
Any particular reason you want an ancient driver?
You can install driver & SDK independently.
So you can install driver 11.12 to get the no CPU bug and then SDK 2.1 to maximize performance of 5000 series cards. Be sure to delete any existing bins and run cgminer to compile bins with SDK 2.1.
Jump to: