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

[Askit2]

I am having a small problem with CGMiner 3.3.1. I have 3 Jalapeno's that reliably get Incorrect result count errors.
It doesn't seem to change my hashing speed and it seems like all valid shares are being sorted correctly.

2 CGMiner instances on Raspberry Pi with 4 Jalapeno's each. Using powered hubs. It doesn't seem like it is a problem but it is putting up a lot of hardware errors and making me wonder if the older firmware is a bit off.

Also Que Job Status failed and Request Que Job Status Failed.
err=-1 and amt = 0 listed below all three errors.

I have a feeling based on my actual hashrate and expected hashrate I am not losing anything or not losing much.

[1713423161]

1713423161

[-ck]

I am having a small problem with CGMiner 3.3.1. I have 3 Jalapeno's that reliably get Incorrect result count errors.
It doesn't seem to change my hashing speed and it seems like all valid shares are being sorted correctly.

2 CGMiner instances on Raspberry Pi with 4 Jalapeno's each. Using powered hubs. It doesn't seem like it is a problem but it is putting up a lot of hardware errors and making me wonder if the older firmware is a bit off.

The Jalapeños are all wildly different in quality due to being all the earliest chips out. Just about any amount of hardware errors is pretty much normal. Some are <.1% while others are 10%.

[mdude77]

This may be a dumb question, but I can't find an answer, despite a lot of searching...

When using CGMiner to mine Litecoin (--scrypt) CGMiner reports the network difficulty as ~55.1m, but the Litecoin client says the network difficulty is 841.46756083.

Why do these numbers disagree so drastically?

I was wondering the same thing.

M

[-ck]

This may be a dumb question, but I can't find an answer, despite a lot of searching...

When using CGMiner to mine Litecoin (--scrypt) CGMiner reports the network difficulty as ~55.1m, but the Litecoin client says the network difficulty is 841.46756083.

Why do these numbers disagree so drastically?

I was wondering the same thing.

M

README FAQ

[xyzzy099]

This may be a dumb question, but I can't find an answer, despite a lot of searching...

When using CGMiner to mine Litecoin (--scrypt) CGMiner reports the network difficulty as ~55.1m, but the Litecoin client says the network difficulty is 841.46756083.

Why do these numbers disagree so drastically?

I was wondering the same thing.

M

README FAQ

Sorry, I read everything in that README file except the FAQ section apparently :/

Q: Why do the scrypt diffs not match with the current difficulty target?
A: The current scrypt block difficulty is expressed in terms of how many
multiples of the BTC difficulty it currently is (eg 28) whereas the shares of
"difficulty 1" are actually 65536 times smaller than the BTC ones. The diff
expressed by cgminer is as multiples of difficulty 1 shares.

[Mylon]

Hello,

This question might have been asked here somewhere before, tried some searches and nothing popped up, so if it has, my apologies.

