<<  >> (p.29)
    Author Topic: [Guide] Dogie's Comprehensive Bitmain Antminer S3 Setup [HD]  (Read 137953 times)

    • notlist3d
    Legendary
    *
    Offline Offline

    Activity: 1456
    Merit: 1000



    View Profile
    March 23, 2016, 03:11:18 AM
     #561
    Quote from: Hojo82 on March 22, 2016, 08:51:03 PM
    Hi I have been trying to set up my antminer s3 with a wireless bridge because I don't have access to a direct ethernet cord into the router. So pretty much I'm connecting the bridge via Wi-Fi to my wireless network and then plugging the antminer directly into the bridge. Is there anything special I need to do to make this work? Is it even possible to do it this way? I'm thinking it is... But I'm not sure if I'm missing something because I can't get it to work. What are the setup steps for doing this?

    When you say " I don't have access to a direct ethernet cord into the router." Do you have temporary access to make changes on S3? Or no access at all?

    Also it would depend on your wireless bridge settings.  But your normally can't go wrong with DHCP on most wireless bridges.   I personally like static if you can get a chance in same IP pool.

  • Mikestang
    Legendary
    *
    Offline Offline

    Activity: 1274
    Merit: 1001



    View Profile
    March 23, 2016, 03:31:42 AM
     #562
    Quote from: Darwin84 on March 22, 2016, 11:55:22 PM
    Change home router to 192.168.1.1
    It is much simpler to change the IP address on one of your computers to 192.168.1.x to then be able to access the antminer rather than changing your router and possibly f'ing up your whole home network.

  • notabeliever
    Hero Member
    *****
    Offline Offline

    Activity: 728
    Merit: 504


    View Profile
    March 24, 2016, 02:37:41 AM
     #563
    I bought 2 used S3's and plugged them in, they immediately started running. Easily changed the pools and man these are super quiet and run better than my s5

  • Darwin84
    Full Member
    ***
    Offline Offline

    Activity: 196
    Merit: 100


    View Profile
    March 25, 2016, 09:08:34 PM
     #564
    Quote from: Mikestang on March 23, 2016, 03:31:42 AM
    Quote from: Darwin84 on March 22, 2016, 11:55:22 PM
    Change home router to 192.168.1.1
    It is much simpler to change the IP address on one of your computers to 192.168.1.x to then be able to access the antminer rather than changing your router and possibly f'ing up your whole home network.

    yes but don't you see he's cableless. and not really any different. they both require one simple change.

  • leowonderful
    Legendary
    *
    Offline Offline

    Activity: 1624
    Merit: 1130


    Bitcoin FTW!


    View Profile
    March 26, 2016, 12:22:27 AM
     #565
    Quote from: notabeliever on March 24, 2016, 02:37:41 AM
    I bought 2 used S3's and plugged them in, they immediately started running. Easily changed the pools and man these are super quiet and run better than my s5
    S3s and S1s are the sweet spot for most home miners, it's not surprising that people like us choose these miners for low noise over power consumption. Because for hobby miners, you'll probably like to keep boise levels down. I run my S3s next to my gaming rig and it's quiet enough to not disturb my mic when i'm playing CS:GO, but S5s I keep in the basement. 2loud5me Cheesy

  • MikeMike
    Legendary
    *
    Offline Offline

    Activity: 2254
    Merit: 1020


    ★ Ⓚ KORE TEAM Ⓚ ★


    View Profile
    April 23, 2016, 01:09:36 AM
     #566
    Hiya,

    Has anyone had good results underclocking the S3?
    I have a bunch not mining for a year and a half and wondering if better to underclock them rather than sell them.

    MM

  • toptek
    Legendary
    *
    Offline Offline

    Activity: 1274
    Merit: 1000


    View Profile
    April 23, 2016, 01:14:39 AM
     #567
    I have and run it for 6 month one time at max over clock with out issue and sold it a few months after that im told by that buyer it still runs great i wish i had keep it . The one i have now i over clock to much with kano update for CGminer that unlocks the over clocking limits in the GUI and Burt out a chip .

    S3 were and still are that good just outdated  !! S1 were to but i don't run my S1 anymore it just sets for parts and i hope some nice bitfury boards one day .


    OPs you said under clocking my bad 

    cya
    For security, your account has been locked. Email acctcomp15@theymos.e4ward.com

  • notlist3d
    Legendary
    *
    Offline Offline

    Activity: 1456
    Merit: 1000



    View Profile
    April 23, 2016, 01:51:05 AM
     #568
    Quote from: toptek on April 23, 2016, 01:14:39 AM
    I have and run it for 6 month one time at max over clock with out issue and sold it a few months after that im told by that buyer it still runs great i wish i had keep it . The one i have now i over clock to much with kano update for CGminer that unlocks the over clocking limits in the GUI and Burt out a chip .

    S3 were and still are that good just outdated  !! S1 were to but i don't run my S1 anymore it just sets for parts and i hope some nice bitfury boards one day .


    OPs you said under clocking my bad 

    cya

    Each S3 had it's own personality.  Even from same batch same everything some did better then others.  Only way to find out is try it... see results.  You will find some overclock well other's do not.

    Also batch 1 was the worst off any of them. If you have S3+ you know you don't have one, but batch 1 was so bad everyone got partial refund.   They just did not hit spec and did not OC well on some.

    So all depends on the unit.  You will have to test to know.

  • usukan
    Legendary
    *
    Offline Offline

    Activity: 1590
    Merit: 1002



    View Profile
    October 17, 2016, 06:49:44 AM
     #569
    absolutely - s3's are like children - each one quite different but from same parents

    Glad all mine are gone
    --


    --

  • bitgwapo
    Newbie
    *
    Offline Offline

    Activity: 27
    Merit: 0


    View Profile
    December 05, 2016, 02:59:13 AM
     #570
    good day guys.. my antminer s3++ stops hashing after 1hr at 200m frequency, the other side of hashing board is dead so it runs around at 200 +-10 Ghs, i tried to reduce to 196m frequency then it started hashing stably but at minimum speed of 100Ghs - 130Ghs...  i know its already broken half but maybe anyone of you guys have an idea whats wrong with this? thank you guys.  Smiley

  • usukan
    Legendary
    *
    Offline Offline

    Activity: 1590
    Merit: 1002



    View Profile
    January 31, 2017, 07:54:08 AM
     #571
    You all should have sold S3's a long time ago
    --


    --

  • kikkelosada
    Newbie
    *
    Offline Offline

    Activity: 2
    Merit: 0


    View Profile
    December 10, 2017, 11:00:52 PM
     #572
    Quote from: Darwin84 on February 26, 2016, 07:42:52 PM
    Quote from: welshy82 on February 26, 2016, 04:06:39 PM
    sorted not sure how i did it took me 2 hrs to sort with a laptop lol

    You lost the IP or interface so just reset it ..

    There is a little pin hole in the back by the ethernet port.  Put a toothpick in there and hold for 5 seconds and release. Wait about 3-4 minutes to reboot, after reboot power down the power supply and reboot one more time. After it comes back up you will see it on the default IP which is 192.168.1.99

    Some people needed to do this process twice but it always worked for me on the first shot.

    OK. I bough a used S3, finally I had the time to get it power up, could not find the IP address, I did the reset button and never got it reset to default 192.168.1.99
     
    I held it for 5 sec. while power on and continue after power off for 5 sec. and same for 10, and 30 seconds and power on and off like any other router type equipment.
    (if I did something wrong or if there is a special sequence please let me know) I would love to set this miner to all factory settings

    I finally bough out an old router and set it up 192.168.1.1 and laptop in one port and Antminer in another port - no internet wifi on , used an app on my phone to scan all IPs on the network and found it at (Static IP) 192.168.1.127 - finally log in and change settings - using DHCP to my own network 192.168.0.xxx

    Got it to start mining and I logged back in and set it to Static IP 192.168.0.95 and after save and restart I can't log in
    network settings
    gateway 192.168.0.1
    submask 255.255.255.0
    DNS 192.168.0.1 8.8.8.8
    broadcast 192.168.0.255
    router is telling me that it is at 192.168.0.95 . S3 is mining but I can SSH in or login through web interface

    I unsure that the reset button works . all previous owner information was on the miner when I finally found the IP addresses and logged in

    any help would be greatly appreciated

  • DKirk
    Newbie
    *
    Offline Offline

    Activity: 61
    Merit: 0


    View Profile
    December 10, 2017, 11:24:22 PM
     #573
    Log back in like you did the first time since it is back on static IP (I think) and enable "DHCP client" under NETWORK>INTERFACES>WAN(edit)>PROTOCOL. Did that for an old S3+ and haven't had an issue with it reverting back to static ever. No reason in my opinion to not be in DHCP for the average person, or at least not that I am aware of.

  • mayitzu
    Newbie
    *
    Offline Offline

    Activity: 5
    Merit: 0


    View Profile
    December 11, 2017, 01:31:46 PM
     #574
    KikkeLosada,

    You could have just connected a network cable from your laptop directly to the Ant Miner and made the IP on the laptop to match the network of the miner. Anyway, you've gotten past this already...
    I recommend you review the settings on your new miner and update with your Bitcoin Address AS SOON AS POSSIBLE, otherwise you may be still mining for the previous owner.
    I recommend youtube. You can find detailed step-by-step videos on how to set up and even overclock your miner if you want to.
    Cheers,

    MA

  • joktel
    Newbie
    *
    Offline Offline

    Activity: 20
    Merit: 0


    View Profile
    January 28, 2018, 01:01:33 PM
    Last edit: January 28, 2018, 07:29:16 PM by frodocooper
     #575
    I just bought a used S3 antminer to learn mining. The box got to me with a broken part. But the seller told me it does not matter that it will still work fine. So I started the S3 and it really worked, but only mined for the previous owner. After changing the miner configuration to my own data the miner stopped mining.
    I have read alots of suggestion in the forum but could not fix the miner to work for me, but I AM STILL LOST... NO SOLUTION...
    Can this be a problem from the broken part during the shipment? There is a small cylinder-like object, see picture below, SORRY FOR MY LAYMAN EXPLANATION
    What is the use of this part and can the S3 work without the part?
    https://drive.google.com/open?id=1vRRzUM84r7hgNpSyDgzeYeGk7CxSjAFy


    here is the system log file: any useful hint here on what is happening with my S3.

    Code:
    Sun Jan 28 20:08:00 2018 daemon.info sysinit: Sun Jan 28 12:08:00 UTC 2018
    Sun Jan 28 20:08:00 2018 user.emerg syslog: kmodloader: loading kernel modules frometc/modules.d/**
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.040000] hidraw: raw HID events driver (C) Jiri Kosina
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.050000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.050000] Backport generated by backports.git backports-20130617-4-ge3220f5
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.070000] nf_conntrack version 0.5.0 (962 buckets, 3848 max)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.090000] usbcore: registered new interface driver usbhid
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.100000] usbhid: USB HID core driver
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.110000] usbcore: registered new interface driver usbserial
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.110000] usbcore: registered new interface driver usbserial_generic
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.120000] usbserial: USB Serial support registered for generic
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.150000] xt_time: kernel timezone is -0000
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.180000] cfg80211: Calling CRDA to update world regulatory domain
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.180000] cfg80211: World regulatory domain updated:
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.190000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.190000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.200000] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.210000] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.220000] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.220000] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.240000] ip_tables: (C) 2000-2006 Netfilter Core Team
    Sun Jan 28 20:08:00 2018 kern.debug kernel: [   13.380000] ath: EEPROM regdomain: 0x0
    Sun Jan 28 20:08:00 2018 kern.debug kernel: [   13.380000] ath: EEPROM indicates default country code should be used
    Sun Jan 28 20:08:00 2018 kern.debug kernel: [   13.380000] ath: doing EEPROM country->regdmn map search
    Sun Jan 28 20:08:00 2018 kern.debug kernel: [   13.380000] ath: country maps to regdmn code: 0x3a
    Sun Jan 28 20:08:00 2018 kern.debug kernel: [   13.380000] ath: Country alpha2 being used: US
    Sun Jan 28 20:08:00 2018 kern.debug kernel: [   13.380000] ath: Regpair used: 0x3a
    Sun Jan 28 20:08:00 2018 kern.debug kernel: [   13.390000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.400000] cfg80211: Calling CRDA for country: US
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.400000] cfg80211: Regulatory domain changed to country: US
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.410000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.420000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.420000] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.430000] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.440000] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.450000] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.460000] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
    Sun Jan 28 20:08:00 2018 kern.info kernel: [   13.460000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
    Sun Jan 28 20:08:00 2018 user.info syslog: ran 16 iterations
    Sun Jan 28 20:08:00 2018 daemon.info sysinit: kmod: ran 16 iterations
    Sun Jan 28 20:08:05 2018 cron.info crond[575]: crond: crond (busybox 1.19.4) started, log level 8
    Sun Jan 28 20:08:05 2018 authpriv.info dropbear[586]: Not backgrounding
    Sun Jan 28 20:08:05 2018 daemon.notice netifd: Interface 'loopback' is now up
    Sun Jan 28 20:08:05 2018 kern.info kernel: [   18.450000] device eth0 entered promiscuous mode
    Sun Jan 28 20:08:06 2018 daemon.notice netifd: lan (630): udhcpc (v1.19.4) started
    Sun Jan 28 20:08:06 2018 daemon.notice netifd: wan (633): udhcpc (v1.19.4) started
    Sun Jan 28 20:08:06 2018 daemon.notice netifd: wan (633): Sending discover...
    Sun Jan 28 20:08:06 2018 daemon.notice netifd: lan (630): Sending discover...
    Sun Jan 28 20:08:08 2018 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
    Sun Jan 28 20:08:08 2018 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
    Sun Jan 28 20:08:08 2018 daemon.info dnsmasq[683]: started, version 2.66 cachesize 150
    Sun Jan 28 20:08:08 2018 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
    Sun Jan 28 20:08:08 2018 daemon.info dnsmasq[683]: using local addresses only for domain lan
    Sun Jan 28 20:08:08 2018 daemon.warn dnsmasq[683]: no servers found intmp/resolv.conf.auto, will retry
    Sun Jan 28 20:08:08 2018 daemon.info dnsmasq[683]: readetc/hosts - 1 addresses
    Sun Jan 28 20:08:08 2018 daemon.info sysinit:etc/config/miner_pic.hex
    Sun Jan 28 20:08:08 2018 kern.info kernel: [   21.430000] usb 1-1.1: USB disconnect, device number 3
    Sun Jan 28 20:08:08 2018 kern.info kernel: [   21.430000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
    Sun Jan 28 20:08:08 2018 kern.info kernel: [   21.690000] usb 1-1.1: new full-speed USB device number 4 using ehci-platform
    Sun Jan 28 20:08:09 2018 kern.info kernel: [   21.840000] bitmainbl 1-1.1:1.0: USB Bitmain bootloader device now attached to USB Bitmain bootloader-0
    Sun Jan 28 20:08:09 2018 kern.warn kernel: [   21.850000] PIC microchip bootloader usb OK
    Sun Jan 28 20:08:09 2018 daemon.notice netifd: wan (633): Sending discover...
    Sun Jan 28 20:08:09 2018 daemon.notice netifd: lan (630): Sending discover...
    Sun Jan 28 20:08:11 2018 kern.info kernel: [   24.050000] eth1: link up (100Mbps/Full duplex)
    Sun Jan 28 20:08:12 2018 daemon.notice netifd: wan (633): Sending discover...
    Sun Jan 28 20:08:12 2018 daemon.notice netifd: wan (633): Sending select for 192.168.0.XXX...
    Sun Jan 28 20:08:12 2018 daemon.notice netifd: lan (630): Sending discover...
    Sun Jan 28 20:08:13 2018 daemon.notice netifd: wan (633): Lease of 192.168.0.XXX obtained, lease time 86400
    Sun Jan 28 20:08:14 2018 daemon.notice netifd: Interface 'wan' is now up
    Sun Jan 28 20:08:14 2018 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
    Sun Jan 28 20:08:18 2018 kern.warn kernel: [   31.380000] no int in filled
    Sun Jan 28 20:08:18 2018 daemon.info sysinit: pic update
    Sun Jan 28 20:08:18 2018 daemon.info sysinit: opendev/bitmain0 to restart pic
    Sun Jan 28 20:08:18 2018 daemon.info sysinit: opendev/bitmainbl0 ok fd = 0x4
    Sun Jan 28 20:08:18 2018 daemon.info sysinit: read data
    Sun Jan 28 20:08:18 2018 daemon.info sysinit: [0]{0x1}, [1]{0x10}, [2]{0x1}, [3]{0x10}, [4]{0x1}, [5]{0}, [6]{0x10}, [7]{0x1}, [8]{0x10}, [9]{0x4}, [10]{0x4},
    Sun Jan 28 20:08:18 2018 daemon.info sysinit: Version 1.0
    Sun Jan 28 20:08:18 2018 daemon.info sysinit: open pic update file fail
    Sun Jan 28 20:08:18 2018 daemon.info sysinit: Control bootloader to app
    Sun Jan 28 20:08:19 2018 daemon.info sysinit: setting up led WAN
    Sun Jan 28 20:08:19 2018 daemon.info sysinit: setting up led WANL
    Sun Jan 28 20:08:19 2018 daemon.info sysinit: setting up led LAN1
    Sun Jan 28 20:08:19 2018 daemon.info sysinit: setting up led LAN2
    Sun Jan 28 20:08:19 2018 daemon.info sysinit: setting up led LAN3
    Sun Jan 28 20:08:19 2018 daemon.info sysinit: setting up led LAN4
    Sun Jan 28 20:08:19 2018 daemon.info sysinit: setting up led WLAN
    Sun Jan 28 20:08:19 2018 daemon.info dnsmasq[683]: readingtmp/resolv.conf.auto
    Sun Jan 28 20:08:19 2018 daemon.info dnsmasq[683]: using nameserver XX.XX.XX.XXX#53
    Sun Jan 28 20:08:19 2018 daemon.info dnsmasq[683]: using nameserver XX.XX.XX.XXX#53
    Sun Jan 28 20:08:19 2018 daemon.info dnsmasq[683]: using local addresses only for domain lan
    Sun Jan 28 20:08:19 2018 kern.info kernel: [   32.690000] usb 1-1.1: USB disconnect, device number 4
    Sun Jan 28 20:08:20 2018 kern.info kernel: [   32.770000] bitmainbl 1-1.1:1.0: USB Bitmain asic #0 now disconnected
    Sun Jan 28 20:08:20 2018 kern.info kernel: [   33.400000] usb 1-1.1: new full-speed USB device number 5 using ehci-platform
    Sun Jan 28 20:08:20 2018 kern.info kernel: [   33.540000] bitmain 1-1.1:1.0: USB Bitmain asic device now attached to USB Bitmain asic-0
    Sun Jan 28 20:08:20 2018 kern.warn kernel: [   33.540000] PIC microchip usb OK
    Sun Jan 28 20:08:21 2018 daemon.info sysinit: --bitmain-options 115200:32:8:18:225:0882 --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --bitmain-voltage 0750 --version-fileusr/bin/compile_time --queue 4096
    Sun Jan 28 20:08:21 2018 daemon.info sysinit: - init complete -
    Sun Jan 28 20:08:22 2018 kern.info kernel: [   34.770000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
    Sun Jan 28 20:09:17 2018 cron.info crond[575]: crond: USER root pid 931 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:12:01 2018 cron.info crond[575]: crond: USER root pid 1017 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:15:01 2018 cron.info crond[575]: crond: USER root pid 1225 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:18:01 2018 cron.info crond[575]: crond: USER root pid 1328 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:21:01 2018 cron.info crond[575]: crond: USER root pid 1385 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:24:01 2018 cron.info crond[575]: crond: USER root pid 1415 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:27:01 2018 cron.info crond[575]: crond: USER root pid 1442 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:30:01 2018 cron.info crond[575]: crond: USER root pid 1466 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:33:01 2018 cron.info crond[575]: crond: USER root pid 1490 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:36:01 2018 cron.info crond[575]: crond: USER root pid 1514 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:39:01 2018 cron.info crond[575]: crond: USER root pid 1538 cmdusr/bin/cgminer-monitor

    Please kindly advices.


    (Moderator's note: This post was edited by frodocooper to use code tags for the log.)

  • joktel
    Newbie
    *
    Offline Offline

    Activity: 20
    Merit: 0


    View Profile
    January 28, 2018, 03:06:18 PM
     #576
    Quote from: joktel on January 28, 2018, 01:01:33 PM
    I just bought a used S3 antminer to learn mining. The box got to me with a broken part. But the seller told me it does not matter that it will still work fine. So I started the S3 and it really worked, but only mined for the previous owner. After changing the miner configuration to my own data the miner stopped mining.
    I have read alots of suggestion in the forum but could not fix the miner to work for me, but I AM STILL LOST... NO SOLUTION...
    Can this be a problem from the broken part during the shipment? There is a small cylinder-like object, see picture below, SORRY FOR MY LAYMAN EXPLANATION
    What is the use of this part and can the S3 work without the part?
    https://drive.google.com/open?id=1vRRzUM84r7hgNpSyDgzeYeGk7CxSjAFy


    here is the system log file: any useful hint here on what is happening with my S3.

    Quote
    Sun Jan 28 20:08:00 2018 daemon.info sysinit: Sun Jan 28 12:08:00 UTC 2018
    Sun Jan 28 20:08:00 2018 user.emerg syslog: kmodloader: loading kernel modules frometc/modules.d/**
    ...
    Sun Jan 28 20:27:01 2018 cron.info crond[575]: crond: USER root pid 1442 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:30:01 2018 cron.info crond[575]: crond: USER root pid 1466 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:33:01 2018 cron.info crond[575]: crond: USER root pid 1490 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:36:01 2018 cron.info crond[575]: crond: USER root pid 1514 cmdusr/bin/cgminer-monitor
    Sun Jan 28 20:39:01 2018 cron.info crond[575]: crond: USER root pid 1538 cmdusr/bin/cgminer-monitor

    Please kindly advices.


    Problem solved...
    I flashed the firmware and reset the Miner.
    It started mining after rebooting and think the problem is setup data corrupted some where.
    however I am still not sure the effect of the broken condenser??  on the whole troubles.
    If anyone know what that pieces does on the S3, I will appreciate advices and suggestions.
    I mean the broken part in this board's picturehttps://drive.google.com/open?id=1vRRzUM84r7hgNpSyDgzeYeGk7CxSjAFy
    Thanks
    Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 [29]
      Print  
Page 28
Viewing Page: 29

IRLBTC™ © 2025 IRLBTC.com