Icarus works fine now on Windows so my 5 BTC bounty goes to ckolivas. I do feel that kano and xiangfu should also get a part of this but con was the man that made it available to me !
Much appreciate the donation. Enjoy. 
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 609. (Read 5805746 times)
March 31, 2012, 08:50:38 AM
March 31, 2012, 08:40:13 AM
Icarus works fine now on Windows so my 5 BTC bounty goes to ckolivas. I do feel that kano and xiangfu should also get a part of this but con was the man that made it available to me !
March 31, 2012, 12:47:48 AM
March 31, 2012, 12:43:20 AM
I downloaded the 64 bit Ubuntu build and it keeps saying it can't find the cgminer executable.
Not sure why exactly; I've downloaded it twice now and I can clearly see the executable in the folder.
My bad, I built it on my desktop arch at home and forgot I used to do it on ubuntu. I'll update it shortly.Code:
tyler@tyler-pc:~/cgminer$ ./cgminer.sh
./cgminer.sh: 3: /home/tyler/cgminer/cgminer: not found
Not sure why exactly; I've downloaded it twice now and I can clearly see the executable in the folder.
March 31, 2012, 12:34:57 AM
I downloaded the 64 bit Ubuntu build and it keeps saying it can't find the cgminer executable.
Not sure why exactly; I've downloaded it twice now and I can clearly see the executable in the folder.
Code:
tyler@tyler-pc:~/cgminer$ ./cgminer.sh
./cgminer.sh: 3: /home/tyler/cgminer/cgminer: not found
Not sure why exactly; I've downloaded it twice now and I can clearly see the executable in the folder.
March 31, 2012, 12:11:39 AM
New version: 2.3.2 March 31 2012
Despite the huge changelog, there should be little risk in updating, with extra features and enhancements that don't affect the internals dramatically which is why the version number is still 2.3.x
Human readable changes:
Better BFL support.
Support for Icarus devices
Better hashrate calculator
Massive rewrite of poclbm kernel for fastest hashrate yet on 2.6 SDKs.
Minor updates to diablo kernel.
Updated diapolo kernel.
Attempt to get ADL stats again if they stop working.
Fanspeed starts at 50% now instead of 85% in auto mode.
Extra RPC API features.
Discarded stale counter won't rise if stales are force submitted.
Display the beginning of the new block in verbose mode in the logs.
Fixed dual GPU device fancontrol.
Monitor app started with -m should be terminated on cgminer exit.
Full changelog:
- Damping small changes in hashrate so dramatically has the tendency to always
make the hashrate underread so go back to gentle damping instead.
- Revert the crossover of variables from Vals to W in poclbm kernel now that
Vals are the first declared variables so they're used more frequently.
- Vals variables appearing first in the array in poclbm is faster.
- Change the preferred vector width to 1 for Tahiti only, not all poclbm
kernels.
- Use a time constant 0.63 for when large changes in hashrate are detected to
damp change in case the large change is an aliasing artefact instead of a real
chang
- Only increment stale counter if the detected stales are discarded.
- Attempt to re-initialise ADL should a device that previously reported fanspeed
stops reporting it.
- Move the ADL setup and clearing to separate functions and provide a reinit_adl
function to be used when adl fails while running.
- Use slightly more damping on the decay time function in the never-ending quest
to smooth off the hashmeter.
- Set the starting fanspeed to a safe and fairly neutral 50% when autofan is
enabled.
- Provide locking around updates of cgpu hashrates as well to prevent multiple
threads accessing data fields on the same device.
- Display the beginning of the new block in verbose mode in the logs.
- Reinstate old diablo kernel variable ordering from 120222, adding only goffset
and vector size hint. The massive variable ordering change only helped one SDK
on
- Change the version number on the correct kernels.
- api.c devicecode/osinfo incorrectly swapped for json
- Add extensive instructions on how to make a native windows build.
- Update version numbers of poclbm and diablo kernels as their APIs have also
changed.
- Use global offset parameter to diablo and poclbm kernel ONLY for 1 vector
kernels.
- Use poclbm preferentially on Tahiti now regardless of SDK.
- Remove unused constant passed to poclbm.
- Clean up use of macros in poclbm and use bitselect everywhere possible.
- Add vector type hint to diablo kernel.
- Add worksize and vector attribute hints to the poclbm kernel.
- Spaces for non-aligned variables in poclbm.
- More tidying of poclbm.
- Swap Vals and W variables where they can overlap in poclbm.
- More tidying of poclbm.
- Tidy up first half of poclbm.
- Clean up use of any() by diablo and poclbm kernels.
- Minor variable symmetry changes in poclbm.
- Put additions on separate lines for consistency in poclbm.
- Consolidate last use of W11 into Vals4 in poclbm.
- Change email due to SPAM
- api.c miner.php add a '*' to the front of all notify counters - simplifies
future support of new counters
- miner.php add display 'notify' command
- Small change to help arch's without processor affinity
- Fix bitforce compile error
- api.c notify should report disabled devices also - of course
- API returns the simple device history with the 'notify' command
- code changes for supporting a simple device history
- api.c Report an OS string in config to help with device issues
- api.c fix Log Interval - integer in JSON
- api.c config 'Device Code' to show list of compiled devices + README
- api.c increase buffer size close to current code allowable limit
- removed 8-component vector support from kernel, as this is not supported in
CGMINER anyway
- forgot to update kernel modification date, fixed
- reordered an addition in the kernel, which results in less instructions used
in the GPU ISA code for GCN
- miner.php: option for readonly or check privileged access
- Ignore reduntant-with-build options --disable-gpu, --no-adl, and --no-restart
- miner.php: ereg_replace is DEPRECATED so use preg_replace instead
- Make curses TUI support optional at compile-time.
- Bugfix: AC_ARG_WITH provides withval instead of enableval
- miner.php split devs output for different devices
- api.c: correct error messages
- icarus.c modify (regular) timeout warning to only be debug
- icarus.c set the windows TODO timeout
- Allow specifying a specific driver for --scan-serial
- optimized nonce-check and output code for -v 2 and -v 4
- Bugfix: Check for libudev header (not just library) in configure, and document
optional dependency
- Add API support for Icarus and Bitforce
- Next API version is 1.4 (1.3 is current)
- README/api.c add "When" the request was processed to STATUS
- Bugfix: ZLX to read BitFORCE temp, not ZKX -.-
- Use libudev to autodetect BitFORCE GPUs, if available
- Use the return value of fan_autotune to set fan_optimal instead of passing it
as a pointer.
- Pass the lasttemp from the device we're using to adjust fanspeed in twin
devices.
- fix the name to 3 chars, fix the multi-icarus support
- Bugfix: "-S auto" is the default if no -S is specified, and there is no such
delay in using it
- README add information missing from --scan-serial
- Update README RPC API Version comment
- Bugfix: Allow enabling CPU even without OpenCL support
- Change failed-to-mine number of requested shares messge to avoid segfault on
recursive calling of quit().
- Get rid of extra char which is just truncated in poclbm kernel.
- only small code formating changes
- removed vec_step() as this could lead to errors on older SDKs
- unified code for generating nonce in kernel and moved addition of base to the
end -> faster
Despite the huge changelog, there should be little risk in updating, with extra features and enhancements that don't affect the internals dramatically which is why the version number is still 2.3.x
Human readable changes:
Better BFL support.
Support for Icarus devices
Better hashrate calculator
Massive rewrite of poclbm kernel for fastest hashrate yet on 2.6 SDKs.
Minor updates to diablo kernel.
Updated diapolo kernel.
Attempt to get ADL stats again if they stop working.
Fanspeed starts at 50% now instead of 85% in auto mode.
Extra RPC API features.
Discarded stale counter won't rise if stales are force submitted.
Display the beginning of the new block in verbose mode in the logs.
Fixed dual GPU device fancontrol.
Monitor app started with -m should be terminated on cgminer exit.
Full changelog:
- Damping small changes in hashrate so dramatically has the tendency to always
make the hashrate underread so go back to gentle damping instead.
- Revert the crossover of variables from Vals to W in poclbm kernel now that
Vals are the first declared variables so they're used more frequently.
- Vals variables appearing first in the array in poclbm is faster.
- Change the preferred vector width to 1 for Tahiti only, not all poclbm
kernels.
- Use a time constant 0.63 for when large changes in hashrate are detected to
damp change in case the large change is an aliasing artefact instead of a real
chang
- Only increment stale counter if the detected stales are discarded.
- Attempt to re-initialise ADL should a device that previously reported fanspeed
stops reporting it.
- Move the ADL setup and clearing to separate functions and provide a reinit_adl
function to be used when adl fails while running.
- Use slightly more damping on the decay time function in the never-ending quest
to smooth off the hashmeter.
- Set the starting fanspeed to a safe and fairly neutral 50% when autofan is
enabled.
- Provide locking around updates of cgpu hashrates as well to prevent multiple
threads accessing data fields on the same device.
- Display the beginning of the new block in verbose mode in the logs.
- Reinstate old diablo kernel variable ordering from 120222, adding only goffset
and vector size hint. The massive variable ordering change only helped one SDK
on
- Change the version number on the correct kernels.
- api.c devicecode/osinfo incorrectly swapped for json
- Add extensive instructions on how to make a native windows build.
- Update version numbers of poclbm and diablo kernels as their APIs have also
changed.
- Use global offset parameter to diablo and poclbm kernel ONLY for 1 vector
kernels.
- Use poclbm preferentially on Tahiti now regardless of SDK.
- Remove unused constant passed to poclbm.
- Clean up use of macros in poclbm and use bitselect everywhere possible.
- Add vector type hint to diablo kernel.
- Add worksize and vector attribute hints to the poclbm kernel.
- Spaces for non-aligned variables in poclbm.
- More tidying of poclbm.
- Swap Vals and W variables where they can overlap in poclbm.
- More tidying of poclbm.
- Tidy up first half of poclbm.
- Clean up use of any() by diablo and poclbm kernels.
- Minor variable symmetry changes in poclbm.
- Put additions on separate lines for consistency in poclbm.
- Consolidate last use of W11 into Vals4 in poclbm.
- Change email due to SPAM
- api.c miner.php add a '*' to the front of all notify counters - simplifies
future support of new counters
- miner.php add display 'notify' command
- Small change to help arch's without processor affinity
- Fix bitforce compile error
- api.c notify should report disabled devices also - of course
- API returns the simple device history with the 'notify' command
- code changes for supporting a simple device history
- api.c Report an OS string in config to help with device issues
- api.c fix Log Interval - integer in JSON
- api.c config 'Device Code' to show list of compiled devices + README
- api.c increase buffer size close to current code allowable limit
- removed 8-component vector support from kernel, as this is not supported in
CGMINER anyway
- forgot to update kernel modification date, fixed
- reordered an addition in the kernel, which results in less instructions used
in the GPU ISA code for GCN
- miner.php: option for readonly or check privileged access
- Ignore reduntant-with-build options --disable-gpu, --no-adl, and --no-restart
- miner.php: ereg_replace is DEPRECATED so use preg_replace instead
- Make curses TUI support optional at compile-time.
- Bugfix: AC_ARG_WITH provides withval instead of enableval
- miner.php split devs output for different devices
- api.c: correct error messages
- icarus.c modify (regular) timeout warning to only be debug
- icarus.c set the windows TODO timeout
- Allow specifying a specific driver for --scan-serial
- optimized nonce-check and output code for -v 2 and -v 4
- Bugfix: Check for libudev header (not just library) in configure, and document
optional dependency
- Add API support for Icarus and Bitforce
- Next API version is 1.4 (1.3 is current)
- README/api.c add "When" the request was processed to STATUS
- Bugfix: ZLX to read BitFORCE temp, not ZKX -.-
- Use libudev to autodetect BitFORCE GPUs, if available
- Use the return value of fan_autotune to set fan_optimal instead of passing it
as a pointer.
- Pass the lasttemp from the device we're using to adjust fanspeed in twin
devices.
- fix the name to 3 chars, fix the multi-icarus support
- Bugfix: "-S auto" is the default if no -S is specified, and there is no such
delay in using it
- README add information missing from --scan-serial
- Update README RPC API Version comment
- Bugfix: Allow enabling CPU even without OpenCL support
- Change failed-to-mine number of requested shares messge to avoid segfault on
recursive calling of quit().
- Get rid of extra char which is just truncated in poclbm kernel.
- only small code formating changes
- removed vec_step() as this could lead to errors on older SDKs
- unified code for generating nonce in kernel and moved addition of base to the
end -> faster
March 30, 2012, 11:12:09 PM
Finally managed to get to my target hashrate for the 7970 with my latest kernel changes to poclbm (at 1200/1050+5%):
GPU 0: 73.0C 3764RPM | 720.0/719.8Mh/s | A:186 R:0 HW:0 U:10.19/m I:11
GPU 0: 73.0C 3764RPM | 720.0/719.8Mh/s | A:186 R:0 HW:0 U:10.19/m I:11
March 30, 2012, 08:44:18 PM
March 30, 2012, 04:28:37 PM
Wow thanks. If it does nothing at all positive then it's not worth it.
I've been using this for over a month now.
Code:
#elif defined VECTORS2
uint result = W[117].x ? 0u:W[3].x;
result = W[117].y ? result:W[3].y;
if (result)
output[FOUND] = output[NFLAG & result] = result;
March 30, 2012, 03:34:52 PM
Wow thanks. If it does nothing at all positive then it's not worth it.
I've been using this for over a month now.
Code:
#elif defined VECTORS2
uint result = W[117].x ? 0u:W[3].x;
result = W[117].y ? result:W[3].y;
if (result)
output[FOUND] = output[NFLAG & result] = result;
What advantage does this give for 5xxx cards ?
Can we have it default for the next cgminer ?
Thanks !
March 30, 2012, 10:06:35 AM
Wow thanks. If it does nothing at all positive then it's not worth it.
I've been using this for over a month now.
Code:
#elif defined VECTORS2
uint result = W[117].x ? 0u:W[3].x;
result = W[117].y ? result:W[3].y;
if (result)
output[FOUND] = output[NFLAG & result] = result;
March 30, 2012, 07:55:42 AM
Wow thanks. If it does nothing at all positive then it's not worth it.
March 30, 2012, 05:08:52 AM
After running for about 10 mins, I'm getting ~51 MH/s with the changes instead of ~56 MH/s without on my Mobility Radeon 5650. (I tried both versions of the kernel with the current git master, so that other changes wouldn't falsify the results.)
sed 's/mins/hours/'The hashmeter has been tweaked, the measurements should be more stable but now, but it starts slow - please give it more time.
I noticed that. However, after the first 5 mins, there was barely any change for either run.
Note that my hashrate isn't particularly high; any fluctuations were never that high to begin with, and certainly not anywhere near 10%. With the hashmeter change, fluctuations have become even smoother, so I doubt that the hashrate would magically jump 10% just because I let it run a little longer.
AAMOF, I just checked on the run with the old version of phatk which has been running since my last post, and it is still stable at 56 MH/s. I'm initiating another run with the newer version of phatk, but I doubt the results will be significantly different.
Edit: As I expected: after 3.5h the average is at 49.5 MH/s. The Diablo kernel seems to be almost on par with the old phatk, though...
March 30, 2012, 04:33:39 AM
After running for about 10 mins, I'm getting ~51 MH/s with the changes instead of ~56 MH/s without on my Mobility Radeon 5650. (I tried both versions of the kernel with the current git master, so that other changes wouldn't falsify the results.)
sed 's/mins/hours/'The hashmeter has been tweaked, the measurements should be more stable but now, but it starts slow - please give it more time.
March 30, 2012, 01:40:12 AM
I've made a couple of what I believe to be low-risk changes to the phatk kernel in the git tree. Given how precarious this kernel has shown to be in the past, I would like it if someone has an R5xxx card and runs from git could please git it a try and confirm no loss of hashrate. Thanks.
After running for about 10 mins, I'm getting ~51 MH/s with the changes instead of ~56 MH/s without on my Mobility Radeon 5650. (I tried both versions of the kernel with the current git master, so that other changes wouldn't falsify the results.)
March 29, 2012, 11:16:06 PM
I'm using cgminer 2.3.1-2 on Windows, and can't get Catalyst 12.2 or later to work with phatk kernel and SDK 2.1. The setup that's working best for me currently is Catalyst 12.1 + SDK 2.1 with the following settings:
"gpu-memclock" : "450",
"gpu-platform" : "1",
"gpu-threads" : "1",
"kernel" : "phatk",
"intensity" : "6",
"vectors" : "2",
"worksize" : "256"
This gets me about 375-380MH/s with a 5870 at stock speed (850MHz). Note that I'm using gpu-platform to select SDK 2.1. Just to clarify, I first install Catalyst 12.1 in express mode, then SDK 2.1. After installing SDK 2.1 cgminer -n shows the additional platform.
There seems to be a problem with Catalyst 12.2 and 12.3, though. I can install either of those + SDK 2.1, and still seem to get the desired hashrate. But no shares are ever submitted! I've tried this a few times now, and cgminer consistently shows the expected hashrate with zero accepted shares. The first time I ran cgminer for a whole night on one rig, and only discovered the problem after looking at my pool stats. Deleting the bin files doesn't help.
It's easy to return to Catalyst 12.1 to get everything working again (already done), but I'd like to have the latest drivers for gaming. If I don't select the SDK at all when installing Catalyst 12.3, and then install SDK 2.4 or 2.5, I still get lower hashrates with underclocked memory. The best I've managed to reach using just Catalyst 12.3 and the included SDK is 365-370MH/s, using diablo kernel. That's close to but still lower than the expected 375-380MH/s. If I'm doing something wrong and diablo should be just as fast as phatk for a 5870, please point that out.
Should phatk + SDK 2.4 or 2.5 have problems with underclocked memory? Does anyone successfully mine with Catalyst 12.2 or later and SDK 2.1, on Windows?
"gpu-memclock" : "450",
"gpu-platform" : "1",
"gpu-threads" : "1",
"kernel" : "phatk",
"intensity" : "6",
"vectors" : "2",
"worksize" : "256"
This gets me about 375-380MH/s with a 5870 at stock speed (850MHz). Note that I'm using gpu-platform to select SDK 2.1. Just to clarify, I first install Catalyst 12.1 in express mode, then SDK 2.1. After installing SDK 2.1 cgminer -n shows the additional platform.
There seems to be a problem with Catalyst 12.2 and 12.3, though. I can install either of those + SDK 2.1, and still seem to get the desired hashrate. But no shares are ever submitted! I've tried this a few times now, and cgminer consistently shows the expected hashrate with zero accepted shares. The first time I ran cgminer for a whole night on one rig, and only discovered the problem after looking at my pool stats. Deleting the bin files doesn't help.
It's easy to return to Catalyst 12.1 to get everything working again (already done), but I'd like to have the latest drivers for gaming. If I don't select the SDK at all when installing Catalyst 12.3, and then install SDK 2.4 or 2.5, I still get lower hashrates with underclocked memory. The best I've managed to reach using just Catalyst 12.3 and the included SDK is 365-370MH/s, using diablo kernel. That's close to but still lower than the expected 375-380MH/s. If I'm doing something wrong and diablo should be just as fast as phatk for a 5870, please point that out.
Should phatk + SDK 2.4 or 2.5 have problems with underclocked memory? Does anyone successfully mine with Catalyst 12.2 or later and SDK 2.1, on Windows?
March 29, 2012, 09:42:32 PM
I've made a couple of what I believe to be low-risk changes to the phatk kernel in the git tree. Given how precarious this kernel has shown to be in the past, I would like it if someone has an R5xxx card and runs from git could please git it a try and confirm no loss of hashrate. Thanks.
Good job, I'm glad to report zero performance loss on either VLIW-4 or VLIW-5 cards.The bad news is, there's no noticeable gain either - I believe at this stage it would take no less than three 8-level wizards, an ancient grimoire, a bucket of cat blood and a slew of minor magical odds and ends to boost the hash rate.
At least git update 532179b24d made the code more elegant...
* ckolivas looks at his cat and gets evil thoughts
March 29, 2012, 07:51:03 PM
I've made a couple of what I believe to be low-risk changes to the phatk kernel in the git tree. Given how precarious this kernel has shown to be in the past, I would like it if someone has an R5xxx card and runs from git could please git it a try and confirm no loss of hashrate. Thanks.
Good job, I'm glad to report zero performance loss on either VLIW-4 or VLIW-5 cards.The bad news is, there's no noticeable gain either - I believe at this stage it would take no less than three 8-level wizards, an ancient grimoire, a bucket of cat blood and a slew of minor magical odds and ends to boost the hash rate.
At least git update 532179b24d made the code more elegant...
March 29, 2012, 05:44:34 PM
I sure hope you guys deleted the .bin files before doing this "testing" with the new kernels / drivers 
Just stating the obvious here
Just stating the obvious here
March 29, 2012, 05:42:01 PM
Thanks.
Finally upgraded to linux 12.3 driver. This one isn't as shit as 12.2 which was making my 7970 die. No difference to performance (as it is the identical 898.1 SDK) so a safe choice for GCN users.
Finally upgraded to linux 12.3 driver. This one isn't as shit as 12.2 which was making my 7970 die. No difference to performance (as it is the identical 898.1 SDK) so a safe choice for GCN users.
Jump to: