|
Make sure that none of the existing S1's is still on the factory default 192.168.1.99. Note that you'll need to power the new S1's one at a time and change their fixed IP addresses (if you turn on more than 1, there might be an IP address clash). As suggested doing a factory reset is a good idea.
Cheers
|
|
|
|
How many of you ordered the s3 kit?
I did, it's probably quite close to replacement, but that would be missing the tinkering fun... Cheers |
|
|
|
Has anyone received the upgrade kit? Bitmain promised shipping on the 20 of Aug or earlier, but so far it is 'unshipped'
Cheers
The promised shipping date is 20 of September! Very true!!! (how could I miss a whole month?!) Cheers Your activity count *is* 420 at the moment. ... Does '420' make me absent minded?....  |
|
|
|
Setting is listed below Pool http://api.bitcoin.cz:8332Pool1 worker Leooo.worker1 Pool1 password Pool 2 stratum+tcp://stratum.btcguild.com:3333 Pool2 worker Leooo_1 Pool2 password Protocol IPv4 address 192.168.1.99 IPv4 netmask 255.255.255.0 IPv4 gateway 192.168.1.1 IPv4 broadcast 192.168.1.255 Use custom DNS servers I want to know the reason. Please help  THANKS Use the address stratum.bitcoin.cz:3333 for Pool1 Use the worker style of "Leooo.worker1", where "Leooo" is your registered user name and worker1 your registered worker. The password of worker1 has to be consistent with what you registered on Slush's pool (check Slush's instructions). These entries have to be precisely what the pool requires, no additional 'spaces' or 'variations'. There is no point in having 2 entries into the same server on the same pool. Cheers |
|
|
|
Has anyone received the upgrade kit? Bitmain promised shipping on the 20 of Aug or earlier, but so far it is 'unshipped'
Cheers
The promised shipping date is 20 of September! Very true!!! (how could I miss a whole month?!) Cheers |
|
|
|
|
Has anyone received the upgrade kit? Bitmain promised shipping on the 20 of Aug or earlier, but so far it is 'unshipped'
Cheers
|
|
|
|
Is it generally agreed that Slush has been trustworthy and nothing shady is happening?
 Does anyone actually make sure when the pool finds a block, that it actually gets distributed to its workers? it would be pretty obvious. why would slush even need to do that since he is making a killing from us all. crazy talk I've been monitoring my payouts from Slush over many months and can 'testify' that they were consistent with the reported values on the Stats page and payout history. There were some rare 'glitches' that caused delays in a small number of cases, but these have been rectified eventually. As suggested, Slush benefits long term from honesty and transparency. Cheers |
