The default IP address of the miner is 192.168.1.99, Username:root, Pwd:root
You can overclock the S3 to 250MHz by first ssh'ing into the device,
and then uncomment the 250M clock speed lines and
making sure other clock speeds are commented out.
The hashrate is ~500GH/s at 250MHz.
I have tried 275MHz and 300MHz, and were no-go since the chip voltage in the S3 is set at 0.784V.
vim /etc/config/asic-freq
Results of overclocking
Solution to random beeping issues
The config now allows you to turn it off if it is really annoying.
I did turn it off, yet it still will randomly just let out a beep. It hashes away happily...then BEEP...still hashing...I think I'll beep now...
It happens at all clock speeds on every pool I've configured (my local p2pool node, another p2pool node, Eligius, BTCGuild, and yes, the pool that shall not be named).
My miners were doing the same random beep as you describe, I setup the dchp server to fix an ip for each and the beeping stopped. Too many iDevices on the network seemed to cause too much conflict for temp. leases.
You can overclock the S3 to 250MHz by first ssh'ing into the device,
and then uncomment the 250M clock speed lines and
making sure other clock speeds are commented out.
The hashrate is ~500GH/s at 250MHz.
I have tried 275MHz and 300MHz, and were no-go since the chip voltage in the S3 is set at 0.784V.
Code:
ssh 192.168.1.99 -lroot
password:root
password:root
vim /etc/config/asic-freq
Code:
config 'asic-freq' 'default'
option 'freq_value' '0982' #250M
option 'chip_freq' '250'
option 'timeout' '16'
#option 'freq_value' '1286' #237.5M
#option 'chip_freq' '237.5'
#option 'timeout' '17'
#option 'freq_value' '0882' #225M
#option 'chip_freq' '225'
#option 'timeout' '18'
#option 'freq_value' '1106' #218.75M
#option 'chip_freq' '218.75'
#option 'timeout' '18'
option 'freq_value' '0982' #250M
option 'chip_freq' '250'
option 'timeout' '16'
#option 'freq_value' '1286' #237.5M
#option 'chip_freq' '237.5'
#option 'timeout' '17'
#option 'freq_value' '0882' #225M
#option 'chip_freq' '225'
#option 'timeout' '18'
#option 'freq_value' '1106' #218.75M
#option 'chip_freq' '218.75'
#option 'timeout' '18'
Results of overclocking
Solution to random beeping issues
General questions about the S3 now that mine have been hashing for a few hours...
1) Why in the name of all that's holy does it randomly beep? Every now and then it just goes "BEEEEEP!" It's not like it's rebooting... it just decides to let everyone know, "Hey, I'm here! Pay attention to me!"
2) I know the "o" in the miner status means "OK" and that "x" means "error". What does "-" mean?
General comments:
1) At stock clocks it hashes almost exactly to spec on p2pool (my local node). Initially it was around 450GH/s, but after settling down and going for a few hours now, it's about 439GH/s.
2) Overclocking it has far less effect on p2pool than on another pool. For example, at 250, I get about 455GH/s on p2pool. I get 500GH/s elsewhere with the same settings.
The beep is internet connection lost or failed to get work. It will retry to get work or listen for the internet connection up to a point. If it keeps hashing then its doing what its supposed too.1) Why in the name of all that's holy does it randomly beep? Every now and then it just goes "BEEEEEP!" It's not like it's rebooting... it just decides to let everyone know, "Hey, I'm here! Pay attention to me!"
2) I know the "o" in the miner status means "OK" and that "x" means "error". What does "-" mean?
General comments:
1) At stock clocks it hashes almost exactly to spec on p2pool (my local node). Initially it was around 450GH/s, but after settling down and going for a few hours now, it's about 439GH/s.
2) Overclocking it has far less effect on p2pool than on another pool. For example, at 250, I get about 455GH/s on p2pool. I get 500GH/s elsewhere with the same settings.
It happens at all clock speeds on every pool I've configured (my local p2pool node, another p2pool node, Eligius, BTCGuild, and yes, the pool that shall not be named).
My miners were doing the same random beep as you describe, I setup the dchp server to fix an ip for each and the beeping stopped. Too many iDevices on the network seemed to cause too much conflict for temp. leases.
Total noob here. Could you please provide a step by step guide to overclocking the S3. Thanks.