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

[-ck]

Hi Con,

Firstly thanks for all the updates aimed at Hashfast devices, 4.2 has helped a lot.

As all Sierra's are not born equal I need to run them at different clock speeds. I successfully used the '--hfa-name Slug --usb 4:42' to rename one device to later allow me to use '--hfa-options "rabbit:650,turtle:550"'
If I add more renaming to the string it simply doesn't find any device. Can you tell me what I have wrong with the below?

--hfa-name NS1 --usb 1:7 --hfa-name NS2 --usb 2:7 --hfa-name NS3 --usb 2:4

Thanks

--hfa-name <arg>    Set a unique name for a single hashfast device specified with --usb or the first device found

Name one at a time. You only need to name them once; the names should keep for ever more even with firmware updates.

[1501224627]

1501224627

[1501224627]

1501224627

[1501224627]

1501224627

[1501224627]

1501224627

[winit]

Thanks man... sorry for being the reading retard!

Cheers

[winit]

I think I have named them all individually but no matter what string I use for --hfa-options I can't get it to load. Can you write me an example?

Thanks

[-ck]

I think I have named them all individually but no matter what string I use for --hfa-options I can't get it to load. Can you write me an example?

Thanks

Shall I quote the docs again?

--hfa-options <arg> Set hashfast options name:clock (comma separated)

This command allows you to set options for each discrete hashfast device by
its name (if the firmware has naming support, i.e. version 0.3+). Currently
this takes only one option, the clock speed, although future options may be
added.
e.g.:
--hfa-options "rabbit:650,turtle:550"

[Biffa]

Here's another new AntS1 binary.

An endian issue was found in the solo code for the ant (no issue for desktop computers), so this update includes the fix for that.
I've removed both old AntS1 binaries

This uses the same patch as before for the luci display.
My source for this version is here:
https://github.com/kanoi/cgminer/tree/ants1-4.2.0-00567a4

The binary and README are in my cgminer-binaries git here:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1  <-- Follow this link to get the new binary

Read the README on the screen there for how to replace the /usr/bin/cgminer binary in your AntS1 with the new one.

This binary includes all cgminer changes up to 4.2.0 and forward after that up to:
https://github.com/ckolivas/cgminer/commit/cec48cee5f1759e5996de5339537fab4aeff416c

The previous report of having trouble with running the binary turned out to be caused by incorrectly specifying cgminer options.

Kano, awesome work again from you for the community. From reading your README, you can restart cgminer on the ant by doing:
/etc/init.d/cgminer stop
/etc/init.d/cgminer start

You can theoretically do it with /etc/init.d/cgminer restart but that sometimes doesn't start the miner, so I found it easier to manually stop and start it. Anyway it saves going into the web interface if you don't want to.

Code:

Syntax: /etc/init.d/cgminer [command]

Available commands:
        start   Start the service
        stop    Stop the service
        restart Restart the service
        reload  Reload configuration files (or restart if that fails)
        enable  Enable service autostart
        disable Disable service autostart

[winit]

I think I have named them all individually but no matter what string I use for --hfa-options I can't get it to load. Can you write me an example?

Thanks

Shall I quote the docs again?

--hfa-options <arg> Set hashfast options name:clock (comma separated)

This command allows you to set options for each discrete hashfast device by
its name (if the firmware has naming support, i.e. version 0.3+). Currently
this takes only one option, the clock speed, although future options may be
added.
e.g.:
--hfa-options "rabbit:650,turtle:550"

Fair enough mate I know it's failure on my part to understand and I do hugely appreciate your work and effort to support it.

I've tried the following:

--hfa-options "NS1:600,NS2:550"   -   No devices found
--hfa-options NS1:600,NS2:550   -   No devices found
--hfa-options clock "NS1:600,NS2:550"   -   No devices found
--hfa-options clock NS1:600,NS2:550   -   No devices found

I guess this either means I have not named the devices correctly or none of the strings I am entering are correct.

[-ck]

I've tried the following:
--hfa-options "NS1:600,NS2:550"   -   No devices found

This would be the correct set of options (as per the readme example I gave you). However it has no bearing on whether cgminer finds devices or not, it just tells cgminer what to set NS1 and NS2 clockspeeds to. If you're not finding devices, you are having other problems.

[zuqka]

Hi, Since sushi nor bitmain are of no help was wondering if you guys can help me out with one of my s1 that wont hash (usb 1-1: device descriptor read/64, error -71) at all. The system log:

Code:

Thu Jan  1 01:00:11 1970 kern.notice kernel: [    0.700000] 0x000000000000-0x000000020000 : "u-boot"
Thu Jan  1 01:00:11 1970 kern.notice kernel: [    0.700000] 0x000000020000-0x000000117d84 : "kernel"
Thu Jan  1 01:00:11 1970 kern.warn kernel: [    0.710000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Thu Jan  1 01:00:11 1970 kern.notice kernel: [    0.720000] 0x000000117d84-0x0000007f0000 : "rootfs"
Thu Jan  1 01:00:11 1970 kern.warn kernel: [    0.730000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Thu Jan  1 01:00:11 1970 kern.notice kernel: [    0.740000] mtd: partition "rootfs" set to be root filesystem
Thu Jan  1 01:00:11 1970 kern.info kernel: [    0.740000] mtd: partition "rootfs_data" created automatically, ofs=0x370000, len=0x480000
Thu Jan  1 01:00:11 1970 kern.notice kernel: [    0.750000] 0x000000370000-0x0000007f0000 : "rootfs_data"
Thu Jan  1 01:00:11 1970 kern.notice kernel: [    0.760000] 0x000000020000-0x0000007f0000 : "firmware"
Thu Jan  1 01:00:11 1970 kern.notice kernel: [    0.770000] 0x0000007f0000-0x000000800000 : "art"
Thu Jan  1 01:00:11 1970 kern.info kernel: [    0.790000] libphy: ag71xx_mdio: probed
Thu Jan  1 01:00:11 1970 kern.info kernel: [    0.790000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
Thu Jan  1 01:00:11 1970 kern.info kernel: [    1.340000] eth0: Found an AR7240/AR9330 built-in switch
Thu Jan  1 01:00:11 1970 kern.info kernel: [    2.380000] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
Thu Jan  1 01:00:11 1970 kern.info kernel: [    2.930000] ag71xx ag71xx.0 eth1: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
Thu Jan  1 01:00:11 1970 kern.info kernel: [    2.940000] TCP: cubic registered
Thu Jan  1 01:00:11 1970 kern.info kernel: [    2.940000] NET: Registered protocol family 17
Thu Jan  1 01:00:11 1970 kern.info kernel: [    2.950000] 8021q: 802.1Q VLAN Support v1.8
Thu Jan  1 01:00:11 1970 kern.info kernel: [    2.960000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Thu Jan  1 01:00:11 1970 kern.info kernel: [    2.970000] Freeing unused kernel memory: 232K (80316000 - 80350000)
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.800000] usbcore: registered new interface driver usbfs
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.800000] usbcore: registered new interface driver hub
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.810000] usbcore: registered new device driver usb
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.810000] usbcore: registered new interface driver bitmain
Thu Jan  1 01:00:11 1970 kern.warn kernel: [    5.820000] hash ok
Thu Jan  1 01:00:11 1970 kern.warn kernel: [    5.820000] hashtest OK
Thu Jan  1 01:00:11 1970 kern.err kernel: [    5.820000] bitmain-asic: success to register device
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.830000] usbcore: registered new interface driver bitmainbl
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.840000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.850000] ehci-platform: EHCI generic platform driver
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.850000] ehci-platform ehci-platform: EHCI Host Controller
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.860000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.860000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.890000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.890000] hub 1-0:1.0: USB hub found
Thu Jan  1 01:00:11 1970 kern.info kernel: [    5.890000] hub 1-0:1.0: 1 port detected
Thu Jan  1 01:00:11 1970 kern.info kernel: [    6.230000] usb 1-1: new full-speed USB device number 2 using ehci-platform
Thu Jan  1 01:00:11 1970 kern.err kernel: [    6.450000] usb 1-1: device descriptor read/64, error -71
Thu Jan  1 01:00:11 1970 kern.err kernel: [    6.770000] usb 1-1: device descriptor read/64, error -71
Thu Jan  1 01:00:11 1970 kern.info kernel: [    7.000000] usb 1-1: new full-speed USB device number 3 using ehci-platform
Thu Jan  1 01:00:11 1970 kern.err kernel: [    7.220000] usb 1-1: device descriptor read/64, error -71
Thu Jan  1 01:00:11 1970 kern.err kernel: [    7.540000] usb 1-1: device descriptor read/64, error -71
Thu Jan  1 01:00:11 1970 kern.info kernel: [    7.770000] usb 1-1: new full-speed USB device number 4 using ehci-platform
Thu Jan  1 01:00:11 1970 kern.err kernel: [    8.250000] usb 1-1: device not accepting address 4, error -71
Thu Jan  1 01:00:11 1970 kern.info kernel: [    8.370000] usb 1-1: new full-speed USB device number 5 using ehci-platform
Thu Jan  1 01:00:11 1970 kern.err kernel: [    8.850000] usb 1-1: device not accepting address 5, error -71
Thu Jan  1 01:00:11 1970 kern.err kernel: [    8.850000] hub 1-0:1.0: unable to enumerate USB device on port 1
Thu Jan  1 01:00:11 1970 kern.notice kernel: [   10.560000] jffs2: notice: (321) jffs2_build_xattr_subsystem: complete building xattr subsystem, 25 of xdatum (1 unchecked, 24 orphan) and 39 of xref (0 dead, 25 orphan) found.
Tue Mar 25 11:36:00 2014 daemon.info sysinit: Tue Mar 25 10:36:00 UTC 2014
Tue Mar 25 11:36:00 2014 user.emerg syslog: kmodloader: loading kernel modules from /etc/modules.d/**
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.790000] hidraw: raw HID events driver (C) Jiri Kosina
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.790000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.800000] Backport generated by backports.git backports-20130617-4-ge3220f5
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.810000] nf_conntrack version 0.5.0 (962 buckets, 3848 max)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.840000] usbcore: registered new interface driver usbhid
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.840000] usbhid: USB HID core driver
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.850000] usbcore: registered new interface driver usbserial
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.860000] usbcore: registered new interface driver usbserial_generic
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.860000] usbserial: USB Serial support registered for generic
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.890000] xt_time: kernel timezone is -0000
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.930000] cfg80211: Calling CRDA to update world regulatory domain
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.930000] cfg80211: World regulatory domain updated:
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.940000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.950000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.950000] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.960000] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.970000] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.980000] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   12.990000] ip_tables: (C) 2000-2006 Netfilter Core Team
Tue Mar 25 11:36:00 2014 kern.debug kernel: [   13.110000] ath: EEPROM regdomain: 0x0
Tue Mar 25 11:36:00 2014 kern.debug kernel: [   13.110000] ath: EEPROM indicates default country code should be used
Tue Mar 25 11:36:00 2014 kern.debug kernel: [   13.110000] ath: doing EEPROM country->regdmn map search
Tue Mar 25 11:36:00 2014 kern.debug kernel: [   13.110000] ath: country maps to regdmn code: 0x3a
Tue Mar 25 11:36:00 2014 kern.debug kernel: [   13.110000] ath: Country alpha2 being used: US
Tue Mar 25 11:36:00 2014 kern.debug kernel: [   13.110000] ath: Regpair used: 0x3a
Tue Mar 25 11:36:00 2014 kern.debug kernel: [   13.130000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Tue Mar 25 11:36:00 2014 kern.info kernel: [   13.130000] cfg80211: Calling CRDA for country: US
Tue Mar 25 11:36:00 2014 user.info syslog: ran 16 iterations
Tue Mar 25 11:36:00 2014 kern.info kernel: [   13.140000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
Tue Mar 25 11:36:00 2014 kern.info kernel: [   13.150000] cfg80211: Regulatory domain changed to country: US
Tue Mar 25 11:36:00 2014 kern.info kernel: [   13.160000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   13.160000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   13.170000] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   13.180000] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   13.190000] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   13.200000] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Tue Mar 25 11:36:00 2014 kern.info kernel: [   13.200000] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Tue Mar 25 11:36:00 2014 daemon.info sysinit: kmod: ran 16 iterations
Tue Mar 25 11:36:04 2014 cron.info crond[564]: crond: crond (busybox 1.19.4) started, log level 8
Tue Mar 25 11:36:05 2014 daemon.notice netifd: Interface 'loopback' is now up
Tue Mar 25 11:36:05 2014 kern.info kernel: [   17.970000] device eth0 entered promiscuous mode
Tue Mar 25 11:36:05 2014 authpriv.info dropbear[575]: Not backgrounding
Tue Mar 25 11:36:05 2014 daemon.notice netifd: Interface 'wan' is now up
Tue Mar 25 11:36:06 2014 daemon.notice netifd: lan (612): udhcpc (v1.19.4) started
Tue Mar 25 11:36:06 2014 daemon.notice netifd: lan (612): Sending discover...
Tue Mar 25 11:36:06 2014 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Tue Mar 25 11:36:07 2014 kern.info kernel: [   20.140000] eth1: link up (100Mbps/Full duplex)
Tue Mar 25 11:36:08 2014 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Tue Mar 25 11:36:08 2014 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Tue Mar 25 11:36:08 2014 daemon.info sysinit: /etc/config/miner_pic.hex
Tue Mar 25 11:36:08 2014 daemon.info dnsmasq[683]: started, version 2.66 cachesize 150
Tue Mar 25 11:36:08 2014 daemon.info dnsmasq[683]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Tue Mar 25 11:36:08 2014 daemon.info dnsmasq[683]: using local addresses only for domain lan
Tue Mar 25 11:36:08 2014 daemon.info dnsmasq[683]: reading /tmp/resolv.conf.auto
Tue Mar 25 11:36:08 2014 daemon.info dnsmasq[683]: using nameserver 8.8.8.8#53
Tue Mar 25 11:36:08 2014 daemon.info dnsmasq[683]: using local addresses only for domain lan
Tue Mar 25 11:36:08 2014 daemon.info dnsmasq[683]: read /etc/hosts - 1 addresses
Tue Mar 25 11:36:08 2014 daemon.info sysinit: Unable to open /dev/bitmainbl0: No such file or directory
Tue Mar 25 11:36:08 2014 daemon.info sysinit: pic update
Tue Mar 25 11:36:08 2014 daemon.info sysinit: setting up led WAN
Tue Mar 25 11:36:08 2014 daemon.info sysinit: setting up led WANL
Tue Mar 25 11:36:08 2014 daemon.info sysinit: setting up led LAN1
Tue Mar 25 11:36:08 2014 daemon.info sysinit: setting up led LAN2
Tue Mar 25 11:36:08 2014 daemon.info sysinit: setting up led LAN3
Tue Mar 25 11:36:08 2014 daemon.info sysinit: setting up led LAN4
Tue Mar 25 11:36:08 2014 daemon.info sysinit: setting up led WLAN
Tue Mar 25 11:36:09 2014 daemon.notice netifd: lan (612): Sending discover...
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 87.237.200.242
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: sent query to 87.237.200.242
Tue Mar 25 11:36:12 2014 daemon.notice netifd: lan (612): Sending discover...
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 217.24.24.144
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: sent query to 217.24.24.144
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 97.107.128.58
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: sent query to 97.107.128.58
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 193.243.171.130
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: sent query to 193.243.171.130
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: reply from 87.237.200.242: reach 0x01 offset 38.838805 delay 0.388920 status 0x24 strat 4 refid 0x55d6d697 rootdelay 0.021424
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: reply from 217.24.24.144: reach 0x01 offset 38.906873 delay 0.256149 status 0x24 strat 4 refid 0x3e70c338 rootdelay 0.019516
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: reply from 97.107.128.58: reach 0x01 offset 39.015995 delay 0.150724 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.001419
Tue Mar 25 11:36:12 2014 daemon.info sysinit: ntpd: reply from 193.243.171.130: reach 0x01 offset 39.022949 delay 0.033117 status 0x24 strat 2 refid 0xc1ab17a3 rootdelay 0.017762
Tue Mar 25 11:36:13 2014 daemon.info sysinit: ntpd: sent query to 87.237.200.242
Tue Mar 25 11:36:13 2014 daemon.info sysinit: ntpd: sent query to 97.107.128.58
Tue Mar 25 11:36:13 2014 daemon.info sysinit: ntpd: sent query to 193.243.171.130
Tue Mar 25 11:36:13 2014 daemon.info sysinit: ntpd: reply from 193.243.171.130: reach 0x03 offset 39.018669 delay 0.023381 status 0x24 strat 2 refid 0xc1ab17a3 rootdelay 0.017762
Tue Mar 25 11:36:13 2014 daemon.info sysinit: ntpd: reply from 87.237.200.242: reach 0x03 offset 39.018608 delay 0.029348 status 0x24 strat 4 refid 0x55d6d697 rootdelay 0.021424
Tue Mar 25 11:36:13 2014 daemon.info sysinit: ntpd: reply from 97.107.128.58: reach 0x03 offset 39.015600 delay 0.148017 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.001419
Tue Mar 25 11:36:14 2014 daemon.info sysinit: ntpd: sent query to 87.237.200.242
Tue Mar 25 11:36:14 2014 daemon.info sysinit: ntpd: sent query to 217.24.24.144
Tue Mar 25 11:36:14 2014 daemon.info sysinit: ntpd: sent query to 97.107.128.58
Tue Mar 25 11:36:14 2014 daemon.info sysinit: ntpd: sent query to 193.243.171.130
Tue Mar 25 11:36:14 2014 daemon.info sysinit: ntpd: reply from 193.243.171.130: reach 0x07 offset 39.032441 delay 0.051831 status 0x24 strat 2 refid 0xc1ab17a3 rootdelay 0.017762
Tue Mar 25 11:36:14 2014 daemon.info sysinit: ntpd: reply from 217.24.24.144: reach 0x03 offset 39.033468 delay 0.053010 status 0x24 strat 4 refid 0x3e70c338 rootdelay 0.019516
Tue Mar 25 11:36:14 2014 daemon.info sysinit: ntpd: reply from 87.237.200.242: reach 0x07 offset 39.032897 delay 0.057734 status 0x24 strat 4 refid 0x55d6d697 rootdelay 0.021424
Tue Mar 25 11:36:15 2014 daemon.info sysinit: ntpd: reply from 97.107.128.58: reach 0x07 offset 39.029740 delay 0.177015 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.001419
Tue Mar 25 11:36:16 2014 daemon.info sysinit: ntpd: sent query to 87.237.200.242
Tue Mar 25 11:36:16 2014 daemon.info sysinit: ntpd: reply from 87.237.200.242: reach 0x0f offset 39.025957 delay 0.043324 status 0x24 strat 4 refid 0x55d6d697 rootdelay 0.021424
Tue Mar 25 11:36:17 2014 daemon.info sysinit: ntpd: sent query to 87.237.200.242
Tue Mar 25 11:36:17 2014 daemon.info sysinit: ntpd: sent query to 217.24.24.144
Tue Mar 25 11:36:17 2014 daemon.info sysinit: ntpd: sent query to 97.107.128.58
Tue Mar 25 11:36:17 2014 daemon.info sysinit: ntpd: sent query to 193.243.171.130
Tue Mar 25 11:36:17 2014 daemon.info sysinit: ntpd: reply from 193.243.171.130: reach 0x0f offset 39.019741 delay 0.026479 status 0x24 strat 2 refid 0xc1ab17a3 rootdelay 0.017762
Tue Mar 25 11:36:17 2014 daemon.info sysinit: ntpd: reply from 217.24.24.144: reach 0x07 offset 39.020825 delay 0.028014 status 0x24 strat 4 refid 0x3e70c338 rootdelay 0.019516
Tue Mar 25 11:36:17 2014 daemon.info sysinit: ntpd: reply from 87.237.200.242: reach 0x1f offset 39.020250 delay 0.032000 status 0x24 strat 4 refid 0x55d6d697 rootdelay 0.021424
Tue Mar 25 11:36:17 2014 daemon.info sysinit: ntpd: reply from 97.107.128.58: reach 0x0f offset 39.017030 delay 0.151643 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.001419
Tue Mar 25 11:36:18 2014 daemon.info sysinit: ntpd: sent query to 87.237.200.242
Tue Mar 25 11:36:18 2014 daemon.info sysinit: ntpd: sent query to 217.24.24.144
Tue Mar 25 11:36:18 2014 daemon.info sysinit: ntpd: reply from 217.24.24.144: reach 0x0f offset 39.021930 delay 0.029886 status 0x24 strat 4 refid 0x3e70c338 rootdelay 0.019516
Tue Mar 25 11:36:18 2014 daemon.info sysinit: ntpd: reply from 87.237.200.242: reach 0x3f offset 39.021374 delay 0.034576 status 0x24 strat 4 refid 0x55d6d697 rootdelay 0.021424
Tue Mar 25 11:36:19 2014 daemon.info sysinit: ntpd: sent query to 97.107.128.58
Tue Mar 25 11:36:19 2014 daemon.info sysinit: ntpd: sent query to 193.243.171.130
Tue Mar 25 11:36:58 2014 daemon.info sysinit: ntpd: reply from 193.243.171.130: reach 0x1f offset 39.021412 delay 0.028603 status 0x24 strat 2 refid 0xc1ab17a3 rootdelay 0.017762
Tue Mar 25 11:36:58 2014 daemon.info sysinit: ntpd: setting clock to Tue Mar 25 11:36:58 CET 2014 (offset 39.010082s)
Tue Mar 25 11:36:58 2014 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o http://us-vip-stratum.btcguild.com:3333 -O zuqka_5:123 -o http://stratum.mining.eligius.st:3334 -O 19U...:123 -o http://stratum.bitcoin.cz:3333 -O ... --api-listen --api-network
Tue Mar 25 11:36:58 2014 daemon.info sysinit: - init complete -
Tue Mar 25 11:39:01 2014 cron.info crond[564]: crond: USER root pid 1037 cmd /usr/bin/cgminer-monitor
Tue Mar 25 11:39:10 2014 authpriv.info dropbear[1084]: Child connection from 192.168.0.18:63291
Tue Mar 25 11:39:17 2014 authpriv.notice dropbear[1084]: Password auth succeeded for 'root' from 192.168.0.18:63291
Tue Mar 25 11:42:01 2014 cron.info crond[564]: crond: USER root pid 1462 cmd /usr/bin/cgminer-monitor

MODERATOR EDIT: Put log into code tags

[kano]

Kano, awesome work again from you for the community. From reading your README, you can restart cgminer on the ant by doing:
/etc/init.d/cgminer stop
/etc/init.d/cgminer start

You can theoretically do it with /etc/init.d/cgminer restart but that sometimes doesn't start the miner, so I found it easier to manually stop and start it. Anyway it saves going into the web interface if you don't want to.

Code:

Syntax: /etc/init.d/cgminer [command]

Available commands:
        start   Start the service
        stop    Stop the service
        restart Restart the service
        reload  Reload configuration files (or restart if that fails)
        enable  Enable service autostart
        disable Disable service autostart

Bitmain was unable to write the /etc/init.d/cgminer properly so it doesn't always work

I've edited my /etc/init.d/cgminer to fix the problem, but if you look in yours you will find it starts cgminer twice:

1) $APP --lowmem --bitmain-options 115200:32:8:$_T0:$_cf:$_regv -q >/dev/null 2>&1

and again lower down correctly after the first one exits:

2) start-stop-daemon -S -x $APP -p $PID_FILE -m -b -- $PARAMS -q

[kano]

Hi, Since sushi nor bitmain are of no help was wondering if you guys can help me out with one of my s1 that wont hash (usb 1-1: device descriptor read/64, error -71) at all. The system log:
...

That log shows normal as far as I can tell.

Maybe "dmesg" would help you more?

Without knowing too much about it, it (-71) sounds like a hardware problem, since it shouldn't be getting that error.

[zuqka]

Hi, Since sushi nor bitmain are of no help was wondering if you guys can help me out with one of my s1 that wont hash (usb 1-1: device descriptor read/64, error -71) at all. The system log:
...

That log shows normal as far as I can tell.

Maybe "dmesg" would help you more?

Without knowing too much about it, it (-71) sounds like a hardware problem, since it shouldn't be getting that error.

I assume that the control board is faulty. Done switching wires, tried diff. PSU's and all firmwares available
Sorry for my noob question but what is dmesg?

[kano]

Hi, Since sushi nor bitmain are of no help was wondering if you guys can help me out with one of my s1 that wont hash (usb 1-1: device descriptor read/64, error -71) at all. The system log:
...

That log shows normal as far as I can tell.

Maybe "dmesg" would help you more?

Without knowing too much about it, it (-71) sounds like a hardware problem, since it shouldn't be getting that error.

I assume that the control board is faulty. Done switching wires, tried diff. PSU's and all firmwares available
Sorry for my noob question but what is dmesg?

When logged in, type dmesg

[zuqka]

Code:

[  211.480000] usb 1-1: clear tt 1 (9041) error -71
[  211.490000] usb 1-1: clear tt 1 (9041) error -71
[  211.500000] usb 1-1: clear tt 1 (9041) error -71
[  211.510000] usb 1-1: clear tt 1 (9041) error -71
[  211.520000] usb 1-1: clear tt 1 (9041) error -71
[  211.530000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.540000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.540000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.560000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.560000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.570000] hub 1-1:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
[  211.590000] hub 1-1:1.0: cannot disable port 1 (err = -71)
[  211.590000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.610000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.610000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.630000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.630000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.640000] hub 1-1:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
[  211.650000] hub 1-1:1.0: cannot disable port 1 (err = -71)
[  211.660000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.680000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.680000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.700000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.700000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.710000] hub 1-1:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
[  211.720000] hub 1-1:1.0: cannot disable port 1 (err = -71)
[  211.730000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.730000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.750000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.750000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.770000] hub 1-1:1.0: cannot reset port 1 (err = -71)
[  211.770000] hub 1-1:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
[  211.790000] hub 1-1:1.0: cannot disable port 1 (err = -71)
[  211.790000] hub 1-1:1.0: cannot disable port 1 (err = -71)
[  211.800000] hub 1-1:1.0: hub_port_status failed (err = -71)

[zuqka]

Well if I disconnect the power and re-connect after 10-15min it runs normally for 5-10min and then the it brakes down. Am clueless

[loshia]

PS:

Guy's
What about
   cg_wlock(&control_lock);
   .....local_work++;
   .....total_work++;
   cg_wunlock(&control_lock);
I think there is a need to lock them everywhere or ?

Thanks

Mostly harmless, but probably wouldn't hurt to protect them with the write lock for when mining at multiple different types of pools at once (eg GBT + stratum), yes, thanks.

Super,
If you can add local_work++ inside total_work_inc will be great 

[BoogieMan82]

Thanks for the information, this is what it looks like now (I still wish the values were doubled though)!

Has anyone tried to bump these u2 miners up.  2.0GH is the start speed so I'd hope we'd get close to 2.5 or 2.6GH

Size being a secondary issue it took a long while for cgminer to see it . I have in total 8 of a combination of u1's and 2's but I only showed 7 till I restarted. I'm still having troubles where the u2 device's lights wont go on or the way I expect them. The one I thought I would need to return is working properly and the one I didn'ts lights don't come on when I shut down cgminer.

These u2's are picky buggers  but it may just be they are different enough to cause me migranes

AMU of 258.3 (2.1GH) is the best I can get out of mine (unless I decide to modify the resistors) or else I get a bunch of HW errors.

[zamot]

Here's another new AntS1 binary.

An endian issue was found in the solo code for the ant (no issue for desktop computers), so this update includes the fix for that.
I've removed both old AntS1 binaries

This uses the same patch as before for the luci display.
My source for this version is here:
https://github.com/kanoi/cgminer/tree/ants1-4.2.0-00567a4

The binary and README are in my cgminer-binaries git here:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1  <-- Follow this link to get the new binary

Read the README on the screen there for how to replace the /usr/bin/cgminer binary in your AntS1 with the new one.

This binary includes all cgminer changes up to 4.2.0 and forward after that up to:
https://github.com/ckolivas/cgminer/commit/cec48cee5f1759e5996de5339537fab4aeff416c

The previous report of having trouble with running the binary turned out to be caused by incorrectly specifying cgminer options.

Kano, there is an minor "optical bug" in miner status displaying LSTime. It does not display actual difference since last time the pool was contacted. Instead displays times remaining since some distant past - i think since 01-01-1970

[-ck]

PS:

Guy's
What about
   cg_wlock(&control_lock);
   .....local_work++;
   .....total_work++;
   cg_wunlock(&control_lock);
I think there is a need to lock them everywhere or ?

Thanks

Mostly harmless, but probably wouldn't hurt to protect them with the write lock for when mining at multiple different types of pools at once (eg GBT + stratum), yes, thanks.

Super,
If you can add local_work++ inside total_work_inc will be great 

That's a purely cosmetic number and adding locking for it does not protect anything of any value.

[kano]

...
Kano, there is an minor "optical bug" in miner status displaying LSTime. It does not display actual difference since last time the pool was contacted. Instead displays times remaining since some distant past - i think since 01-01-1970

I've mentioned this before.

The problem is that bitmain changed the content of the API field.
So from a cgminer point of view, there is no fix.
What they changed in their fork was: instead of providing a unix time stamp like 1395777236, which cgminer did, still does, and forever will, they now send out a string like "10:05:23" meaning a bit over 10 minutes in the past.

Of course I will not change the API to break all code that uses LSTime.
The only fix that doesn't break cgminer is to revert the antminer code that displays the web page.

Artpego posted an antminer luci fix (revert) about 2 pages back:
https://bitcointalk.org/index.php?topic=28402.msg5852062#msg5852062

[kano]

Well if I disconnect the power and re-connect after 10-15min it runs normally for 5-10min and then the it brakes down. Am clueless

It sounds like a hardware problem - but since it is all custom hardware, it's most likely a bitmain hardware issue for them to fix, since we know the software works under normal conditions for literally 10 of thousands of antminers.