Author

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

legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
- Pools: add RollTime info to API 'stats' and 'Stats' button in miner.php
Oh nice, I was just looking for this a couple days ago.
My donation address is in my sig Cheesy
hero member
Activity: 591
Merit: 500
- Pools: add RollTime info to API 'stats' and 'Stats' button in miner.php
Oh nice, I was just looking for this a couple days ago.
sr. member
Activity: 344
Merit: 250
I'll probably give 2.7.4 a try tomorrow if 2.7.5 isn't out by then.  Smiley

For what it's worth, I ran 2.7.0 for a few days, then 2.7.2, and now 2.7.3, and I haven't had any issues with them.  I'm using BFL devices, though.

Appreciate your work.  Thanks.
legendary
Activity: 916
Merit: 1003
Dude you sound like you need another vacation from cgminer.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
New  version: 2.7.4, 23rd August 2012

All the showstoppers are fixed. Status upgraded to stable on this release.

Human readable changelog

Once again completely rehashed the work queueing mechanism trying to take -everything- into account. It should all be fixed now.
There are updated kernels here designed to never accidentally miss a share which previous kernels might have - if you underclock your memory a lot, you may find it needs to be slightly higher to not lose hashrate, increasing memory from say 150 to 250 OR you may need to play with worksize on R5xxx if previously you found 128 better because it defaults to 256 now. Others might even notice a slight increase in hashrate.

Full changelog

- Perform select_pool even when not lagging to allow it to switch back if needed
to the primary.
- Simplify macros in output kernels avoiding apparent loops and local variables.
- Carry the needed bool over the work command queue.
- Move the decision to queue further work upstream before threads are spawned
based on fine grained per-pool stats and increment the queued count immediately.
- Track queued and staged per pool once again for future use.
- OpenCL 1.0 does not have native atomic_add and extremely slow support with
atom_add so detect opencl1.0 and use a non-atomic workaround.
- Pools: add RollTime info to API 'stats' and 'Stats' button in miner.php
member
Activity: 136
Merit: 10
tester
now it is OK, run normal

 Wink Cheesy Grin
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
windosw 7 x64 SP1
Driver 12.8
SDK 2.7
cgminer 2.6.6 - crash !
Code:
 [2012-08-23 15:15:44] Started cgminer 2.6.6
 [2012-08-23 15:15:45] Probing for an alive pool
 [2012-08-23 15:15:45] Long-polling activated for http://lp.abcpool.co:8337/longpoll
 [2012-08-23 15:15:45] Unable to open diablo120724.cl or ./diablo120724.cl for reading
 [2012-08-23 15:15:45] Failed to init GPU thread 0, disabling device 0
 [2012-08-23 15:15:45] Restarting the GPU from the menu will not fix this.
 [2012-08-23 15:15:45] Try restarting cgminer.
 [2012-08-23 15:15:57] Unable to open diablo120724.cl or ./diablo120724.cl for reading
 [2012-08-23 15:15:57] Failed to init GPU thread 1, disabling device 1
Redownload the zip file please.
member
Activity: 136
Merit: 10
tester
windosw 7 x64 SP1
Driver 12.8
SDK 2.7
cgminer 2.6.6 - crash !
Code:
 [2012-08-23 15:15:44] Started cgminer 2.6.6
 [2012-08-23 15:15:45] Probing for an alive pool
 [2012-08-23 15:15:45] Long-polling activated for http://lp.abcpool.co:8337/longpoll
 [2012-08-23 15:15:45] Unable to open diablo120724.cl or ./diablo120724.cl for reading
 [2012-08-23 15:15:45] Failed to init GPU thread 0, disabling device 0
 [2012-08-23 15:15:45] Restarting the GPU from the menu will not fix this.
 [2012-08-23 15:15:45] Try restarting cgminer.
 [2012-08-23 15:15:57] Unable to open diablo120724.cl or ./diablo120724.cl for reading
 [2012-08-23 15:15:57] Failed to init GPU thread 1, disabling device 1
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Stable release update: 2.6.6
Right, I am totally utterly completely over 2.7, so I've released a stable release of 2.6 without the queueing and kernel changes in 2.7: 2.6.6. Get it in the usual place.
legendary
Activity: 2576
Merit: 1186
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hi. I have a severe bug. I was using 2.7.1 no problems. I tried 2.7.3 and got this error.


restarting cgminer doesn't fix it. it prevents me from mining entirely. I am using a single 5870 on 12.1 driver, 2.1 sdk (platform 1 specified in conf file), dynamic intensity, phatk, worksize 128, and vectors = 2. I reverted back to 2.7.1 and have no problems.

windows 7 x64 ultimate
Looks like sdk 2.1 doesn't support atomics. I had no idea... hrm....

This is one endless series of fucking bullshit. I can't seem to get out of the cycle of upgrade=break.
legendary
Activity: 1344
Merit: 1004
Hi. I have a severe bug. I was using 2.7.1 no problems. I tried 2.7.3 and got this error.


restarting cgminer doesn't fix it. it prevents me from mining entirely. I am using a single 5870 on 12.1 driver, 2.1 sdk (platform 1 specified in conf file), dynamic intensity, phatk, worksize 128, and vectors = 2. I reverted back to 2.7.1 and have no problems.

windows 7 x64 ultimate
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Yes, if you blinked, you missed 2.7.2.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/

- Give warning with sdk2.7 and phatk as well.
- Whitelist sdk2.7 for diablo kernel as well.


Do i have to set the Kerneloption (-k ) to use the modified poclbm if a had an AMD 7xxxx with SDK 2.7 or does cgminer set it automatical?

Don't do anything different to what you already do.
sr. member
Activity: 344
Merit: 250
Flixxo - Watch, Share, Earn!

- Give warning with sdk2.7 and phatk as well.
- Whitelist sdk2.7 for diablo kernel as well.


Do i have to set the Kerneloption (-k ) to use the modified poclbm if a had an AMD 7xxxx with SDK 2.7 or does cgminer set it automatical?
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
cut/paste ...

2.7.2
An Xubuntu 11.04 x86_64 executable is in my github downloads called cgminer-2.7.2a
https://github.com/kanoi/cgminer/downloads

For anyone who didn't realise, it's just the executable file to put in place of 'cgminer'
Nothing else needs changing
First get and extract the full binary release from ckolivas and then copy my file in place of 'cgminer'
I highlighted that coz the 2.7.2 release has different version numbers in the OpenCL for the modified GPU code.

No problems so far on my BFL or my 2xGPU+2xIcarus

The same configure options as cvolivas' binary version
In case anyone was wondering:
CFLAGS="-O2 -W -Wall" ./configure --enable-icarus --enable-bitforce --enable-ztex --enable-modminer --enable-scrypt

FYI:
 I included Luke-jr's (as ckolivas' release clearly says) Linux BFL flash code.
 I have no idea where he got the details from - BFL wouldn't tell me when I asked them long ago.
 The FPGA-README explains how to compile and use it

 It works for me with an error at the end, as I mentioned in the FPGA-README
 I also worked for someone else without an error, who has a BFL that doesn't do the strange things my BFL does Smiley
 I put my bitstream up to 896 and found it would throttle - so back down to 880 again and running fine.

---

I have also added a WinXP cgminer-2.7.2a.exe

This ONLY has BFL + ICA (as below) thus it doesn't need a computer with OpenCL on it
CFLAGS="-O2 -W -Wall" ./configure --enable-icarus --enable-bitforce

You will most likely also need the windowsdlls.zip file there in my downloads since some of my *.dll might be slightly different to ckolivas
legendary
Activity: 1795
Merit: 1208
This is not OK.
With your new-fangled get working, does scanhash still need to operate (send work)...(get result), or can it work now work (get previous result)...(send new work) ?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
New version - 2.7.3, 23rd August 2012

LATEST STABLE IS 2.6.6! DON'T USE 2.7.3

Not happy with 2.7.1, NOR 2.7.2, NOR 2.7.3 but this is what we're up to:
Bugfixes for networking, dynamic mode, new kernels, updated miner.php, and a bfl flash utility for linux.

Full changelog:
- Minimise the number of getwork threads we generate.
- Pick worksize 256 with Cypress if none is specified.
- Give warning with sdk2.7 and phatk as well.
- Whitelist sdk2.7 for diablo kernel as well.
- Only keep the last 6 blocks in the uthash database to keep memory usage
constant. Storing more is unhelpful anyway.
- BFL Flash - always distribute source
- Increase kernel versions signifying changed APIs.
- BFL flash - include source in builds and more FPGA-README
- Check we haven't staged work while waiting for a curl entry before proceeding.
- Use atomic ops to never miss a nonce on opencl kernels, including nonce==0,
also allowing us to make the output buffer smaller.
- Remove compile errors/warnings and document compile/usage in FPGA-README
- bitforce-firmware-flash.c by Luke-jr
- Ignore the submit_fail flag when deciding whether to recruit more curls or not
since we have upper bounds on how many curls can be recruited, this test is
redundant and can lead to problems.
- API-README update cgminer version number
- API-README fix groups P: example mistake
- API-README add COIN and other edits
- gpu->hit should be reset on new work as well.
- Do not add time to dynamic opencl calculations over a getwork.
- miner.php allow 'coin' is custom pages
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Okay I believe I've found the problem with 2.7.1 and pushed it to master git branch (this is not included in the test binary I uploaded).
DrG
legendary
Activity: 2086
Merit: 1035
So I upgraded to 2.7.1 and I've been getting cgminer quiting after about an hour. It doesn't crash, it just closes itself.

Yeah I had this happen on all 21 of my rigs.  10 shut down CGMiner all at once, the other 11 shut it down about 20 minutes after.  Obviously something was triggering mass closure of CGMiner.  I reverted to 2.7.0 and they've all been running fine for 12 hours.  My debugging days are behind me so I don't have any clue why it closed down.

How do I get CGminer to output the log to a file so I can review it under (I'm using Win 7 x64).
Jump to: