CGMiner 4.1.11 doesn't start mining until 2nd notify

[elfarto69]

I'm using some miners that are using cgminer 4.1.11. I've noticed that they don't seem to start submitting shares until the pool sends the second mining.notify message ? Is there a parameter i can tweak in cgminer to make it start mining as soon as the first notify message is received ?

I tried adding --queue 0 to cgminer params to no avail.

[1714660963]

1714660963

[1714660963]

1714660963

[1714660963]

1714660963

[1714660963]

1714660963

[os2sam]

I don't know what your hash rate is but if it is low then the pool may be setting you to a high difficulty, which is normal, and it may be taking a while for your miner to find the high diff share before it adjusts down to a difficulty more reasonable for your hash rate.

mining.notify message

What do you mean by "mining.notify"?  I've never seen that message.

[elfarto69]

Let me put it this way,cgminer doesn't start mining until the pool sends the second job (mining.notify stratum messages),i purposedly connected to my pool instance and forced it not to send the second job and it never produces a single share no matter what the diff is.