|
|
|
|
Like most of the people who oc'd the S1, I have a few second fans already. These 2nd fans can be 'recycled' into the S1-to-S3 upgrade. While the cost of the upgrade is marginally lower than a full S3, it gives an opportunity to double the hash rate with a significantly better efficiency.
Cheers
|
|
|
|
Do you know how long takes EMS delivery to arrive Europe?
2014-07-31 19:23:00 Posting
2014-07-31 19:44:00 SJYX Despatch from Sorting Center
2014-07-31 21:36:00 SHENZHEN Arrival at Sorting Center
2014-07-31 21:48:58 SHENZHEN Despatch from Sorting Center
Hopefully you've already received your units, EMS looks very slow. My order is going via the long route using UPS. It is showing expected delivery in about 2 days to Australia. That's after I pay what should be around $260 odd import tax as well for 4 x S3s. Cant wait for Bitmain to go back to single unit orders. Don't think that's gonna happen though. Single orders will get Aussie buyers under the $1000 import tax level. Mumbai, India 08/05/2014 1:52 P.M. Departure Scan 08/05/2014 12:08 P.M. Arrival Scan Bangkok, Thailand 08/05/2014 8:50 A.M. Departure Scan 08/05/2014 6:28 A.M. Arrival Scan Shenzhen, China 08/05/2014 4:50 A.M. Departure Scan I ordered S3's in pairs to Australia and so far it was always under the customs/GST threshold. You probably paid because it was an order of 4 that clearly goes over that $1000 threshold. Last B4 delivery was fairly fast by UPS. Cheers |
|
|
|
Observation.
In one of the Batch 4 machines I got, there is a machine with a July 28 firmware date within the Kernel Log.
Anyone noticed that? Is that an experimental firmware?
The cooling fans report constant 7000-9000 RPM range. That doesn't look normal. Recommendations?
Got my B4 S3's today. Both of them have also the July 28 firmware ("Linux version 3.10.12 (xxl@ubuntu) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2013.05 r38031) ) #140 Mon Jul 21 17:27:04 CST 2014"). Both of them run with very high fan speeds, much higher than the B1 units 3780 3960 4680 10560 The B1 units, at freq=225 run 1740 1620 and 1680 1500 rpm The Bitmain support page does not mention this firmware. Any clues why the high fan speed? I'm now getting fan speeds of ~14000, it 'sounds' like a software bug more that a super-sonic fan.... (the fans on the new B4 units sound similar to the older B1 units with the July 21 firmware) - BITMAIN what is happening with this July 28 firmware on the Batch 4 Antminer S3s? Cheers |
|
|
|
Observation.
In one of the Batch 4 machines I got, there is a machine with a July 28 firmware date within the Kernel Log.
Anyone noticed that? Is that an experimental firmware?
The cooling fans report constant 7000-9000 RPM range. That doesn't look normal. Recommendations?
Got my B4 S3's today. Both of them have also the July 28 firmware ("Linux version 3.10.12 (xxl@ubuntu) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2013.05 r38031) ) #140 Mon Jul 21 17:27:04 CST 2014"). Both of them run with very high fan speeds, much higher than the B1 units 3780 3960 4680 10560 The B1 units, at freq=225 run 1740 1620 and 1680 1500 rpm The Bitmain support page does not mention this firmware. Any clues why the high fan speed? |
|
|
|
This thread is no longer a channel for me to communicate with the clients. I didn't read the thread for the last month because of SP30 FW development, and the ground shifted. Few months ago it was a great place to get feedback, and to resolve issues. Now it is same trashing over and over and over, every day. I am very sorry that we didn't perform to the specs we were committed, but Guy is committed to compensate in a reasonable way, and reading all this trashing is just not what I want to do with my time. And now I see some people talking about race, religion, politics etc`, and even the smallest jokes provoke crazy reactions.
So I will be stopping reading the thread for a while at least, unless Guy will ask me specifically to reply somewhere. If you have technical issues, feedbacks etc`, feel free to use my email. Best of luck to all those getting SP30. Please remember we got the ASICs just about 10 days ago and working around the clock to make the FW as good and stable as possible.
Regards`
Zvi, While certainly you need to focus on your engineering task, don't let the negative posts here upset you too much, use your mental 'iron dome' to ignore them... most of these posts fall in 'unpopulated areas' anyway... (consider that many members here were exploited by various shady operators and have developed some level of mistrust and suspicion, which is sometimes a healthy protective mechanism, but can 'overshoot' too). Cheers |
|
|
|
i cannoct connect the miner also with direct cable miner-pc
the pc address is 192.168.0.xxx
i changed it according to dogie's guide to 192.168.1.1 and connect the miner
i changed the protocol into dhcp client ands save and apply
after no more connection, also repeating the same steps
the problem is that i didn't set the pools data
why change to DHCP? It is simpler and more reliable to stay with a fixed IP address in the range supported by your router. You can always go back by using the reset button (on the S3 it is behind a hole in the front panel, see Dogie's guide under 'troubleshooting'). (The 'D' in DHCP stands in this case for 'Dumb'.... A fixed IP (as long as you use a different one for each Antminer) is repeatable, predictable, easy to monitor and free of DHCP lease issues. Cheers |
|
|
|
Is this normal???
same on both S3. Both with default frequency: 218.75
why so many discarded??
someone suggested that its possibly backwards, the accepted are actually the discarded, and vice versa. probably fixed in a new firmware upgrade soon Hello oskuro, did you end up getting a resolution for this problem. As you can see my discarded shared are a huge problem I have upgraded to the latest firmware from bitmaintech but still no luck. Any help would be greatly appreciated. PS I have 6 Antminer S3's All with the same problem Checkout ckolivas post earlier in this thread https://bitcointalk.org/index.php?topic=671189.msg8056057#msg8056057Discards are a non-issue. "They have nothing to do with hashrate, share acceptance, efficiency or anything else of any relevance today. They are an internal value which was only of relevance in the getwork era. Trying to optimise this value is futile, and lowering the value achieves nothing. It annoys the crap out of me that it was ever displayed in these standalone devices because people get hung up about it and it is of zero relevance." Cheers |
|
|
|
Proposed sanctions include Arms deals....... edit: never have i said boycotting Spondoolies will bring a end to a ongoing political war. I just said support boycotting israel(products) and support sanctions imposed on them. Even if it means a loss for your own nation. eidt: I have no idea why I am engaging you in conversation, you are the person who red tagged me for not supporting spondoolies..... take your twisted politics somewhere else |
|
|
|
|
All of my PSUs have a built-in power switch, I leave the jumper permanently on the 24 pin connector and use the power supply switch on the rare instances that I need to power the miner on or off. Simply have no use/need for a 'switch board' (certainly not one with the 'shorting feature' of these exposed pins).
Bitmain should focus on the stuff that you are good at - miners. (what about the upgrade kits for S1/S2?)
Cheers
|
|
|
|
The firmware will get rid of the beeping. You can still lower the beeping in the current firmware, there was some mentions some pages back.
That x is a chip not hashing, try to give it a reboot and see if it goes back to normal
I rebooted and now the X is gone, however, I am getting this sudden drop in average hashrate:  any ideas why ? EDIT: also, again how do I check what firmware I am already running? thanks You need to give it some time to reach the steady hash rate, it can take a few hours until the Avg GH/sec reaches that value. It goes slower on slower frequency settings and faster when you over-clock. Cheers |
|
|
|
The best thermal pads are not as good as the worst grease....I can see why they said not to use pads as the heatsinks were machined with a certain tolerance to be in direct contact with the ASICs (I will find out how much now when I take 1 machine apart again) pads are garbage just use a good grease and you can be messy applying it like Bitmain a la birthday cake icing style but its better not to get it where its not needed...the inside should pretty much cover the metal part with grease for optimal heat transfer ...I am about to take off the sinks from 1 of the machines and reverse the blades to see if it makes a difference..this machine went from 420ish to 400 now after a reboot  Don't rush into conclusions immediately after reboot. It takes a while for hash rate to 'ramp up' after reboot. Making a judgment after less than say an hour is quite premature (at stock). At the lower frequency settings (212.5) it can take about 4 hours before the average hash rate stabilizes. Then you need to check after about 24 hours, as it tends to get lower again (thermal issues?). Cheers Cheers |
|
|
|
I received my 2 Antminer S3's today. One is happily mining away at about 430Gh/s the other I logged into once and attempted to configure it but something happened and the S3 rebooted and now I am no longer able to sign into it. I have changed the working miners IP address so its not conflicting and the miner does show on my router at the 192.168.1.99 address. but the page will not load and I get an error saying the page could not be loaded. Is there some magical reset or something to recover this or am I SOL?
You could try resetting it to 'factory default' using the reset switch on the 'front' panel. See https://bitcointalk.org/index.php?topic=702653 in the Troubleshooting section where it says "How do I reset settings to default? - Use a paperclip to press the reset button - located next to the ethernet connector - down for 5-10 seconds. The miner will then reset with stock settings." If that fails, you could try powering it down and after some minutes up again and hopefully it will sort itself (some patience is required, it is a slooooow controller, adequate for the task). (just wondering why does the S3 'show on my router at 192.168.1.99', if you left it with a different fixed IP) Cheers |
|
|
|
|
Show Posts
