Author

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

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Start low. Go slowly up. Do not increase -g count. Do not assume what worked on mine will work on yours. Read the scrypt readme. No two systems are alike.

--gpu-engine 1135 --gpu-memclock 1890 --thread-concurrency 22392 -I 20

Was worth 715kH, but it also drew 305W from the one GPU and was on my machine with my hardware running my OS.

I am NOT going to say this again. Everyone experiment for yourselves. Scrypt tuning is witchcraft and you need to find the right incantation for your device and sacrifice the correct number of goats while facing towards your holy centre.

Me? After upgrading the scrypt code, I'm back to mining bitcoin like I always have been.
member
Activity: 102
Merit: 10
For all you crazy scrypt/LTC mining fanatics, I have finally found the reason you cannot set very high thread concurrencies or intensities on 79x0 cards. It shall be fixed in the next version. I'm able to run my 7970s at TCs of 22392 now.

And how much faster is it? :-p

7970 @ 1135/1890, LG 2, TC 22392:
Code:
 GPU 0:  72.0C 3413RPM | 714.6K/715.7Kh/s | A:0 R:1 HW:0 U:0.00/m I:20
No, the memory speed is not a typo. Ignore the accept/reject ratio; I was trying solo.

EDIT: The code is now in git, and here's a windows build with the changes:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
Can you post the bat file ! It doesn't work on my 7970.
My bat file: cgminer -o coinotron.com:9322 -u romantic1.ltc -p 12345 --scrypt --lookup-gap 2 --thread-concurrency 20992 -g 5 -I 20
I tried g 1. It doesn't work too.
I also tried: "cgminer -o coinotron.com:9322 -u romantic1.ltc -p 123 --scrypt --lookup-gap 2 --thread-concurrency 22392 -g 5 -I 20"
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Don't suppose you tried the larger thread concurrencies... everything needs retuning.
hero member
Activity: 505
Merit: 500
I tried last version too, but nothing changed ..lots of errors same as previous version.Anything above I 13 on my 7950 = lots of errors and at I 19 only errors. WinVista x64 bit, 8 Gb RAM, cgminer  2.11.3, -g 1, -w 256
sr. member
Activity: 451
Merit: 250
New release: 2.11.3, 17th March 2013


Quick test of scrypt mining on my Windows 7 machine.  Same everything.

2.11.2 - No HW errors.
2.11.3 - Lot of HW errors, very low accepted rate.

Don't have time to play with it so I sticking with 2.11.2 for now.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
2.11.3a 2.11.3 recompiled on 64 bit xubuntu 11.04 (as usual) and also on the RPi 32 (2012-12-16-wheezy-raspbian and rpi-update today)

https://github.com/kanoi/cgminer-binaries
(the 64 bit version also works on Fedora 16 and 17)

To get the 64 bit xubuntu 11.04 binary:
wget https://github.com/kanoi/cgminer-binaries/raw/master/Ubuntu_11.04_x86_64/cgminer-2.11.3a
chmod +x cgminer-2.11.3a
md5sum cgminer-2.11.3a

f73035fdd0284cedc8b238869d45a073  cgminer-2.11.3a

To get the RPi 32bit binary:
wget https://github.com/kanoi/cgminer-binaries/raw/master/RPi_32/cgminer-2.11.3a
chmod +x cgminer-2.11.3a
md5sum cgminer-2.11.3a

ab34a2511b3f7325e3ab40d0c6e3424f  cgminer-2.11.3a

For anyone who didn't realise, it's just the executable file to put in place of 'cgminer'
Nothing else needs changing
On xubuntu 11.04 - first get and extract the full binary release from ckolivas and then copy my file in place of 'cgminer'

I've run both binaries without any problems with 1x6950, 1xBFL, 2xICA and 1xMMQ

The same configure options as cvolivas' binary version for 64 bit xubuntu 11.04
In case anyone was wondering:
CFLAGS="-g -W -Wall" ./autogen.sh --enable-icarus --enable-bitforce --enable-ztex --enable-modminer --enable-scrypt
make clean
make

However, the -g (instead of -O2) means it's a debug build so if anyone finds a problem and has core dumps enabled, it will dump a much more useful debug core.

All FPGAs (only) for the RPi 32bit version
CFLAGS="-g -W -Wall" ./autogen.sh --enable-icarus --enable-bitforce --enable-modminer --enable-ztex
make clean
make

You will need to install libusb-1.0.0

Reminders from before:

1
Important re-paste from before:
Now some important information about the BFL USB driver.
On linux, if you wish to switch back to the 2.10.5a, 2.10.4a or earlier version, you'll need to unplug and re-plug in your FPGAs or reboot your rig.
On windows (as described in FPGA-README) you'll need to update your windows USB driver to use the new cgminer


2
OK, if you are running cgminer 2.11.0 (or later) on linux as non-root user you may need to do the following also:

Create /etc/udev/rules.d/01-cgminer.rules
With:
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6014", SUBSYSTEMS=="usb", ACTION=="add", MODE="0666", GROUP="plugdev"
ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="0003", SUBSYSTEMS=="usb", ACTION=="add", MODE="0666", GROUP="plugdev"


And also:
sudo usermod -G plugdev -a `whoami`

Then reboot ... (or use udevadm to reload the rules and retrigger the devices - but I couldn't get that to work on my RPi without rebooting)

That is a bit overkill, but for now that's what I suggest unless I come up with a simpler set of rules.

Edit: if your linux distro doesn't have the 'plugdev' group, you can create it like:
sudo groupadd plugdev


3
If you read the FPGA-README, it mentions you need to use the WinUSB driver - not the FTDI one.
As per:
Code:
For ModMinerQuad (MMQ) and BitForce (BFL)
-----------------------------------------

...

The best solution for this is to use a tool called Zadig to set the driver:
 http://sourceforge.net/projects/libwdi/files/zadig/

This allows you set the driver for the device to be WinUSB which is usually
required to make it work if your having problems
Cgminer no longer uses the specific drivers - it's direct USB using the single libusb driver
(for everything 'USB' except Icarus - until I get around to changing that ... possibly one day in the far future Tongue)

Edit: 2 suggestions about zadig:
1) Run it as administrator
2) Menu: Options -> List all devices
legendary
Activity: 916
Merit: 1003
I've been experimenting with LTC mining lately with cgminer.  I found some settings that worked best with my little GPU and noticed some changes in changing from 2.11.2 to 2.11.3.  I had found with 2.11.2 that I got best performance with "-g 3" but with 2.11.3 it was best with "-g 1".  Also, my peak performance has improved slightly from 138 kh/s to 141 kh/s between the 2 most recent versions.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
New release: 2.11.3, 17th March 2013

Building further on the stability of 2.11 with more bugfixes, and the first significant scrypt update in some time thanks to a surge in its popularity and virtually the first ever donations towards developing and maintaining it since it was first added to cgminer.


Human readable changelog:

- Updated USB detection code by Kano will now show known devices with cgminer -n, and you can manually select devices to mine with using the new --usb option - read the README for full documentation! (Yeah right, no one reads documentation  Tongue)
- Fixes for certain USB communication problems should make them more reliable.
- Workaround for the rare crash on switching pools with stratum with older libcurl builds.
- Adding a pool now from the menu will return quickly while it leaves probing it to the background.
- Internal improvements in scalability in preparation for ASIC devices (must be close now? Roll Eyes)
- Changes to the hashmeter to update it more frequently - for fast devices it will update smoother but for long-return devices (like slow FPGAs) it will look worse. This is in preparation for faster devices...
- Scrypt updates:
 Fixed the failure to create high thread concurrencies.
 Intensities above 13 will not lead to garbage being generated on GCN (7xxx) hardware now.
 Decreased default GPU threads to 1. Intensities above 13 cannot handle more.
 Changed the default choice of thread concurrency if no options are passed to cgminer as a hint, based on amount of available GPU ram.
 Scrypt mining now shows the Work Utility as BTC mining does (total amount of diff 1 work done per minute).
 Extensive updates to the SCRYPT-README file in line with changes to the code and new information (but no one reads documentation anyway Tongue)


Full changelog:

- Update the hashmeter at most 5 times per second.
- Usbutils use its own internal read buffer
- Calculate work utility for devices that support target diffs of greater than
1, and update scrypt code to use it.
- usbutils allow read termination match to be a string
- Set default GPU threads to 1 for scrypt.
- Connect backup stratum pools if the primary pool cannot deliver work.
- Use a new algorithm for choosing a thread concurrency when none or no shader
value is specified for scrypt.
- Do not round up the bufsize to the maximum allocable with scrypt.
- Remove the rounding-up of the scrypt padbuffer which was not effectual and
counter-productive on devices with lots of ram, limiting thread concurrencies
and intensities.
- bufsize is an unsigned integer, make it so for debug.
- Update the hashmeter once per second but only display the extra logs every
opt_log_inteval.
- add a dummy ztex to usbutils so cgminer -n lists ztex also
- nDevs required for -n with usb
- USB device list - convert some common error numbers to messages
- USB -n 'known' text only without ---usb-list-all
- USB modify -n and --usb-dump to only show known devices or use new
--usb-list-all option to see all
- Make pool adding while running asynchronous, using the pool test thread
functionality.
- Only curl easy cleanup a stratum curl if it exists.
- Sacrifice the ram of curl handles in stratum disconnects when we have built
with old libcurl to avoid crashes.
- cgminer -n to include a USB device list
- usbutils allow call of usb_all() from other code
- Convert gbt_lock to a cg_lock.
- Add intermediate variants of cglocks that can be up or downgraded to read or
write locks and use them for stratum work generation.
- Move the stratum and GBT data to be protected under a new cg_lock data_lock.
- Convert the ch_lock to cg_lock.
- Convert the control_lock to a cg_lock.
- Remove unused qd_lock.
- Implement cg_lock write biased rwlocks.
- do usb_initialise() after the started message so we see it
- --usb-dump display brief dump if value = 0
- USB add --usb options to limit USB device selection v0.1
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
On another thread you mentioned 7970 fixes for litecoin.  What version is that ?
-i higher than 13 ?

