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

New Windows build instructions.

http://pastebin.com/3pzivj32

Can someone with a Windows rig that has a Ztex test the new libusb section?
Need to know if you can mine successfully using libusb instead of libusbx because that is what cgminer will be going to in the future supposedly.

There ya go!  Thanks, it works now.

I assume you mean on windows? I may have built it without adl support, lemme check

EDIT: yes my fault. Repackaged the windows binaries. Try redownloading.

The auto-gpu switch is no longer recognized.

Thanks once again for all your hard work. I will send a donation tomorrow when I get back to my wallet!

New release - 2.9.5, 25th November 2012

Bugfix release.


Human readable changelog:

Fixed the crash when a GBT pool was used either as primary or backup when its gbt coinbase was very large.
Fixed the ztex submits lots of dupes bug based on an idea by luke-jr
Fixed the much larger amount of shares being leaked to backup pools
"getworks" will not be counted now from backup pools when they're just being used to see the pool is alive
Mips openwrt fixes


Full changelog:

- fixes target calc for mips openwrt
- openwrt needs roundl
- Get rid of unused last_work in opencl thread data.
- Do away with the flaky free_work api in the driver code which would often lose
the work data in opencl and simply flush it before exiting the opencl scanhash.
- Use base_work for comparison just for cleanness in __copy_work
- Remove all static work structs, using the make and free functions.
- Add pool no. to stale share detected message.
- Add info about which pool share became stale while resubmitting.
- Copy the work on opencl_free_work
- Add an extra slot in the max backlog for ztex to minimise dupes.
- Do not use or count the getworks submitted which are simply testing that pools
are still up. This was increasing share leakage and making stats not reflect
real work.
- Track all dynamically allocated memory within the work struct by copying work
structs in a common place, creating freshly allocated heap ram for all arrays
within the copied struct. Clear all work structs from the same place to ensure
memory does not leak from arrays within the struct. Convert the gbt coinbase and
stratum strings within the work struct to heap ram. This will allow arbitrary
lengths without an upper limit for the strings, preventing the overflows that
happen with GBT.
- libztex: Work around ZTEX USB firmware bug exposed by the FreeBSD libusb
- opencl: Use new dev_error function for REASON_DEV_NOSTART

Um.. Oz has variable difficulty, I'm not seeing people complain it not working there.

M

Come on now, lets be honest.  The variable difficulty isn't the problem here, Stratum is the problem: it's difficulty to work relation is broken from the ground up and needs to be fixed.  If the difficulty were too unstable, why can GW and GBT keep up just fine?  CGminer doesn't seem to have any trouble keeping up with it in GW, right?

Yes you are correct, U is accepted shares per minute.

You can calculate U directly from the screen: 60 * A / Elapsed
(Elapsed = now - Started: at the top)

Also, WU is the amount of 1 diff work done per minute by the hardware.

Note the other difference there: U is shares per minute, WU is 1 diff work per minute.
Share per minute is obviously affected by the share difficulty.

The API has all the numbers in it (both of: based on shares and based on difficulty)

Pretty sure it was just Accepted shares. Since rejects kill your hashrate I would expect the U (SPM) to drop off too.
HW in my experience (BFL single) did change U (SPM). This would be caused by 15 seconds of doing nothing. I am not sure about GPU based work as I do not own profitable hardware for that.

I am sure Kano, Con or someone far better informed will let you know if I am wrong. I could be wrong and it is even semi-likely that I am.

sorry if this has been asked again:
(U)tility is a sum of all the shares, accepted,rejected,HW?
is there any measurement (shares/min) only for accepted ones?

Inaba were you able to resolve this? I'm running into exactly the same issue.

compiled by my own.
ubuntu 12.4

./configure --enable-btcforce

at the end: curses-TUI NOT FOUND. TUI support DISABLED

what to do?

Edit: installed now libncurses5-dev ... seems to work, recompiling now
Edit2: working thx

Most likely you used -T which stops you from using the menu options ...

If you compiled it yourself (and didn't use -T), then you didn't take note that configure told you CURSES was not available
(the curses.TUI message at the end)

If someone else compiled it - don't use their version, use ckolivas or my version (depending on Linux OS version)

If you are running on a 32bit linux, then you'll need to take note of how whoever compiled it for you (and the configure reply at the end)

i.e. supply more information about OS and who compiled it and what configure said.

hey,

can someone tell me, why I dont can't use the menu options?
Or why I dont see the output like the sample output from the first post?

I've been using CGMiner on Windoze since it's 2.0 version because it could do what no other miner or GPU management software could do with controlling my GPU's.  Been very happy with the capabilities since.

Thanks ckolivas for additional work you have put into Windoze support.  I haven't experienced any Windoze related issues since not being able to press Q and get the closing stats, that I know of anyway.
Thanks,
Sam

censored.

No take-backs!


I find it hilarious that you can manage to fix all these Win bugs without even using it for yourself. Crazy.

Of course, I realize that and appreciate all your hard work greatly - it was a very tongue in cheek comment, text can come across very blatant & uncaring sometimes - especially when I write it......

All good, and thanks again. Now that I'm mining properly again I'll make a wee donation - my first incoming will be yours my man.

Well... I actually have busted my balls for months on end trying to sort out the windows issues, so that is a slight understatement saying "not bothering much"  
 Enjoy anyway.