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

Here are some photos from Kanoi on his trip to BFL to inspect their ASIC progress. He returns this weekend, and the chips have not yet arrived to be assembled, as they're still in the bumping facility - BFL couldn't manage to make the bumping facility work any faster, but they're poised and ready to assemble when they do.

http://198.245.60.111/Pix/

Meanwhile myself and him have made some progress generically on preparing for ASIC support in cgminer, but the real driver won't be written until there's some hardware to actually test it on.

If anyone's in Australia and interested in buying the 7970s used by me in developing cgminer, now's your chance to buy one

http://www.ebay.com.au/itm/SAPPHIRE-HD-7970-3GB-GDDR5-/321074334615

Ironically I've made some tiny improvements to the OpenCL kernel and will be squeezing a few tiny drops more out of them in the next cgminer release. I feel it's my last chance to do anything with OpenCL and bitcoin mining and I'm gonna miss it.

I also found this to be the case, I too am mining with ozcoin ATM. Wasn't sure if it was due to the server or my miner though.

It is not actually RPC, it is just a JSON formatted packet into a raw socket and a JSON packet read out.

I have an example of how to use the interface to change pools though, I use it in MinePeon ( http://mineforeman.com/minepeon/ )
so users can change their mining pool from the WebUI.

You can either download MinePeon and grab the code for yourself or if you can wait I will post the code here in about 8 hours.

Mark,
 There are php tools out there.. kanos miner.php i think does it. and i use my own that shows aggregated fans speeds and other stuff>

https://bitcointalksearch.org/topic/cgminer-web-monitor-beta-v08-58834

I haven't updated it in a long time,  my current version is only different as it shows highest share and blocks found fields.

Maybe related: during recent ozco.in server reorganization I noticed that if your primary pool is a stratum one and it is down when cgminer starts, it just hangs there and does nothing (beside of searching for active pools).

cgminer used was commit 0b833131616 from three days ago.

Sorry if this has already been reported, didn't follow cgminer discussion since it is working rock-solid

Thats great news!
I am glad the resume function is being added (actually that it even got added to the spcification). That will help alleviate the last few shares that seem to go unpaid execpt for a lost in transmission packet.
Thank You for all your hard work!

You're welcome.

The issue is some disconnects are impossible to detect, apart from noticing the pool has gone silent for an extended time. During that sort of outage, cgminer continues mining until it times out, not getting a response. The timeout needs to be long enough to be sure the pool is no longer sending info, and not too long to waste ages mining. So yes, it keeps mining. Anyway hopefully this should be better since the next version will include support for the new mining.resume function. This is already built into the git version, but only rEligius currently supports it. Hopefully other pools will follow suit.

I noticed with 2.10.4 and in 2.10.5 that when the stratum pool disconnects CGMiner keeps working on that pool's work. At least it appears that is what it does. I get a disconnect and eventually a number of shares discarded last time I noticed it was 17. Of course this seems like too many to me with 1 BFL single currently running on Eclipse 1 at a WU of 12.

The reasons I think it keeps working on the disconnected pool for 2 reason. Both may be faulty and I don't want to alarm anyone. Firstly the discarded shares are usually 60-90 seconds after the disconnect. Expiry would account for that much but not why I had 90 seconds backlog at disconnect. If the pool hadn't taken 90 seconds worth of work it was already sick or dying. Secondly although the BFL single keeps hashing I see no mention of swiching pools (it could be a cosmetic issue). This is substantiated by bad luck notwithstanding 0 shares being delivered to 3 backup pools (eclipse 2 diff1, Eclipse 3 diff1 and a local bitpenny Diff8). I am sure that in 60 seconds I wouldn't expect to see a share everytime for difficulty 8 bitpenny. Aside from a work unit being used from getwork while switching to a stratum server on a change I would expect 1 work unit to bitpenny, then (in 60 seconds) ~11 to eclipse 2 (the next pool in order). I also have never noticed the pool at the top Connected to (blah blah blah) change when this happens. Again that could be cosmetic.

Running windows 7, 1 BFL single, and stratum to Eclipse (three different servers) and a backup bitpenny using getwork.

Also I am pretty sure even factoring in discards as rejects my reject rate is lower using stratum. Thank You for the stratum support.

Kon,

There is a potential memleak introduced with latest commit:
Add timestamps to stratum_share structs as they're generated and copy
https://github.com/ckolivas/cgminer/commit/1bf1f4a2174c28a3ae358c6a8b9544e93f35bfac

work->sessionid = strdup(pool->sessionid);

However work->sessionid has been never freed.

Probably the right place to free it is:

void clean_work(struct work *work) {
  if(work->sessionid)
      free(work->sessionid);
....

}

More over it might be a memleak here also even though i am not quite sure about it

https://github.com/ckolivas/cgminer/commit/c851f3959894379b213cd81ecbf8317b2ad4f313

pool->sessionid = json_array_string(res_val, 3);

if json_array_string returns a copy pool->sessionid shall be freed also somewhere right?


PS: probably this is not an issue as long as  json_array_string - > json_array_get returns  Borrowed reference and there is no need to be freed

Thank you Kon! it has been fixed:
https://github.com/ckolivas/cgminer/commit/16c7c983ae9e5ce03a2adc2c573a0c62bfdfefde


 

Is it the driver that keeps mucking things up, or the ocl runtime that gets updated every month?

It keeps changing as AMD skillfully keeps releasing broken shit... plus GPUs are going the way of the dodos shortly for BTC, so our attention to GPU issues is dropping off to almost zero. Try driver 12.8

Would it be possible to update the first post with the optimal driver/sdk config for CGMiner? Not knowing this, I just defaulted to latest

13.1 is fucked.

Although your post lacks info, I'm also having performance issues with a 5870 on the latest build of CGMiner doing Scrypt, so perhaps our symptoms are related.

I built latest from git this morning on CentOS 6.3 with the latest 13.1 drivers from AMD as well as the APP SDK 2.8, so it's all up to date. The command line I'm using is:


I'm currently only geting about 150Khash/sec on this card and unable to push past intensity 11 without getting GPU errors such as:
                 

Using the same card with CGMiner in Windows I'm able to get 300Khash/sec no problem with a higher intensity (19) and no hardware errors.

Curious if anyone else is having this issue! Thanks in advance!

why do I have only max. 48.5 K cgminer with --scrypt option on a 5870?

TIA

My computer is sitting mostly idle, it is a headless low cpu unit, this is true, being a HP 5530 thin client, but cgminer 2.9.7 hasn't this problem on the same hardware with the same number of CM1 boards.

It is something that has changed since 2.10.4, so, for the time being I'll keep using 2.9.7.

Thanks for the explanation on the way it works.

spiccioli

Like I said, I didn't take that part out. Your card reports it wont take it, the function returns an error and then just generates even more crap than usual.

Nope, still doesn't work for me for really large thread-concurrency values.  It gives an error that the maximum size for a buffer is 2^29 still.

It's not enough to warrant a new release but here is a 2.10.5 win32 build with that one change:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

I'm well aware of the need for higher memory clocks but it makes no difference since I was already setting clock speeds high and getting 575kh.

I am unable to go beyond 12288 without the padbuffer being completely broken, and ignoring the return message that it fails to set the padbuffer just generates garbage if I disable it (which I haven't in this binary). Could have something to do with me having 4 GPUs in that rig as well, but I'm not taking it down from mining BTC to work on scrypt. This was a coincidental finding and I have admitted many times I don't understand how opencl scrypt really works and am not inclined to study it any further.

Intensities over 13 continue to generate garbage instead of more hashes. YMMV.

Can you rebuild and re-release for win32?  After testing it I'll put it in the litecoin mining FAQ

Your card will only run faster with higher thread-concurrencies if you make corresponding changes in intensity; for 7970s you need thread-concurrency = 21000 or and then you can crank intensity up to 19 or 20 instead of 13.  You additionally need memory to be moving quickly, ratio of 0.66666 seems best to me (eg core 800 MHz, memory 1200 MHz).  7xxx GCN is weird about memory ratios and having the memory set too low reduces hash speed in a bizarre and inexplicable fashion, see

https://bitcointalksearch.org/topic/m.1302319