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

[candoo]

Hey

i tried to write the following code in the cgminer.conf file. but he doesnt accept it

"avalon-cutoff"    : "90"
"avalon-temp"    : "90"
"avalon-opions"    : "115200:32:10:35:360"

may anyone please be so kindly and correct it? avalon-temp is fine, because my fans are spinning at 100% all the time. It never goes above 70

[-ck]

Hey

i tried to write the following code in the cgminer.conf file. but he doesnt accept it

"avalon-cutoff"    : "90"
"avalon-temp"    : "90"
"avalon-opions"    : "115200:32:10:35:360"

may anyone please be so kindly and correct it? avalon-temp is fine, because my fans are spinning at 100% all the time. It never goes above 70

opions...

[candoo]

Hey

i tried to write the following code in the cgminer.conf file. but he doesnt accept it

"avalon-cutoff"    : "90"
"avalon-temp"    : "90"
"avalon-opions"    : "115200:32:10:35:360"

may anyone please be so kindly and correct it? avalon-temp is fine, because my fans are spinning at 100% all the time. It never goes above 70

opions...

goddamn it!!

Is there any method to start a specific Avalon? I might want to connect a couple of Avalons to my windows pc. I like cgminer in combination with cgwatch. CGwatch restarts cgminer when there are 0 new accept shares after XX minutes. How can i specific which com port he should use?

Thanks in advance for your patience

[-ck]

You should really set your temp to lower than your cutoff as well. It might not like them being the same, and I certainly wouldn't want 90 degrees as my target, I'd recommend 70.

[candoo]

You should really set your temp to lower than your cutoff as well. It might not like them being the same, and I certainly wouldn't want 90 degrees as my target, I'd recommend 70.

Thanks. I have custom fans with 5400 RPM with fixed 12volt. (connected via molex) They cant overheat, but I will look into it

Is there any method to start a specific Avalon? I might want to connect a couple of Avalons to my windows pc. I like cgminer in combination with cgwatch. CGwatch restarts cgminer when there are 0 new accept shares after XX minutes. How can i specific which com port he should use?

Thanks in advance for your patience

[pawlak2]

Since I am often making changes, testing stuff, I always run cgminer in a loop that simply restarts if it fails.
The windows version of this is

Code:

@echo off
REM cgminer
:Loop
Set NOW=%date:~10,4%%date:~7,2%%date:~4,2%.%time:~0,2%%time:~3,2%%time:~6,2%
.\cgminer.exe --no-restart --api-port 4028 --api-listen --api-allow W:127.0.0.1,W:192.168.1.0/24 --api-description Des -c pools.json 2> "run.%NOW%.log"
echo Sleeping for 5 seconds
ping -n 5 127.0.0.1 > NUL
GOTO Loop

The 5s sleep is good in case you change the options and it keeps hard looping due to a mistake

If someone is interested, here is my linux version:

Code:

#!/bin/bash
for (( ; ; ))
do
cgminer --config cg_$1_$2.conf 2>log$2.log
echo sleeping.....
sleep 5
echo done sleeping
done

I'm using few instances of cgminer for different devices and with parameters I can start different configs.

For example:
./gocg btc e
Runs config file cg_btc_e.conf logfile loge.log for my erupters.

[xyzzy099]

You should really set your temp to lower than your cutoff as well. It might not like them being the same, and I certainly wouldn't want 90 degrees as my target, I'd recommend 70.

Thanks. I have custom fans with 5400 RPM with fixed 12volt. (connected via molex) They cant overheat, but I will look into it

Is there any method to start a specific Avalon? I might want to connect a couple of Avalons to my windows pc. I like cgminer in combination with cgwatch. CGwatch restarts cgminer when there are 0 new accept shares after XX minutes. How can i specific which com port he should use?

Thanks in advance for your patience

What if a fan fails?

[candoo]

You should really set your temp to lower than your cutoff as well. It might not like them being the same, and I certainly wouldn't want 90 degrees as my target, I'd recommend 70.

Thanks. I have custom fans with 5400 RPM with fixed 12volt. (connected via molex) They cant overheat, but I will look into it

Is there any method to start a specific Avalon? I might want to connect a couple of Avalons to my windows pc. I like cgminer in combination with cgwatch. CGwatch restarts cgminer when there are 0 new accept shares after XX minutes. How can i specific which com port he should use?

Thanks in advance for your patience

What if a fan fails?

You hear a dying fans weeks before he's dead. Even though 90°C cutoff is the setting in the stock avalon firmware from the new batch 3.

