OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[m5]

I have one 5770 card (default 850/1200 clocks) on which I was trying to mine litecoin in my home computer and then moved it to a HP server in datacenter, however there I can only reach about 60% of performance, but don't know why.

At home, I had Windows 7 64bit, 4 GB RAM, cgminer 3.1.0, latest AMD driver and SDK and card in x16 PCIe 2.0 slot. With TC 3968 (more TC was not working) and intensity 18, I was getting about 200 kHash/s which is good for this card.

On server, I have 64bit debian linux 6.0 (squeeze), but only 3 GB RAM and the PCIe slot is only version 1.0 (x8 using a riser). Cgminer is also 3.1.0, driver 12.10, SDK 2.8 (I followed this guide http://www.scribd.com/doc/132505278/Debian-GPU-Litecoin-cgminer-install-guide ).

I was trying various TC and other options, intensities 12-20, but can't get more than 117 kHash/s. What was different is that I was able to compile bin with more TC (even more than 5000), but it had no effect on performance. Even OC didn't have any effect. Bin files for Windows had "l4" on end, those on linux have "l8". From documentation it is "size of long". Does it matter in something? Can for example linux cgminer use bin file prepared on windows version or is it incompatible?

What could be causing this?
1) Maybe is the PCIe 1.0 the bottleneck? How does scrypt mining work? Does cgminer transfer huge amounts of data to GPU memory? Or mainly the GPU itself does majority of GPU memory accesses?
2) Or only 3 GB of system RAM? But cgminer is using only 300 MB of RAM, which should be OK for just 200 KHash/s... I have read that scrypt mining needs a lot of system RAM. How does it use it? For some pre-computations or does it transfer the data to GPU memory?
3) Or is it just bad combination of driver/SDK versions?
BTW bitcoin performance is OK on the linux server (about 195 MHash/s), only scrypt is affected.

[1714002138]

1714002138

[1714002138]

1714002138

[1714002138]

1714002138

[shawtux]

Hi guys tried searching but could not find an answer.
It's probably a noob question.

Can i run different FPGA from one rasp pi on the same cgminer instance?
Or do I have to run different instances?
Can I run icarus , BFL together for example?

[crazyates]

Can I run icarus , BFL together for example?

Yep. You can even run GPUs, FPGAs, and ASICs all at the same time.

[Beaflag VonRathburg]

Having issues with how to assign and determine device IDs with ztex board in Windows 7. My previous experience has been with BFL singles, CM1 boards, and using the ztex boards with Linux. With the BFL singles and CM1 boards those get assigned COM numbers that you just call with -S COMn. Linux, has the nice -S auto feature which calls them automatically. The ztex boards under Windows operate differently.

I read the FPGA read me and was able to use Zadig to convert the driver to WinUSB. Cgminer now detects all of the attached boards, but crashes immediately. Using -debug returns:

Code:

-d: Invalid device number

I'm trying to help someone figure this out so any help would be greatly appreciated.

[MWNinja]

I am getting frequent crashes somewhere in the pool failover code, happening both in cgminer and the fork of cgminer.  Keeps trying to write address 0x0, so I suspect its a Null pointer dereference somewhere in there.  It's happening any time the primary pool gets flaky, which lately has been often.

[kano]

Having issues with how to assign and determine device IDs with ztex board in Windows 7. My previous experience has been with BFL singles, CM1 boards, and using the ztex boards with Linux. With the BFL singles and CM1 boards those get assigned COM numbers that you just call with -S COMn. Linux, has the nice -S auto feature which calls them automatically. The ztex boards under Windows operate differently.

I read the FPGA read me and was able to use Zadig to convert the driver to WinUSB. Cgminer now detects all of the attached boards, but crashes immediately. Using -debug returns:

Code:

-d: Invalid device number

I'm trying to help someone figure this out so any help would be greatly appreciated.

Ztex's don't use any device specification code.
They auto identify them all and mine on them all and that's it.
nelisky/dennisx wrote the ztex code before I wrote and integrated the new usbutils library into cgminer.
I guess you'd have to chase one of them to switch it over to the new way to get hotplug and add use the --usb option (etc).
(I don't have a ztex)

[kano]

I am getting frequent crashes somewhere in the pool failover code, happening both in cgminer and the fork of cgminer.  Keeps trying to write address 0x0, so I suspect its a Null pointer dereference somewhere in there.  It's happening any time the primary pool gets flaky, which lately has been often.

3.1.0 does that - try 3.1.1

[RedLine888]

And it happens with any kernel! How to fix that?

[bitpop]

And you do have those files in there?

[RedLine888]

Yes, I have just unpacked .7z archive to a folder, created .bat and saw the above problem

[bitpop]

Have you tried right clicking and running as administrator?

[RedLine888]

Yes! CGminer is also ticked to run as admin. I have W8x64

[bitpop]

That's because you put it in one of the protected folders.

[RedLine888]

How to check whether it is protected or not?

[bitpop]

Some are default like that like c: users

[RedLine888]

my path is D:\cgminer-3.1.1-windows

[bitpop]

Just check administrator under compatibility

[RedLine888]

Of CGminer.exe? It is already checked

[-ck]

You probably have not changed directories with 'cd' into the directory and are calling cgminer with a pathname instead.

[Xian01]

I'm noticing after a couple hours of hashing, that every single Block Erupter USB I have running under CGMiner 3.1.1 with the --icarus-options and timings set is displaying Hardware Errors under Windows 7 64 bit.

Am I doing something wrong ?



cgminer -o xxx -u xxx -p x -I 9 --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S //./COM4 -S //./COM5 -S //./COM6 -S //./COM7
-S //./COM8 -S //./COM9 -S //./COM10 -S //./COM11 -S //./COM13 -S //./COM14 -S //./COM15  -S //./COM17 -S //./COM21 -S //./COM22 -S //./COM23 -S //./COM24 -S //./COM25 -S
//./COM26 -S //./COM27 -S //./COM28