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

Quick bugfix then, and I'm going to release it as 2.2.3. Thanks.

Running more than twice as long as before and no crash yet. I'll post again, should this post trigger another crash, but so far it looks good.


@kano: The first thing I did before posting was "ulimit -c unlimited; make clean; ./autogen.sh && ..." just to get a clean core dump.

IMHO all of these strange cgminer issues are on Windblows only / mostly. I would avoid that platform if I were mining.

You are gamers so that is why you won't consider Linux. Try dual booting and cgminer works flawlessfly for me on Linux.

I think it should be like Xchat program : free for Linux and if you need support on Windows you have to pay.

Windows is just too much hassle for mining. Good luck !

Sigh - after running for quite a while - even my lowly 725MH/s finally got the error (just now) ... wait for another update.

I haven't used it remote. I have one with a monitor and it is the same.

They will tell you it is because you are remote controlling your computer. As in you are controlling your PC form another PC (VNC, Logmein, etc...)

For me that explanation is rubbish though. I use a KVM.

I too would like a valid explanation as to why this is happening.

I just compiled the new cgminer direct from git using git clone and the steps recommended (./autogen.sh then CFLAGS="-O3 -Wall -march=native" ./configure)
I'm getting an incomprehensible bunch of data after a few minutes of mining (cgminer with -w 256 and --submit-stale shuts down and gives me this info):

Any ideas why?  (I wasn't getting this with 2.2.1)

have you find something why cgminer stats go away after a longer term? (on y rigs on windows 64bit after 10-10.5 days cgminer don't show temp and fan speed, after quit and restart (only cgminer) all is okay)

oops no binary yet - sorry
I compiled it without checking if there was a binary.
(and my lowly 725Mh/s is running OK on 2.2.2)

Hmm... could be a race on the work item. Can you "git checkout a3e77937c8b8d924b2671aa4a77e9f13689ac64a", rebuild, and see if it goes away?

1) does the binary also give you that?
2) If you must compile, did you start afresh?
3) If you didn't it's better to, but at least be sure you autogen'd and configure'd and make clean'd

With the latest version from git, I keep getting this:

Anyone who used the old one this one should be interesting to look at once or twice
(I of course use it to view the status of my rig since it's all in one page)
Of course there are other more complex ones out there for pure display only
This one also happens to allow you to change everything that the API allows (unless I missed something )

New version 2.2.2, source up for now, top post, binaries pending.

Changelog:
Version 2.2.2 - February 6, 2012

- Provide support for the submitold extension on a per-pool basis based on the
value being detected in a longpoll.
- Don't send a ping to a dynamic device if it's not enabled as that will just
enable it for one pass and then disable it again.
- Rewrite the convoluted get_work() function to be much simpler and roll work as
much as possible with each new work item.
- Roll as much work as possible from the work returned from a longpoll.
- Rolling work on each loop through the mining thread serves no purpose.
- Allow to stage more than necessary work items if we're just rolling work.
- Replace divide_work with reuse_work function used twice.
- Give rolled work a new ID to make sure there is no confusion in the hashtable
lookups.
- Remove now-defunct hash_div variables.
- Remove unused get_dondata function.
- Silence ADL warnings.
- Silence unused parameter warnings.
- Stagger the restart of every next thread per device to keep devices busy ahead
of accessory threads per device.
- Deprecate the --donation feature. Needlessly complex, questionable usefulness,
depends on author's server and a central pool of some kind, and was not heavily
adopted.
- It's devices that report back now, not threads, update message.
- Continue auto-management of fan and engine speeds even if a device is disabled
for safety reasons.
- No need to check we're highest performance level when throttling GPU engine
speed.
- Abstract out tests for whether work has come from a block that has been seen
before and whether a string is from a previously seen block.
- Probe but don't set the timeout to 15 seconds as some networks take a long
time to timeout.
- Remove most compiler warnings from api.c
- Add last share's pool info in cgpu_info
- Allow the OpenCL platform ID to be chosen with --gpu-platform.
- Iterate over all platforms displaying their information and number of devices
when --ndevs is called.
- Deprecate main.c
- Some networks can take a long time to resolve so go back to 60 second timeouts
instead of 15.
- Only enable curses on failure if curses is desired.
- Fix warnings in bitforce.c
- Bugfix: Need to open BitForce tty for read-write
- Fix various build issues.
- Modularize code: main.c -> device-cpu + device-gpu
- Fix phatk kernel not working on non-bitalign capable devices (Nvidia, older
ATI).
- Update poclbm kernel for better performance on GCN and new SDKs with bitalign
support when not BFI INT patching. Update phatk kernel to work properly for non
BFI INT patched kernels, providing support for phatk to run on GCN and non-ATI
cards.
- Return last accepted share pool/time for devices
- Display accepted share pool/time for CPUs
- Bug intensity always shows GPU 0
- Update example web miner.php to use new API commands

Honestly, unless you are running 7000 series cards, you can leave all these at their defaults with the exception of "Intensity", which should be set to "d" for you desktop monitor, and 8 for dedicated mining cards.

OK. So AFAIK there are 5 kernel settings we have to adjust here :

BFI_INT ( where can I see if this is on / off ? )
Fastloop ( where can I see if this is on / off ? )

Vectors
Worksize
Intensity

What is the long8 at the end of the .bin produced ?

Thanks !

Just started using this over GUI, and I must say, I am very impressed.
I bumped up from 1.8Ghash to 2.1. The improvement was definitely worth the few seconds of setup. 

I'll make it prettier

That it does. Just looks a little strange.