[Xian01]

 Reporting in from the field, my 3.3.4 setup under Windows has experienced a few General Protection Faults over the past couple days driving ~50 AMU's per instance, where the cgminer.exe crashes and I need to kill the cmd.exe session to relaunch a new instance.

 Happens on both USB 2.0 and 3.0 systems.

[kano]

Since I am often making changes, testing stuff, I always run cgminer in a loop that simply restarts if it fails.
The windows version of this is

Code:

@echo off
REM cgminer
:Loop
Set NOW=%date:~10,4%%date:~7,2%%date:~4,2%.%time:~0,2%%time:~3,2%%time:~6,2%
.\cgminer.exe --no-restart --api-port 4028 --api-listen --api-allow W:127.0.0.1,W:192.168.1.0/24 --api-description Des -c pools.json 2> "run.%NOW%.log"
echo Sleeping for 5 seconds
ping -n 5 127.0.0.1 > NUL
GOTO Loop

The 5s sleep is good in case you change the options and it keeps hard looping due to a mistake

If someone is interested, here is my linux version:

Code:

#!/bin/bash
for (( ; ; ))
do
cgminer --config cg_$1_$2.conf 2>log$2.log
echo sleeping.....
sleep 5
echo done sleeping
done

I'm using few instances of cgminer for different devices and with parameters I can start different configs.

For example:
./gocg btc e
Runs config file cg_btc_e.conf logfile loge.log for my erupters.

Oh on linux - here's a better way
(how I do it - though I do it in 2 scripts one that calls the other - this is essentially what it is)

Code:

#!/bin/bash
#
nam="$HOME/cgminer-run.log"
while true ; do
 echo "`date`: Starting cgminer" 2>&1 | tee -a "$nam"
 ulimit -c 2097152
 now="`date +%Y%m%d%H%M%S`"
 ./cgminer --api-listen "$@" 2> "$HOME/run.$now.$$.log"
 s="$?"
 echo "`date`: cgminer exited status ($s)" 2>&1 | tee -a "$nam"
 echo "`date`: Sleeping for 5..." 2>&1 | tee -a "$nam"
 sleep 5
done

Add all your default options at line 8
Any other options you want you can add when you run it
So e.g. if you call it cgminer.sh
You can run it as:
./cgminer.sh -c pools.conf

In your $HOME directory you'll have cgminer-run.log that will list all the starts and stops
And run.YYYYMMDDHHMMSS.$$.log for each run

[kano]

...
I was using the released binaries on Windows7 x64 and I was continuously getting the failures described above.

I tried CrapMiner first on Linux (which I did build myself), and it worked flawlessly - so I never tried building CGMiner.  My problem is fixed.

I am just posting this in case others have the same problems I did with the Windows binary release of CGMiner, and so that you guys are aware that there may be an issue.

The problem there is that is failed logic (as a certain other developer enjoys ...)

Firstly, make sure you have the right libusb.dll - that is the actual cause of the problems.
If you use your old libusb.dll it of course will not work.

If, however, it still doesn't work, then it wont work with the clone either.
The problem will be either bad cables or a USB3 that causes it to fail.

On linux, it will work fine, but you simply are advertising using some other clone software coz you couldn't be bothered running cgminer.

i.e. go away.

[xyzzy099]

...
I was using the released binaries on Windows7 x64 and I was continuously getting the failures described above.

I tried CrapMiner first on Linux (which I did build myself), and it worked flawlessly - so I never tried building CGMiner.  My problem is fixed.

I am just posting this in case others have the same problems I did with the Windows binary release of CGMiner, and so that you guys are aware that there may be an issue.

The problem there is that is failed logic (as a certain other developer enjoys ...)

Firstly, make sure you have the right libusb.dll - that is the actual cause of the problems.
If you use your old libusb.dll it of course will not work.

If, however, it still doesn't work, then it wont work with the clone either.
The problem will be either bad cables or a USB3 that causes it to fail.

On linux, it will work fine, but you simply are advertising using some other clone software coz you couldn't be bothered running cgminer.

i.e. go away.

It's not clear to me what I did to get you into such a defensive stance.  Whatever it was, I apologize.

I thought I was just reporting an issue you might want to know about.

Again, I was using whatever binaries that were in your official Windows distribution, from the link at the beginning of this topic, and the zadig binary that is linked there also.

[bitpop]

Go away

[-ck]

Now now, no need to get narky. Most people aren't aware of the bitter history there and why Kano gets so pissed off at the mention of brickminer. It seemed an innocent enough report to me, he just didn't know that mere mention of the hostile fork makes it hard to see through the seething rage that it brings on.