On my new mining rig, I got an integrated gpu on the Intel CPU, which I activated to run the monitor on. (so its not pulling resources of the regular GPU's)

The thing I'm facing now though... is that CGMiner is going nuts, complaining that it sees more OpenCL devices than devices with ADL.

I've been trying to figure out a fix for this, with remapping and stuff, but I have not been able too (still no temp / fan monitoring, on any of the cards)

Anybody any idea how to work around this? Aka telling CGMiner to ignore the Intel Graphics, and continue within everything else as usual. (its sees the gpu's as 0:0-3 and the intel gpu as 1:0)

Any tips would be much appreciated!!

[os2sam]

complaining that it sees more OpenCL devices than devices with ADL.

Try using dummy plug's on all GPU's.

Also search the Mining Support group.  I think someone else had a productive suggestion a while back.  Can't remember what it was though.

[-ck]

As of today I'll be travelling overseas for the next 6 weeks. I plan to intermittently available online and coordinate releases if necessary but do not expect heavy development or support from myself during that time.

[kano]

Hello,
...
Any tips would be much appreciated!!

--gpu-map --gpu-reorder --gpu-platform
-n

[twmz]

As of today I'll be travelling overseas for the next 6 weeks. I plan to intermittently available online and coordinate releases if necessary but do not expect heavy development or support from myself during that time.

Have fun!

[Mylon]

Hello,
...
Any tips would be much appreciated!!

--gpu-map --gpu-reorder --gpu-platform
-n

Thanks Kano, got a bit further

Any way to have it print what kind of ADL devices it sees? Still not outputting any monitoring data for any card :S

Code:

C:\Users\miner\Downloads\cgminer-3.2.2-windows>cgminer.exe --gpu-map 0:0,
1:1,2:2,3:3 --gpu-reorder --gpu-platform 0 -n
 [2013-07-04 06:24:37] CL Platform 0 vendor: Advanced Micro Devices, Inc.

 [2013-07-04 06:24:37] CL Platform 0 name: AMD Accelerated Parallel Processing

 [2013-07-04 06:24:37] CL Platform 0 version: OpenCL 1.2 AMD-APP (1124.2)

 [2013-07-04 06:24:37] Platform 0 devices: 4
 [2013-07-04 06:24:37]  0       Tahiti
 [2013-07-04 06:24:37]  1       Tahiti
 [2013-07-04 06:24:37]  2       Tahiti
 [2013-07-04 06:24:37]  3       Tahiti
 [2013-07-04 06:24:37] Failed to ADL_Adapter_ID_Get. Error -1 ## Printing this error 27 times...

 [2013-07-04 06:24:38] ADL found less devices than opencl!
 [2013-07-04 06:24:38] There is possibly more than one display attached to a GPU

 [2013-07-04 06:24:38] Use the gpu map feature to reliably map OpenCL to ADL

 [2013-07-04 06:24:38] Mapping OpenCL device 0 to ADL device 0

 [2013-07-04 06:24:38] Mapping OpenCL device 1 to ADL device 1

 [2013-07-04 06:24:38] Mapping OpenCL device 2 to ADL device 2

 [2013-07-04 06:24:38] Mapping OpenCL device 3 to ADL device 3

 [2013-07-04 06:24:38] WARNING: Number of OpenCL and ADL devices did not match!

 [2013-07-04 06:24:38] Hardware monitoring may NOT match up with devices!

 [2013-07-04 06:24:38] 4 GPU devices max detected
 [2013-07-04 06:24:38] USB all: found 6 devices - listing known devices

 [2013-07-04 06:24:38] No known USB devices

C:\Users\miner\Downloads\cgminer-3.2.2-windows>

Would be real nice to get the monitoring up, as cards are randomly getting SICK/DEAD, and they haven't even been overclocked yet :S Edit2: Think I fixed this sick thingy, UPLS crap...

Update: Think I found why its printing the error: "[2013-07-04 06:24:37] Failed to ADL_Adapter_ID_Get. Error -1" 27 times, 3 displays on the igpu, 4x 6 displays on the 7950's, still not figured out to what to map them though,  trying the 4 at the end, just gives an error (expecting out of range) trying +1 on all still no values, trying +3 on all still no values... If I could just get one to display something, I  would find a way to map them... but weirdly enough I can't get any of them to display any monitoring values... Looks like this igpu is becoming a real pain in the butt...

As of today I'll be travelling overseas for the next 6 weeks. I plan to intermittently available online and coordinate releases if necessary but do not expect heavy development or support from myself during that time.

Have fun and enjoy your holiday!!

[shawtux]

yay!! i'm back
so i installed everything as kano said for my cm1

now im running it

 cgminer version 3.1.1

i'm using this command
./cgminer -c ../miner.conf -S /dev/ttyUSB0 -S /dev/ttyUSB1 -S /dev/ttyUSB2 -S /dev/ttyUSB3


miner.conf only has api and pool options.

even so, after a little while this text appears

all ok here

Code:

(5s):1.461G (avg):1.301Gh/s | A:9  R:0  HW:0  U:11.8/m  WU:11.8/m
 ST: 2  SS: 0  NB: 1  LW: 33  GF: 0  RF: 0
 Connected to stratum.bitcoin.cz diff 1 with stratum as user shawtux.2
 Block: 005b778b2574d43f...  Diff:21.3M  Started: [01:05:17]  Best share: 6
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 ICA 0:                | 306.8M/299.8Mh/s | A:5 R:0 HW:0 U: 6.53/m
 ICA 1:                | 306.5M/378.4Mh/s | A:1 R:0 HW:0 U: 1.31/m
 ICA 2:                | 309.0M/317.1Mh/s | A:1 R:0 HW:0 U: 1.31/m
 ICA 3:                | 296.1M/305.8Mh/s | A:2 R:0 HW:0 U: 2.61/m
--------------------------------------------------------------------------------

 [2013-07-04 01:05:30] Accepted c3b4878c Diff 1/1 ICA 1 pool 0
 [2013-07-04 01:05:30] Stratum from pool 0 requested work restart
 [2013-07-04 01:05:32] Accepted eb7d154a Diff 1/1 ICA 0 pool 0
 [2013-07-04 01:05:34] Accepted 80b99e56 Diff 1/1 ICA 0 pool 0
 [2013-07-04 01:05:34] Accepted 677735c7 Diff 2/1 ICA 0 pool 0
 [2013-07-04 01:05:37] Accepted e46e8ee2 Diff 1/1 ICA 3 pool 0
 [2013-07-04 01:05:55] Accepted fbd0ef4e Diff 1/1 ICA 0 pool 0
 [2013-07-04 01:05:57] Accepted fc4c45fc Diff 1/1 ICA 2 pool 0
 [2013-07-04 01:05:57] Accepted b8156d9e Diff 1/1 ICA 0 pool 0
 [2013-07-04 01:05:58] Accepted 2a79f19d Diff 6/1 ICA 3 pool 0

here it fails out of the blue like after 10min.

Code:

(5s):1.571G (avg):1.441Gh/s | A:100  R:0  HW:0  U:9.2/m  WU:9.2/m
 ST: 2  SS: 0  NB: 1  LW: 318  GF: 0  RF: 0
 Connected to stratum.bitcoin.cz diff 1 with stratum as user shawtux.2
 Block: 005b778b2574d43f...  Diff:21.3M  Started: [01:05:17]  Best share: 2.01K
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 ICA 0:                | OFF   /358.0Mh/s | A:28 R:0 HW:0 U: 2.58/m
 ICA 1:                | OFF   /365.6Mh/s | A:20 R:0 HW:0 U: 1.84/m
 ICA 2:                | OFF   /360.7Mh/s | A:25 R:0 HW:0 U: 2.30/m
 ICA 3:                | OFF   /357.3Mh/s | A:27 R:0 HW:0 U: 2.49/m
--------------------------------------------------------------------------------

 [2013-07-04 01:16:05] ICA1: Comms error
 [2013-07-04 01:16:05] Failed to open Icarus on /dev/ttyUSB1
 [2013-07-04 01:16:05] ICA1: Comms error
 [2013-07-04 01:16:05] ICA 1 failure, disabling!
 [2013-07-04 01:16:05] Thread 1 being disabled
 [2013-07-04 01:16:05] ICA3: Comms error
 [2013-07-04 01:16:05] Failed to open Icarus on /dev/ttyUSB3
 [2013-07-04 01:16:05] ICA3: Comms error
 [2013-07-04 01:16:05] ICA 3 failure, disabling!
 [2013-07-04 01:16:05] Thread 3 being disabled

any ideas?

[pvtbrutus]

Yeah why are u using 3.1.1? Try the latest because alot has changed since 3.1.1.

[kano]

...

any ideas?

Not really, but guesses:

The devices should always be available to be opened ... so I'm not sure why that would change.
Make sure the dialup (or whatever privs) are correct as per the old 3.1.1 FPGA-README and reboot
(but I don't think this is the problem, but at least make sure it is all correct anyway)

The 10 minute issue seems to be some sort of BTC problem going around
It was supposed to only be with the new USB code ... but that is the old serial-USB code in 3.1.1 with the CM1 ...
Maybe check it's not using a USB3 port ... coz I'm next to certain at least some problems are USB3 related and nothing to do with whether you use serial-USB or our new direct USB ...

You can't use direct USB fully on that device since it actually has 4 end point pairs on a single USB chip ... so I'd need the device to get the support to work properly.
... and anyone thinking that this is some idea to get people to send me hardware for no reason ... consider that they really don't mine much any more ... just getting the USB driver to work with 8 end points in a single USB chip will take some effort and without the hardware it's a right pain in the ass to try and do it ... and certainly no incentive at all to do it ... as I've said before, I wrote the original chip dividing support for CM1 but I also have/had an Icarus I could test it on with the default divisions back then.
Supporting the FTDI 0x8350 chip is a different issue since I've not had to add multiple end point support for anything yet (though it's a pity that nothing actually uses multiple end points 'properly' i.e. more than 2 end points per mining device ... the CM1 just creates multiple mining devices with the multiple end points)
I'm pretty sure how I'd do it (oddly - it would be like the MMQ) but I'd need the hardware.

I presume it really does have a pair of FPGA attached to each /dev/ttyUSBx ?
If not, and it's only one FPGA per /dev/ttyUSBx then you'll need --icarus-options 115200:1:1 (or 57600:1:1) not sure which speed CM1 is any more

Edit: and use --icarus-timing short

[HellDiverUK]

complaining that it sees more OpenCL devices than devices with ADL.

Try using dummy plug's on all GPU's.

Try swinging a dead wombat around the room too, because it's probably as useful as dummy plugs. 

When will people get it in to their heads that dummy plugs haven't been needed in over 18 months?  This old issue was fixed back in late 2011.

[shawtux]

Thanks kano!
Will try it out.  I'm with a rPi so no usb3 here. Thabks though. Will try the short thingy (tried it with long and no go). Also could be the bitstream cause (here i'll get hit) in bfgminer the clock is around 200mH/s each and in cgminer it goes all the way to 350. Dunno. An idea.

Will read further cause i wanna use cgminer.


And im using cm1 cause it sounds fun and dont have enough for an asic.

[os2sam]

complaining that it sees more OpenCL devices than devices with ADL.

Try using dummy plug's on all GPU's.

Try swinging a dead wombat around the room too, because it's probably as useful as dummy plugs.

Don't have one of those, but I do have resistors.

When will people get it in to their heads that dummy plugs haven't been needed in over 18 months?  This old issue was fixed back in late 2011.

For an old issue that has been fixed it sure has resolved allot of odd problems here and there.

But my suggestion is just a WAG, no idea if it would really help but I know it doesn't hurt.
Sam

[silverston]

hello.
can I be use directly cgminer with Avalon? what settings need to write to the configuration file.? how I connect avalon with PC? I think my tp-link dont working
thanks in advance

[Mylon]

complaining that it sees more OpenCL devices than devices with ADL.

Try using dummy plug's on all GPU's.

Try swinging a dead wombat around the room too, because it's probably as useful as dummy plugs.

Don't have one of those, but I do have resistors.

When will people get it in to their heads that dummy plugs haven't been needed in over 18 months?  This old issue was fixed back in late 2011.

For an old issue that has been fixed it sure has resolved allot of odd problems here and there.

But my suggestion is just a WAG, no idea if it would really help but I know it doesn't hurt.
Sam

Except my wallet, I'll try the wombat swinging though, don't think it can hurt.

Just to recap;

I disable the igpu, monitoring works with issues. I enable the igpu, can't get monitoring to work...
The issue is somewhere in ADL, and the moment I know what it is, I don't mind digging into the files and editing a couple of lines.
Dummy plugs are NOT the issue, please stop suggesting them. (next one suggesting them, will get the flat lie back that I'm using them)

Why do I want to use the igpu, because then Windows / VNC etc, don't try to steal resources from the dedicated cards, decreasing mining efficiency. (And I have a feeling many people will want this just like me, but most will just choose the easy way out and disable the igpu again)

[os2sam]

Anybody any idea how to work around this? Aka telling CGMiner to ignore the Intel Graphics, and continue within everything else as usual. (its sees the gpu's as 0:0-3 and the intel gpu as 1:0)

Try using the CGMiner argument --remove-disable for the Intel GPU.

-------------Readme-----------------------
--remove-disabled   Remove disabled devices entirely, as if they didn't exist
--device|-d <arg>   Select device to use, one value, range and/or comma separated (e.g. 0-2,4) default: all

-------------Top Post-----------------------
Q: Can I mine with AMD while running Nvidia or Intel GPUs at the same time?
A: If you can install both drivers successfully (easier on windows) then
yes, using the --gpu-platform option.
---------------------------------------------

May not be better than a dead flying whombat or dummy plugs.  But worth looking into.
Sam