Bitcoin Forum
December 08, 2016, 02:39:29 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 [210] 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 ... 830 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.9.2  (Read 4822255 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
johnyj
Legendary
*
Offline Offline

Activity: 1806


Beyond Imagination


View Profile
February 23, 2012, 10:18:20 AM
 #4181

I'm interested in AMDOverdriveCtrl  you talked about,
I downloaded the package and find out that it is a GUI software,
I wonder if it can be used remotely to control clock/voltage?

AMdOverdriveCtrl can't change anything that cgminer can't.  cgminer already gives you remote access to clock/voltage/fan/inensity/etc.
Cheesy Straight from my script:

14) An OC option:
 This is no longer needed since cgminer 2.* includes OC, however:

I use AMDoverdriveCtrl for 2 reason:

1. I want cgminer to focus on the mining without caring about the GPU management, it will be much easy to trouble shooting when something went wrong

2. The fan speed control of AMDoverdriveCtrl is more convenient to use. In cgminer, the fan speed keeps shooting up and down, lagging the real change in GPU temperature

Actually I did build cgminer once without ADL_SDK, but then I'm not able to see the GPU info, especially when doing ssh into the machine. So the function  of monitoring the GPU is still very useful

1481164769
Hero Member
*
Offline Offline

Posts: 1481164769

View Profile Personal Message (Offline)

Ignore
1481164769
Reply with quote  #2

1481164769
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
February 23, 2012, 10:24:15 AM
 #4182

New version: Version 2.3.0 - February 23, 2012

Human readable summary:
New kernels across the board, including Diablo kernel. Selection is carefully designed to be optimal by default according to device and SDK combination.
Much better coping with SDK 2.6 so it no longer warns excessively about it, but note it's STILL faster with most cards on earlier SDKs.
Fixed the huge dip in hashrate with all the extra longpolls.
Fixed the number of extra longpolls during pool switch.
Hopefully fixed the device OFF problem.
Added Icarus FPGA support.
Can set kernel, vector and worksize per device now with -k diablo,phatk,phatk,poclbm -v 2,2,2,1 -w 128,256,256,64 for example
Hashrate at startup should be more meaningful sooner.
New --benchmark feature to test hashrate. Leave it running for ~3 mins to get reliable results, then quit and check the summary! Great for testing multiple same devices with different kernels, vectors etc. Produces NO HASHES so don't leave it running  Wink
Engine clock speed should ramp up instantly after a period of network outage which drops the profile to low power.
New API commands for pool management.
Fixes to API code to shut down cleanly.


Full changelog:
- Consider extra longpoll work items as staged_extra so as to make sure we queue
more work if queueing regular work items as longpolls.
- Use diablo kernel on all future SDKs for Tahiti and set preferred vector width
to 1 on poclbm kernel only.
- Explicitly type the constants in diakgcn kernel as uint, to be in line with
poclbm kernel.
- Reset all hash counters at the same time as resetting start times to get
accurate hashrates on exiting which is mandatory for benchmarking.
- Report thread out before it starts to avoid being flagged as sick when waiting
for the first work item.
- Don't disable and re-enable devices as they may recover and in the meantime
have their status set to OFF.
- API new commands enablepool and disablepool (version already incremented)
- Tolerate new-format temperature readings for bitforce
- Modify cgminer.c pool control to allow API to call it
- Bugfix: Fix BitFORCE driver memory leak in debug logging
- Extra byte was being unused in poclbm leading to failure on some platforms.
- Explicitly type the constants in poclbm kernel as uint.
- Don't save 'include' when saving the configuration
- Allow configuration file to include another recursively
- Use the SDK and hardware information to choose good performing default
kernels.
- Move phatk kernel to offset vector based nonce bases as well.
- Add a --benchmark feature which works on a fake item indefinitely to compare
device performance without any server or networking influence.
- Allow writing of multiple worksizes to the configuration file.
- Allow writing of multiple vector sizes to the configuration file.
- Allow writing of multiple kernels to the configuration file.
- Allow multiple different kernels to be chosen per device.
- Allow the worksize to be set per-device.
- Allow different vectors to be set per device.
- If we're well below the target temperature, increase gpu engine speed back to
maximum in case we have gotten lost between profiles during an idle period.
- We should be setting the value of fan_optimal, not its address.
- As all kernels will be new versions it's an opportunity to change the .bin
format and make it simpler. Specifying bitalign is redundant and long can be l.
- Use any() in kernel output code.
- Put the nonce for each vector offset in advance, avoiding one extra addition
in the kernel.
- Reset times after all mining threads are started to make estimating hashrates
easier at startup.
- Bugfix: allow no-exec (NX) stack
- Fix minor warning.
- fix the bitforce.c code style follow 1TBS
- fix icarus.c compile warning
- small changes to speedup no vec for AMD 898.1 OCL runtime
- Update licensing to GPL V3.
- Reset the longpoll flag after it's been used once to prevent it restarting
work again.
- Begin import of DiabloMiner kernel.
- Modify API debug messages to say API instead of DBG
- When API shuts down cgminer don't kill itself
- Don't make rolled work from the longpoll be seen as other longpoll work items.
- API add 'privileged' command so can verify access level
- Set the lp_sent variable under lock since there will almost always be a race
on setting this variable, potentially leading to multiple LPs being sent out.
- API restrict access to all non display commands by default
- Update API version to 1.2 for new 'Log Interval'
- API add --log Interval to 'config' reply
- --api-allow special case 0/0 means all

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Vbs
Hero Member
*****
Offline Offline

Activity: 504


View Profile
February 23, 2012, 10:41:12 AM
 #4183

New version: Version 2.3.0 - February 23, 2012

Thanks for the update mate, but this version doesn't compile a bitalign kernel for my cards (5850's), it's the non-bitalign kernel which is much slower (~320MH/s vs ~400MH/s).

Copying over the bin from the previous version and renaming it from "phatk120213Cypressbitalignv2w256long4" to "phatk120222Cypressv2w256l4" doesn't work also (HW failures).
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
February 23, 2012, 10:42:45 AM
 #4184

New version: Version 2.3.0 - February 23, 2012

Thanks for the update mate, but this version doesn't compile a bitalign kernel for my cards (5850's), it's the non-bitalign kernel which is much slower (~320MH/s vs ~400MH/s).

Copying over the bin from the previous version and renaming it from "phatk120213Cypressbitalignv2w256long4" to "phatk120222Cypressv2w256l4" doesn't work also (HW failures).
Woah now there is nothing that should stop it compiling a bitalign kernel. It just stops CALLING it bitalign. You're not doing the SDK 2.6 dance are you?

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Vbs
Hero Member
*****
Offline Offline

Activity: 504


View Profile
February 23, 2012, 10:49:51 AM
 #4185

New version: Version 2.3.0 - February 23, 2012

Thanks for the update mate, but this version doesn't compile a bitalign kernel for my cards (5850's), it's the non-bitalign kernel which is much slower (~320MH/s vs ~400MH/s).

Copying over the bin from the previous version and renaming it from "phatk120213Cypressbitalignv2w256long4" to "phatk120222Cypressv2w256l4" doesn't work also (HW failures).
Woah now there is nothing that should stop it compiling a bitalign kernel. It just stops CALLING it bitalign. You're not doing the SDK 2.6 dance are you?

Yeah, I just read the changelog carefully. Nope, no dance, jumping back to 2.2.7 immediately gets back to ~400MH/s (I always unpack each cgminer version to a fresh folder, no leftovers from prev vers). I'll try the other kernels to see how they go. Tongue
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
February 23, 2012, 10:53:20 AM
 #4186

New version: Version 2.3.0 - February 23, 2012

Thanks for the update mate, but this version doesn't compile a bitalign kernel for my cards (5850's), it's the non-bitalign kernel which is much slower (~320MH/s vs ~400MH/s).

Copying over the bin from the previous version and renaming it from "phatk120213Cypressbitalignv2w256long4" to "phatk120222Cypressv2w256l4" doesn't work also (HW failures).
Woah now there is nothing that should stop it compiling a bitalign kernel. It just stops CALLING it bitalign. You're not doing the SDK 2.6 dance are you?

Yeah, I just read the changelog carefully. Nope, no dance, jumping back to 2.2.7 immediately gets back to ~400MH/s (I always unpack each cgminer version to a fresh folder, no leftovers from prev vers). I'll try the other kernels to see how they go. Tongue
What does:
cgminer -n
report? And what kernel .bin file is being generated for you by default?

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
The00Dustin
Hero Member
*****
Offline Offline

Activity: 806


View Profile
February 23, 2012, 11:03:06 AM
 #4187

Nope, no dance, jumping back to 2.2.7 immediately gets back to ~400MH/s (I always unpack each cgminer version to a fresh folder, no leftovers from prev vers).
Unless you can say "Nope, no dance, I don't have SDK 2.6 installed" or "Nope, no dance, jumping back to a fresh install of 2.2.7 that compiles a fresh kernel immediately gets back to ~400MH/s" you are probably doing the dance.  Most people doing the dance don't know it.
The00Dustin
Hero Member
*****
Offline Offline

Activity: 806


View Profile
February 23, 2012, 11:04:46 AM
 #4188

ck, if you can give me a hint as to how to compile a 32-bit version on a 64-bit linux machine, I can provide cypress kernels for l4 along with l8 from SDK 2.1.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
February 23, 2012, 11:06:03 AM
 #4189

ck, if you can give me a hint as to how to compile a 32-bit version on a 64-bit linux machine, I can provide cypress kernels for l4 along with l8 from SDK 2.1.
Cannot do. You can only make 32 bit kernels from running on 32 bit OS I'm afraid.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Vbs
Hero Member
*****
Offline Offline

Activity: 504


View Profile
February 23, 2012, 11:07:19 AM
 #4190

The cgminer window closes really fast on Windows, you really need to put an #ifdef win getch() at the end of execution, since piping the output doesn't work either Tongue

Anyway, by a screen grab, it shows Platform version: OpenCL 1.1 AMD-APP-SDK-v2.5 (793.1), with 1 platform device (GPU 0 ATI Radeon HD 5800 Series), and my settings for engine (970) and mem (150).

The default kernel is phatk120222Cypressv2w128l4.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
February 23, 2012, 11:10:19 AM
 #4191

The cgminer window closes really fast on Windows, you really need to put an #ifdef win getch() at the end of execution, since piping the output doesn't work either Tongue

Anyway, by a screen grab, it shows Platform version: OpenCL 1.1 AMD-APP-SDK-v2.5 (793.1), with 1 platform device (GPU 0 ATI Radeon HD 5800 Series), and my settings for engine (970) and mem (150).

The default kernel is phatk120222Cypressv2w128l4.
Now that's a serious groaner since the phatk kernel is only trivially changed it should not perform any differently  Huh Try -v 2 -w 256 since you're grossly underclocking memory.

If you start it from a dos prompt window the window won't close...

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Vbs
Hero Member
*****
Offline Offline

Activity: 504


View Profile
February 23, 2012, 11:19:11 AM
 #4192

The cgminer window closes really fast on Windows, you really need to put an #ifdef win getch() at the end of execution, since piping the output doesn't work either Tongue

Anyway, by a screen grab, it shows Platform version: OpenCL 1.1 AMD-APP-SDK-v2.5 (793.1), with 1 platform device (GPU 0 ATI Radeon HD 5800 Series), and my settings for engine (970) and mem (150).

The default kernel is phatk120222Cypressv2w128l4.
Now that's a serious groaner since the phatk kernel is only trivially changed it should not perform any differently  Huh Try -v 2 -w 256 since you're grossly underclocking memory.

If you start it from a dos prompt window the window won't close...

V2w256 is what I always use to get the ~400MH/s, but it seems to hover around ~320MH/s now. Gonna let it run more time and see if the stats change.

I did start it from a dos prompt, but it creates a new (console) window and closes it after it's done. Piping the output like "cgminer -n > report.txt" doesn't work either. Windows really sucks on these small things :S
Vbs
Hero Member
*****
Offline Offline

Activity: 504


View Profile
February 23, 2012, 11:32:39 AM
 #4193

I now have one 5850 running cgminer 2.2.7 and another on 2.3.0, on the same engine/mem clocks. I'll be counting the accepted shares on the pool they are connected to and see if there is a significant difference. Cgminer 2.2.7 is reporting ~400MH/s and 2.3.0 is reporting ~320MH/s atm. At first glance, it seems they are submitting the same amount of shares (39 vs 40), so this could just be a "cosmetic" change in cgminer 2.3.0.  Grin
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
February 23, 2012, 11:36:18 AM
 #4194