[Askit2]

Kano,
I recompiled, make clean and make'd the 3.3.4 on Raspbian. I used the command you posted. Thank You!

I am still getting nearly 100% load. I am getting with 4 BFL jalapeno's 40% load cgminer and 33% load on ksoftirqd/0. I can not kill ksoftirqd/o so I assume its required. If it is then it has always been available but as I check top to see how much load cgminer has per instance I think I would have noticed a long time ago that it was pinning the processor. Running all 9 BFL jalapeno's results in 58% CGMiner and 40% Ksoftirqd/0.

I am running it with logging now. Is there something I should be looking for?

[-ck]

Kano,
I recompiled, make clean and make'd the 3.3.4 on Raspbian. I used the command you posted. Thank You!

I am still getting nearly 100% load. I am getting with 4 BFL jalapeno's 40% load cgminer and 33% load on ksoftirqd/0. I can not kill ksoftirqd/o so I assume its required. If it is then it has always been available but as I check top to see how much load cgminer has per instance I think I would have noticed a long time ago that it was pinning the processor. Running all 9 BFL jalapeno's results in 58% CGMiner and 40% Ksoftirqd/0.

I am running it with logging now. Is there something I should be looking for?

Have you been using 3.3.4 official or a git pull? At various stages there were issues in the git master tree and only now it has stabilised in preparation for the next release. If you are building from git, try pulling the latest git now.

[kano]

Kano,
I recompiled, make clean and make'd the 3.3.4 on Raspbian. I used the command you posted. Thank You!

I am still getting nearly 100% load. I am getting with 4 BFL jalapeno's 40% load cgminer and 33% load on ksoftirqd/0. I can not kill ksoftirqd/o so I assume its required. If it is then it has always been available but as I check top to see how much load cgminer has per instance I think I would have noticed a long time ago that it was pinning the processor. Running all 9 BFL jalapeno's results in 58% CGMiner and 40% Ksoftirqd/0.

I am running it with logging now. Is there something I should be looking for?

As Con said above, but also:
I got my 2nd RPi yesterday I bought.
I did already put a Raspbian 3.3.4a in cgminer-binaries yesterday, but yeah wait until the next release now (or you can build current git)
I'll be running some tests today with current git across a few platforms also, just to be sure there's nothing strange.
Next version release I'll of course have both an RPI_Arch and an RPI_Raspbian in cgminer-binaries also
However, I presume you've found it is quite easy to build even on RPi - just a bit slow

[Askit2]

Kano,
I recompiled, make clean and make'd the 3.3.4 on Raspbian. I used the command you posted. Thank You!

I am still getting nearly 100% load. I am getting with 4 BFL jalapeno's 40% load cgminer and 33% load on ksoftirqd/0. I can not kill ksoftirqd/o so I assume its required. If it is then it has always been available but as I check top to see how much load cgminer has per instance I think I would have noticed a long time ago that it was pinning the processor. Running all 9 BFL jalapeno's results in 58% CGMiner and 40% Ksoftirqd/0.

I am running it with logging now. Is there something I should be looking for?

Have you been using 3.3.4 official or a git pull? At various stages there were issues in the git master tree and only now it has stabilised in preparation for the next release. If you are building from git, try pulling the latest git now.

I pulled from git. recompiled and now it peaks up to 14%. Most of the time it is under 10%. Thank You for letting me know what caused the higher load.

I don't mind compiling directly and I really haven't had that much trouble in the past. Had the card dying not taken out all my old versions I would have just went back a version and ran that. Still I am thrilled that its again working at the low processor load I am used to.

[dooglio]

Hello,

I just got two Block Erupter USBs today. I plugged them both into my USB-2 port on my computer, using a Digital 7-Port Hub. cgminer recognizes them, but when I run I get really low hash rates (~100Mh/s). Both AMUs report timeouts:

AMU0: TIMEOUT GetResults took...

Thing is, when I pull one of the USB sticks out, and restart cgminer, it starts to hash at 335Mh/s, more what I was expecting. But even if I plug the other USB dongle into the other USB-2 port on my computer (without using the hub), I get the same results. I tried this on my laptop as well. It seems more than one Erupter is too much at a time.

Has anyone else had this problem? What if anything can I do to fix it?

It's not a total loss because I can plug in and run the two separately, but it would be nice to buy more Erupters and be able to plug them all into the same hub.

Any ideas?

[bitpop]

Have you tried both into your computer?