How is the performance now ?

I got some water cooled cards I want to push a nice OC.

Current development code only which you can get if you're building from git, but there's a sample executable linked a few posts back for windows. Next version 2.11.3 will have a few scrypt improvements.
sr. member
Activity: 791
Merit: 273
This is personal
On another thread you mentioned 7970 fixes for litecoin.  What version is that ?
-i higher than 13 ?

How is the performance now ?

I got some water cooled cards I want to push a nice OC.
full member
Activity: 206
Merit: 100
+1.2 btc. Thank you for your work, ckolivas.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Quote
Driver and SDK versions matter but in a different way to those for bitcoin mining. There is no reason you can't ltc mine the same on linux for 5xxx with the right driver/sdk combo. I'd recommend AMD driver 12.8 with SDK 2.7 for litecoin mining.

Thanks for the tip.  I installed driver 12.8 and SDK 2.7 and now litecoin mining works.

But it still works better in Windows.

Same hardware, cgminer 2.11.2, same cgminer parameters:

Ubuntu 11.04             Ubuntu 11.04            Windows 7
AMD 12.8                  AMD 12.8                  AMD 13.1
SDK 2.7                    SDK 2.7
Intensity 16              Intensity 13                Intensity 16
634 kHash/sec          534 kHash/sec            637 kHash/sec
3 accepted/minute    14 accepted/minute     34 accepted/minute
A lot of HW errors     A lot of HW errors        No HW errors

Should I put AMD 13.1 on linux?  Or should I put Windows 7 on my linux boxes?
Pretty sure with the right driver and SDK combo there should be no difference between the  OSes. However win7 does offer some extra options for overclocking/undervolting that many find advantageous for mining, and apart from OS stability, there is no mining performance advantage to linux. It's up to you.
420
hero member
Activity: 756
Merit: 500
Getting high reject rate in cgminer 2.11.1:

BTC Guild admin says common problem
https://bitcointalksearch.org/topic/m.1631802

going to get he latest cgminer

EDIT: I upgraded to cgminer 2.11.2 and my problem is fixed! 0 rejects
hero member
Activity: 591
Merit: 500
That doesn't turn off dynamic mode.
Yes it does. Set a static intensity (9 is about right for most cards), just like it says.
full member
Activity: 235
Merit: 100
Well I figured it out last night, It's best to use no args with 7850 and 13 intensity, Floats around 340~ Kh/s on average and about 8-10 shares per minute. If I use higher intensities the shares per minute goes to shit. (No rejects..just slower shares being accepted) Great work ckolivas, I hope you will work on the scrypt code soon with ASIC's coming soon. I'm sure there's a way to optimize it a wee bit more.
sr. member
Activity: 451
Merit: 250
Quote
Driver and SDK versions matter but in a different way to those for bitcoin mining. There is no reason you can't ltc mine the same on linux for 5xxx with the right driver/sdk combo. I'd recommend AMD driver 12.8 with SDK 2.7 for litecoin mining.

Thanks for the tip.  I installed driver 12.8 and SDK 2.7 and now litecoin mining works.

But it still works better in Windows.

Same hardware, cgminer 2.11.2, same cgminer parameters:

Ubuntu 11.04             Ubuntu 11.04            Windows 7
AMD 12.8                  AMD 12.8                  AMD 13.1
SDK 2.7                    SDK 2.7
Intensity 16              Intensity 13                Intensity 16
634 kHash/sec          534 kHash/sec            637 kHash/sec
3 accepted/minute    14 accepted/minute     34 accepted/minute
A lot of HW errors     A lot of HW errors        No HW errors

Should I put AMD 13.1 on linux?  Or should I put Windows 7 on my linux boxes?
Lem
newbie
Activity: 78
Merit: 0
However -g 1 is now almost mandatory with these higher TCs.

YOU DA MAN!!!! Smiley

Excellent work!!! Smiley
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
Try increasing intesity by 1 and see that errors/rejects will happen or not Smiley
full member
Activity: 235
Merit: 100
So I figured I'd try getting some LTC as I haven't mined them in ages and I wanted to try it on my new GPU. What are some args and Clocks that would be workable with a 7850? using --scrypt -I 13 -w 256 -g 1 --shaders 1024 right now and getting around 240Kh/s with 1000/1375 clocks. I've heard that pushing past 13 intensity is bad, is this true? If so..I think I can get 340~ Kh/s outta this card.
hero member
Activity: 607
Merit: 500
one question though, i am using cgminer to solo mine PPC and i have also an alternative pool (coinotron)
in command line. localhost doesn't support LP but coinotron does so
Local mining NEVER have LP because you mine ENTIRE block all the time Smiley
Same for every coin.

thanks, i know that, my question was what it means to have LP activated for solo mining via a pool that supports LP
Jump to: