OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 194.

EfterlysT

full member

Activity: 425

Merit: 109

Quote from: aigeezer on October 27, 2013, 03:00:22 PM

Quote from: EfterlysT on October 27, 2013, 02:57:44 PM

I have a question because i dont get it to work.

I just setup some USB Erupters for mining PPC instead of PPC.

This is the command line i use right now:
cgminer -o http://stratum.d7.lt:3333 -u user -p pass

Everything runs ok but my GPU also starts to mine. What do i add to disable my GPU from mining ?

Try cgminer-nogpu instead of cgminer

Thanks, that solved it.

Now i feel like a retard to

aigeezer

legendary

Activity: 1450

Merit: 1013

Cryptanalyst castrated by his government, 1952

Quote from: EfterlysT on October 27, 2013, 02:57:44 PM

I have a question because i dont get it to work.

I just setup some USB Erupters for mining PPC instead of PPC.

This is the command line i use right now:
cgminer -o http://stratum.d7.lt:3333 -u user -p pass

Everything runs ok but my GPU also starts to mine. What do i add to disable my GPU from mining ?

Try cgminer-nogpu instead of cgminer

EfterlysT

full member

Activity: 425

Merit: 109

I have a question because i dont get it to work.

I just setup some USB Erupters for mining PPC instead of PPC.

This is the command line i use right now:
cgminer -o http://stratum.d7.lt:3333 -u user -p pass

Everything runs ok but my GPU also starts to mine. What do i add to disable my GPU from mining ?

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: -ck on October 27, 2013, 08:15:13 AM

If the latest buglet fix does not fix the problem, here are some other binaries to try with various experiments.

http://ck.kolivas.org/apps/cgminer/temp/cgminer-4444.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-allrw.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-allwrites.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-oh.exe

Thanks

I`m still running previous one w/o any trouble 7hrs now. 2x usb erupter directly to PC + 30GH/s BFL.
Should I try another one?

jmc1517

newbie

Activity: 56

Merit: 0

Yep - There were no zombies when I had logging and --debug on with the new "bugfix" build. May be that's the way to go.

Edit: Two more results, both no-go's:

cgminer-allwrites : 3 zombies in 38 minutes
cgminer-oh : 1 zombie in 5 minutes

logfiles here (without --debug), if required:
https://dl.dropboxusercontent.com/u/44240170/logfile-allwrites.txt
https://dl.dropboxusercontent.com/u/44240170/logfile-oh.txt

Back to 3.3.1 for me then Sad

aigeezer

legendary

Activity: 1450

Merit: 1013

Cryptanalyst castrated by his government, 1952

Quote from: jmc1517 on October 27, 2013, 11:17:19 AM

I can confirm aigeezer's experience so far, and a bit more:

cgminer-4444 : 6 zombies in 1.5 hours
cgminer-allrw : 1 zombie after 9 minutes

logfiles (without --debug) here if required:
https://dl.dropboxusercontent.com/u/44240170/logfile-4444.txt
https://dl.dropboxusercontent.com/u/44240170/logfile-allrw.txt

And so, on to the next one...

Yup, my allrw has one zombie now, AMU 11, after an hour unattended. Not sure when it happened.

Crowdsource debugging - wish I'd had that back in the day.

Trying allwrites next.

Edit: update, 4 zombies in quick succession after about 20 minutes using allwrites (AMU 9-12). On to the "oh" test.

Edit: update, 1 zombie after 7 minutes using "oh" (AMU 10).

I guess I'll turn logging on, superstitiously hoping that will keep the zombie horde at bay until there's some new development.

jmc1517

newbie

Activity: 56

Merit: 0

I can confirm aigeezer's experience so far, and a bit more:

cgminer-4444 : 6 zombies in 1.5 hours
cgminer-allrw : 1 zombie after 9 minutes

logfiles (without --debug) here if required:
https://dl.dropboxusercontent.com/u/44240170/logfile-4444.txt
https://dl.dropboxusercontent.com/u/44240170/logfile-allrw.txt

And so, on to the next one...

aigeezer

legendary

Activity: 1450

Merit: 1013

Cryptanalyst castrated by his government, 1952

Quote from: -ck on October 27, 2013, 08:15:13 AM

If the latest buglet fix does not fix the problem, here are some other binaries to try with various experiments.

http://ck.kolivas.org/apps/cgminer/temp/cgminer-4444.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-allrw.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-allwrites.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-oh.exe

Thanks

I've been using cgminer-nogpu. Are these all replacement candidates for it?

Edit: Ah, they must be, judging by the file size. I had been comparing them to an earlier smaller cgminer-nogpu.

Anyway, now running the 4444 version as cgminer-nogpu within 3.6.6 and no problems in the first few minutes.

Edit: I left the room for a while and when I came back AMUs 3,4,5,6 and 12 were zombies. Elapsed time of run about one hour but I don't know exactly when the failures happened.
I'll try the allrw version next.

aigeezer

legendary

Activity: 1450

Merit: 1013

Cryptanalyst castrated by his government, 1952

Quote from: -ck on October 27, 2013, 08:17:26 AM

Quote from: aigeezer on October 27, 2013, 08:03:31 AM

Edit: AMU 8 went zombie 14 minutes into the run. I'll rerun with logging and see if anything shows up.

Nope, more important to try the other experiments please.

OK. The logged "little buglet" version has been fine for 32 minutes - shutting it down now to try the other stuff.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: aigeezer on October 27, 2013, 08:03:31 AM

Edit: AMU 8 went zombie 14 minutes into the run. I'll rerun with logging and see if anything shows up.

Nope, more important to try the other experiments please.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

If the latest buglet fix does not fix the problem, here are some other binaries to try with various experiments.

http://ck.kolivas.org/apps/cgminer/temp/cgminer-4444.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-allrw.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-allwrites.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-oh.exe

Thanks

aigeezer

legendary

Activity: 1450

Merit: 1013

Cryptanalyst castrated by his government, 1952

Quote from: -ck on October 27, 2013, 07:28:12 AM

So I'm assuming that turning debugging on is having some subtle effect on timing, slowing down writes to the device or something like that, and is indirectly making your devices more stable. So that gives me some other avenues to check out. Give the bugfix a try and I'll make some other binaries trying other shit out, thanks.

Yes, that's how it feels to me.

The bugfix version is up and running now, without logging. It's been fine for the first 10 minutes. If it fails, I'll restart it with logging on.

Edit: AMU 8 went zombie 14 minutes into the run. I'll rerun with logging and see if anything shows up.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: aigeezer on October 27, 2013, 07:25:56 AM

Quote from: -ck on October 26, 2013, 08:38:00 AM

Quote from: aigeezer on October 26, 2013, 08:34:15 AM

Quote from: -ck on October 26, 2013, 08:17:54 AM

Quote from: aigeezer on October 26, 2013, 07:55:47 AM

3.6.6 reports two zombies (literally) after about 20 minutes. I'll restart it shortly with logging on.

3.6.6 is almost identical to the experimental .exe you last downloaded.

OK, thanks for the info. Behavior seems about the same. Working fine with logging, only running with log for about half an hour so far though.

It's still bizarre that it would not go zombie with logging on only. Either way it will be nice to know what error specifically causes cgminer to consider the device dead. All we can do is keep watching and maybe capture something on the log.

My 3.6.6 test with logging on has run for just under 24 hours - log size is 1.16GB. Nothing unusual happened - no errors of any kind that I can see, but I haven't read every line of the log.

13 AMUs and one BAL, Win 7 64.

I'll shut it down shortly to try your new "little buglet" fix.

So I'm assuming that turning debugging on is having some subtle effect on timing, slowing down writes to the device or something like that, and is indirectly making your devices more stable. So that gives me some other avenues to check out. Give the bugfix a try and I'll make some other binaries trying other shit out, thanks.

aigeezer

legendary

Activity: 1450

Merit: 1013

Cryptanalyst castrated by his government, 1952

Quote from: -ck on October 26, 2013, 08:38:00 AM

Quote from: aigeezer on October 26, 2013, 08:34:15 AM

Quote from: -ck on October 26, 2013, 08:17:54 AM

Quote from: aigeezer on October 26, 2013, 07:55:47 AM

3.6.6 reports two zombies (literally) after about 20 minutes. I'll restart it shortly with logging on.

3.6.6 is almost identical to the experimental .exe you last downloaded.

OK, thanks for the info. Behavior seems about the same. Working fine with logging, only running with log for about half an hour so far though.

It's still bizarre that it would not go zombie with logging on only. Either way it will be nice to know what error specifically causes cgminer to consider the device dead. All we can do is keep watching and maybe capture something on the log.

My 3.6.6 test with logging on has run for just under 24 hours - log size is 1.16GB. Nothing unusual happened - no errors of any kind that I can see, but I haven't read every line of the log.

13 AMUs and one BAL, Win 7 64.

I'll shut it down shortly to try your new "little buglet" fix.

jmc1517

newbie

Activity: 56

Merit: 0

Just realised that that last run was without the --debug option. Trying again with --debug and logging turned on :/

jmc1517

newbie

Activity: 56

Merit: 0

Quote from: -ck on October 26, 2013, 05:44:54 PM

Do you see a message just before one of them goes zombie about any usb errors in particular?

I've downloaded the latest 3.6.6. cgminer-nogpu.exe but it still gives me a couple of zombies after 10 minutes and also continuous timeouts on another AMU which is NOT one of the zombies.

I've now restarted with a logfile - see below for the exact details.

Another thing I noticed, which may or may not be important:- When I first ran cgminer-nogpu after changing from 3.3.1, I didn't bother to power the hubs off/on, and when cgminer-nogpu started up it turned off all the green LEDs on all 34 erupters - i.e. it found them all - but it was only showing 33 erupters (0-32). Cgwatcher was reporting 33 devices also. As far as I could see, shares were being processed from all the AMUs (green flashes) - so what happened to the missing device? I powered off/on after that and got all 34 devices working as normal. Not sure if it's important, but I thought it worth mentioning as I haven't seen this behaviour before, as cgwatcher has always reported the correct number of devices, even if they were not showing on the cgminer screen.

Ah, just about to post, and now I have errors and a logfile. Here's an extract:

Code:

 [2013-10-27 10:59:29] Started cgminer 3.6.6
 :
 [2013-10-27 11:05:21] Accepted 0db97324 Diff 18/8 AMU 31 pool 0 
  :
 [2013-10-27 11:05:59] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:05:59] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:00] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:00] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:01] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:01] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:02] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:02] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:03] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:03] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:04] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:04] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:05] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:05] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:05] Accepted 031d7613 Diff 82/8 AMU 20 pool 0 
 [2013-10-27 11:06:06] AMU 31 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:06:06] AMU31: Comms error (werr=-7 amt=0)
 [2013-10-27 11:06:07] Accepted 1928fe55 Diff 10/8 AMU 5 pool 0 
 [2013-10-27 11:06:16] Stratum from pool 0 detected new block
 [2013-10-27 11:06:16] Rejected 035c23e1 Diff 76/8 AMU 21 pool 0 (Job '84396' not found) 
 [2013-10-27 11:06:16] Rejected 0b03fc59 Diff 23/8 AMU 29 pool 0 (Job '84396' not found) 
 [2013-10-27 11:06:16] Accepted 0432dd08 Diff 60/8 AMU 19 pool 0 
 [2013-10-27 11:06:18] Accepted 1d3203f8 Diff 8/8 AMU 31 pool 0
 :
 [2013-10-27 11:10:59] Accepted 1772e531 Diff 10/8 AMU 13 pool 0 
 :
 [2013-10-27 11:13:27] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:27] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:28] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:28] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:28] Accepted 0c9c1e70 Diff 20/8 AMU 28 pool 0 
 [2013-10-27 11:13:29] Accepted 057ce3b2 Diff 46/8 AMU 27 pool 0 
 [2013-10-27 11:13:29] Accepted 160bf5ea Diff 11/8 AMU 5 pool 0 
 [2013-10-27 11:13:29] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:29] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:30] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:30] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:31] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:31] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:31] Accepted 1bdbce81 Diff 9/8 AMU 18 pool 0 
 [2013-10-27 11:13:31] Accepted 1df086ca Diff 8/8 AMU 25 pool 0 
 [2013-10-27 11:13:32] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:32] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:33] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:33] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:34] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:34] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:34] Accepted 0db2ded2 Diff 18/8 AMU 21 pool 0 
 [2013-10-27 11:13:35] AMU 13 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-10-27 11:13:35] AMU13: Comms error (werr=-7 amt=0)
 [2013-10-27 11:13:36] Accepted 0ff4b00e Diff 16/8 AMU 14 pool 0 
 [2013-10-27 11:13:40] Accepted 0f865896 Diff 16/8 AMU 13 pool 0 
 :
 [2013-10-27 11:13:55] Accepted 19b8a6cd Diff 9/8 AMU 13 pool 0 
 :
 [2013-10-27 11:14:22] AMU 13 SendWork usb write err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2013-10-27 11:14:22] AMU13: Comms error (werr=-4 amt=0)
 [2013-10-27 11:14:22] AMU 13 failure, disabling!
 [2013-10-27 11:14:22] Thread 13 being disabled
 :
 [2013-10-27 11:14:30] Icarus detect (5:34) failed to initialise (incorrect device?)

The full log is here:
https://dl.dropboxusercontent.com/u/44240170/logfile.txt

Does it help?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: rav3n_pl on October 27, 2013, 05:06:37 AM

Stared on 2x USB erupters + 1x BFL 30GH/s
What should I expect? ;]

Thanks.

Hopefully... nothing untoward \o/

Anyway I sneaked up fresh binary packages anyway with the -1 suffix since it's an obvious bugfix, but not big enough to warrant a new version.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Stared on 2x USB erupters + 1x BFL 30GH/s
What should I expect? ;]

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: -ck on October 26, 2013, 09:41:41 PM

Found another little buglet. Uploading another cgminer-nogpu.exe into the temp directory. Windows users with AMU issues please try it.

http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe

I know you're all tested out, but this one's a big fix for AMUs...

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Found another little buglet. Uploading another cgminer-nogpu.exe into the temp directory. Windows users with AMU issues please try it.

http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 194. (Read 5805670 times)