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

[ZPK]

why in title contained osx ...? please delete or give answer how did it)))

[1713999211]

1713999211

[1713999211]

1713999211

[1713999211]

1713999211

[-ck]

why in title contained osx ...? please delete or give answer how did it)))

The software should compile with osx. But since no one who uses osx is willing to compile it regularly and help me debug minor issues as they arise with osx, I can't tell you if it compiles or not. The software IS cross platform, but with no users what is there to say? The number of people building on osx is basically zero now. Mining on osx is expensive an inefficient; the hashrate is never as good as win/linux.

[kano]

...
re: 2 COM ports
Device manager sees ONE COM5.  My command line is cgminer -c cgminer.conf
My cgminer.conf is in my previous post.

This has been discussed before ...

cgminer will load the default cgminer.conf (if it finds it) no matter what you specify on the command line ... then it also does what you say on the command line.

[ZPK]

why in title contained osx ...? please delete or give answer how did it)))

The software should compile with osx. But since no one who uses osx is willing to compile it regularly and help me debug minor issues as they arise with osx, I can't tell you if it compiles or not. The software IS cross platform, but with no users what is there to say? The number of people building on osx is basically zero now. Mining on osx is expensive an inefficient; the hashrate is never as good as win/linux.

thx

[JWU42]

I've downgraded to the 8.921 driver for my 7970 on linux. 12.2 would crash the 7970 at lower engine clocks than normal and 12.3 would introduce rare but occasional hardware errors on the 7970 and would spontaneously crash a 6970, taking the device with it and I'd need to cold boot the machine for the 6970 to reappear. 8.921 was the version that needed a manually edited xorg.conf and specific card order to work with 7970 and 6970 was mixed.

Way to go AMD..

Here is a link to the driver - kinda hard to find...

http://www2.ati.com/DRIVERS/hotfix/radeon_7900_series/amd-driver-installer-8.921-x86.x86_64.run

[nathanghart]

I've downgraded to the 8.921 driver for my 7970 on linux. 12.2 would crash the 7970 at lower engine clocks than normal and 12.3 would introduce rare but occasional hardware errors on the 7970 and would spontaneously crash a 6970, taking the device with it and I'd need to cold boot the machine for the 6970 to reappear. 8.921 was the version that needed a manually edited xorg.conf and specific card order to work with 7970 and 6970 was mixed.

What is the specific changes needed in the xorg.conf file? Is there a link or resource somewhere?

TIA

[-ck]

I've downgraded to the 8.921 driver for my 7970 on linux. 12.2 would crash the 7970 at lower engine clocks than normal and 12.3 would introduce rare but occasional hardware errors on the 7970 and would spontaneously crash a 6970, taking the device with it and I'd need to cold boot the machine for the 6970 to reappear. 8.921 was the version that needed a manually edited xorg.conf and specific card order to work with 7970 and 6970 was mixed.

What are the specific changes needed in the xorg.conf file? Is there a link or resource somewhere?

The driver simply did not configure my 6970s at all so I had to manually add them. It was a basic blank configuration so all I had to do was find out what pci bus number they were and add them:

Changed:
Section "ServerLayout"
        Identifier     "aticonfig Layout"
        Screen      0  "aticonfig-Screen[0]-0" 0 0

to also have:
        Screen         "aticonfig-Screen[1]-0" RightOf "aticonfig-Screen[0]-0"
        Screen         "aticonfig-Screen[2]-0" RightOf "aticonfig-Screen[1]-0"
etc..


Changed
Section "Monitor"
        Identifier   "aticonfig-Monitor[0]-0"
        Option      "VendorName" "ATI Proprietary Driver"
        Option      "ModelName" "Generic Autodetecting Monitor"
        Option      "DPMS" "true"
EndSection

to have extra entries of:
Section "Monitor"
        Identifier   "aticonfig-Monitor[1]-0"
        Option      "VendorName" "ATI Proprietary Driver"
        Option      "ModelName" "Generic Autodetecting Monitor"
        Option      "DPMS" "true"
EndSection
etc...

Changed
Section "Device"
        Identifier  "aticonfig-Device[0]-0"
        Driver      "fglrx"
        BusID       "PCI:1:0:0"
EndSection

to have extra entries of:
Section "Device"
        Identifier  "aticonfig-Device[1]-0"
        Driver      "fglrx"
        BusID       "PCI:6:0:0"
EndSection
etc...

Note I manually figured out what PCI bus numbers to put in based on the output of:
lspci  | grep VGA
which reads:
01:00.0 VGA compatible controller: ATI Technologies Inc Device 6798
06:00.0 VGA compatible controller: ATI Technologies Inc Device 6718
07:00.0 VGA compatible controller: ATI Technologies Inc Device 6718
etc.

And finally
Section "Screen"
        Identifier "aticonfig-Screen[0]-0"
        Device     "aticonfig-Device[0]-0"
        Monitor    "aticonfig-Monitor[0]-0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
        EndSubSection
EndSection

had extra entries of:

Section "Screen"
        Identifier "aticonfig-Screen[1]-0"
        Device     "aticonfig-Device[1]-0"
        Monitor    "aticonfig-Monitor[1]-0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
        EndSubSection
EndSection
etc..

So yeah not exactly a straight forward operation. It's supposed to work automatically with the command:
aticonfig --adapter=all --initial -f

but it didn't...

[kano]

A few things ...

I'm wary of any code that includes "not sure if"

I guess I'll look at that windows stuff if I ever get around to fixing my windows compile and read up on the details of SetupComm, SetCommConfig and PurgeComm
... and find out what problems that PurgeComm could cause ...

As for the linux code:

Yes it is supposed to be a DEBUG, it is not an ERR.
I happens every time a work request doesn't have a share within the 'total' timeout
I changed it way back to DEBUG since it was originally a WARNING (always displayed).

Your read will write off the end of the buffer when there are more than 4 bytes available ...

My suggestion Post ideas, not code ...

[-ck]

I'll be away for ~10 days. Behave while I'm away kids.

[m3ta]

I'll be away for ~10 days. Behave while I'm away kids.

We will try, mommy.

[kano]

My suggestion Post ideas, not code ...

Done.  One of my last posts.

Code gets sent to git pull requests

[twmz]

In case anyone else runs into a similar situation...

I was wondering how to put multiple scan-serial command line arguments (for my icarus boards) into the cgminer config files so that I could stop including them on the command line.  After some experimentation, it seems the right way to do this is to use JSON array syntax to indicate the multiple values.  For example, here is a sample config file for my icarus devices (the line with scan-serial in it is the relevant line):

Code:

{
"pools" : [
        {
                "url" : "http://p2pool.local:9332",
                "user" : "user",
                "pass" : "x"
        },
        {
                "url" : "http://p2pool-backup.local:9332",
                "user" : "user",
                "pass" : "x"
        }
],
"scan-serial" : [ "icarus:/dev/ttyUSB0", "icarus:/dev/ttyUSB1" ],
"disable-gpu" : true,
"failover-only" : true,
"submit-stale" : true
}

[boozer]

EDIT:  Found out it was fix 20 for bamt, just happened to apply that the same time i went to 2.3.2.... thank Kano!

I have a weird problem, doesn't happen in 2.3.1, but 2.3.2 has the problem... whenever I run in a screen, cgminer stops within a minute or two with this in the log:

Code:

[2012-04-04 16:50:02] API: connection from 127.0.0.1 - Accepted
[2012-04-04 16:50:02] API: recv command: (6) 'quit|
'
[2012-04-04 16:50:02] API: access denied to '127.0.0.1' for 'quit' command
[2012-04-04 16:50:02] API: send reply: (96) 'STATUS=E,W...'
[2012-04-04 16:50:02] API: sent 96

However, if I run it without the screen command, it runs just fine....

My script to start with screen is:

Code:

/usr/bin/screen -dmS cgminer /root/quickcgminer.sh

Where quickcgminer.sh is:

Code:

export GPU_USE_SYNC_OBJECTS=1
export DISPLAY=:0
cd /opt/miners/ckolivas-cgminer-ef76ec8
/opt/miners/ckolivas-cgminer-ef76ec8/cgminer -D --verbose --api-listen -Q 8 --gpu-threads 2 --gpu-engine 800-1180,800-1190,800-1220 --gpu-memdiff -150 --auto-fan --auto-gpu --temp-target 75 -I 11 -o http://gpumax.com:8332 -u x -p x -o http://pool.bitlc.net:80 -u x -p x -o http://mint.bitminter.com:8332 -u x -p x 2>/root/log.txt

If run just /root/quickcgminer.sh, then it runs just fine... without any quitting, so seems to be something with the screen command?

Any ideas?

[kano]

I have a weird problem, doesn't happen in 2.3.1, but 2.3.2 has the problem... whenever I run in a screen, cgminer stops within a minute or two with this in the log:

Code:

[2012-04-04 16:50:02] API: connection from 127.0.0.1 - Accepted
[2012-04-04 16:50:02] API: recv command: (6) 'quit|
'
[2012-04-04 16:50:02] API: access denied to '127.0.0.1' for 'quit' command
[2012-04-04 16:50:02] API: send reply: (96) 'STATUS=E,W...'
[2012-04-04 16:50:02] API: sent 96

...

BAMT running?

That "quit|\n" is what BAMT used to send cgminer (and probably still does) rather than just "quit"

Anyway the message means that something somewhere on your computer is send a "quit|\n" to cgminer and then killing the cgminer process (when the quit fails)

My guess would be BAMT - since that's what it does.
(unless someone else has written something to work like BAMT)

[boozer]

I have a weird problem, doesn't happen in 2.3.1, but 2.3.2 has the problem... whenever I run in a screen, cgminer stops within a minute or two with this in the log:

Code:

[2012-04-04 16:50:02] API: connection from 127.0.0.1 - Accepted
[2012-04-04 16:50:02] API: recv command: (6) 'quit|
'
[2012-04-04 16:50:02] API: access denied to '127.0.0.1' for 'quit' command
[2012-04-04 16:50:02] API: send reply: (96) 'STATUS=E,W...'
[2012-04-04 16:50:02] API: sent 96

...

BAMT running?

That "quit|\n" is what BAMT used to send cgminer (and probably still does) rather than just "quit"

Anyway the message means that something somewhere on your computer is send a "quit|\n" to cgminer and then killing the cgminer process (when the quit fails)

My guess would be BAMT - since that's what it does.
(unless someone else has written something to work like BAMT)

Yup... BAMT.  Now that I look there, I see it sending the quit in the logs...  But the quit only kills cgminer when I run cgminer in a screen... weird.
It was fix 20 that added a cgminer watchdog.... since I'm not starting cgminer with the official BAMT profile, that probably caused some issue.  I removed BAMT fix 20 and its running fine now.  Thanks Kano!

Any way to make the cgminer API "readonly" or block the "quit" command?

[kano]

I have a weird problem, doesn't happen in 2.3.1, but 2.3.2 has the problem... whenever I run in a screen, cgminer stops within a minute or two with this in the log:

Code:

[2012-04-04 16:50:02] API: connection from 127.0.0.1 - Accepted
[2012-04-04 16:50:02] API: recv command: (6) 'quit|
'
[2012-04-04 16:50:02] API: access denied to '127.0.0.1' for 'quit' command
[2012-04-04 16:50:02] API: send reply: (96) 'STATUS=E,W...'
[2012-04-04 16:50:02] API: sent 96

...

BAMT running?

That "quit|\n" is what BAMT used to send cgminer (and probably still does) rather than just "quit"

Anyway the message means that something somewhere on your computer is send a "quit|\n" to cgminer and then killing the cgminer process (when the quit fails)

My guess would be BAMT - since that's what it does.
(unless someone else has written something to work like BAMT)

Yup... BAMT.  Now that I look there, I see it sending the quit in the logs...  But the quit only kills cgminer when I run cgminer in a screen... weird.
It was fix 20 that added a cgminer watchdog.... since I'm not starting cgminer with the official BAMT profile, that probably caused some issue.  I removed BAMT fix 20 and its running fine now.  Thanks Kano!

Any way to make the cgminer API "readonly" or block the "quit" command?

As it says - the quit command is blocked (which it is by default)

Code:

[2012-04-04 16:50:02] API: access denied to '127.0.0.1' for 'quit' command

The problem is that BAMT then does a process kill after the quit command - which of course only a program running on the same machine can kill a process.

[boozer]

The problem is that BAMT then does a process kill after the quit command - which of course only a program running on the same machine can kill a process.

Ahh that makes sense.  Thanks a lot!

[bulanula]

Seems like diablo and poclbm now fail to compile on SDK 2.1 and seg fault.

Not a problem just letting others know on 5870s.

Use diakgcn or phatk with 5870s and SDK 2.1

It seems that diakgcn is not as good as phatk.

[bitlane]

I'm a bit out of the loop, but, did something drastic change in 2.3.2 ?

I have rigs reporting as high as 170% Efficiency right now, with 125-150% being the average range for the others.

Win7 x64, CGMiner 2.3.2
5 rigs each with either SDK 2.1 or 2.4 and CAT 11.12 on all.
Mixed 5xxx/6xxx series card machines, exclusive 5xxx series card machines and exclusive 6xxx series card machines.

The performance is not specific to any card/config. The ONLY thing they all have in common is the 11.12 driver and CGminer version 2.3.2.

WTF ?

I double checked and didn't rely on the Efficiency% readout only. The ratio of GetWork's to Accepted's (even with Rejected included/excluded) does not lie.

Colour me impressed

[DeathAndTaxes]

likely your pool implemented longer/better NTimeRolling.

BTW high (or low) efficiency has absolutely no effect on your bottom line.  It is a pretty useless stat.