Search content
Sort by
Showing 20 of 154 results by JakeTri
I'm using BlackSun hosting for my SP10 and I think it would be a very good option for my fellow Canadians 
=====================
URL: http://www.blacksun.ca/
Price: SP10 ~$160 CDN / month with 1 year contract, no installation fee!
Location: Saskatoon, Saskatchewan, Canada
Comment: Prices may vary slightly based on available space.
=====================
They provide 208V for my SP10 but temperature is a little bit high.
=====================
URL: http://www.blacksun.ca/
Price: SP10 ~$160 CDN / month with 1 year contract, no installation fee!
Location: Saskatoon, Saskatchewan, Canada
Comment: Prices may vary slightly based on available space.
=====================
They provide 208V for my SP10 but temperature is a little bit high.
Code:
Mining Rate: 1.4Ths
Temp Front / Back
30 °C / 81 °C
Temp Front / Back
30 °C / 81 °C
I want to provide an update and raise a RED flag for the hosting company!
After 5 months of hosting (without any issues) they claim that my miner use more power than expected (in the contract and all my invoices is listed as 7A at 208V) so the new monthly payments for one SP10 would be ~$270 CAD!
Obviously I canceled the contract in this new conditions and received back my miner in good conditions. Still waiting for my refund on the unused advanced payments.
I advise to be extremely careful when dealing signing new contracts with them.
I have an Emerson 1200 PSU failure .. what would be the easiest way to contact SPT for warranty?
The PSU green LED light does not power up anymore. I tried to SWAP them .. just powering the other part of the SP30.
The PSU green LED light does not power up anymore. I tried to SWAP them .. just powering the other part of the SP30.
I hope you received the replacement PSU from SPT by now ...
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
Anybody else have issue for the last days with the SP30 from GB hosted at SP-tech ?
I'm asking because mine was running at 375 GH/s hole day yesterday from stable 4.4TH/s and today hash rate was increased to about 2.1TH/s ...
I'm asking because mine was running at 375 GH/s hole day yesterday from stable 4.4TH/s and today hash rate was increased to about 2.1TH/s ...
Would sure be nice if they opened up the source as required by the CGMiner license...
I hope they do it soon .. I'm waiting for this to be able to play with code and see if it is possible to set frequency for each board from the miner.
Hi,
I just try to update S320140811 with frequency management.
The frequency 225 is not part of the option (I do not know why?), it goes directly from 218.75 to 237,5.
Can someone tell me which file to edit to add the 225 frequency in choice?
THX.
I just try to update S320140811 with frequency management.
The frequency 225 is not part of the option (I do not know why?), it goes directly from 218.75 to 237,5.
Can someone tell me which file to edit to add the 225 frequency in choice?
THX.
The file with frequency values for the advanced page with miner settings is
Code:
/usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Look at the end of the file for the frequency list.
Here are highlighted in red the lines with new frequency not included in the stock firmware.
Quote
pb:value("13:300:0b82", translate("300M"))
pb:value("14:293.75:1706", translate("293.75M"))
pb:value("14:287.5:0b02", translate("287.5M"))
pb:value("14:281.25:1606", translate("281.25M"))
pb:value("15:275:0a82", translate("275M"))
pb:value("15:268.75:1506", translate("268.75M"))
pb:value("15:262.5:0a02", translate("262.5M"))
pb:value("16:256.25:1406", translate("256.25M"))
pb:value("16:250:0982", translate("250M"))
pb:value("16:243.75:1306", translate("243.75M"))
pb:value("17:237.5:1286", translate("237.5M"))
pb:value("17:231.25:1206", translate("231.25M"))
pb:value("18:225:0882", translate("225M"))
pb:value("18:218.75:1106", translate("218.75M (default)"))
pb:value("18:212.5:1086", translate("212.5M"))
pb:value("19:206.25:1006", translate("206.25M"))
pb:value("20:200:0782", translate("200M"))
pb:value("20:196:1f07", translate("196M"))
pb:value("20:193:0f03", translate("193M"))
pb:value("23:175:0d83", translate("175M"))
pb:value("27:150:0b83", translate("150M"))
pb:value("33:125:0983", translate("125M"))
pb:value("40:100:0783", translate("100M"))
pb:value("14:293.75:1706", translate("293.75M"))
pb:value("14:287.5:0b02", translate("287.5M"))
pb:value("14:281.25:1606", translate("281.25M"))
pb:value("15:275:0a82", translate("275M"))
pb:value("15:268.75:1506", translate("268.75M"))
pb:value("15:262.5:0a02", translate("262.5M"))
pb:value("16:256.25:1406", translate("256.25M"))
pb:value("16:250:0982", translate("250M"))
pb:value("16:243.75:1306", translate("243.75M"))
pb:value("17:237.5:1286", translate("237.5M"))
pb:value("17:231.25:1206", translate("231.25M"))
pb:value("18:225:0882", translate("225M"))
pb:value("18:218.75:1106", translate("218.75M (default)"))
pb:value("18:212.5:1086", translate("212.5M"))
pb:value("19:206.25:1006", translate("206.25M"))
pb:value("20:200:0782", translate("200M"))
pb:value("20:196:1f07", translate("196M"))
pb:value("20:193:0f03", translate("193M"))
pb:value("23:175:0d83", translate("175M"))
pb:value("27:150:0b83", translate("150M"))
pb:value("33:125:0983", translate("125M"))
pb:value("40:100:0783", translate("100M"))
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
I am a little confused about the voltage posts.
Do I need to find out if my voltage is actually 208V, 220V/230V or 240V since electricians seem to just throw around the number that suits them when speaking of 110/120, 220/240V and 460V? Would the SP30 actually perform worse if the answer is 208V?
No. 208 is fine. 220 is fine. 240 is fine. You don't need to know which it is. The power supply will figure it all out for you and work great at any of these inputs. You just can't expect good performance at 120V, 110V, et cetera.Do I need to find out if my voltage is actually 208V, 220V/230V or 240V since electricians seem to just throw around the number that suits them when speaking of 110/120, 220/240V and 460V? Would the SP30 actually perform worse if the answer is 208V?
I think 208V is still limiting factor for SP30 with Emerson PSU.
Collider, jtoomim, Roadsress or anyone with the early machines:
Please post your statistics and whether you achieved sustained ~4.5TH at 208-220V (please post your voltage) and what was the speed at 110/120V if applicable (I assume 4.1Th). Thanks.
Please post your statistics and whether you achieved sustained ~4.5TH at 208-220V (please post your voltage) and what was the speed at 110/120V if applicable (I assume 4.1Th). Thanks.
I'm getting just under 4.4Th/s @ 205v/205v
Input temp is 19C
Hoping to tweak a little more and get it up to 4.5, any suggestions (other than what ive already read in this thread, and tried)?
Under 210V we can not pull more then 1250watt from the Emerson because of the FCC limitations on current in wires.
If I understand correctly, SP30 have 3 performance levels based on input voltage:
High level at voltage level 220/240V where PSU is able to pull >1300W
Mid level at voltage level 208V where PSU is able to pull up to 1250W (at least for Emerson PSU units)
Low level at voltage level 110/120V where PSU is able to pull up to 1100W
JakeTri -- I would like to thank you for your work, I know the request wasn't mine, but I was wondering about this the same as la7eralus. I'm interested in how you calculated those Reg. values. I would like to break this down one more level and be able to find the nitch between 250 and 243.75. I looked at the Reg. values and attempted to convert from HEX...but that didn't look even close to right. So...i'm interested in how you calculated them. If you could explain, or point me to some documentation that explains it...i would be grateful. I have done a few Google searches...but found zip. Any direction you could give would be appreciated.
I started with the bit layout for freq_value and from there you can calculate the chip_freq.
Bit layout for the freq_value is as follow:
OD can have values between 0 and 3
R can have values between 0 and 31
F can have values between 0 and 127
BS can have only 0 or 1
From page 6 of BM1382 spec (https://www.bitmaintech.com/files/download/BM1382_Datasheet_v3.0.pdf) you get:
NR = R + 1
NF = 2 * (F + 1)
NO value from OD value (see Table 4 from same spec page)
Fref = Fin / NR
Fvco = Fout * NO
Fout = Fin * NF / (NR*NO)
So Fout is "chip_freq" and can be calculated based on valued from above ("OD", "R" and "F"). BS select "high-band" or "low-band" (see page 7 from BM1382 spec for valid freq values for each band).
chip_freq = 50 * ( F + 1 ) / ( ( R + 1 ) * POWER( 2 , OD ) )
For timeout I used following formula:
timeout = 4000 / chip_freq
I suggest to calculate all 3 Fref, Fvco and Fout and make sure all 3 value are in range described on page 7 for the band specified by "BS" value.
EDIT: Here is an example:
freq_value = 1306
OD = 2
R = 1
F = 38
You can compute the rest as following:
NR = 2
NF = 78
NO = 4
Fref = 12.5
Fvco = 975
Fout = 243.75
BS = 0 and all 3 values for Fref, Fvco and Fout are in range for Low-Band.
I was able to seperate the above frequencies into smaller incremental steps, but I have no idea how to calculate the "reg. value" or the "ideal delay" for them. Anyone with a little more know-how than myself willing to help out? I know a few other people in this thread were looking for something like this as well, and any help at all would be appreciated. Thanks!
Adjusting the S1 formula based on S3 ASIC spec I was able to get following register values (and timeout). Use the settings below at your own risk!| Clock_Freq | Register value | Timeout |
| (chip_freq) | (freq_value) | (timeout) |
| 100 | 0783 | 40 |
| 103.125 | 1007 | 39 |
| 106.25 | 0803 | 38 |
| 109.375 | 1107 | 37 |
| 112.5 | 0883 | 36 |
| 115.625 | 1207 | 35 |
| 118.75 | 0903 | 34 |
| 121.875 | 1307 | 33 |
| 125 | 0983 | 32 |
| 128.125 | 1407 | 31 |
| 131.25 | 0A03 | 30 |
| 134.375 | 1507 | 30 |
| 137.5 | 0A83 | 29 |
| 140.625 | 1607 | 28 |
| 143.75 | 0B03 | 28 |
| 146.875 | 1707 | 27 |
| 150 | 0B83 | 27 |
| 153.125 | 1807 | 26 |
| 156.25 | 0C03 | 26 |
| 159.375 | 1907 | 25 |
| 162.5 | 0C83 | 25 |
| 165.625 | 1A07 | 24 |
| 168.75 | 0D03 | 24 |
| 171.875 | 1B07 | 23 |
| 175 | 0D83 | 23 |
| 178.125 | 1C07 | 22 |
| 181.25 | 0E03 | 22 |
| 184.375 | 1D07 | 22 |
| 187.5 | 0E83 | 21 |
| 190.625 | 1E07 | 21 |
| 193.75 | 0F03 | 21 |
| 196.875 | 1F07 | 20 |
| 200 | 0782 | 20 |
| 206.25 | 1006 | 19 |
| 212.5 | 0802 | 19 |
| 218.75 | 1106 | 18 |
| 225 | 0882 | 18 |
| 231.25 | 1206 | 17 |
| 237.5 | 0902 | 17 |
| 243.75 | 1306 | 16 |
| 250 | 0982 | 16 |
| 256.25 | 1406 | 16 |
| 262.5 | 0A02 | 15 |
| 268.75 | 1506 | 15 |
| 275 | 0A82 | 15 |
| 281.25 | 1606 | 14 |
| 287.5 | 0B02 | 14 |
| 293.75 | 1706 | 14 |
| 300 | 0B82 | 13 |
| 306.25 | 1806 | 13 |
| 312.5 | 0C02 | 13 |
| 318.75 | 1906 | 13 |
| 325 | 0C82 | 12 |
| 331.25 | 1A06 | 12 |
| 337.5 | 0D02 | 12 |
| 343.75 | 1B06 | 12 |
| 350 | 0D82 | 11 |
| 356.25 | 1C06 | 11 |
| 362.5 | 0E02 | 11 |
| 368.75 | 1D06 | 11 |
| 375 | 0E82 | 11 |
| 381.25 | 1E06 | 10 |
| 387.5 | 0F02 | 10 |
| 393.75 | 1F06 | 10 |
| 400 | 0F82 | 10 |
Re: The Habanero - 650GH/s - Batch 2 Shipping June 9th, $850 ($1.3/GH/s)
...
Had a look at Cgminer from JakeTri and in Read ME file I can't see any voltage settings
Had a look at Cgminer from JakeTri and in Read ME file I can't see any voltage settings
Here is copy and paste with relevant information from ASIC-README file from https://github.com/jaketri/cgminer
Code:
--hfa-options Set hashfast options name:clock@voltage0@voltage1@voltage2@voltage3:clk0:clk1:clk2:clk3
This command allows you to set options for each discrete hashfast device by
its name (if the firmware has naming support, i.e. version 0.3+). Currently
this takes as option the clock speed, 4 voltages and 4 clock offsets (voltage and
clock offset for each of the 4 cores of the ASIC)
e.g.:
--hfa-options "rabbit:650,turtle:550@800,bee:950@905@925@975@985:-100:-50:0:25"
Would set a device named rabbit to clock speed 650 MHz using default voltage, the
one named turtle to 550 MHz using a voltage of 800 mV for all cores and the one
named bee is set with different clock and voltage for each ASIC core as following:
> core 0 at 850 MHz (950 MHZ base clock with -100 MHz clock offset) and voltage of 905mV
> core 1 at 900 MHz (950 MHZ base clock with -50 MHz clock offset) and voltage of 925mV
> core 2 at 950 MHz (950 MHZ base clock with 0 MHz clock offset) and voltage of 975mV
> core 3 at 975 MHz (950 MHZ base clock with 25 MHz clock offset) and voltage of 985mV
Starting the device at a speed where it is most stable will give more reliable
hashrates long term and prevent it interacting with other devices, rather than
depending on the clockdown feature in cgminer.
Note: Setting voltage may cause a board reset and hotplug event on cgminer startup.
This command allows you to set options for each discrete hashfast device by
its name (if the firmware has naming support, i.e. version 0.3+). Currently
this takes as option the clock speed, 4 voltages and 4 clock offsets (voltage and
clock offset for each of the 4 cores of the ASIC)
e.g.:
--hfa-options "rabbit:650,turtle:550@800,bee:950@905@925@975@985:-100:-50:0:25"
Would set a device named rabbit to clock speed 650 MHz using default voltage, the
one named turtle to 550 MHz using a voltage of 800 mV for all cores and the one
named bee is set with different clock and voltage for each ASIC core as following:
> core 0 at 850 MHz (950 MHZ base clock with -100 MHz clock offset) and voltage of 905mV
> core 1 at 900 MHz (950 MHZ base clock with -50 MHz clock offset) and voltage of 925mV
> core 2 at 950 MHz (950 MHZ base clock with 0 MHz clock offset) and voltage of 975mV
> core 3 at 975 MHz (950 MHZ base clock with 25 MHz clock offset) and voltage of 985mV
Starting the device at a speed where it is most stable will give more reliable
hashrates long term and prevent it interacting with other devices, rather than
depending on the clockdown feature in cgminer.
Note: Setting voltage may cause a board reset and hotplug event on cgminer startup.
Is it possible to run it without voltage modification yet still individual core speed settings? If so, what would be the syntax? Thanks
The new settings are send to device only if voltage values are different from the voltage value stored on the device flash memory.
You can start this cgminer as normal (without any voltage setting) and look to the cgminer info message about current device settings from flash memory. Look for something like this:
Code:
[2014-07-02 10:02:16] HFA0: Device settings (875MHz@930mV,875MHz@930mV,875MHz@930mV,875MHz@930mV)
After that use the voltage values from device and adjust only the core speed settings. This will not modify the device settings from flash storage.
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
jtoomim: I'd connect to the cgminer API exactly like the web interface does when you click the UI buttons. The idea is to "API Allow" connections from all over the LAN, not only from localhost, and you can have a nice monitoring tool.
For home mining users it is OK to allow API access for all over the LAN but it may not be a good idea to allow access to cgminer API from anywhere if you use hosting ...
You can use a ssh connection to your SP10/SP30 and open a tunnel to remote address "-L 4028:localhost:4028" if you want to do remote monitoring but on same time keep cgminer setup with API access only from localhost.
I use this trick to remotely monitor my SP10 located in a data-center.
Re: The Habanero - 650GH/s - Batch 2 Shipping June 9th, $850 ($1.3/GH/s)
...
Had a look at Cgminer from JakeTri and in Read ME file I can't see any voltage settings
Had a look at Cgminer from JakeTri and in Read ME file I can't see any voltage settings
Here is copy and paste with relevant information from ASIC-README file from https://github.com/jaketri/cgminer
Code:
--hfa-options Set hashfast options name:clock@voltage0@voltage1@voltage2@voltage3:clk0:clk1:clk2:clk3
This command allows you to set options for each discrete hashfast device by
its name (if the firmware has naming support, i.e. version 0.3+). Currently
this takes as option the clock speed, 4 voltages and 4 clock offsets (voltage and
clock offset for each of the 4 cores of the ASIC)
e.g.:
--hfa-options "rabbit:650,turtle:550@800,bee:950@905@925@975@985:-100:-50:0:25"
Would set a device named rabbit to clock speed 650 MHz using default voltage, the
one named turtle to 550 MHz using a voltage of 800 mV for all cores and the one
named bee is set with different clock and voltage for each ASIC core as following:
> core 0 at 850 MHz (950 MHZ base clock with -100 MHz clock offset) and voltage of 905mV
> core 1 at 900 MHz (950 MHZ base clock with -50 MHz clock offset) and voltage of 925mV
> core 2 at 950 MHz (950 MHZ base clock with 0 MHz clock offset) and voltage of 975mV
> core 3 at 975 MHz (950 MHZ base clock with 25 MHz clock offset) and voltage of 985mV
Starting the device at a speed where it is most stable will give more reliable
hashrates long term and prevent it interacting with other devices, rather than
depending on the clockdown feature in cgminer.
Note: Setting voltage may cause a board reset and hotplug event on cgminer startup.
This command allows you to set options for each discrete hashfast device by
its name (if the firmware has naming support, i.e. version 0.3+). Currently
this takes as option the clock speed, 4 voltages and 4 clock offsets (voltage and
clock offset for each of the 4 cores of the ASIC)
e.g.:
--hfa-options "rabbit:650,turtle:550@800,bee:950@905@925@975@985:-100:-50:0:25"
Would set a device named rabbit to clock speed 650 MHz using default voltage, the
one named turtle to 550 MHz using a voltage of 800 mV for all cores and the one
named bee is set with different clock and voltage for each ASIC core as following:
> core 0 at 850 MHz (950 MHZ base clock with -100 MHz clock offset) and voltage of 905mV
> core 1 at 900 MHz (950 MHZ base clock with -50 MHz clock offset) and voltage of 925mV
> core 2 at 950 MHz (950 MHZ base clock with 0 MHz clock offset) and voltage of 975mV
> core 3 at 975 MHz (950 MHZ base clock with 25 MHz clock offset) and voltage of 985mV
Starting the device at a speed where it is most stable will give more reliable
hashrates long term and prevent it interacting with other devices, rather than
depending on the clockdown feature in cgminer.
Note: Setting voltage may cause a board reset and hotplug event on cgminer startup.
Many thanks
I didn't look at that file
Unfortunately it doesn't work
No surprise Folder does not contain cgminer.exe file and when I insert this:
cgminer.exe --usb HFA:1 --hfa-name HFA3 -o eu-stratum.btcguild.com:3333 -u -p 123 -o
stratum+tcp://stratum.d7.lt:3333 -u -p 12345 --hfa-fan 100 --hfa-temp-target 0 --hfa-
temp-overheat 104 --hfa-fail-drop 0 --hfa-options HFA3:537@860 --api-listen --api-port 4030
just black screen flashes and that's it
What I'm doing wrong ?
Did I download wrong file ?
Should I copy cgminer.exe from normal cgminer folder ?
Thank you very much for your help
Update
I have copied cgminer.exe from cgminer 4.3.4 folder and I'm getting error lib.dll
If you really need / want to play with voltage settings then keep in mind that you need to set the voltage only once because voltage settings are stored in flash storage on the board.
To adjust voltage settings for Habanero board you can use either HFTool ( https://bitcointalk.org/index.php?topic=639810.0 ) or my cgminer fork.
Each solution have it's own challenges ...
- HFTtool need python with pip and pyusb support.
- cgminer fork need to be compiled from sources.
For Linux users both solution are relatively easy to use.
For windows users each solution have it's own challenges ... For HFTool it is not easy to setup a Windows system with python + pip + pyusb (I did not see any confirmation of windows system working with HFTool). For cgminer you need to know how to use a C compiler .... if you have one ...
I guess it may be possible to use a Linux LiveCD and install pip & pyusb to be able to run once HFTool and setup the voltage.
Unfortunately I cannot run any tests because I sold all my Habanero boards.
Re: The Habanero - 650GH/s - Batch 2 Shipping June 9th, $850 ($1.3/GH/s)
...
Had a look at Cgminer from JakeTri and in Read ME file I can't see any voltage settings
Had a look at Cgminer from JakeTri and in Read ME file I can't see any voltage settings
Here is copy and paste with relevant information from ASIC-README file from https://github.com/jaketri/cgminer
Code:
--hfa-options Set hashfast options name:clock@voltage0@voltage1@voltage2@voltage3:clk0:clk1:clk2:clk3
This command allows you to set options for each discrete hashfast device by
its name (if the firmware has naming support, i.e. version 0.3+). Currently
this takes as option the clock speed, 4 voltages and 4 clock offsets (voltage and
clock offset for each of the 4 cores of the ASIC)
e.g.:
--hfa-options "rabbit:650,turtle:550@800,bee:950@905@925@975@985:-100:-50:0:25"
Would set a device named rabbit to clock speed 650 MHz using default voltage, the
one named turtle to 550 MHz using a voltage of 800 mV for all cores and the one
named bee is set with different clock and voltage for each ASIC core as following:
> core 0 at 850 MHz (950 MHZ base clock with -100 MHz clock offset) and voltage of 905mV
> core 1 at 900 MHz (950 MHZ base clock with -50 MHz clock offset) and voltage of 925mV
> core 2 at 950 MHz (950 MHZ base clock with 0 MHz clock offset) and voltage of 975mV
> core 3 at 975 MHz (950 MHZ base clock with 25 MHz clock offset) and voltage of 985mV
Starting the device at a speed where it is most stable will give more reliable
hashrates long term and prevent it interacting with other devices, rather than
depending on the clockdown feature in cgminer.
Note: Setting voltage may cause a board reset and hotplug event on cgminer startup.
This command allows you to set options for each discrete hashfast device by
its name (if the firmware has naming support, i.e. version 0.3+). Currently
this takes as option the clock speed, 4 voltages and 4 clock offsets (voltage and
clock offset for each of the 4 cores of the ASIC)
e.g.:
--hfa-options "rabbit:650,turtle:550@800,bee:950@905@925@975@985:-100:-50:0:25"
Would set a device named rabbit to clock speed 650 MHz using default voltage, the
one named turtle to 550 MHz using a voltage of 800 mV for all cores and the one
named bee is set with different clock and voltage for each ASIC core as following:
> core 0 at 850 MHz (950 MHZ base clock with -100 MHz clock offset) and voltage of 905mV
> core 1 at 900 MHz (950 MHZ base clock with -50 MHz clock offset) and voltage of 925mV
> core 2 at 950 MHz (950 MHZ base clock with 0 MHz clock offset) and voltage of 975mV
> core 3 at 975 MHz (950 MHZ base clock with 25 MHz clock offset) and voltage of 985mV
Starting the device at a speed where it is most stable will give more reliable
hashrates long term and prevent it interacting with other devices, rather than
depending on the clockdown feature in cgminer.
Note: Setting voltage may cause a board reset and hotplug event on cgminer startup.
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
It is interesting to see if hosting price (in WA data center) is affected for RoadStress August group-buy.
I'm asking because previous price quote for the group buy hosting cover only 2.5kW and/or 2.7kW ... now we are talking about 3K. It is not a big jump in power but it would be good to know the updated price quote.
(I'll not send them an email with this question because I'm sure they are already bombarded with email from everyone)
I'm asking because previous price quote for the group buy hosting cover only 2.5kW and/or 2.7kW ... now we are talking about 3K. It is not a big jump in power but it would be good to know the updated price quote.
(I'll not send them an email with this question because I'm sure they are already bombarded with email from everyone)
First time BM purchaser! Got my 8 S3s today, 7 run like champs around 441ish, although I have one that has a massive 25% HW errors, hashing at about 60-65% of what it should be doing. Any ideas?
http://s15.postimg.org/rfrh5roc9/S3limp.jpg
http://s15.postimg.org/rfrh5roc9/S3limp.jpg
I'll suggest to flash firmware (without preserving settings) from bitmaintech webpage and see how it goes ...
So the firmware on the website is an update to what is already on the system?
For me it was. One of my units had a wrong firmware from factory and start working as advertised after I installed the firmware.
If you look closely to dimaze image you will notice that it show a non-zero value for BestShare but the S3 firmware show 0 all the time for BestShare so I guess he may have same issue that can be easily fixed by flashing the firmware without preserving settings.
First time BM purchaser! Got my 8 S3s today, 7 run like champs around 441ish, although I have one that has a massive 25% HW errors, hashing at about 60-65% of what it should be doing. Any ideas?
http://s15.postimg.org/rfrh5roc9/S3limp.jpg
http://s15.postimg.org/rfrh5roc9/S3limp.jpg
I'll suggest to flash firmware (without preserving settings) from bitmaintech webpage and see how it goes ...
I got today my S3. One is working fine but the other one was not hashing at all because it had frequency set to 350 MHz.
I tried to reset settings but same so I manually edit the "asic-freq" file and set it to 218MHz. After that it start hashing around 440GH/S but it show a strange status page with double number of ASICs but half are "x".
Using ssh I notice that cgminer binary is different on the 2 systems. I tried copy the binary from the "good" one to the "bad" one but it does not hash at all.
The "bad" one also show fan speed of 0 for chain #2 but visually both fans are spinning at high speed.
I hope this is just an old firmware of something like that. I guess it will be fixed when Bitmain will release a firmware update for S3 and after that I'll get consistent Miner Status results on both units.
Power usage at the wall for the "good" is 337W and for the "bad" one is 323W.
I tried to reset settings but same so I manually edit the "asic-freq" file and set it to 218MHz. After that it start hashing around 440GH/S but it show a strange status page with double number of ASICs but half are "x".
Using ssh I notice that cgminer binary is different on the 2 systems. I tried copy the binary from the "good" one to the "bad" one but it does not hash at all.
The "bad" one also show fan speed of 0 for chain #2 but visually both fans are spinning at high speed.
I hope this is just an old firmware of something like that. I guess it will be fixed when Bitmain will release a firmware update for S3 and after that I'll get consistent Miner Status results on both units.
Power usage at the wall for the "good" is 337W and for the "bad" one is 323W.
Re: The Habanero - 650GH/s - Batch 2 Shipping June 9th, $850 ($1.3/GH/s)
Am i right in assuming flashing the new firmware will set the voltages back to default?
No, it shouldn't affect the voltages or the name of the device.To set device name use:
Code:
cgminer --hfa-name "name"
How about for different devices(habs) on same cgminer instance?
Device name is saved to the board flash so you need to set the device name only once for each board.
Use "--usb" to specify the board when you have multiple connected to the same system. For example to set name "hab1" for habanero board connected as device 5 from usb bus 2 use:
Code:
--hfa-name hab1 --usb 2:5
To get the usb bus ID and device ID use "lsusb" as described in cgminer ASIC-README file.
Re: The Habanero - 650GH/s - Batch 2 Shipping June 9th, $850 ($1.3/GH/s)
Am i right in assuming flashing the new firmware will set the voltages back to default?
No, it shouldn't affect the voltages or the name of the device.To set device name use:
Code:
cgminer --hfa-name "name"
