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

[PandaMiner]

ckolivas, your miner is great for my scrypt mining.

There's just one thing that bothers me, and only me I believe.  I mine on working computers, and I find myself changing intensities a lot.  I wish that cgminer could use the "enter" key on the 10-key as well as the regular "enter" key.

Lol, in the early days, i would press: "G U 0", then go to the 10-key and finish with "1 2 enter" but that enter never worked!

Maybe include that in the next full release? It's not that big a deal tho.

[ocminer]

Is there a possibility to stop a ICA/ZTX worker/thread ?

I'd like to "Disable" ICA2 i.e. and let the others running.. like with GPU's

No.

Is it planned to be possible some day?

As this way I can very easy identify a particular FPGA Board and debug it further/reflash it and so on..

[Plazzman]

@Kano have you had any success with getting the Modminer driver working?

[OgNasty]

Perhaps I'm doing doing something right...  But it seems like when a pool goes down, cgminer just keeps submitting stale shares to the pool instead of switching to a backup, despite having it set to do so. 

[kano]

@Kano have you had any success with getting the Modminer driver working?

Nothing working yet.
I've been 'non-BTC work' busy for a few days, with 1 or 2 still to go

Thanks to TheSeven for MPBM
I've actually been running MPBM, since on my linux (Xubu 11.04 and Fedora 17) the current MMQ code doesn't even work ...
(and also been getting rather annoyed at not having the time to do it)
I guess the current code may actually work on windows since the I/O is done differently, but I didn't get to trying that out

After spending some effort working out what was wrong with the current code on linux and deciding what to do about it - I just need a couple of days to rewrite all the linux I/O code which should be done this week - and yes decision made with help from ckolivas also
I'll put up a pull once I get the basics done, then get to optimising and chasing bugs anyone finds in it after that.

This will also be in preparation for the up coming bASIC of course - so once I've changed/rewritten the MMQ code, the design should be ready also for a hopefully quick bASIC implementation once we get the dev devices.

[Askit2]

I am not sure if this is the expected result but on 2.7.7 (I think it was) when most of eclipse died a while back (bad data center) one of the servers (good data center) kept working. The falling back to a lower pool happened. The good eclipse server was marked dead or sick, so the hashing fell back to my last backup. So far all is expected. When the one that would live seemed to be not dead cgminer switched to that pool. I was actually watching it work so I was really impressed. The next day I noticed something strange, cgminer was still mining on pool 3. I checked and pools 0, 1, and 2 all where alive and enabled but the priority was not in the order I had them set. Pool 3 was now priority 0. I expect that since switching pools manually does alter priority (thats how I got back to the priority I wanted) that the automated switching does the same.

I could now use the API to periodically reorder them. I wonder if there is a way to make the automatic switching not mess with the priority. I have been trying 2.8.x. I don't even have a stratum pool so it's fairly worthless to try. I won't find any bugs. Since eclipse is so reliable I really have not been able to retest the failover.

[Krak]

I could now use the API to periodically reorder them. I wonder if there is a way to make the automatic switching not mess with the priority. I have been trying 2.8.x. I don't even have a stratum pool so it's fairly worthless to try. I won't find any bugs. Since eclipse is so reliable I really have not been able to retest the failover.

I think it would be pretty cool to be able to easily reorder and add pools in miner.php.

[Askit2]

I could now use the API to periodically reorder them. I wonder if there is a way to make the automatic switching not mess with the priority. I have been trying 2.8.x. I don't even have a stratum pool so it's fairly worthless to try. I won't find any bugs. Since eclipse is so reliable I really have not been able to retest the failover.

I think it would be pretty cool to be able to easily reorder and add pools in miner.php.

If you can switch pools and switching causes the one switched to, to move in the order to the top you just have to start at lowest priority then switch to increasingly higher priorities. At least the java API it works just fine.

[Krak]

If you can switch pools and switching causes the one switched to, to move in the order to the top you just have to start at lowest priority then switch to increasingly higher priorities. At least I thought you could switch in the API.

Yeah, I'm just saying it would be nice if it was a bit easier. Like have an entry box for priorities and an entry box for adding a pool on the fly.

[Mobius]

I could now use the API to periodically reorder them. I wonder if there is a way to make the automatic switching not mess with the priority. I have been trying 2.8.x. I don't even have a stratum pool so it's fairly worthless to try. I won't find any bugs. Since eclipse is so reliable I really have not been able to retest the failover.

I think it would be pretty cool to be able to easily reorder and add pools in miner.php.

If you can switch pools and switching causes the one switched to, to move in the order to the top you just have to start at lowest priority then switch to increasingly higher priorities. At least I thought you could switch in the API.

setup a script to run in reverse order:
echo -n "switchpool|$1" | nc "$ip" "$port"

where $1 is the pool to switch to
$ip is your rig's ip
$port is the api port - default is 4028

[-ck]

I was using 2.7.6 on my dual 7970 (Club 3D and Sapphire with AMD cooling) rigs for as long as it was out now, with 1125MHz core & 1000 mem, no voltage change, power setting at -20%, all Win7 32, 1250Mh per rig.
I have noticed all 2.8 builds have the problem of declaring the GPUs sick with that clock rate.
They work with the stock 925 and a little bit more, but above 1000 i get sick fast.
I have not modded the cards in any way, just plugged them in, installed latest AMD driver and started CGM.
It (or the driver?) itself set the clock up to 1125, the maximum, more is not allowed by the bios.
I have to manually reduce engine clock to below 1000 to have it run a few hours, but then it inevitably dies with GPU declared sick, and a windows pops up "CGMiner.exe has stopped working".
What is going on here?

I better stick to 2.7.6 and use the proxy, that does work for days now.

This post is the most interesting and do you know why? The GPU code is UNCHANGED between 2.7.6 and 2.8.3. The only thing that is different is the stratum code. Now why would that make your GPUs SICK now when they didn't previously? Because with the stratum code, the device is busier than ever. There is no possible way to keep the device as busy as doing it in the c code internally in cgminer. So your devices are no longer getting any rest between work.

EDIT: This is precisely why stratum was developed by the way; in order to be able to keep much higher hashrate devices busy. If you want to test this theory, use version 2.8.3 and connect to the proxy in http mode by using --fix-protocol.

[-ck]

Dynamic intensity is still messed up in 2.8.3. Now it's going up to 15.

Eh? I tested it on windows and linux...

Hmm I dunno then. It took about a minute or two for it to start happening after I started up 2.8.3; it was happening instantly in 2.8.2.

Try this build then please (I'm assuming it's windows?):
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

[Krak]

Try this build then please (I'm assuming it's windows?):
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Nope, I'm running Ubuntu 12.04.

[-ck]

Try this build then please (I'm assuming it's windows?):
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Nope, I'm running Ubuntu 12.04.

Try git master then please.

[gigica viteazu`]

@ckolivas
is there any reason to leave 2.7.7 behind if i`m mining on a pool which doesn`t support stratum ?

[-ck]

@ckolivas
is there any reason to leave 2.7.7 behind if i`m mining on a pool which doesn`t support stratum ?

There are a few minor changes, but basically no.

[kitsura]

I'm getting very high CPU usage on Win7 using ver 2.7.7. Basically 1 core is almost always near 100%. Anyone else with the same issue?

[Mobius]

I'm getting very high CPU usage on Win7 using ver 2.7.7. Basically 1 core is almost always near 100%. Anyone else with the same issue?

Use linux.

[luffy]

I'm getting very high CPU usage on Win7 using ver 2.7.7. Basically 1 core is almost always near 100%. Anyone else with the same issue?

what drivers are you using? i have 12.8 without such issues. I believe is a driver issue and no cgminer.

[crazyates]

I'm getting very high CPU usage on Win7 using ver 2.7.7. Basically 1 core is almost always near 100%. Anyone else with the same issue?

what drivers are you using? i have 12.8 without such issues. I believe is a driver issue and no cgminer.

Drop you intensity?