Azmodeus
Newbie
Offline
Activity: 30
Merit: 0
|
|
July 19, 2014, 03:00:54 PM |
|
Mine are due to arrive Monday. So what cut-off frequency have testers found for needing 2 pci-e vs 4 pci-e? Can you get by with 2 cables for frequencies 225 and 237 but need 4 cables for 250??
|
|
|
|
minter12345
Member
Offline
Activity: 74
Merit: 10
|
|
July 19, 2014, 03:01:15 PM |
|
Yep, set it to false and it still beeps randomly.
I got the Beeping sorted Removed the casing 5 screws each side speaker/beeper on the top open it with a sharp blade and pulled out the round steel thingy no more beeps Oh gees lol. I wont be doing that. Under the Processes tab: one of those processes must be telling it to beep. And here's what is send to cgminer: cgminer --bitmain-options 115200:32:8:18:218.75:1106 -o USERNAME:PASSWORD --bitmain-nobeeper --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096 What is: --bitmain-checkn2diff and --bitmain-hwerror Maybe one of those is doing something related to beeping?
|
Free coins every day: QoinPro Including Bitcoins!
|
|
|
minter12345
Member
Offline
Activity: 74
Merit: 10
|
|
July 19, 2014, 03:02:56 PM |
|
I used a mac mini and terminal to ssh in .
windows use putty.. same as the s1 here is the hardest thing to remember:
vi /etc/config/asic-freq same spot as the s-1
Thank you, its the same as S1 Thats handy.
|
Free coins every day: QoinPro Including Bitcoins!
|
|
|
philipma1957
Legendary
Offline
Activity: 4256
Merit: 8603
'The right to privacy matters'
|
|
July 19, 2014, 03:17:24 PM |
|
I used a mac mini and terminal to ssh in .
windows use putty.. same as the s1 here is the hardest thing to remember:
vi /etc/config/asic-freq same spot as the s-1
Thank you, its the same as S1 Thats handy. yeah I always forget it and have to search it out. even though I am running these at my friends office and I will set them at freq 212.5 for his place. I am now going to try setting them to 225 to see what I get.
|
|
|
|
data55
Member
Offline
Activity: 112
Merit: 10
|
|
July 19, 2014, 03:31:25 PM |
|
Looks like I paid extra so I could say I was part of Batch 1. Sane here, oh well live and learn. It took them almost 9 hours to process my payment so I'm assuming that's what pushed me to end of batch 1 aka batch 2, lol.
|
I'm addicted to hashpower and horsepower. *Reinstated from hack - Dec. 2020*
|
|
|
allcoinminer
|
|
July 19, 2014, 03:33:22 PM Last edit: July 23, 2014, 10:09:23 PM by allcoinminer |
|
Can anyone explain the below image? Its from UPS tracking.
i think perhaps customs in your country do not accept import that and item must be return The funny thing is 1 miner is Held in Warehouse of UPS and the other one gone to Indonasia. Both of them is part of one order and shipped in the same tracking number. Wonder how one miner gone to a different country when both are of same shipment tracking id. I contacted UPS and they said the below status: Exception: The number of packages does not match the invoice, waybill, or label. We're working to resolve this discrepancy.
Means one miner is lost in transit or not shipped / picked up. I already found the lost one went for vacation to Indonesia. I order in the initial minutes of S3 Batch 1 sales opening. Hope bitmain will compensate for my earning loss and lost miner.
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4256
Merit: 8603
'The right to privacy matters'
|
|
July 19, 2014, 03:39:01 PM |
|
I used a mac mini and terminal to ssh in .
windows use putty.. same as the s1 here is the hardest thing to remember:
vi /etc/config/asic-freq same spot as the s-1
Thank you, its the same as S1 Thats handy. yeah I always forget it and have to search it out. even though I am running these at my friends office and I will set them at freq 212.5 for his place. I am now going to try setting them to 225 to see what I get. and my miners run worse at 225 then at 212.5 . they hash with lower numbers and with more power drawn. I will go back to 212.5 in an hour or so.
|
|
|
|
sjc1490
|
|
July 19, 2014, 03:40:05 PM |
|
for me the beep occurs once every three hours right when the network switches to a new block. I increased the difficulty from 256 to 512. It been 3 hours and no beep yet...
Several pages back when the B1 started arriving some investigation determined the random beeps occurs when there is a HW error.
|
BTC ADDRESS: 12Qwd8VKLQ4xF44ytHXBpCAKuF9VknG4X2
|
|
|
bjalbert
|
|
July 19, 2014, 03:45:57 PM |
|
My HW errors are almost non-existent no matter what freq I pick but all 3 miners appear to max out in the low 440's. I tried 250mhz and it appeared to be running at 470 but then overnight the avg came down to like 450 so I went back to 218. This is with all 4 PCI-E plugged in so maybe firmware update or some more tinkering can push the numbers up a bit
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4256
Merit: 8603
'The right to privacy matters'
|
|
July 19, 2014, 03:55:05 PM |
|
My HW errors are almost non-existent no matter what freq I pick but all 3 miners appear to max out in the low 440's. I tried 250mhz and it appeared to be running at 470 but then overnight the avg came down to like 450 so I went back to 218. This is with all 4 PCI-E plugged in so maybe firmware update or some more tinkering can push the numbers up a bit
I have 1 machine that prefers 212.5 freq I have 1 machine that does well at 212.5 and 225 freq. So there is a variance. I will run one at each. It does appear that a good plat psu like a 1000 watt seasonic gives .75 watts a hash at the wall. I was doing 846-850 gh and 630-640 watts with both at 212.5 The beeping occurs much less when set to false. I think a few things do it. 1) ssh in change the freq does 1 beep 2) gui boot does 1 beep 3) hw may do a beep not sure. 4) pool switchover does a beep
|
|
|
|
aigeezer
Legendary
Offline
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
|
|
July 19, 2014, 04:01:55 PM Last edit: July 19, 2014, 04:22:11 PM by aigeezer |
|
for me the beep occurs once every three hours right when the network switches to a new block. I increased the difficulty from 256 to 512. It been 3 hours and no beep yet...
Several pages back when the B1 started arriving some investigation determined the random beeps occurs when there is a HW error. The plot thickens. One of my S3s reports 14,478 HW (I don't think I believe it) while another beside it reports 66 HW (might match the total number of beeps heard). They report 31,614 and 32,399 Accepted respectively, which I'm inclined to believe from the pool stats. I haven't opened a case yet - gotta do unrelated things for a few hours. Edit: detail I forgot to mention - both have "Beeper ringing" set to False and I'm not sure whether one or both actually make(s) the sounds. Edit: more detail - both of mine have been running at 256 difficulty. They can go well over 3 hours without a beep though, then might have a few beeps in quick succession. I'll try 512 in any case.
|
|
|
|
Cy13er007
Newbie
Offline
Activity: 7
Merit: 0
|
|
July 19, 2014, 04:18:02 PM |
|
I got in on the B2 batch of Antminer S3, below is info from Bitmain website. Below that, is the info from UPS order tracking w/ time stamps.
Info from Bitmain Website
Order Placed DATE: 2014-07-01 20:31:24
Payment Confirmed: Date 2014-07-01 21:15:06
Shipped: Date 2014-07-19 10:08:26
Info from UPS Tracking:
Scheduled Delivery: Tuesday, 07/22/2014, By End of Day -- Minnesota USA Local time which is CDT
Location Date Local Time Activity Shenzhen, China 07/19/2014 11:22 P.M. Origin Scan 07/19/2014 5:02 P.M. Pickup Scan China 07/19/2014 4:08 A.M. Order Processed: Ready for UPS
|
|
|
|
achow101
Staff
Legendary
Offline
Activity: 3500
Merit: 6840
Just writing some code
|
|
July 19, 2014, 04:21:39 PM |
|
Can't wait my ANTMINER S3 hope it will arrive my home soon
|
|
|
|
minter12345
Member
Offline
Activity: 74
Merit: 10
|
|
July 19, 2014, 04:30:57 PM |
|
for me the beep occurs once every three hours right when the network switches to a new block. I increased the difficulty from 256 to 512. It been 3 hours and no beep yet...
Several pages back when the B1 started arriving some investigation determined the random beeps occurs when there is a HW error. The plot thickens. One of my S3s reports 14,478 HW (I don't think I believe it) while another beside it reports 66 HW (might match the total number of beeps heard). They report 31,614 and 32,399 Accepted respectively, which I'm inclined to believe from the pool stats. I haven't opened a case yet - gotta do unrelated things for a few hours. Edit: detail I forgot to mention - both have "Beeper ringing" set to False and I'm not sure whether one or both actually make(s) the sounds. Edit: more detail - both of mine have been running at 256 difficulty. They can go well over 3 hours without a beep though, then might have a few beeps in quick succession. I'll try 512 in any case. Yeah once when changing settings it started up and did load of hw errors like that. A simple reboot sorted that out. Its defo not a beep per hw error lol
|
Free coins every day: QoinPro Including Bitcoins!
|
|
|
Red_Wolf_2
|
|
July 19, 2014, 04:59:47 PM |
|
Some comments:
1) Can't the beeper ringing be disabled on the configuration page by setting beeper to false?
Yep, set it to false and it still beeps randomly. I got the Beeping sorted Removed the casing 5 screws each side speaker/beeper on the top open it with a sharp blade and pulled out the round steel thingy no more beeps !!! The techie within me cries out in alarm... This is like removing the engine warning light to fix an engine problem! If anyone wants to sort the beeping noise in a more appropriate way, I'd recommend the tape method. It will not stop the sound completely, but it will definitely deaden it. The intermittent beeps are purely a software issue, and will almost certainly be fixed in a future firmware release. I suspect its whatever is mixed in with CGMiner. Seriously hoping that future firmware will improve CGMiner efficiency too, it bothers me seeing it load out the controller board as high as it does, and I reckon it would probably reduce reject rates too...
|
Probably should put something here.... Maybe an LTC address? LeNdJidEvsyogSu2KbC1u3bfJSdcjACFsF
|
|
|
philipma1957
Legendary
Offline
Activity: 4256
Merit: 8603
'The right to privacy matters'
|
|
July 19, 2014, 05:13:54 PM |
|
Some comments:
1) Can't the beeper ringing be disabled on the configuration page by setting beeper to false?
Yep, set it to false and it still beeps randomly. I got the Beeping sorted Removed the casing 5 screws each side speaker/beeper on the top open it with a sharp blade and pulled out the round steel thingy no more beeps !!! The techie within me cries out in alarm... This is like removing the engine warning light to fix an engine problem! If anyone wants to sort the beeping noise in a more appropriate way, I'd recommend the tape method. It will not stop the sound completely, but it will definitely deaden it. The intermittent beeps are purely a software issue, and will almost certainly be fixed in a future firmware release. I suspect its whatever is mixed in with CGMiner. Seriously hoping that future firmware will improve CGMiner efficiency too, it bothers me seeing it load out the controller board as high as it does, and I reckon it would probably reduce reject rates too... A piece of felt like this http://www.amazon.com/Waxman-Self-Stick-Home-Helper-Combo-Brown/dp/B000SL4GEM/ref=sr_1_9?ie=UTF8&qid=1405790000&sr=8-9&keywords=felt+pad
|
|
|
|
sixteendigits
|
|
July 19, 2014, 05:14:21 PM |
|
for me the beep occurs once every three hours right when the network switches to a new block. I increased the difficulty from 256 to 512. It been 3 hours and no beep yet...
Several pages back when the B1 started arriving some investigation determined the random beeps occurs when there is a HW error. The plot thickens. One of my S3s reports 14,478 HW (I don't think I believe it) while another beside it reports 66 HW (might match the total number of beeps heard). They report 31,614 and 32,399 Accepted respectively, which I'm inclined to believe from the pool stats. I haven't opened a case yet - gotta do unrelated things for a few hours. Edit: detail I forgot to mention - both have "Beeper ringing" set to False and I'm not sure whether one or both actually make(s) the sounds. Edit: more detail - both of mine have been running at 256 difficulty. They can go well over 3 hours without a beep though, then might have a few beeps in quick succession. I'll try 512 in any case. If it's the same as the S1, you can't go by the raw numbers alone. They use this convoluted formula for some reason. I remember having an S1 that had ridiculous numbers for HW errors, I was sure it was faulty. When I plugged everything into this formula and did the math, turns out I was getting like 0.003% HW errors. I found a handy calculator. http://www.coincadence.com/antminer-s1-hardware-error/On another topic, am I also to assume the overclocking procedures are the same as the S1? My S3's seem to be stabilizing around 440GHs which is a bit of an improvement but still low. Wanna see what happens when I crank them up a bit.
|
|
|
|
Lowell904
Member
Offline
Activity: 119
Merit: 10
|
|
July 19, 2014, 05:20:25 PM |
|
My Batch 1 order finally shipped!! Ordered :2014-06-30 22:04:41 Paid :2014-06-30 22:10:30 Shipped :2014-07-19 10:08:07 Batch 2 is shipping too. Looks like I paid extra so I could say I was part of Batch 1. Me too. A bunch of us for that matter. Lets hope they fixed some of the bugs on this latest shipment. Otherwise we paid more than the batch 2 people for the same delivery time frame.
|
|
|
|
spazzdla
Legendary
Offline
Activity: 1722
Merit: 1000
|
|
July 19, 2014, 05:34:25 PM |
|
S3 delivered yesterday, UPS FFFFFFFFAILED and left my other S3 at the warehouse... gonna get it Monday.. Ne ways S3 up and running in like 10 minutes lmao if not less, running as advertised.
|
|
|
|
-droid-
Legendary
Offline
Activity: 1050
Merit: 1001
|
|
July 19, 2014, 05:44:51 PM |
|
My Batch 1 order finally shipped!! Ordered :2014-06-30 22:04:41 Paid :2014-06-30 22:10:30 Shipped :2014-07-19 10:08:07 Batch 2 is shipping too. Looks like I paid extra so I could say I was part of Batch 1. Me too. A bunch of us for that matter. Lets hope they fixed some of the bugs on this latest shipment. Otherwise we paid more than the batch 2 people for the same delivery time frame. Ya I got a feeling they didn't do anything to the units, we just overpaid for our batch 1 giving us same batch 2 shipping timeframe
|
|
|
|
|