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

[twmz]

How difficult would it be to allow several instances of cgminer in the same system?

Why would I want to do that? I am building a "Condo" system where miners are hosted in a remote location. I want to give each user full control of his mining unit, which may be only part of a boxed system. For example, an Avalon box can have as many as 4 hardware modules, and each module can have 8 hashing units. A user in the condo system can own as small as a single hashing unit, and I want her to be able to launch her own instance of cgminer on the same box where other users are running their own instance of cgminer. Each cgminer instance is associated with a user ID, and that user ID is in turn associated with particular hashing unit(s). The association of a user ID to hashing unit(s) is done by another subsystem, so all that really needs to happen is to allow cgminer to accept a command-line parameter that indicates which hashing unit(s) it will use exclusively.

Each cgminer instance should be separately addressable in the RPC protocol/API.

I believe this requires substantial code changes (may be changes to both cgminer itself and the Avalon drivers), so I will give a hashing unit in the condo I am building to whoever can get this done, and yes, it's OK for it to be open source.

Edit: Please PM me if you would be interested in implementing this project.

THis shouldn't require any code change at all.  I routinely run multiple instances of cgminer on my mining rigs.  One for GPUs, one for BFL FPGA devices, one for BFL SC devices, etc.  Each has an independent API endpoint.  You just have to start each version with command line parameters to make sure that it selects the correct devices (see the --usb parameter and the discussion of it in the READMEs) so that no two cgminer instances try to mine against the same devices.  You also want to specify a different API port for each instance. 

[os2sam]

How difficult would it be to allow several instances of cgminer in the same system?

Easy, I run 3 to 5 instances with 3.3.1

[salfter]

How difficult would it be to allow several instances of cgminer in the same system?

Easy, I run 3 to 5 instances with 3.3.1

I'm trying to run one instance on each of my Jalapeños so I can have one mine on BTCGuild and the other on P2Pool.  I'm trying to use something like this to launch two instances of cgminer:

Code:

screen -dmS miner_0  cgminer --api-listen --api-allow W:127.0.0.1 --api-port 4028 --device 0 --remove-disabled --url stratum+tcp://stratum.btcguild.com:3333 --user ____ --pass ____
screen -dmS miner_1  cgminer --api-listen --api-allow W:127.0.0.1 --api-port 4029 --device 1 --remove-disabled --url stratum+tcp://salfter.gotdns.org:9332 --user ____ --pass ____

The first one starts properly and runs on just one Jalapeño, but the other doesn't. Removing the screen invocation and adding --text-only produces this:

Code:

 [2013-07-09 10:02:34] Started cgminer 3.3.1
 [2013-07-09 10:02:34] Loaded configuration file /home/salfter/.cgminer/cgminer.conf
 [2013-07-09 10:02:34] SEM: BitForceSC USB failed to get (1409024) '/tmp/cgminer-usb-1-6' - device in use
 [2013-07-09 10:02:34] SEM: BitForceSC USB failed to get (1441793) '/tmp/cgminer-usb-1-5' - device in use
 [2013-07-09 10:02:34] Command line options set a device that doesn't exist   

It says both are in use, even though only one is actually in use.

[os2sam]

How difficult would it be to allow several instances of cgminer in the same system?

Easy, I run 3 to 5 instances with 3.3.1

I'm trying to run one instance on each of my Jalapeños so I can have one mine on BTCGuild and the other on P2Pool.  I'm trying to use something like this to launch two instances of cgminer:

Code:

screen -dmS miner_0  cgminer --api-listen --api-allow W:127.0.0.1 --api-port 4028 --device 0 --remove-disabled --url stratum+tcp://stratum.btcguild.com:3333 --user ____ --pass ____
screen -dmS miner_1  cgminer --api-listen --api-allow W:127.0.0.1 --api-port 4029 --device 1 --remove-disabled --url stratum+tcp://salfter.gotdns.org:9332 --user ____ --pass ____

The first one starts properly and runs on just one Jalapeño, but the other doesn't. Removing the screen invocation and adding --text-only produces this:

Code:

 [2013-07-09 10:02:34] Started cgminer 3.3.1
 [2013-07-09 10:02:34] Loaded configuration file /home/salfter/.cgminer/cgminer.conf
 [2013-07-09 10:02:34] SEM: BitForceSC USB failed to get (1409024) '/tmp/cgminer-usb-1-6' - device in use
 [2013-07-09 10:02:34] SEM: BitForceSC USB failed to get (1441793) '/tmp/cgminer-usb-1-5' - device in use
 [2013-07-09 10:02:34] Command line options set a device that doesn't exist   

It says both are in use, even though only one is actually in use.

Just use --usb bfl:1 for each instance

[-ck]

--device is a very coarse tool designed for GPU rigs predominantly. Use --usb for pretty much everything else.

[crazyates]

How difficult would it be to allow several instances of cgminer in the same system?

Easy, I run 3 to 5 instances with 3.3.1

I'm trying to run one instance on each of my Jalapeños so I can have one mine on BTCGuild and the other on P2Pool.  I'm trying to use something like this to launch two instances of cgminer:
It says both are in use, even though only one is actually in use.

Just use --usb bfl:1 for each instance

"--usb bfl:1" is for the old FPGA Singles. For Jalapenos, you want "--usb baj:1".

I run two instances of CGMiner on one computer, where --usb bfl:1 points my FPGA to one pool, and another instnace with --usb bas:1 points my Single at another pool.

[twmz]

"--usb bfl:1" is for the old FPGA Singles. For Jalapenos, you want "--usb baj:1".

I run two instances of CGMiner on one computer, where --usb bfl:1 points my FPGA to one pool, and another instnace with --usb bas:1 points my Single at another pool.

Actually, all BFL SC devices (jalanpenos, singles, etc) are "--usb bas:#".  It's based on the driver (bas for the new sc driver, bfl for the old fpga driver).

[flyonwall]

Cool! So can one instance of cgminer use a particular hashing unit (or several hashing units) in an Avalon system? What would be the command line for doing this?

[MineForeman.com]

While trying to sort out the RPi USB1.1 problems I decided to (finally) try everything on my Xubu 11.04 rig
(Seems everything works fine on Fedora18 and Xubu 11.04 ...)

You should also try Arch on your RPi, I have been running it for months (along with hundreds of MinePeon users) without issues.

Neil

[salfter]

"--usb bfl:1" is for the old FPGA Singles. For Jalapenos, you want "--usb baj:1".

I run two instances of CGMiner on one computer, where --usb bfl:1 points my FPGA to one pool, and another instnace with --usb bas:1 points my Single at another pool.

Actually, all BFL SC devices (jalanpenos, singles, etc) are "--usb bas:#".  It's based on the driver (bas for the new sc driver, bfl for the old fpga driver).

I found that this worked, with the device index starting at 1.  Also, --usb x:y works, with x and y being the bus and device numbers for the miner as reported by lsusb.

Now I can have my mining split between pools...just need for P2Pool to switch over to v13 now.

[os2sam]

"--usb bfl:1" is for the old FPGA Singles. For Jalapenos, you want "--usb baj:1".

I run two instances of CGMiner on one computer, where --usb bfl:1 points my FPGA to one pool, and another instnace with --usb bas:1 points my Single at another pool.

Actually, all BFL SC devices (jalanpenos, singles, etc) are "--usb bas:#".  It's based on the driver (bas for the new sc driver, bfl for the old fpga driver).

I found that this worked, with the device index starting at 1.  Also, --usb x:y works, with x and y being the bus and device numbers for the miner as reported by lsusb.

Now I can have my mining split between pools...just need for P2Pool to switch over to v13 now.

I was using the Bus:Device at first too.  But on reboot those assignments can change so switched my methodology to --usb ICA:3 for each instance.  That way it doesn't matter which device it actually uses just grabs the first 3 available.

Also you would use --usb BAS:1 in case you missed the posts correcting my mistake.

Any way you want to do it, it does work great.

Also the options are explained in the readme.txt under advanced usb options.
Sam

[twmz]

Cool! So can one instance of cgminer use a particular hashing unit (or several hashing units) in an Avalon system? What would be the command line for doing this?

Please read the README   Search it for '--usb'

[GrapeApe]

I just got my second 7770 and I can't get cgminer to recognize it. I'll be honest I have no idea what I'm doing here. I am new to linux Ubuntu 12.04. It was dumb luck getting everything to work to begin with because of fgrlx driver corruption issues when installing thru the system settings on Ubuntu and being forced to update the driver thru the terminal.Do I need to put a dummy plug in the card? I'm sure I need to tell linux I put in a second card but I have no idea where to start.

Edit: I got cgminer to recognize the card but now the 2 cards are hashing at the speed of 1 card (half speed). Everything on my display monitor is doubled up as well 2 clocks 2 everything. Does this mean I need a dummy plug?

[flyonwall]

How difficult would it be to allow several instances of cgminer in the same system?

Why would I want to do that? I am building a "Condo" system where miners are hosted in a remote location. I want to give each user full control of his mining unit, which may be only part of a boxed system. For example, an Avalon box can have as many as 4 hardware modules, and each module can have 8 hashing units. A user in the condo system can own as small as a single hashing unit, and I want her to be able to launch her own instance of cgminer on the same box where other users are running their own instance of cgminer. Each cgminer instance is associated with a user ID, and that user ID is in turn associated with particular hashing unit(s). The association of a user ID to hashing unit(s) is done by another subsystem, so all that really needs to happen is to allow cgminer to accept a command-line parameter that indicates which hashing unit(s) it will use exclusively.

