MrTeal
Legendary
Offline
Activity: 1274
Merit: 1004
|
|
January 09, 2015, 03:32:01 AM |
|
Are their any recovery SD images like the ones SP provides that would allow you to recover your BBB in the event you can't communicate with it or it gets damaged and you need to replace it? I don't believe so, later S5s won't even have an SD card slot. That's unfortunate since the BBB is essentially off the shelf. It would save a bunch of time if people could just swap the BBB instead of having to send the thing back to Bitmain.
|
|
|
|
notlist3d
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
January 09, 2015, 03:48:51 AM |
|
Are their any recovery SD images like the ones SP provides that would allow you to recover your BBB in the event you can't communicate with it or it gets damaged and you need to replace it? I don't believe so, later S5s won't even have an SD card slot. That's unfortunate since the BBB is essentially off the shelf. It would save a bunch of time if people could just swap the BBB instead of having to send the thing back to Bitmain. Amazingly quick shipping as always. If there is not a image I can upload one soon. (It appears I jumped the gun no SD card to backup) I was busy and didn't get to do all I was wanting just some initial pictures.
|
|
|
|
Duce
|
|
January 09, 2015, 04:09:53 AM |
|
|
|
|
|
TrevorS
|
|
January 09, 2015, 07:54:15 AM |
|
Thanks, much appreciated! Was trying to dance with 140mm !
|
|
|
|
BITMAIN_Kiddy
Newbie
Offline
Activity: 22
Merit: 0
|
|
January 09, 2015, 10:56:57 AM |
|
Thanks, much appreciated! Was trying to dance with 140mm ! Fan specs for S3/+: voltage: 12V DC current: 1.2A (MAX) 3600rpm PWM modulation size: 119*119*38 (mm)
|
|
|
|
KeezAZA
Full Member
Offline
Activity: 224
Merit: 100
https://eloncity.io
|
|
January 09, 2015, 11:47:02 AM |
|
I moved mine to get a little more cold air. The fan slowed enough that the high pitch whine went away, but it was still moving an incredible amount of air considering the ambient. The RPM to temp is the problem. The S1 does 2500-2700 RPM @ 45-48C and 2900-3100 RPM @ 48-52C. If the conditions for the PWM for the fan are set lower then this thread would not be so drawn out. Example: 800-1200RPM @ 40C 1250-1900RPM @ 45C 1950-2700RPM @ 50C 2800-3000RPM @ 60C
|
|
|
|
Rabinovitch
Legendary
Offline
Activity: 2030
Merit: 1076
BTCLife.global participant
|
|
January 09, 2015, 12:54:55 PM Last edit: January 09, 2015, 01:06:03 PM by Rabinovitch |
|
Damn... I was planning to do this (close the top of S5 case to provide more directed airflow) with my test unit that arrived much later than to other forum members...
But I still have a couple ideas on how to play with S5.
If you find any combination of things that help with either/both noise and reported temp, please let us know. I've ordered a couple S5 and plan to try S3 fans and homemade covers. My environment gets very warm in summer. Now I got it, and right out of the box, at stock frequency 350 it gives about 1.1 Th/s at Slush's side. Firmware version: It IS LOUD. Especially right after power on. ) I have no noise meter (and I doubt that I'll measure any new values, they are all measured before me), but if anyone need, I'll take a noise meter for a while. With normal temperature in the living room the boards of S5 are 51 C and 55 C with this stock fan. And it looks like huge part of air from the fan is blowing away upward from this open semi-case (since my S5 is placed at the glass shelf for TV and audio equipment), so the idea of making a kind of cover is looking not so useless... I have an unpacked Navipower HDB-1212UA fan (veeery cheap but... 2800 RPM... 105.81 CFM...), will try it later. If S5 be able to work with reasonable temperatures using that fan - it would be great. Later I'll share another results of testing and experiments.
|
|
|
|
BITMAIN_Janet
Member
Offline
Activity: 112
Merit: 10
|
|
January 09, 2015, 04:16:02 PM |
|
Could someone please update me on the safest over clocking potential?
If you have a cold air source, or can handle a lot of noise, 412.5MHz seems to be about the limit before hashrate starts nose-diving. Board temperature around 65C doesn't seem to be the problem. Peaks out around 1.32-1.35TH, and at 425MHz is down to 1.25TH Catch it I am looking through posts to find this for a buyer's reference. Thank you klondike_bar
|
Skype: yaxuan.ai, +86 18511636219, Twitter:@Janet_Ai_YaXuan
|
|
|
BITMAIN_Janet
Member
Offline
Activity: 112
Merit: 10
|
|
January 09, 2015, 04:16:49 PM |
|
Well they arrived today! Now we've got some work to do. host imagesStrato Awesome
|
Skype: yaxuan.ai, +86 18511636219, Twitter:@Janet_Ai_YaXuan
|
|
|
MrTeal
Legendary
Offline
Activity: 1274
Merit: 1004
|
|
January 09, 2015, 04:29:26 PM |
|
So, the unit I have that I'm having issues with seems to just lock up. cgminer is still running as the elapsed time, local works and discarded keep going up. I'm not near the unit to verify if it is actually hot or if the temp sensors are reporting incorrectly, but if they are reporting correctly it would appear that the unit is still at least dissipating a normal amount of heat. It's just not submitting any shares. Restarting cgminer fixes the problem.
|
|
|
|
alienesb
|
|
January 09, 2015, 04:40:28 PM |
|
I've got a sick blade it seems: Changed the PSU, checked the cables, rebooted, flashed the unit but still this.
|
|
|
|
Phosphorous
|
|
January 09, 2015, 05:13:22 PM |
|
Yes, I wonder what the new firmware will fix. After running over night, I notice a large increase in rejects from my pool, Westhash. Any idea what if anything can be done?
Rejects are the red tips. You can see where I turned on the S5 and then later decommissioned the S3s.
Did you load your S3s with the cgminer 4.7/extranonoce.subscribe patch found on their website? If you did then that explains why the reject rate was almost nonexistent with those units. Without the patch (indicated with the green check on your Westhash status page) your miner will have a higher reject rate. I do not see a patch for the S5 units yet. Does anyone know if the S3 version will work with the S5?
|
|
|
|
dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
January 09, 2015, 05:32:38 PM |
|
I've got a sick blade it seems: Changed the PSU, checked the cables, rebooted, flashed the unit but still this. When you say rebooted, does that include hard reboots? If so, you can try getting it to wake up with a frequency change and another hard reboot. If still nothing then PM BitmainWarranty to arrange an RMA. Be sure to link to your post describing the issues, what type and how many miners you wish to have repaired/replaced and your bitmaintech.com order number.
|
|
|
|
dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
January 09, 2015, 05:33:39 PM |
|
So, the unit I have that I'm having issues with seems to just lock up. cgminer is still running as the elapsed time, local works and discarded keep going up. I'm not near the unit to verify if it is actually hot or if the temp sensors are reporting incorrectly, but if they are reporting correctly it would appear that the unit is still at least dissipating a normal amount of heat. It's just not submitting any shares.
Restarting cgminer fixes the problem.
Known bug currently, sorry about that. Soft (usually) or hard reboots will clear it. In terms of frequency, I had this happen once in the first 24 hours, and then never again.
|
|
|
|
IITravel01
|
|
January 09, 2015, 05:49:21 PM Last edit: January 09, 2015, 06:24:37 PM by IITravel01 |
|
For comparison, I've measured my 2 S5's downclocked to 312.5M (about 1,030Gh/s each, temp. 73) on a single 1,500w titanium power supply with 230v and it's using about 1,064 watts (with 2 extra fans, would make it about 1,060 watts without them) at the wall (increase about 2% for 120v = about 542 watts each). Compared to a S3 downclocked to 206.25M at 0725 voltage (about 405Gh/s, temp. 39) on a 750w platinum power supply with 120v using about 316w and my C1 at default speed with 0725 voltage on a 1200w gold power supply on 120v using about 835 watts (770 watts at the power supply with 7 fans and 1 pump) getting about 1,005Gh/s.
|
|
|
|
MrTeal
Legendary
Offline
Activity: 1274
Merit: 1004
|
|
January 09, 2015, 05:53:21 PM |
|
So, the unit I have that I'm having issues with seems to just lock up. cgminer is still running as the elapsed time, local works and discarded keep going up. I'm not near the unit to verify if it is actually hot or if the temp sensors are reporting incorrectly, but if they are reporting correctly it would appear that the unit is still at least dissipating a normal amount of heat. It's just not submitting any shares.
Restarting cgminer fixes the problem.
Known bug currently, sorry about that. Soft (usually) or hard reboots will clear it. In terms of frequency, I had this happen once in the first 24 hours, and then never again. When they do lock up like that, are they chips still doing work? The temps reported were the same as when the unit is under full load, so it would seem that it is unless the temp values stop reporting at that point as well. The old Gen1 Avalon minis would do that as well. I could deal with a miner crashing and going down, but those stupid things would crash and sit there burning 600W until they were power cycled. They're the reason all my gear is on networked PDUs now. Note: After the cgminer restart the unit ran for 40 minutes and then crashed again.
|
|
|
|
MrTeal
Legendary
Offline
Activity: 1274
Merit: 1004
|
|
January 09, 2015, 07:33:15 PM |
|
Crashed again, ran for an hour but down for the last 40 minutes. I flashed to 0107, we'll see if that helps.
|
|
|
|
dogie
Legendary
Offline
Activity: 1666
Merit: 1183
dogiecoin.com
|
|
January 09, 2015, 08:13:18 PM |
|
So, the unit I have that I'm having issues with seems to just lock up. cgminer is still running as the elapsed time, local works and discarded keep going up. I'm not near the unit to verify if it is actually hot or if the temp sensors are reporting incorrectly, but if they are reporting correctly it would appear that the unit is still at least dissipating a normal amount of heat. It's just not submitting any shares.
Restarting cgminer fixes the problem.
Known bug currently, sorry about that. Soft (usually) or hard reboots will clear it. In terms of frequency, I had this happen once in the first 24 hours, and then never again. When they do lock up like that, are they chips still doing work? The temps reported were the same as when the unit is under full load, so it would seem that it is unless the temp values stop reporting at that point as well. The old Gen1 Avalon minis would do that as well. I could deal with a miner crashing and going down, but those stupid things would crash and sit there burning 600W until they were power cycled. They're the reason all my gear is on networked PDUs now. Note: After the cgminer restart the unit ran for 40 minutes and then crashed again. Crashed again, ran for an hour but down for the last 40 minutes. I flashed to 0107, we'll see if that helps. In my case, no. Only one module stopped mining during the freeze [can see on pool], but both temperatures + RPMs had frozen on the dashboard. What PSU are you on? This is the first generation where 12V load balancing [12.3V under load or 11.6V etc] so would be good to know for information's sake.
|
|
|
|
TrevorS
|
|
January 10, 2015, 12:08:03 AM |
|
Yes, I wonder what the new firmware will fix. After running over night, I notice a large increase in rejects from my pool, Westhash. Any idea what if anything can be done?
Rejects are the red tips. You can see where I turned on the S5 and then later decommissioned the S3s.
Did you load your S3s with the cgminer 4.7/extranonoce.subscribe patch found on their website? If you did then that explains why the reject rate was almost nonexistent with those units. Without the patch (indicated with the green check on your Westhash status page) your miner will have a higher reject rate. I do not see a patch for the S5 units yet. Wasn't aware of that Westhash status page but now have it up. I went through my S3s installing cgminer 4.7.0 aprox two weeks ago and yet the status page shows all red crosses. I'm running the Tues Aug 26 firmware release in each (original S3+ version) and just used PuTTY to recheck cgminer version ("cgminer-api version") and each reports 4.7.0. Any idea what the problem might be? PS. Each S3 has had configuration modifications since then as well as having been rebooted, but normally the cgminer install isn't affected by that.
|
|
|
|
Phosphorous
|
|
January 10, 2015, 12:20:35 AM |
|
Yes, I wonder what the new firmware will fix. After running over night, I notice a large increase in rejects from my pool, Westhash. Any idea what if anything can be done?
Rejects are the red tips. You can see where I turned on the S5 and then later decommissioned the S3s.
Did you load your S3s with the cgminer 4.7/extranonoce.subscribe patch found on their website? If you did then that explains why the reject rate was almost nonexistent with those units. Without the patch (indicated with the green check on your Westhash status page) your miner will have a higher reject rate. I do not see a patch for the S5 units yet. Wasn't aware of that Westhash status page but now have it up. I went through my S3s installing cgminer 4.7.0 aprox two weeks ago and yet the status page shows all red crosses. I'm running the Tues Aug 26 firmware release in each (original S3+ version) and just used PuTTY to recheck cgminer version ("cgminer-api version") and each reports 4.7.0. Any idea what the problem might be? PS. Each S3 has had configuration modifications since then as well as having been rebooted, but normally the cgminer install isn't affected by that. Did you append #xnsub at the end of your miner host configuration entry?
|
|
|
|
|