Obviously, if the value of bitcoin skyrocketed, one would have done better by simply buying and holding. If I knew the future and knew that bitcoin would significantly increase in value, I would buy and hold.
I suppose significantly is the key word there. It's definitely going to rise over time. No surefire way to know how much time or value. B&H is one solid thing to do with these coins, in addition to mining. With these numbers, I expect a Neptune to generate 7.5 BTC before it stops being profitable. I had no illusions about receiving more BTC than the ~12/each I spent. And yet I still bought three.
Finally, one of only a couple of us who is making a realistic projection. Mine was 4-6 with an upper of 12 depending on factors. All I could do was shake my head in disbelief at the folks who bought Neptunes thinking they would crank out like 50 coins. Realistic? 8 billion jump in one change in July? 57266 TH/s added to the network in a 10-12 days period? That's 10K Neptunes at 5TH/s. |
|
|
|
As far as helping people overclock their KNC rigs, it's probably a wash. So few people have the skills to follow really simple command line instructions, I figure an overclocking guide will brick as many machines as it overclocks! What percentage of the average public has ever used a non-gui based text editor? Try to explain vi to them!
Next, throw some cryptic pseudo-MS-DOS (I know it's the other way around) shit like manually copying files and changing directories. Did you know the slashes / \ go the opposite directions in windows and unix? And in Unix directories can have a . in the middle of it's name? Holy crap, that alone is gonna screw half the people right there.
So you changed my mind, PLEASE WRITE AN OVERCLOCKING GUIDE. Gonna fuck some shit up, yes we are.
-Dana
Good points. I am no Linux guru, but back in 2011 when I was GPU mining I managed to run a headless Ubuntu rig with no prior unix experience. Most of it is having good computer skills in general and using Google. Until today I've never used vi, but again using Google I got all the required information: hint use xxdd to delete a specific number of lines - example 85dd to delete 85 lines. |
|
|
|
I think I managed to make it work. Please have a look at my code and tell me if it is OK: This code is for overclocking each individual die on each board to 850Mhz, so 16 total individual settings for boards at position 0, 1, 2, 3: http://pastebin.com/dSWrP4jFIt works, so I assume it is all good. I think I understand it better now, so I will probably write a very detailed tutorial tomorrow for people who are not sure what they are doing. But first I will try to switch to BFGMiner to better fine tuning. Looks good. But please, don't help add a couple hundred THs to the network by being the hero and writing an overclocking tutorial! Anyway, you can change each individual die to whatever clock speed you want with your code. It's great for people who have issues with bad boards, but simply changing the preceeding 0x86 register will cover 95% of the people who have no bad dies without over complicating things: if [ -n "$good_ports" ] ; then
for p in $good_ports ; do
# Re-enable PLL
i2cset -y 2 0x71 1 $((p+1))
for c in 0 1 2 3 ; do
cmd=$(printf "0x84,0x%02X,0,0" $c)
spi-test -s 50000 -OHC -D /dev/spidev1.0 $cmd >/dev/null
cmd=$(printf "0x86,0x%02X,0x02,0x11" $c) True that. I will refrain from making it easy for the average joe then. Btw what are your observations in regards to unhappy dies? One of my miners clocked with 201 is showing this: https://i.imgur.com/NSl59Iz.pngShall I increase the voltage at the Advanced tab, then /config/zzz.sh restart or try first with more/less OC? @CYPER Please DO write a very detailed tutorial for people who are not sure what they are doing? I made a contribution to tolip_wen for his shared work and will do the same for you and as well encourage others to as well. None of us would be here without some help from someone else at some point. Thanks I would rather help individual people in person like ElGabo did, than write a tutorial  Find me on Skype and I can help when I am free. |
|
|
|
There will be a tuning suite for Nov, but not this side of Jan, as everything there is winding down. There's just some ongoing Neptune work. There will also be the means to vary SPI clock frequency. I saw it in the original tuning suite as a feature, but that hadn't been developed into the recent release. It was purely part of a template I saw.
Can you please elaborate on what that option does as I believe many of us are just changing values without knowing what they actually do  The voltage settings are clear, but the SPI voltage and frequency not so much. I know they are related to the communication between each board and the controller board, so do they increase the signal to noise ratio or am I talking rubbish |
|
|
|
I think I managed to make it work. Please have a look at my code and tell me if it is OK: This code is for overclocking each individual die on each board to 850Mhz, so 16 total individual settings for boards at position 0, 1, 2, 3: http://pastebin.com/dSWrP4jFIt works, so I assume it is all good. I think I understand it better now, so I will probably write a very detailed tutorial tomorrow for people who are not sure what they are doing. But first I will try to switch to BFGMiner to better fine tuning. Looks good. But please, don't help add a couple hundred THs to the network by being the hero and writing an overclocking tutorial! Anyway, you can change each individual die to whatever clock speed you want with your code. It's great for people who have issues with bad boards, but simply changing the preceeding 0x86 register will cover 95% of the people who have no bad dies without over complicating things: if [ -n "$good_ports" ] ; then
for p in $good_ports ; do
# Re-enable PLL
i2cset -y 2 0x71 1 $((p+1))
for c in 0 1 2 3 ; do
cmd=$(printf "0x84,0x%02X,0,0" $c)
spi-test -s 50000 -OHC -D /dev/spidev1.0 $cmd >/dev/null
cmd=$(printf "0x86,0x%02X,0x02,0x11" $c) True that. I will refrain from making it easy for the average joe then. Btw what are your observations in regards to unhappy dies? One of my miners clocked with 201 is showing this: https://i.imgur.com/NSl59Iz.pngShall I increase the voltage at the Advanced tab, then /config/zzz.sh restart or try first with more/less OC? |
|
|
|
I think I managed to make it work. Please have a look at my code and tell me if it is OK: This code is for overclocking each individual die on each board to 850Mhz, so 16 total individual settings for boards at position 0, 1, 2, 3: http://pastebin.com/dSWrP4jFIt works, so I assume it is all good. I think I understand it better now, so I will probably write a very detailed tutorial tomorrow for people who are not sure what they are doing. But first I will try to switch to BFGMiner to better fine tuning. |
|
|
|
Btw why I can't find the strings for tuning each chip/die individually in either cgminer.sh or zzz.sh? This is all that is inside: done
done
for p in 0 1 2 3 4 5 ; do
i2cset -y 2 0x71 1 $((p+1))
good_flag=0
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,3,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,2,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,1,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,0,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
if [ "$good_flag" = "1" ] ; then
good_ports=$good_ports" $p"
else
bad_ports=$bad_ports" $p"
fi
done
if [ -n "$good_ports" ] ; then
for p in $good_ports ; do
# Re-enable PLL
i2cset -y 2 0x71 1 $((p+1))
for c in 0 1 2 3 ; do
cmd=$(printf "0x84,0x%02X,0,0" $c)
spi-test -s 50000 -OHC -D /dev/spidev1.0 $cmd >/dev/null
cmd=$(printf "0x86,0x%02X,0x01,0xF1" $c)
spi-test -s 50000 -OHC -D /dev/spidev1.0 $cmd >/dev/null
cmd=$(printf "0x85,0x%02X,0,0" $c)
spi-test -s 50000 -OHC -D /dev/spidev1.0 $cmd >/dev/null
done
# re-enable all cores
i=0
while [[ $i -lt 192 ]] ; do
i2cset -y 2 0x2$p $i 1
i=$((i+1))
done
spi_ena=$(( spi_ena | (1 << $p) ))
done
fi
if [ -n "$bad_ports" ] ; then
for p in $bad_ports ; do
root@Jupiter-6:/config# /config/zzz.sh restart
Restarting Cgminer daemon: cgminer.
root@Jupiter-6:/config# screen -r
[detached]
root@Jupiter-6:/config# vi /etc/init.d/cgminer.sh
#!/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/bin/cgminer
NAME=cgminer
DESC="Cgminer daemon"
set -e
test -x "$DAEMON" || exit 0
do_start() {
# Stop SPI poller
spi_ena=0
i2cset -y 2 0x71 2 $spi_ena
good_ports=""
bad_ports=""
# CLear faults in megadlynx's
for b in 3 4 5 6 7 8 ; do
for d in 0 1 2 3 4 5 6 7 ; do
i2cset -y $b 0x1$d 3 >/dev/null 2>&1 || true
done
done
for p in 0 1 2 3 4 5 ; do
i2cset -y 2 0x71 1 $((p+1))
good_flag=0
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,3,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,2,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,1,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,0,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
if [ "$good_flag" = "1" ] ; then
good_ports=$good_ports" $p"
else
bad_ports=$bad_ports" $p"
fi
done
if [ -n "$good_ports" ] ; then
root@Jupiter-6:/config# screen -r
[detached]
root@Jupiter-6:/config# vi /config/zzz.sh
fi
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,2,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,1,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
ar="$(spi-test -s 50000 -OHC -D /dev/spidev1.0 0x80,0,0,0,0,0,0,0 | tail -c 13)"
if [ "x$ar" = "x00 30 A0 01" ] ; then
good_flag=1
fi
if [ "$good_flag" = "1" ] ; then
good_ports=$good_ports" $p"
else
bad_ports=$bad_ports" $p"
fi
done
if [ -n "$good_ports" ] ; then
for p in $good_ports ; do
# Re-enable PLL
i2cset -y 2 0x71 1 $((p+1))
for c in 0 1 2 3 ; do
cmd=$(printf "0x84,0x%02X,0,0" $c)
spi-test -s 50000 -OHC -D /dev/spidev1.0 $cmd >/dev/null
cmd=$(printf "0x86,0x%02X,0x01,0xF1" $c)
spi-test -s 50000 -OHC -D /dev/spidev1.0 $cmd >/dev/null
cmd=$(printf "0x85,0x%02X,0,0" $c)
spi-test -s 50000 -OHC -D /dev/spidev1.0 $cmd >/dev/null
done
# re-enable all cores
i=0
while [[ $i -lt 192 ]] ; do
i2cset -y 2 0x2$p $i 1
i=$((i+1))
done
spi_ena=$(( spi_ena | (1 << $p) ))
done
fi
if [ -n "$bad_ports" ] ; then
for p in $bad_ports ; do
# Disable PLL
i2cset -y 2 0x71 1 $((p+1))
for c in 0 1 2 3 ; do
cmd=$(printf "0x84,0x%02X,0,0" $c)
spi-test -s 50000 -OHC -D /dev/spidev1.0 $cmd >/dev/null
done
# disable all cores
i=0
- /config/zzz.sh 61/131 46%
|
|
|
|
Is there a sed command that goes higher than 7%?
No, because the next value in line is different: 201 It can probably be done with 2 sed commands or you can just edit the zzz.sh manually. Line 61, find this string: cmd=$(printf "0x86,0x%02X,0x01,0xF1" $c) 800Mhz - cmd=$(printf "0x86,0x%02X,0x01,0xF1" $c) 825Mhz - cmd=$(printf "0x86,0x%02X,0x02,0x01" $c) 850Mhz - cmd=$(printf "0x86,0x%02X,0x02,0x11" $c) Please use your own judgement as I cannot 100% guarantee this code is correct. Wait for someone to confirm. |
|
|
|
|
I'm trying to get into /etc/init.d but it won't let me.
Permissions are drwxr-xr-x (755) — Everyone can read the directory, but its contents can only be changed by the user.
I type su which gives me no error, and still I get this:
root@Jupiter-6:/etc# cd /init.d
sh: cd: can't cd to /init.d
root@Jupiter-6:/etc#
I am no Unix guru, so can you please tell me what is wrong?
This is an October 8VRM machine - I want to open the cgminer.sh file and see if it is the same as the one on October 4VRM.
Maybe I should install sudo?
|
|
|
|
ElGabo was kind enough to help me with the OC Btw on one of the miners I am testing the OC I have a board with 2 dead dies, which I usually revive by increasing the voltage of all dies to the max and then immediately lowering them back to normal. So is there a way to increase the voltage for these 2 dies to revive them while zzz.sh is running. I get it if I change anything in the Advanced tab then the miner switches back to the original file. Why is that? |
|
|
|
I think this is a pretty good indication of when shit is going to happen: Being out of stock is tough on us all. Customers want to buy more, we want to supply more and every day the 'out of stock' situation continues it frustrates all involved.
We have not been sitting still however. For the past few weeks we have been working on plans to develop hosted hashing into a truly interactive enterprise. All our future plans revolve around having access to extremely large amount of hashing power so that many more people can get involved and try hosted hashing for themselves.
Until we can offer a steady, continuous supply of hashing power our shop will have to remain closed.
We are working with hardware partners to bring to market a large hashing facility that we expect to be online during the month of JANUARY 2014. You all seem bored, so I'll let you find the source of that news for yourselves  |
|
|
|
|
So guys, is it riskier to try it on a 8VRM October Jupiter, or shall I try it first on a 4VRM October one?
|
|
|
|
Truth is heavy and they can not take the truth
Wow so deep, even Adele can't roll in it |
|
|
|
but until the end of 2014 years, diff will be about 676 trilion.
Today diff 1.2 billion for next 6 monthy +75000% , it is diff 900 billion,
and for following 6 month in 2014 year,
again +75000%, 900 billion + 75000% = diff 675900 billion or 675.9 trilion !!!
This is only for the following 12 months !
impressive I give up! you convinced me! All companies will soon give up, for about 4-5 months, and mining is finished, BTC go to bottom. I give up then. Do you want to buy my Jupiters for a very low price? no give him bitcoin directly. he needs something to eat. Igor from Russia is hungry |
|
|
|
but until the end of 2014 years, diff will be about 676 trilion.
Today diff 1.2 billion for next 6 monthy +75000% , it is diff 900 billion,
and for following 6 month in 2014 year,
again +75000%, 900 billion + 75000% = diff 675900 billion or 675.9 trilion !!!
This is only for the following 12 months !
impressive I give up! you convinced me! All companies will soon give up, for about 4-5 months, and mining is finished, BTC go to bottom. I give up then. Do you want to buy my Jupiters for a very low price? |
|
|
|
Why are you wasting your time with this complete noob or maybe a troll  |
|
|
|
still isn't getting anywhere close to 1000 billion.
do you know maths?
Check above, for last 6 months diff rise 75000%, from 1.7 million to 1200 million !!! It also comes in the next 6 month, diff will rise + 75000%, from 1200 million to 900000 million !!! Quit. Get out while you still can. |
|
|
|
None that I know of. I suppose u have to do the math yourself percentage wise...
How exactly? What numbers do I use for such calculation? |
|
|
|
One of my miners started acting even more weird today. One of the dies is getting half the required current:  If I increase the voltage to the max then it eventually revives, but the wattage goes thought the roof at 70W. And when I decrease it back to normal it dies again   |
|
|
|
Avenger...
Awww, cmon man... lol.... BTC went down for a bit, that's all... I won't chastise you for thinking it's a sinking ship, that's your right, and isn't impossible, however unlikely IMHO
I wasn't talking about BTC being a sinking ship, as well you know. I was talking about a certain shovel makers shovels seeming less and less attractive by the minute and even their most loyal followers jumping from that ship before it sinks. That's just it... I'm not "Jumping Ship" by any means... I call it leveraging more machines, which is just the opposite. I'm doubling down my bets technically. Hasn't happened yet anyway... he asked...I offered. That's all... Why read so much into it? I admire your patience to reason with Avenger. |
|
|
|
|
Show Posts