I now have one 5850 running cgminer 2.2.7 and another on 2.3.0, on the same engine/mem clocks. I'll be counting the accepted shares on the pool they are connected to and see if there is a significant difference. Cgminer 2.2.7 is reporting ~400MH/s and 2.3.0 is reporting ~320MH/s atm. At first glance, it seems they are submitting the same amount of shares (39 vs 40), so this could just be a "cosmetic" change in cgminer 2.3.0.  Grin
That, unfortunately, does not make sense... and this hashrate drop is more than a little disturbing since there is no real valid explanation for it.

edit: it's so big it's like one has an intensity set and the other is running dynamic.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Vbs
Hero Member
*****
Offline Offline

Activity: 504


View Profile
February 23, 2012, 11:42:26 AM
 #4195

I now have one 5850 running cgminer 2.2.7 and another on 2.3.0, on the same engine/mem clocks. I'll be counting the accepted shares on the pool they are connected to and see if there is a significant difference. Cgminer 2.2.7 is reporting ~400MH/s and 2.3.0 is reporting ~320MH/s atm. At first glance, it seems they are submitting the same amount of shares (39 vs 40), so this could just be a "cosmetic" change in cgminer 2.3.0.  Grin
That, unfortunately, does not make sense... and this hashrate drop is more than a little disturbing since there is no real valid explanation for it.

edit: it's so big it's like one has an intensity set and the other is running dynamic.

Yeah, you're right, it was just wishful thinking... The one on 2.3.0 has a U:4.22 vs 2.2.7 with U:5.35. Both are running at I:9.
stevegee58
Hero Member
*****
Offline Offline

Activity: 783



View Profile
February 23, 2012, 11:57:39 AM
 #4196

My 6770 runs waaaaaaaaaaaaaaaaay faster with the diablo kernel.

I was reliably getting around 185-190 Mhash/sec with poclbm and phatk.  Now it's reliably around 202 with diablo.  Really noice!

I did notice that suddenly my poclbm performance dropped from around 185 to like 165 with this new release.  But I'm not complaining because of the pleasant diablo surprise.

You are in a maze of twisty little passages, all alike.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
February 23, 2012, 12:00:14 PM
 #4197

My 6770 runs waaaaaaaaaaaaaaaaay faster with the diablo kernel.

I was reliably getting around 185-190 Mhash/sec with poclbm.  Now it's reliably around 202 with diablo.  Really noice!
Excellent, that's more the sort of news I was hoping for  Grin

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
tenzor
Sr. Member
****
Offline Offline

Activity: 316


View Profile
February 23, 2012, 12:01:48 PM
 #4198

My 6770 runs waaaaaaaaaaaaaaaaay faster with the diablo kernel.

I was reliably getting around 185-190 Mhash/sec with poclbm.  Now it's reliably around 202 with diablo.  Really noice!

Hmm. my 6770 runs around 230 Nhash/sec with phatk at 1030/300 clocks. -v2 -w256
stevegee58
Hero Member
*****
Offline Offline

Activity: 783



View Profile
February 23, 2012, 12:03:39 PM
 #4199

My 6770 runs waaaaaaaaaaaaaaaaay faster with the diablo kernel.

I was reliably getting around 185-190 Mhash/sec with poclbm.  Now it's reliably around 202 with diablo.  Really noice!

Hmm. my 6770 runs around 230 Nhash/sec with phatk at 1030/300 clocks. -v2 -w256

I haven't been able to reliably run my 6770 above 960.

You are in a maze of twisty little passages, all alike.
tenzor
Sr. Member
****
Offline Offline

Activity: 316


View Profile
February 23, 2012, 12:29:44 PM
 #4200

I haven't been able to reliably run my 6770 above 960.
Ok. @960/300 I have 220-225
cgminer 2.2.6

Edit:
Summary:
@960/300 = 220-225
@1000/300 = around 230

cgminer 2.2.6
-I 9 -v 2 -w 256 -k phatk
SDK 2.4, ubuntu, catalyst 11.6
Pages: « 1 ... 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 [210] 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 ... 830 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!