Each cgminer instance should be separately addressable in the RPC protocol/API.

I believe this requires substantial code changes (may be changes to both cgminer itself and the Avalon drivers), so I will give a hashing unit in the condo I am building to whoever can get this done, and yes, it's OK for it to be open source.

Edit: Please PM me if you would be interested in implementing this project.

THis shouldn't require any code change at all.  I routinely run multiple instances of cgminer on my mining rigs.  One for GPUs, one for BFL FPGA devices, one for BFL SC devices, etc.  Each has an independent API endpoint.  You just have to start each version with command line parameters to make sure that it selects the correct devices (see the --usb parameter and the discussion of it in the READMEs) so that no two cgminer instances try to mine against the same devices.  You also want to specify a different API port for each instance. 

Thanks! I will give that a try.

[GrapeApe]

Alright so I have solved the double gnome panels I mentioned above. Cgminer sees my second gpu but the 2 together hash at the same rate as one. When I disable the 2nd card the 1st card immediately speeds up to normal speed. Also I'm not able to adjust anything on second card. Engine clock speed and memory are stuck at 300. I could adjust the intensity on it. I've removed the card for now and I am just hashing on the original. Some help here would be appreciated.

edit: when I enter this command I get the double gnome panels. Which I can fix mow.

sudo aticonfig --adapter=all --initial

I then reboot and check to see if both cards are there.

sudo aticonfig --adapter=all --odgt
Ubuntu can see both of them and the temps.

I then check to see if cgminer detects both cards ./cgminer -n and it does with no errors.
I run cgminer and it splits the normal hash rate of 1 card between the 2. 110 MH/s on each card. When I disable the 2nd card the hash rate on the first goes up to normal 220MH/s...
I've seen this talked about in other threads but no solution.

[crazyearner]

Problems mining on a pool is this cgminer problem within unit or is this problem on their side on the pool

The shares you sent have been looking like this:
020000005e4757cdbd7b756ceac436c46fe3ba6d9f532adaca8541c3beba010000000000246cf2c 7800231d5d50c5a7c9241e7465fb2085346478a4b95c70a34d43fec20daa1dc518db6011b70523f dc80000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000280

I think your miner messed up formatting the shares from mining to results.

it seems that it puts the result at the beginning

correct form should be:
result of the hash:
020000005e4757cdbd7b756ceac436c46fe3ba6d9f532adaca8541c3beba01
data sent to pool
0000000000246cf2c7800231d5d50c5a7c9241e7465fb2085346478a4b95c70a34d43fec20daa1d c518db6011b70523fdc800000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000280

Is this a bug to be fixed? or something to do with cgminer or something to do on their side on the pool ?

[GenTarkin]

think I MAY have found a bug in most recent avy firmware ..

It seems w/ avalon-auto & avalon-freq & an initial clock frequency > min of avalon-freq...
once avy clocks down the the min specified per avalon-freq, it seems to no go back up from that floor no matter what temps / hw error rate is =(
Example:

My initial clock is 350mhz, freq 315-400, during hot day avy will slowly clock down to 315, but even when it cools down and HW error rate is below 2% & temps are below their specified max...
It wont start climbing from 315 =(

[-ck]

Problems mining on a pool is this cgminer problem within unit or is this problem on their side on the pool

The shares you sent have been looking like this:
020000005e4757cdbd7b756ceac436c46fe3ba6d9f532adaca8541c3beba010000000000246cf2c 7800231d5d50c5a7c9241e7465fb2085346478a4b95c70a34d43fec20daa1dc518db6011b70523f dc80000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000280

I think your miner messed up formatting the shares from mining to results.

it seems that it puts the result at the beginning

correct form should be:
result of the hash:
020000005e4757cdbd7b756ceac436c46fe3ba6d9f532adaca8541c3beba01
data sent to pool
0000000000246cf2c7800231d5d50c5a7c9241e7465fb2085346478a4b95c70a34d43fec20daa1d c518db6011b70523fdc800000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000280

Is this a bug to be fixed? or something to do with cgminer or something to do on their side on the pool ?

There's a standard way to submit shares in terms of byte swapping and endian order. cgminer secures more than half the bitcoin network having sent gazillions of shares since its inception. Look at the pool instead.

[paladin281978]

Why decreased speed?
cgminer 3.2.1 - 645 kh
cgminer 3.3.1 - 605-610 kh

[tom_o]

Just an idea which could be very useful over the summer, could temperature control by dynamic intensity be possible? I've had to reduce intensity from 20 to 16 to keep my 7970s under 86°C this last week due to the how hot it's been in the UK but they can run at 19 overnight fine cause it's quite a bit cooler.