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

[-ck]

dmesg

Sorry No log file. Apparently it isn't setup. I will look into that next I guess.
Restarting cgminer was all I had to do to get them running again though. It didn't seem that bad.

dmesg is a command you run by itself

[1714093999]

1714093999

[1714093999]

1714093999

[Askit2]

dmesg

Sorry No log file. Apparently it isn't setup. I will look into that next I guess.
Restarting cgminer was all I had to do to get them running again though. It didn't seem that bad.

dmesg is a command you run by itself

It spit out a lot of stuff. Seems like everything since it started. I guess it not writing to a log doesn't stop logging.....

Code:

[    5.986608] usb 1-1.3.2.2: new high-speed USB device number 17 using dwc_otg
[    6.092568] usb 1-1.3.2.2: New USB device found, idVendor=0403, idProduct=6014
[    6.092602] usb 1-1.3.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.092622] usb 1-1.3.2.2: Product: BitFORCE SHA256 SC
[    6.092638] usb 1-1.3.2.2: Manufacturer: Butterfly Labs
[    6.092653] usb 1-1.3.2.2: SerialNumber: FTWVXEG2
[    6.096119] ftdi_sio 1-1.3.2.2:1.0: FTDI USB Serial Device converter detected
[    6.096379] usb 1-1.3.2.2: Detected FT232H
[    6.096405] usb 1-1.3.2.2: Number of endpoints 2
[    6.096425] usb 1-1.3.2.2: Endpoint 1 MaxPacketSize 512
[    6.096441] usb 1-1.3.2.2: Endpoint 2 MaxPacketSize 512
[    6.096456] usb 1-1.3.2.2: Setting MaxPacketSize 512
[    6.106712] usb 1-1.3.2.2: FTDI USB Serial Device converter now attached to ttyUSB7
[    6.186963] usb 1-1.3.2.3: new high-speed USB device number 18 using dwc_otg
[    6.292252] usb 1-1.3.2.3: New USB device found, idVendor=0403, idProduct=6014
[    6.292290] usb 1-1.3.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.292309] usb 1-1.3.2.3: Product: BitFORCE SHA256 SC
[    6.292327] usb 1-1.3.2.3: Manufacturer: Butterfly Labs
[    6.292360] usb 1-1.3.2.3: SerialNumber: FTWVJCP2
[    6.295926] ftdi_sio 1-1.3.2.3:1.0: FTDI USB Serial Device converter detected
[    6.296304] usb 1-1.3.2.3: Detected FT232H
[    6.296334] usb 1-1.3.2.3: Number of endpoints 2
[    6.296352] usb 1-1.3.2.3: Endpoint 1 MaxPacketSize 512
[    6.296368] usb 1-1.3.2.3: Endpoint 2 MaxPacketSize 512
[    6.296382] usb 1-1.3.2.3: Setting MaxPacketSize 512
[    6.315260] usb 1-1.3.2.3: FTDI USB Serial Device converter now attached to ttyUSB8
[    6.397348] usb 1-1.3.2.4: new high-speed USB device number 19 using dwc_otg
[    6.502699] usb 1-1.3.2.4: New USB device found, idVendor=0403, idProduct=6014
[    6.502739] usb 1-1.3.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.502758] usb 1-1.3.2.4: Product: BitFORCE SHA256 SC
[    6.502775] usb 1-1.3.2.4: Manufacturer: Butterfly Labs
[    6.502791] usb 1-1.3.2.4: SerialNumber: FTWVJCXH
[    6.514960] ftdi_sio 1-1.3.2.4:1.0: FTDI USB Serial Device converter detected
[    6.515166] usb 1-1.3.2.4: Detected FT232H
[    6.515190] usb 1-1.3.2.4: Number of endpoints 2
[    6.515208] usb 1-1.3.2.4: Endpoint 1 MaxPacketSize 512
[    6.515227] usb 1-1.3.2.4: Endpoint 2 MaxPacketSize 512
[    6.515244] usb 1-1.3.2.4: Setting MaxPacketSize 512
[    6.516207] usb 1-1.3.2.4: FTDI USB Serial Device converter now attached to ttyUSB9
[    6.624736] usb 1-1.3.3.1: new high-speed USB device number 20 using dwc_otg
[    6.742508] usb 1-1.3.3.1: New USB device found, idVendor=0403, idProduct=6014
[    6.742545] usb 1-1.3.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.742565] usb 1-1.3.3.1: Product: BitFORCE SHA256 SC
[    6.742581] usb 1-1.3.3.1: Manufacturer: Butterfly Labs
[    6.742597] usb 1-1.3.3.1: SerialNumber: FTWNQPX2
[    6.754640] ftdi_sio 1-1.3.3.1:1.0: FTDI USB Serial Device converter detected
[    6.754916] usb 1-1.3.3.1: Detected FT232H
[    6.754943] usb 1-1.3.3.1: Number of endpoints 2
[    6.754962] usb 1-1.3.3.1: Endpoint 1 MaxPacketSize 512
[    6.754979] usb 1-1.3.3.1: Endpoint 2 MaxPacketSize 512
[    6.754995] usb 1-1.3.3.1: Setting MaxPacketSize 512
[    6.755852] usb 1-1.3.3.1: FTDI USB Serial Device converter now attached to ttyUSB10
[    6.804709] Adding 1048564k swap on /dev/mmcblk0p6.  Priority:-1 extents:1 across:1048564k SS
[    6.856336] usb 1-1.3.3.2: new high-speed USB device number 21 using dwc_otg
[    6.981331] usb 1-1.3.3.2: New USB device found, idVendor=0403, idProduct=6014
[    6.981349] usb 1-1.3.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.981361] usb 1-1.3.3.2: Product: BitFORCE SHA256 SC
[    6.981370] usb 1-1.3.3.2: Manufacturer: FTDI
[    6.981378] usb 1-1.3.3.2: SerialNumber: FTWPZMCD
[    6.984774] ftdi_sio 1-1.3.3.2:1.0: FTDI USB Serial Device converter detected
[    6.984989] usb 1-1.3.3.2: Detected FT232H
[    6.985003] usb 1-1.3.3.2: Number of endpoints 2
[    6.985014] usb 1-1.3.3.2: Endpoint 1 MaxPacketSize 512
[    6.985024] usb 1-1.3.3.2: Endpoint 2 MaxPacketSize 512
[    6.985033] usb 1-1.3.3.2: Setting MaxPacketSize 512
[    6.985896] usb 1-1.3.3.2: FTDI USB Serial Device converter now attached to ttyUSB11
[    7.086377] usb 1-1.3.3.4: new high-speed USB device number 22 using dwc_otg
[    7.157321] systemd-journald[59]: Received request to flush runtime journal from PID 1
[    7.202326] usb 1-1.3.3.4: New USB device found, idVendor=0403, idProduct=6014
[    7.202389] usb 1-1.3.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    7.202402] usb 1-1.3.3.4: Product: BitFORCE SHA256 SC
[    7.202411] usb 1-1.3.3.4: Manufacturer: Butterfly Labs
[    7.202420] usb 1-1.3.3.4: SerialNumber: FTWNQPYZ
[    7.205866] ftdi_sio 1-1.3.3.4:1.0: FTDI USB Serial Device converter detected
[    7.206206] usb 1-1.3.3.4: Detected FT232H
[    7.206221] usb 1-1.3.3.4: Number of endpoints 2
[    7.206232] usb 1-1.3.3.4: Endpoint 1 MaxPacketSize 512
[    7.206242] usb 1-1.3.3.4: Endpoint 2 MaxPacketSize 512
[    7.206251] usb 1-1.3.3.4: Setting MaxPacketSize 512
[    7.208043] usb 1-1.3.3.4: FTDI USB Serial Device converter now attached to ttyUSB12
[   10.469086] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[   51.237152] ftdi_sio ttyUSB12: FTDI USB Serial Device converter now disconnected from ttyUSB12
[   51.237316] ftdi_sio 1-1.3.3.4:1.0: device disconnected
[   52.255172] ftdi_sio ttyUSB11: FTDI USB Serial Device converter now disconnected from ttyUSB11
[   52.255337] ftdi_sio 1-1.3.3.2:1.0: device disconnected
[   53.198744] ftdi_sio ttyUSB10: FTDI USB Serial Device converter now disconnected from ttyUSB10
[   53.198905] ftdi_sio 1-1.3.3.1:1.0: device disconnected
[   54.142399] ftdi_sio ttyUSB9: FTDI USB Serial Device converter now disconnected from ttyUSB9
[   54.142563] ftdi_sio 1-1.3.2.4:1.0: device disconnected
[   55.089457] ftdi_sio ttyUSB8: FTDI USB Serial Device converter now disconnected from ttyUSB8
[   55.089619] ftdi_sio 1-1.3.2.3:1.0: device disconnected
[   55.935746] ftdi_sio ttyUSB7: FTDI USB Serial Device converter now disconnected from ttyUSB7
[   55.935907] ftdi_sio 1-1.3.2.2:1.0: device disconnected
[   56.944595] ftdi_sio ttyUSB6: FTDI USB Serial Device converter now disconnected from ttyUSB6
[   56.944822] ftdi_sio 1-1.3.2.1:1.0: device disconnected
[   57.888536] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[   57.888697] ftdi_sio 1-1.3.1.4:1.0: device disconnected
[   58.794401] ftdi_sio ttyUSB5: FTDI USB Serial Device converter now disconnected from ttyUSB5
[   58.794552] ftdi_sio 1-1.3.1.3:1.0: device disconnected
[   59.713660] ftdi_sio ttyUSB4: FTDI USB Serial Device converter now disconnected from ttyUSB4
[   59.713821] ftdi_sio 1-1.3.1.2:1.0: device disconnected
[   60.594022] ftdi_sio ttyUSB3: FTDI USB Serial Device converter now disconnected from ttyUSB3
[   60.594185] ftdi_sio 1-1.3.1.1:1.0: device disconnected
[   61.506846] ftdi_sio ttyUSB2: FTDI USB Serial Device converter now disconnected from ttyUSB2
[   61.507007] ftdi_sio 1-1.2.3:1.0: device disconnected
[   62.379625] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[   62.379763] ftdi_sio 1-1.2.2:1.0: device disconnected
[67374.452970] usb 1-1.2.4: new high-speed USB device number 23 using dwc_otg
[67374.552956] usb 1-1.2.4: New USB device found, idVendor=0409, idProduct=005a
[67374.552995] usb 1-1.2.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[67374.556448] hub 1-1.2.4:1.0: USB hub found
[67374.556849] hub 1-1.2.4:1.0: 4 ports detected
[67374.832450] usb 1-1.2.4.1: new high-speed USB device number 24 using dwc_otg
[67374.938029] usb 1-1.2.4.1: New USB device found, idVendor=0403, idProduct=6014
[67374.938067] usb 1-1.2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[67374.938088] usb 1-1.2.4.1: Product: BitFORCE SHA256 SC
[67374.938104] usb 1-1.2.4.1: Manufacturer: Butterfly Labs
[67374.938120] usb 1-1.2.4.1: SerialNumber: FTWVRBUA
[67374.954826] ftdi_sio 1-1.2.4.1:1.0: FTDI USB Serial Device converter detected
[67374.955033] usb 1-1.2.4.1: Detected FT232H
[67374.955061] usb 1-1.2.4.1: Number of endpoints 2
[67374.955080] usb 1-1.2.4.1: Endpoint 1 MaxPacketSize 512
[67374.955096] usb 1-1.2.4.1: Endpoint 2 MaxPacketSize 512
[67374.955112] usb 1-1.2.4.1: Setting MaxPacketSize 512
[67374.956719] usb 1-1.2.4.1: FTDI USB Serial Device converter now attached to ttyUSB0
[67375.052377] usb 1-1.2.4.2: new high-speed USB device number 25 using dwc_otg
[67375.158624] usb 1-1.2.4.2: New USB device found, idVendor=0403, idProduct=6014
[67375.158660] usb 1-1.2.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[67375.158679] usb 1-1.2.4.2: Product: BitFORCE SHA256 SC
[67375.158698] usb 1-1.2.4.2: Manufacturer: Butterfly Labs
[67375.158714] usb 1-1.2.4.2: SerialNumber: FTWVX1WT
[67375.174487] ftdi_sio 1-1.2.4.2:1.0: FTDI USB Serial Device converter detected
[67375.174728] usb 1-1.2.4.2: Detected FT232H
[67375.174755] usb 1-1.2.4.2: Number of endpoints 2
[67375.174773] usb 1-1.2.4.2: Endpoint 1 MaxPacketSize 512
[67375.174790] usb 1-1.2.4.2: Endpoint 2 MaxPacketSize 512
[67375.174805] usb 1-1.2.4.2: Setting MaxPacketSize 512
[67375.175774] usb 1-1.2.4.2: FTDI USB Serial Device converter now attached to ttyUSB1
[67375.272562] usb 1-1.2.4.3: new high-speed USB device number 26 using dwc_otg
[67375.378639] usb 1-1.2.4.3: New USB device found, idVendor=0403, idProduct=6014
[67375.378676] usb 1-1.2.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[67375.378696] usb 1-1.2.4.3: Product: BitFORCE SHA256 SC
[67375.378712] usb 1-1.2.4.3: Manufacturer: Butterfly Labs
[67375.378729] usb 1-1.2.4.3: SerialNumber: FTWVXE2E
[67375.394993] ftdi_sio 1-1.2.4.3:1.0: FTDI USB Serial Device converter detected
[67375.395203] usb 1-1.2.4.3: Detected FT232H
[67375.395231] usb 1-1.2.4.3: Number of endpoints 2
[67375.395250] usb 1-1.2.4.3: Endpoint 1 MaxPacketSize 512
[67375.395267] usb 1-1.2.4.3: Endpoint 2 MaxPacketSize 512
[67375.395282] usb 1-1.2.4.3: Setting MaxPacketSize 512
[67375.396171] usb 1-1.2.4.3: FTDI USB Serial Device converter now attached to ttyUSB2
[67375.492575] usb 1-1.2.4.4: new high-speed USB device number 27 using dwc_otg
[67375.598991] usb 1-1.2.4.4: New USB device found, idVendor=0403, idProduct=6014
[67375.599053] usb 1-1.2.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[67375.599075] usb 1-1.2.4.4: Product: BitFORCE SHA256 SC
[67375.599092] usb 1-1.2.4.4: Manufacturer: Butterfly Labs
[67375.599106] usb 1-1.2.4.4: SerialNumber: FTWVX3C8
[67375.614891] ftdi_sio 1-1.2.4.4:1.0: FTDI USB Serial Device converter detected
[67375.615184] usb 1-1.2.4.4: Detected FT232H
[67375.615212] usb 1-1.2.4.4: Number of endpoints 2
[67375.615231] usb 1-1.2.4.4: Endpoint 1 MaxPacketSize 512
[67375.615248] usb 1-1.2.4.4: Endpoint 2 MaxPacketSize 512
[67375.615264] usb 1-1.2.4.4: Setting MaxPacketSize 512
[67375.616287] usb 1-1.2.4.4: FTDI USB Serial Device converter now attached to ttyUSB3
[67377.762760] ftdi_sio ttyUSB3: FTDI USB Serial Device converter now disconnected from ttyUSB3
[67377.762918] ftdi_sio 1-1.2.4.4:1.0: device disconnected
[67378.746598] ftdi_sio ttyUSB2: FTDI USB Serial Device converter now disconnected from ttyUSB2
[67378.746760] ftdi_sio 1-1.2.4.3:1.0: device disconnected
[67379.723256] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[67379.723420] ftdi_sio 1-1.2.4.2:1.0: device disconnected
[67380.638095] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[67380.638326] ftdi_sio 1-1.2.4.1:1.0: device disconnected
[root@cgminerPi1 journal]#

Hopefully you see something in there. Sorry I am slow at Linux. I really do try to learn. Thank You for helping me learn!

[lano1106]

3.6.4 ONLY builds with the jansson and libusb included in cgminer (which is libusb-1.0.16-rc10, NOT libusbx). It ignores any installed libraries on your machine since it's the only way I can guarantee people are using the most stable libraries. As for it hanging on closing, it's a clusterfuck that I've never been able to completely fix due to millions of threads going wild and no clean way to shut it down with some things never returning. Blame me.

Con,

you must know that it is trivial for a ArchLinux maintainer to sed your configure.ac script to do whatever he wants. Here is a snippet of the PKGBUILD script:

Code:

  # We have latest jansson and libusb - just use them
  sed "s|ac_subdirs_all='compat/libusb\-1.0\ncompat/jansson-2.5'||" -i ./configure
  sed 's|subdirs="$subdirs compat/libusb\-1.0"||' -i ./configure
  sed 's|subdirs="$subdirs compat/jansson\-2.5"||' -i ./configure
  sed 's|LIBUSB_LIBS="compat/libusb-1.0/libusb/.libs/libusb-1.0.a"|LIBUSB_LIBS=-lusb-1.0|' -i ./configure
  sed 's|JANSSON_LIBS="compat/jansson-2.5/src/.libs/libjansson.a"|JANSSON_LIBS=-ljansson|' -i ./configure
  sed 's|compat/Makefile ||' -i ./configure

  sed 's|JANSSON_INCLUDES = -I$(top_srcdir)/compat/jansson-2.5/src||' -i ./Makefile.in
  sed 's|USBUTILS_INCLUDES = -I$(top_srcdir)/compat/libusb\-1.0/libusb|USBUTILS_INCLUDES = -I/usr/include/libusb-1.0|' -i ./Makefile.in
  sed 's|SUBDIRS = lib compat ccan|SUBDIRS = lib ccan|' -i ./Makefile.in

  rm -r compat

but hey thanks for the suggestion to try out the git version. I'll do that and report back if it fix my problem.

Thank you very much!

[-ck]

3.6.4 ONLY builds with the jansson and libusb included in cgminer (which is libusb-1.0.16-rc10, NOT libusbx). It ignores any installed libraries on your machine since it's the only way I can guarantee people are using the most stable libraries. As for it hanging on closing, it's a clusterfuck that I've never been able to completely fix due to millions of threads going wild and no clean way to shut it down with some things never returning. Blame me.

Con,

you must know that it is trivial for a ArchLinux maintainer to sed your configure.ac script to do whatever he wants. Here is a snippet of the PKGBUILD script:

Code:

  # We have latest jansson and libusb - just use them
  sed "s|ac_subdirs_all='compat/libusb\-1.0\ncompat/jansson-2.5'||" -i ./configure
  sed 's|subdirs="$subdirs compat/libusb\-1.0"||' -i ./configure
  sed 's|subdirs="$subdirs compat/jansson\-2.5"||' -i ./configure
  sed 's|LIBUSB_LIBS="compat/libusb-1.0/libusb/.libs/libusb-1.0.a"|LIBUSB_LIBS=-lusb-1.0|' -i ./configure
  sed 's|JANSSON_LIBS="compat/jansson-2.5/src/.libs/libjansson.a"|JANSSON_LIBS=-ljansson|' -i ./configure
  sed 's|compat/Makefile ||' -i ./configure

  sed 's|JANSSON_INCLUDES = -I$(top_srcdir)/compat/jansson-2.5/src||' -i ./Makefile.in
  sed 's|USBUTILS_INCLUDES = -I$(top_srcdir)/compat/libusb\-1.0/libusb|USBUTILS_INCLUDES = -I/usr/include/libusb-1.0|' -i ./Makefile.in
  sed 's|SUBDIRS = lib compat ccan|SUBDIRS = lib ccan|' -i ./Makefile.in

  rm -r compat

but hey thanks for the suggestion to try out the git version. I'll do that and report back if it fix my problem.

Thank you very much!

Sure, but just be aware that many distros include libusbx and not libusb native, and that libusbx is LESS reliable despite being a later version which is precisely why I include the one that I want people to use in-tree.

[lano1106]

Sure, but just be aware that many distros include libusbx and not libusb native, and that libusbx is LESS reliable despite being a later version which is precisely why I include the one that I want people to use in-tree.

Oups. then maybe we should report that to the maintainer as this is precisely what all ArchLinux users are using with cgminer binary package:

Code:

lano1106@whippet2 /var/abs/community/cgminer $ pacman -Qs libusb
local/libgusb 0.1.6-1
    GLib wrapper around libusb1
local/libusbx 1.0.17-1
    Library that provides generic access to USB device

[-ck]

Sure, but just be aware that many distros include libusbx and not libusb native, and that libusbx is LESS reliable despite being a later version which is precisely why I include the one that I want people to use in-tree.

Oups. then maybe we should report that to the maintainer as this is precisely what all ArchLinux users are using with cgminer binary package:

Code:

lano1106@whippet2 /var/abs/community/cgminer $ pacman -Qs libusb
local/libgusb 0.1.6-1
    GLib wrapper around libusb1
local/libusbx 1.0.17-1
    Library that provides generic access to USB device

Indeed, especially since I spent a lot of time trying to shoehorn it into the build process seamlessly considering I can't seem to make heads or tails out of autotools after all these years...

[vayvanne]

TeckNet USB3.0 hub, BFL Jala 7.5GH, 8 BEs, Win7 x64, got zombied BEs few times. Was ok with 3.5.1.

Did you try experimental .exes in the temp directory? Some fixes there.

Tried, zombies with them too. All 3.6.x has this issue.

[-ck]

TeckNet USB3.0 hub, BFL Jala 7.5GH, 8 BEs, Win7 x64, got zombied BEs few times. Was ok with 3.5.1.

Did you try experimental .exes in the temp directory? Some fixes there.

Tried, zombies with them too. All 3.6.x has this issue.

* ckolivas laughs hysterically as he completely loses his marbles

I can't believe it. I spend ages fixing a billion problems with windows for some people, and somehow the solution presents a problem in windows for someone else...

Try newer exes just uploaded in temp directory please.

[aigeezer]

TeckNet USB3.0 hub, BFL Jala 7.5GH, 8 BEs, Win7 x64, got zombied BEs few times. Was ok with 3.5.1.

Did you try experimental .exes in the temp directory? Some fixes there.

Tried, zombies with them too. All 3.6.x has this issue.

* ckolivas laughs hysterically as he completely loses his marbles

I can't believe it. I spend ages fixing a billion problems with windows for some people, and somehow the solution presents a problem in windows for someone else...

Try newer exes just uploaded in temp directory please.

Just started the new ones, working fine in the first few minutes. Like some other posters, I've been having random zombies for a while, 3.4.x IIRC, including with the previous experimental exes.
Looking good right now though, but it often takes many hours before the first zombie appears.

Thanks for working on it - nasty challenge!

Edit: 3 minutes later, first zombie just appeared. Sorry.

[-ck]

腹切り
切腹

[-ck]

Edit: 3 minutes later, first zombie just appeared. Sorry.

Run it in full debug mode storing the log somewhere until the zombies appear to see what it might be that provokes them.

i.e. start it with the extra commands: -D 2>log.txt
and send me the log.txt file.

Note that if, despite all the absurd extra code I put in, you are still having problems, it may not be code at all, so check connections, power cables, adequate power, OS etc.

[techman05]

Minor heads up, there is a newer version of zadig, and I have uploaded it to my website, BUT it contains the same version of the WinUSB driver so it will not change the performance or the behaviour of the drivers once they're installed/assigned.

I was hoping it would have. I want more programs to see my devices on windows.

[aigeezer]

Note that if, despite all the absurd extra code I put in, you are still having problems, it may not be code at all, so check connections, power cables, adequate power, OS etc.

I know, and I keep trying to isolate such things but no clear result yet other than - one of my machines ran 24/7 for weeks without a single anomaly, no zombies or crashes, on 3.1.something but two of my machines started to have random zombies on all versions from 3.4 on. I'm not saying cgminer is flawed - the later versions might have uncovered some previously unseen Windows bug, for instance, but the problems (for me) seemed to start after 3.1.

Because of this, I'm fairly sure it's not most of the things you list, but it could certainly be OS, which for me is latest Win7 64.

Gotta do some dirtspace things for most of the day, but I'll get a log Real Soon Now and also set a machine back to 3.1 and see if it becomes stable again.

Edit: changed to 3.1 from incorrect 3.3 in several places.
 

[josephliton]

can anyone  help me out please,I am using cg miner ,I want to split my hashing asic power in two different mining pool but in one pool it will be 1 GHz and other pool will have the rest of the hashing power,is there any way do to do this.

Thanks.

[twmz]

can anyone  help me out please,I am using cg miner ,I want to split my hashing asic power in two different mining pool but in one pool it will be 1 GHz and other pool will have the rest of the hashing power,is there any way do to do this.

Thanks.

Yes, you can do this.  Read the README document.  Search for the section 'QUOTAS'.

https://github.com/ckolivas/cgminer/blob/master/README

[josephliton]

can anyone  help me out please,I am using cg miner ,I want to split my hashing asic power in two different mining pool but in one pool it will be 1 GHz and other pool will have the rest of the hashing power,is there any way do to do this.

Thanks.

Yes, you can do this.  Read the README document.  Search for the section 'QUOTAS'.

https://github.com/ckolivas/cgminer/blob/master/README

Thank you .

[Blisk]

What i mostly miss in this mining software is central managed clients software where i can manage a client from one comuputer.
for instance, Like I have 10 client computers where all are in network connected to server, so I have on server an administration software to define when cgminer is runned on client computer with pre defined intensity. So in morning hours intensity is low when people work on computers and out of working hours intensity is high when nobody works on them. On administration software I can see a video card, temperatures, etc. for each client and can set for each client differend setting for differend hours. I will pay for that software like 3$ per client licence. I am soure many other wil do too.
I know many companies where computer are newer turned off, so why can't someone use it for mining at that time?
And we all knows that many use that computer to mine. Bitcoin is almost over but there are new currency which will go on. And script mining have some flaws, like dynamic intensity doesn't work well.
And I have permission from company ovner to use those 10 computers to mine after working hours.
So what I need is client software and administration software for client. Maybe is there someone which will do that?

[vayvanne]

Edit: 3 minutes later, first zombie just appeared. Sorry.

Run it in full debug mode storing the log somewhere until the zombies appear to see what it might be that provokes them.

i.e. start it with the extra commands: -D 2>log.txt
and send me the log.txt file.

Note that if, despite all the absurd extra code I put in, you are still having problems, it may not be code at all, so check connections, power cables, adequate power, OS etc.

Latest binaries are ok for last 4 hours for me. Still logging just in case.
By the way is that only me using --text-only to get proper debug.log?
That -D 2 > log.txt does not work in windows for me. Is there a way to log and keep console updating in windows?
PS. That was great to know about quotas

[guitarplinker]

So CGMiner isn't going to support the 290X and similar cards, correct?

[xyzzy099]

腹切り
切腹

I put this in Google translate, and it said:

Belly cut ri
Seppuku

Are you threatening suicide here?