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

[Killerloop]

Mine isn't

Yeah sorry, a little misunderstanding on my part 

[1714046689]

1714046689

[1714046689]

1714046689

[1714046689]

1714046689

[PatMan]

Bitmain does some terrible things in their driver including ... discarding stale work in the driver before passing it to the work validation code.
This means on p2pool that if you find a stale block that is still a valid network block, it will be discarded. Oh well.

Use my driver for S1 if you don't want to throw such valid blocks away on p2pool.

My S2 driver is still in development - I'm still trying to work out why the device thinks it's a good idea to have >8000 work items queued in it - more than 30s of work - and to work out how to reduce that without letting it get idle - so I'm still waiting on source code from bitmain.

Hey Kano - did Bitmain get back to you yet my man?

My poor S2's are crying out to be set free.........

Peace.

[MarketNeutral]

The mandatory solo mining parameter "btc-address" almost sneaked by me——don't want to be mining for someone else. A reminder to everyone to actually read the readme.

[-ck]

The mandatory solo mining parameter "btc-address" almost sneaked by me——don't want to be mining for someone else. A reminder to everyone to actually read the readme.

You can't mine for someone else. It simply wont mine without an address. There was only one older version that would mine somewhere else if you didn't put an address in and it was removed quickly because of the complaints.

[-ck]

http://ck.kolivas.org/apps/cgminer/debug/

Read the README-debug file.

Hardware is actively cooled and working in air conditioned room - always below 42C.

Here is the debug:

Code:

Thanks. There's not much information in that. Did you use the debug cgminer.exe binary from that directory as well?

Yes I did. I've run it again.
On the miner console I get this:

Code:

[2014-05-27 07:50:08] BXF 2 BXFWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
[2014-05-27 07:50:14] BXF 2 attempted reset got err:(0) LIBUSB_SUCCESS
[2014-05-27 07:50:14] BXF 2: Error 0 sending BXFWork sent 0 of 162

Debug:

Code:

cgminerDebug.exe caused an Access Violation at location 74de9a24 in module msvcrt.dll Reading from location 7881399c.

Registers:
eax=00000001 ebx=00000000 ecx=74616368 edx=00000003 esi=78813999 edi=78813d65
eip=74de9a24 esp=041fd4f0 ebp=041fd4f8 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202

Thanks. For whatever reason there's not enough information to know exactly why it's crashing suggesting it's crashing outside the debug built code within cgminer. I'll look through that particular code part of cgminer to see if I can figure out what might be triggering it.

[-ck]

Yes I did. I've run it again.
On the miner console I get this:

Code:

[2014-05-27 07:50:08] BXF 2 BXFWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
[2014-05-27 07:50:14] BXF 2 attempted reset got err:(0) LIBUSB_SUCCESS
[2014-05-27 07:50:14] BXF 2: Error 0 sending BXFWork sent 0 of 162

Debug:

Code:

cgminerDebug.exe caused an Access Violation at location 74de9a24 in module msvcrt.dll Reading from location 7881399c.

Registers:
eax=00000001 ebx=00000000 ecx=74616368 edx=00000003 esi=78813999 edi=78813d65
eip=74de9a24 esp=041fd4f0 ebp=041fd4f8 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202

Thanks. For whatever reason there's not enough information to know exactly why it's crashing suggesting it's crashing outside the debug built code within cgminer. I'll look through that particular code part of cgminer to see if I can figure out what might be triggering it.

Here try this experimental binary and see if it helps please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

[kefky]

Is cgminerdownload.com a fake download site?

[mdude77]

Is cgminerdownload.com a fake download site?

Probably.  Why not use the known published legit one?

M

[kefky]

Sure, I wouldn't download anything from this site!

Is cgminerdownload.com a fake download site?

Probably.  Why not use the known published legit one?

M

[kano]

Bitmain does some terrible things in their driver including ... discarding stale work in the driver before passing it to the work validation code.
This means on p2pool that if you find a stale block that is still a valid network block, it will be discarded. Oh well.

Use my driver for S1 if you don't want to throw such valid blocks away on p2pool.

My S2 driver is still in development - I'm still trying to work out why the device thinks it's a good idea to have >8000 work items queued in it - more than 30s of work - and to work out how to reduce that without letting it get idle - so I'm still waiting on source code from bitmain.

Hey Kano - did Bitmain get back to you yet my man?

My poor S2's are crying out to be set free.........

Peace.

No more source yet.
I have everything except the SPI kernel code (which I'll implement in cgminer if I can get it - and solve it all in one place)
Code, of course, is necessary since there are no Bitmain docs on the AntMiner hardware.

Bitmain US has been ever so helpful with my S2 though
Replacement boards and controllers after that pile of damage that originally arrived.

It's rather annoying though that mine doesn't work 100%, since I'm really not sure how my current replacement driver performs.
I can get it running at >990GH/s for hours, but then find it drops. At least I do also get the same issue with their version of the driver ... so it must be my S2 - but I simply cant be 100% certain if it is hardware, the SPI kernel module, or the driver.
I'll probably put out a test firmware next week anyway - with the new cgminer and also a small collection of changes here and there in the firmware itself - so I can see some comparisons on various S2s.

Running yet another overnight run to see how it goes ... after a few hours.
This time it's a new backplane AND a new controller ... fingers crossed.
(I'm 99% sure the 10 boards are OK since I can swap them around without effect)

[-ck]

Is cgminerdownload.com a fake download site?

I've never heard of it so I would say it is guaranteed to be a fake. My site and kano's mirrored files listed in the opening post are the only official cgminer downloads.

[Buchi-88]

@ckolivas

My Raspberry with Cgminer 4.3.4 is very unstable, it's possible that the Cgminer have a problem with BiFuryTwin and Antminers at the same time?

When i used only "./configure --enable-bitfury" the Raspberry would't crash, but when i used "./configure --enable-bitfury --enable-icarus" at the same time my Raspberry crash and restart!

Cgminer config:

"api-listen" : true,
"api-allow" : "W:192.168.0.15",
"api-port" : "4028",
"expiry" : "120",
"failover-only" : true,
"log" : "5",
"no-pool-disable" : true,
"queue" : "2",
"scan-time" : "60",
"worktime" : true,
"shares" : "0",
"kernel-path" : "/usr/local/bin",
"api-allow" : "0/0",
"bxm-bits" : "53",
"anu-freq" : "250"

regards and thanks for your answer

[-ck]

@ckolivas

My Raspberry with Cgminer 4.3.4 is very unstable, it's possible that the Cgminer have a problem with BiFuryTwin and Antminers at the same time?

When i used only "./configure --enable-bitfury" the Raspberry would't crash, but when i used "./configure --enable-bitfury --enable-icarus" at the same time my Raspberry crash and restart!

Does only cgminer crash or the whole RPi? If it's the whole RPi then you have an instability problem with your Pi which is common, not cgminer. Usually a different SD card or kernel upgrade or different distribution is the way to fix that. If it's just cgminer that crashes, try making a debug build using the instructions here:
http://ck.kolivas.org/apps/cgminer/debug/

As a workaround you can simply set cgminer to restart whenever there's a problem (if it's just cgminer crashing and not the whole Pi).

while true ; do ./cgminer [commands] && sleep 5 ; done

[Buchi-88]

Hello and thanks for your answer. I think the problem is the Antminer (Icarus) driver, by me the Raspberry start a reboot when Cgminer hangs (Watchdog).

With the 8 x Bifurys (./configure --enable-bitfury) i have no problem the miners run without a reboot!

But whn i test my 8 x Antminers U2+ (./configure --enable-icarus) the Cgminer reboot my Raspberry about one time in a hour!?

With the command (./configure --enable-bitfury --enable-icarus) its the same?

Also the follow command i have set:

Raspberry Pi is locking up when running CGMiner

If your RPi is freezing randomly after some time (could be minutes, could be hours or days) with error like Oops: PREEMPT ARM, CPU0 Not tainted printed out over HDMI, and with locked up ethernet and USB interfaces, you have to add following option to the /boot/cmdline.txt file on SD card:
slub_debug=FP

regards

[-ck]

Software should never make the operating system crash, even if it's always the same software driver in this case.

[Buchi-88]

OK, when i make a debug file, help that?

Is this so correct when im using the ANT and BiFury?

./configure --enable-bitfury --enable-icarus

make -g

Then i build a debug file?

It's strange, I hardly use the ants launches the Pi always new (since Cgminer hangs) at the BiFurys there are no problems?

regards

Edit:

At time i use the Cgminer 4.2.3 and over 4 hours it's all OK with the configs no Pi restart...!!??

[PatMan]

It's rather annoying though that mine doesn't work 100%, since I'm really not sure how my current replacement driver performs.
I can get it running at >990GH/s for hours, but then find it drops. At least I do also get the same issue with their version of the driver ... so it must be my S2 - but I simply cant be 100% certain if it is hardware, the SPI kernel module, or the driver.
I'll probably put out a test firmware next week anyway - with the new cgminer and also a small collection of changes here and there in the firmware itself - so I can see some comparisons on various S2s.

I hear you, it's very frustrating - especially as I can't use it on p2pool without losing even more hashing rate. I must have been lucky with mine though, only minor courier impact (loose/disconnected cables) & it hashes at ~1050Gh/s steady. I'd be happy to help if you need any testers by the way - just let me know.

Thanks again Kano 

[Buchi-88]

OK, when i make a debug file, help that?

Is this so correct when im using the ANT and BiFury?

./configure --enable-bitfury --enable-icarus

make -g

Then i build a debug file?

It's strange, I hardly use the ants launches the Pi always new (since Cgminer hangs) at the BiFurys there are no problems?

regards

Edit:

At time i use the Cgminer 4.2.3 and over 4 hours it's all OK with the configs no Pi restart...!!??

Hello after a few of tests, I think its a compatibility problem between Cgminer and a other Software (RaspControl for the Cgminer) to Log the Cgminer!

http://sven-goessling.de/12/01/2014/raspcontrol-cgminer-auf-dem-raspberry-pi-11-01-14/

But the crashes are only by the Antminers and very often with the new 4.3.4 with 4.2.0 it's better.

regards

[PatMan]

Hi again guys - another question about the S2 thing. I've noticed that there is an Ubuntu distro for the Beaglebone, which is the S2 controller, so was wondering if it would be possible to use cgminer on this instead of the current Linux distro? Would cgminer be able to detect the hashing boards via pci though? Maybe in the same way it used to detect GPU's? I'm not sure - just throwing stuff out there.........if only they were usb .......

Peace 

[Aexcu]

I've been solo mining with cgminer 3.12.3 and now updated to 4.3.4.

However, the same setup (BITMAIN AntMiner U1) which worked on the earlier version, no longer seems to work on the new. (Startup simply: "cgminer.exe -u blah -p blah -o 127.0.0.1:8332")

Running a --debug gives the following:

Popping work from get queue to get work
Testing pool stratum+tcp://localhost:8332
Succeeded delayed connect
Socket closed waiting in recv_line
Closing socket for stratum pool 0
Failed to parse a \n terminated string in recv_line
Initiate stratum failed
Closing socket for stratum pool 0
Waiting for work to be available from pools


I tried starting it with the --fix-protocol -option, but to no avail.