OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[-ck]

So I worked on fixing bugs only in this quick release, especially with the performance regression in there. Interestingly, 6970s didn't mind at all having the 4K output buffers, but other cards did.

Version 1.5.8 (download links in first post):

- Minimise how much more work can be given in cpu mining threads each interval.
- Make the fail-pause progressively longer each time it fails until the network
recovers.
- Only display the lagging message if we've requested the work earlier.
- Clean up the pool switching to not be dependent on whether the work can roll
or not by setting a lagging flag and then the idle flag.
- Only use one thread to determine if a GPU is sick or well, and make sure to
reset the sick restart attempt time.
- The worksize was unintentionally changed back to 4k by mistake, this caused a
slowdown.

EXECUTIVE SUMMARY:
Pool switching should be fixed, performance should be better. GPU SICK/DEAD confusion should be fixed.

[1714120048]

1714120048

[huayra.agera]

@ckolivas: Hi! Great work as usual. I just have a suggestion, maybe you can put the change log into the first page/first post since it's where each one of us turn into.

[Endeavour79]

Thanks for your work ckolivas, unfortunately the 6970s performance problem still exists. No change..

[-ck]

Thanks for your work ckolivas, unfortunately the 6970s performance problem still exists. No change..

Whatever that is, it's something else... Whatever it is... seems to be related to your move to the new phatk kernel. My 6970s on the other hand, like it a lot. Something to do with you mixing cards perhaps? Really no idea offhand

[dlasher]

Pool switching should be fixed, performance should be better. GPU SICK/DEAD confusion should be fixed.

GPU SICK/DEAD is fixed - thank you for the quick response.

[joulesbeef]

1.5.8 keeps crashing on me at random times.. and then i cant restart it without a reboot.

[-ck]

1.5.8 keeps crashing on me at random times.. and then i cant restart it without a reboot.

If it requires a reboot, then that's NOT cgminer but the driver that's crashing. A few people have found their overclocks have had to be relaxed with the latest versions of phatk. Personally I fixed all my instability issues by tossing out the 11.8 and 11.7 drivers and going back to 11.6.

[Remember remember the 5th of November]

Conman, can you tell me how to get pkg-config? I did the usual: mingw-get install pkg-config, but no dice.

[-ck]

Conman, can you tell me how to get pkg-config? I did the usual: mingw-get install pkg-config, but no dice.

See: http://www.mingw.org/wiki/FAQ
for: How do I get pkg-config installed?

It's still not easy to get it compiling under mingw32, but at least the dependencies are sorted out.

[Remember remember the 5th of November]

Partially because of my laziness, i will stay with what i've got for now. I.e 1.5.3

[miscreanity]

Multiple 69xx; Linux 2.6.38; Cat 11.6/SDK 2.4; cgminer 1.5.8 == fantastic.

I wasn't thrilled with Cat 11.7/8 processor usage and saw no discernible performance improvement with SDK 2.5 over 2.4. The 1.5.8 build maintains the same Mhash/s but utility is about 0.5% higher over several hours. No changes have been made to clock speeds or any other hardware settings since 1.5.3.

[EskimoBob]

I found some hardware that I can reproduce the slowdown on and have found the offending change. It was actually unintentional. I've pushed the fix to git and it will be in the next version.

Thank you for the fix. I lost about 14% with the update to cgminer-1.5.7
Running  Gentoo Linux, vid card is 6950, x11-drivers/ati-drivers-11.6 and ati-stream-sdk-v2.3  

EDIT: cgminer-1.5.8 is about 3% slower
EDIT: cgminer-1.5.8 is back to normal 371Hhs

[DBordello]

Would it be possible to not have cgminer try to restart a SICK gpu?  Doing so locks my machine completely.  This is the last thing I see:


[2011-08-23 16:50:05] Accepted 0427cc9b GPU 0 thread 3 pool 0
[2011-08-23 16:50:36] Thread 2 idle for more than 60 seconds, GPU 2 declared SICK!

[2011-08-23 16:50:36] Attempting to restart GPU
[2011-08-23 16:50:36] Thread 2 still exists, killing it off
[2011-08-23 16:50:36] Thread 5 still exists, killing it off

[joulesbeef]

1.5.8 keeps crashing on me at random times.. and then i cant restart it without a reboot.

If it requires a reboot, then that's NOT cgminer but the driver that's crashing. A few people have found their overclocks have had to be relaxed with the latest versions of phatk. Personally I fixed all my instability issues by tossing out the 11.8 and 11.7 drivers and going back to 11.6.

Hmm I have no problem with phatk 2.1 or 2.2 or the diablo builds any date with my other software

and i threw out 11.8 and 11.7 a while ago and went back to straight old 11.6 no B included.

but thanks for the info I will play with clocks a little(i'm also barely overclocked.. i dont like pushing it that hard)

[-ck]

1.5.8 keeps crashing on me at random times.. and then i cant restart it without a reboot.

If it requires a reboot, then that's NOT cgminer but the driver that's crashing. A few people have found their overclocks have had to be relaxed with the latest versions of phatk. Personally I fixed all my instability issues by tossing out the 11.8 and 11.7 drivers and going back to 11.6.

Hmm I have no problem with phatk 2.1 or 2.2 or the diablo builds any date with my other software

and i threw out 11.8 and 11.7 a while ago and went back to straight old 11.6 no B included.

but thanks for the info I will play with clocks a little(i'm also barely overclocked.. i dont like pushing it that hard)

Decreasing intensity can help as well. It's the combination of the latest phatk kernel and the high intensity in cgminer that pushes cards to their limit. You may find the reduction in hash rate to be insignificant but the stability to increase. Try -I 7 instead of 8.

[iopq]

I'm using -I 4 and I get hardware errors with 1.5.8
like 300 hardware errors when I was at the gym and some accepted

changing kernels (as in killing 1.5.8 and starting 1.5.6) also locks up my computer :/

I'll use the newer version a little bit more and investigate
I just rebooted and got two more hardware errors while posting and I'm kinda giving up

[sharky112065]

OK, I'm going to try cgminer in Linux via Linuxcoin and using Smartcoin to manage the windows/screens.

I noticed that Linuxcoin the release version comes with cgminer 1.5.5. What is the best way to upgrade it to 1.5.8 on Linuxcoin?

[phase]

OK, I'm going to try cgminer in Linux via Linuxcoin and using Smartcoin to manage the windows/screens.

No way! You mean you're actually going to put in some effort yourself to get it working the way you want to? No, seriously, I'm also running it on Linuxcoin, same resolution, if it's of any help: you should be able to fit 4 windows next to each other on the same screen easily.

I noticed that Linuxcoin the release version comes with cgminer 1.5.5. What is the best way to upgrade it to 1.5.8 on Linuxcoin?

Best way: Download source & compile it.
Easiest: Download 64bit Ubuntu binary from first post, works like a charm.

[sharky112065]

OK, I'm going to try cgminer in Linux via Linuxcoin and using Smartcoin to manage the windows/screens.

No way! You mean you're actually going to put in some effort yourself to get it working the way you want to? No, seriously, I'm also running it on Linuxcoin, same resolution, if it's of any help: you should be able to fit 4 windows next to each other on the same screen easily.

I noticed that Linuxcoin the release version comes with cgminer 1.5.5. What is the best way to upgrade it to 1.5.8 on Linuxcoin?

Best way: Download source & compile it.
Easiest: Download 64bit Ubuntu binary from first post, works like a charm.

I'm trying lol.

Yeah I got it thanks. I used the Ubuntu binary and put it in /usr/bin along with the .cl files.

Gonna try smartcoin first as it has gpu temps and I can toggle between the screens for more detail.

[The00Dustin]

I'm using -I 4 and I get hardware errors with 1.5.8
like 300 hardware errors when I was at the gym and some accepted

changing kernels (as in killing 1.5.8 and starting 1.5.6) also locks up my computer :/

I'll use the newer version a little bit more and investigate
I just rebooted and got two more hardware errors while posting and I'm kinda giving up

For the record, when I went from 1.5.3 to 1.5.6 it would consistentsy lock up my GPU (and pretty much my computer) within an hour (sometimes in minutes) until I lowered my OC settings.  I am now getting a higher MHash/s and higher efficiency with lower OC settings.  This was true on a multi-day run with 1.5.6 (over the weekend, so at least three days) and appears to be holding true for 1.5.8 (installed yesterday) as well.  Giving up may not be to your advantage in the long run.