try to configure both lan and wan devices with fixed ip (put two different ip's that you don't use, 192.168.1.188 and 192.168.1.189, for example).
and try to connect only one chain (hashboard) to the psu, i think it is too small for the miner (not sure).
Topic: I know it's probably some silly, crucial little detail, but... (Read 1243 times)
It looks like it may be a connectivity issue. While it shows up on my router's DHCP client table, instead of being unnamed it shows as an Android device; given that the Antminer's "OS" is Linux, I'm not startled. I had the miner ping the router, and it experienced 100% packet loss. This wasn't the case before, but such is the life in networking. I then had it ping my pc, to which it is connected via CAT5 and again it experienced 100% packet loss.
Ok, I've got my gateway set at 192.168.1.1.
I gave stratum+tcp://solo.antpool.com:3333 a go, and still no activity
I also use Bitminter; it's actually the pool that got me interested in mining. I couldn't get that one to work either.
I purchased the miner off of Ebay. It came with a Raidmax 365 watt power supply (in original box, for whatever that's worth). The seller didn't post too much information about the units, just what they are, what the expected hash rate is, that it easily overclocks (which at this point I'm not really interested in) and the expected power usage from the wall.
I haven't changed any firewall settings. I have reset the miner about a dozen times!
It took me a while to be able to log into the miner, changing settings in Windows, trying them in Linux, and finally I logged into my router, found the IP on my network with no name, adjusted my settings to that IP and I was then able to log into my miner's admin panel. In the miner's admin panel, I've gone through forums with all kinds of different WAN settings/configuration suggestions, including but not limited t setting the gateway to 192.168.2.1, 192.168.1.1, 192.168.1.254, 10.0.1.1, and 74.254.197.1, and/or setting DNS to 192.168.1.1, 10.0.1.1, and 8.8.8.8. Per forum suggestions I have changed my broadcast to 10.0.1.255, 192.168.1.240, and 192.168.1.255.
My miner is connected to my main pc via CAT5 ethernet. My router is old, but reliable; I've never had any issues with it. Since I can see the miner on the network but can't seem to get it recognized on my of my pools, I am thinking it might be a connectivity issue not with the router but the web itself, although there was that one glorious hour or so that Hashpool saw that I had a miner, it just wan't hashing. I have tried to recreate that connection to no avail. I'm still open to that hypothesis.
One last odd thing, every time I "save and apply" changes to my miner configuration password, it changes the password for pool 1 back to root.
Screenshots of miner configuration and status will be posted shortly.
And thanks a lot everyone, I do appreciate the help.
I gave stratum+tcp://solo.antpool.com:3333 a go, and still no activity
I also use Bitminter; it's actually the pool that got me interested in mining. I couldn't get that one to work either.
I purchased the miner off of Ebay. It came with a Raidmax 365 watt power supply (in original box, for whatever that's worth). The seller didn't post too much information about the units, just what they are, what the expected hash rate is, that it easily overclocks (which at this point I'm not really interested in) and the expected power usage from the wall.
I haven't changed any firewall settings. I have reset the miner about a dozen times!
It took me a while to be able to log into the miner, changing settings in Windows, trying them in Linux, and finally I logged into my router, found the IP on my network with no name, adjusted my settings to that IP and I was then able to log into my miner's admin panel. In the miner's admin panel, I've gone through forums with all kinds of different WAN settings/configuration suggestions, including but not limited t setting the gateway to 192.168.2.1, 192.168.1.1, 192.168.1.254, 10.0.1.1, and 74.254.197.1, and/or setting DNS to 192.168.1.1, 10.0.1.1, and 8.8.8.8. Per forum suggestions I have changed my broadcast to 10.0.1.255, 192.168.1.240, and 192.168.1.255.
My miner is connected to my main pc via CAT5 ethernet. My router is old, but reliable; I've never had any issues with it. Since I can see the miner on the network but can't seem to get it recognized on my of my pools, I am thinking it might be a connectivity issue not with the router but the web itself, although there was that one glorious hour or so that Hashpool saw that I had a miner, it just wan't hashing. I have tried to recreate that connection to no avail. I'm still open to that hypothesis.
One last odd thing, every time I "save and apply" changes to my miner configuration password, it changes the password for pool 1 back to root.
Screenshots of miner configuration and status will be posted shortly.
And thanks a lot everyone, I do appreciate the help.
I would try different pools as well.
Specifically one where you know they have implemented vardiff - variable difficulty
I can say that www.kano.is has this as probably most pools do. All pools who primarily mine bitcoin probably have either their main or a specific port with vardiff.
I call pools major and minor for one reason. They either primarily mine bitcoin and have one or more significant attributes or they have many coins and do not have a significant bitcoin mining hashrate.
https://bitminter.com is a long-standing pool who has been around for years.
http://mining.bitcoin.cz is Slush's pool and has a large hashrate.
I would try these three pools before any other to check my functionality.
I do not see this to start some flame argument with other forum members, as I know some are vocal if one leaves a specific name off a list, but these have been used in my experience. YMMV
Can you post a screen shot of a couple of screens? Make sure you block out any details which could be used against you. Most cover their user name, even if it is address, many still cover it. I'm not paranoid either
The miner status screen would be a great start.
I'll assume you bought it from e-bay, a forum, etc, but not from someone you know? Did they share a screenshot of it hashing? Can you share such? If not, what if any details did they provide?
Firewall? I don't see how anything "standard" would do it.
When you say you tried every configuration suggested what does this mean exactly? What items have you changed / tried?
Worst case maybe a reset or firmware something or other. I have upgraded and downgraded many different brands of miners, but I, most unfortunately, was not aware of Bitcoin when the S1 was in its prime and do not own an S1.
The good news is there are many, many people here who have.
I am not recommending you load firmware. I only recommend such if you are doing it for a known reason, not as a step to try when throwing shit at the wall to see what sticks.
In my opinion, the absolutely best thing you can do is read miner threads. I spent weeks reading entire threads here that were old, older, oldest, some that span all of the above. I read the 'official" threads from Bitmain, Spondoolies, and then started reading the others. Over-clocking threads, now under-clocking threads, and in general any hardware thread. I started taking notes and have a good troubleshooting sense. The miner threads have over and over corrected for me what you said is your biggest weakness. By the way, that is all of us. We all get stuck on the tiniest, crappiest, most fubared detail, and eventually get it to click, --- or find out we'd have to spend too much money to do so, heh
I wish you the best luck in getting it going.
Specifically one where you know they have implemented vardiff - variable difficulty
I can say that www.kano.is has this as probably most pools do. All pools who primarily mine bitcoin probably have either their main or a specific port with vardiff.
I call pools major and minor for one reason. They either primarily mine bitcoin and have one or more significant attributes or they have many coins and do not have a significant bitcoin mining hashrate.
https://bitminter.com is a long-standing pool who has been around for years.
http://mining.bitcoin.cz is Slush's pool and has a large hashrate.
I would try these three pools before any other to check my functionality.
I do not see this to start some flame argument with other forum members, as I know some are vocal if one leaves a specific name off a list, but these have been used in my experience. YMMV
Can you post a screen shot of a couple of screens? Make sure you block out any details which could be used against you. Most cover their user name, even if it is address, many still cover it. I'm not paranoid either
The miner status screen would be a great start.
I'll assume you bought it from e-bay, a forum, etc, but not from someone you know? Did they share a screenshot of it hashing? Can you share such? If not, what if any details did they provide?
Firewall? I don't see how anything "standard" would do it.
When you say you tried every configuration suggested what does this mean exactly? What items have you changed / tried?
Worst case maybe a reset or firmware something or other. I have upgraded and downgraded many different brands of miners, but I, most unfortunately, was not aware of Bitcoin when the S1 was in its prime and do not own an S1.
The good news is there are many, many people here who have.
I am not recommending you load firmware. I only recommend such if you are doing it for a known reason, not as a step to try when throwing shit at the wall to see what sticks.
In my opinion, the absolutely best thing you can do is read miner threads. I spent weeks reading entire threads here that were old, older, oldest, some that span all of the above. I read the 'official" threads from Bitmain, Spondoolies, and then started reading the others. Over-clocking threads, now under-clocking threads, and in general any hardware thread. I started taking notes and have a good troubleshooting sense. The miner threads have over and over corrected for me what you said is your biggest weakness. By the way, that is all of us. We all get stuck on the tiniest, crappiest, most fubared detail, and eventually get it to click, --- or find out we'd have to spend too much money to do so, heh
I wish you the best luck in getting it going.
Hi, the IP-broadcast is not important, you can leave it blank.
- Check the miner configuration you have; remember to use the default ones (400 3.2 4F81 35) -you can change it reading: https://bitcointalksearch.org/topic/m.3857079
- Change the pool to:
Pool1: stratum+tcp://solo.antpool.com:3333
User: simply put something here; if it starts to mine, change the pool configuration
Password: none
I know how work the S3 and S5, but no the S1...
Good luck!
EDIT: The first time, my error was what sais philipma1957
- Check the miner configuration you have; remember to use the default ones (400 3.2 4F81 35) -you can change it reading: https://bitcointalksearch.org/topic/m.3857079
- Change the pool to:
Pool1: stratum+tcp://solo.antpool.com:3333
User: simply put something here; if it starts to mine, change the pool configuration
Password: none
I know how work the S3 and S5, but no the S1...
Good luck!
EDIT: The first time, my error was what sais philipma1957
Greetings all, I've combed through all kinds of forums and read so many guides (Dogie's included) and You Tube videos galore. Between the lot of them, I was able to get my Antminer S1 on my network, but it won't hash. For a little while Hashpool said I had one miner running, but it was not hashing. I've tried every configuration suggested, and it's just not hashing. I'm new to mining, but I am somewhat familiar with computer and network stuff, and it's been my experience in the past that the things that have me hung up for weeks turn out to be one silly, stupid little crucial detail. Would someone mind helping me out here, I've googled so much I can google no more. I'd really appreciate it.
Antminer S1
Model TP-Link TL-WR743N/ND v2
Firmware Version OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909)
Kernel Version 3.10.12
IPv4 address 192.168.1.xx (within my router's IP range)
IPv4 netmask 255.255.255.0
IPv4 gateway 192.168.1.xx try 192.168.1.1
IPv4 broadcast 192.168.1.xxx
Use custom DNS servers 8.8.8.8
Pool 1 stratum+tcp://smokeydeville.p2p2.hashpool.com:9332
Pool1 worker 1JZz9qYjf5md4Wir2xwZdX8xaP7s1yZM1H
Pool1 password 123
Pool 2 http://stratum+tcp://mint.bitminter.com:3333
Pool2 worker SmokeyDeVille_antminerS1
Pool2 password 123
Antminer S1
Model TP-Link TL-WR743N/ND v2
Firmware Version OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909)
Kernel Version 3.10.12
IPv4 address 192.168.1.xx (within my router's IP range)
IPv4 netmask 255.255.255.0
IPv4 gateway 192.168.1.xx try 192.168.1.1
IPv4 broadcast 192.168.1.xxx
Use custom DNS servers 8.8.8.8
Pool 1 stratum+tcp://smokeydeville.p2p2.hashpool.com:9332
Pool1 worker 1JZz9qYjf5md4Wir2xwZdX8xaP7s1yZM1H
Pool1 password 123
Pool 2 http://stratum+tcp://mint.bitminter.com:3333
Pool2 worker SmokeyDeVille_antminerS1
Pool2 password 123
look at my bolded suggestion I am assuming you are plugged in with a cat 5/6 cable not wifi
Greetings all, I've combed through all kinds of forums and read so many guides (Dogie's included) and You Tube videos galore. Between the lot of them, I was able to get my Antminer S1 on my network, but it won't hash. For a little while Hashpool said I had one miner running, but it was not hashing. I've tried every configuration suggested, and it's just not hashing. I'm new to mining, but I am somewhat familiar with computer and network stuff, and it's been my experience in the past that the things that have me hung up for weeks turn out to be one silly, stupid little crucial detail. Would someone mind helping me out here, I've googled so much I can google no more. I'd really appreciate it.
Antminer S1
Model TP-Link TL-WR743N/ND v2
Firmware Version OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909)
Kernel Version 3.10.12
IPv4 address 192.168.1.xx (within my router's IP range)
IPv4 netmask 255.255.255.0
IPv4 gateway 192.168.1.xx
IPv4 broadcast 192.168.1.xxx
Use custom DNS servers 8.8.8.8
Pool 1 stratum+tcp://smokeydeville.p2p2.hashpool.com:9332
Pool1 worker 1JZz9qYjf5md4Wir2xwZdX8xaP7s1yZM1H
Pool1 password 123
Pool 2 http://stratum+tcp://mint.bitminter.com:3333
Pool2 worker SmokeyDeVille_antminerS1
Pool2 password 123
Antminer S1
Model TP-Link TL-WR743N/ND v2
Firmware Version OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909)
Kernel Version 3.10.12
IPv4 address 192.168.1.xx (within my router's IP range)
IPv4 netmask 255.255.255.0
IPv4 gateway 192.168.1.xx
IPv4 broadcast 192.168.1.xxx
Use custom DNS servers 8.8.8.8
Pool 1 stratum+tcp://smokeydeville.p2p2.hashpool.com:9332
Pool1 worker 1JZz9qYjf5md4Wir2xwZdX8xaP7s1yZM1H
Pool1 password 123
Pool 2 http://stratum+tcp://mint.bitminter.com:3333
Pool2 worker SmokeyDeVille_antminerS1
Pool2 password 123
Jump to: